-
Notifications
You must be signed in to change notification settings - Fork 102
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
"customer" variable need to be an annotation, not a label #32
Comments
Same problem. The field I use Docker image
It's curious because the prometheus webhook seems correct : https://github.com/alerta/alerta/blob/v8.7.0/alerta/webhooks/prometheus.py#L49
The customer field was introduced in alerta on Jan 11, 2019 by this commit, and always filled from the label: |
It seems that the field is correct for the alert object : we can see the correct value for the It is a display bug in the web UI. My UI is translated in french, can it be the cause ? |
Solved by adding Not sure that it should be the correct behaviour.
|
Hello, I have the same problem with the customer label. Moreover, alertad receives the value of the client annotation (with the debug mode in alertad.conf) but the postgres "alerts" table does not contain the client value (the column is empty for all alerts). When I set the both values in the same time (annotation and label, I don't receive the alerts). The customer filtering don't work. alertad : 8.7.0 |
Issue Summary
Hi there !
I was tring to deploy Alerta, and lost sometime on the customer field.
As the documentation says here, the customer field need to be in the label section, which seems to be logical, but its was not working.
To get the customer field ok, I had to add it as an "annotation".
Environment
OS: linux
API version: 8.1.0
Deployment: Helmchart (Kubernetes)
Database: Postgres
Server config:
Auth enabled? Yes
Auth provider? Basic
Customer views? No
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Add the customer field in the labels, not annotation section
The text was updated successfully, but these errors were encountered: