New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"<no value>" after templating #4012
Comments
@hagen1778 What do you think about this? |
Replace empty labels with "" instead of "<no value>" during templating, as Prometheus does. See #4012 Signed-off-by: hagen1778 <roman@victoriametrics.com>
Replace empty labels with "" instead of "<no value>" during templating, as Prometheus does. See #4012 Signed-off-by: hagen1778 <roman@victoriametrics.com>
@Z9n2JktHlZDmlhSvqc9X2MmL3BwQG7tk Starting from 4a49577 vmalert should convert In the meantime, could you please try the following image and check if it helps?
If you don't use docker for deployment you can build a binary by using this doc and check if that works for you. |
Thanks ! I will wait for the next release. |
Replace empty labels with "" instead of "<no value>" during templating, as Prometheus does. See #4012 Signed-off-by: hagen1778 <roman@victoriametrics.com>
FYI, the issues should be fixed in vmalert v1.90.0. |
Is your feature request related to a problem? Please describe
When I use label name that does not exist in the expression result I get
<no value>
label value in alert.Test alerting rule
Prometheus was converting
nil
to an empty string, so I could useif ne $labels.host ""
, but now I need to add an extranil
check to all affected alerting rules. It is not so convenient. And what's more, it's not so obvious to check label value againstnil
(first I tried to checkif ne $labels.host "<no value>"
).Describe the solution you'd like
Propose to convert non-existent label values to an empty string.
What do you think ?
Describe alternatives you've considered
No response
Additional information
Version: victoria-metrics-20221126-045002-tags-v1.84.0-0-gad105147d
Type: single node
The text was updated successfully, but these errors were encountered: