Skip to content
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

Alert Labels not updated while alert is firing #3694

Closed
mweinelt opened this Issue Jan 17, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@mweinelt
Copy link

mweinelt commented Jan 17, 2018

What did you do?

Created an alert rule that passes the value as a label.

What did you expect to see?

The label value should be updated while the alert is firing.

What did you see instead? Under which circumstances?

The label value was stuck at the value when it initially triggered.

Environment

  • System information:

Linux 4.9.0-5-amd64 x86_64

  • Prometheus version:

prometheus, version 2.0.0 (branch: HEAD, revision: 0a74f98)
build user: root@615b82cb36b6
build date: 20171108-07:11:59
go version: go1.9.2

  • Prometheus configuration file:
alert: RoomHighTemp
expr: arduino_temperature{job="c303env"}
  > 28
for: 10m
labels:
  severity: page
  value: '{{ $value }}'
annotations:
  description: The air temperature in C303 is above 28°C
  summary: Air temperature in C303 is {{ $value }}°C
  • Example:

alert

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jan 17, 2018

Alerts are defined by their labels, having varying alert labels like this is a bad idea. Use annotations instead.

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.