mirror of
https://github.com/nvim-treesitter/nvim-treesitter.git
synced 2026-07-01 19:17:02 -04:00
d2ff400641
In Prometheus, label values are treated as strings when used with the
`=` and `!=` operators, and as regular expressions when used with the
`=~` and `!~` operators.
Injecting and then highlighting all label values as regex leads to a
situation where entirely valid **string** label values containing regex
special characters are mistakenly parsed and highlighted as regex. This
results in syntax errors, causing labels to be highlighted incorrectly.
For example, in `foo{bar=~"[a-z]{1,3}"}`, `{` and `}` are regex special
characters, so regex highlighting is expected. However, in
`foo{path="/foo/{id}"}`, `{` and `}` are just part of the string and
have no special meaning, so the whole value should be highlighted as a
string.
33 lines
1.1 KiB
YAML
33 lines
1.1 KiB
YAML
groups:
|
|
- name: Hardware alerts
|
|
rules:
|
|
- alert: Node down
|
|
expr: up{job="node_exporter"} == 0
|
|
# ^ @promql
|
|
for: 3m
|
|
labels:
|
|
severity: warning
|
|
annotations:
|
|
title: Node {{ $labels.instance }} is down
|
|
description: Failed to scrape {{ $labels.job }} on {{ $labels.instance }} for more than 3 minutes. Node seems down.
|
|
- alert: Node down
|
|
expr: |
|
|
up{job="node_exporter"} == 0
|
|
# ^ @promql
|
|
for: 3m
|
|
labels:
|
|
severity: warning
|
|
- alert: Regex and String matching
|
|
expr: |
|
|
foo{path=~"^foo$"}[5m] or foo{path!~"[a-zA-Z0-9]{1,3}"}[5m] or foo{path="/api/users/{userId}"}[5m] or foo{path!="/api/users/{userId}"}[5m]
|
|
# ^ @promql
|
|
# ^ @regex
|
|
# ^ @regex
|
|
# ^ @!regex
|
|
# ^ @!regex
|
|
for: 3m
|
|
labels:
|
|
severity: warning
|
|
annotations:
|
|
title: Foo
|
|
description: Bar
|