The "prometheusrules" is invalid: - Error - kubernetes

Question

I am trying to run this prometheus rules out of a yaml file and I am getting this error. I have serach all over the web and since it is quite long and as well very specific to elastic. I have not been able to find any sort of documentation, help or advise. I would really appreciate any guidance or someone pointing me at the right direction.
kubectl apply -f prometheus-es-rules.yaml -n centralized-logging
The "prometheusrules" is invalid:
* : 43:11: group "elastic", rule 1, "elasticsearch_filesystem_data_used_percent": could not parse expression: 1:71: parse error: unexpected identifier "elasticsearch" in label matching, expected "," or "}"
* : 43:11: group "elastic", rule 2, "elasticsearch_filesystem_data_free_percent": could not parse expression: 1:72: parse error: unexpected identifier "elasticsearch" in label matching, expected "," or "}"
* : 43:11: group "elastic", rule 3, "ElasticsearchTooFewNodesRunning": could not parse expression: 1:68: parse error: unexpected identifier "elasticsearch" in label matching, expected "," or "}"
* : 43:11: group "elastic", rule 4, "ElasticsearchHeapTooHigh": could not parse expression: 1:59: parse error: unexpected identifier "elasticsearch" in label matching, expected "," or "}"
This is my promethus-rules.yaml file:
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
labels:
role: alert-rules
app: elastic
name: prometheus-rules
spec:
groups:
- name: elastic
rules:
- record: elasticsearch_filesystem_data_used_percent
expr: |
100 * (elasticsearch_filesystem_data_size_bytes{service="{{ template "elasticsearch-exporter.fullname" . }}"} - elasticsearch_filesystem_data_free_bytes{service="{{ template "elasticsearch-exporter.fullname" . }}"})
/ elasticsearch_filesystem_data_size_bytes{service="{{ template "elasticsearch-exporter.fullname" . }}"}
- record: elasticsearch_filesystem_data_free_percent
expr: 100 - elasticsearch_filesystem_data_used_percent{service="{{ template "elasticsearch-exporter.fullname" . }}"}
- alert: ElasticsearchTooFewNodesRunning
expr: elasticsearch_cluster_health_number_of_nodes{service="{{ template "elasticsearch-exporter.fullname" . }}"} < 3
for: 5m
labels:
severity: critical
annotations:
description: There are only {{ "{{ $value }}" }} < 3 ElasticSearch nodes running
summary: ElasticSearch running on less than 3 nodes
- alert: ElasticsearchHeapTooHigh
expr: |
elasticsearch_jvm_memory_used_bytes{service="{{ template "elasticsearch-exporter.fullname" . }}", area="heap"} / elasticsearch_jvm_memory_max_bytes{service="{{ template "elasticsearch-exporter.fullname" . }}", area="heap"}
> 0.9
for: 15m
labels:
severity: critical
annotations:
description: The heap usage is over 90% for 15m
summary: ElasticSearch node {{ "{{ $labels.node }}" }} heap usage is high
- alert: ElasticNoAvailableSpace
expr: es_fs_path_free_bytes * 100 / es_fs_path_total_bytes < 10
for: 10m
labels:
severity: critical
annotations:
summary: Instance {{$labels.instance}}
description: Elasticsearch reports that there are only {{ $value }}% left on {{ $labels.path }} at {{$labels.instance}}. Please check it
- alert: NumberOfPendingTasks
expr: es_cluster_pending_tasks_number > 0
for: 5m
labels:
severity: warning
annotations:
summary: Instance {{ $labels.instance }}
description: Number of pending tasks for 10 min. Cluster works slowly
I am not sure if this is an indentation problem?