-
Notifications
You must be signed in to change notification settings - Fork 457
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
Operational data display issue in Zabbix problems panel #1832
Comments
+1 |
2 similar comments
+1 |
+1 |
I'm getting the same error with operational data with a similar trigger configuration:
|
+1 |
2 similar comments
+1 |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the {ITEM.VALUE} macro in operational data and multiple event generation, Grafana displays the latest item value in the operational data inside the event detail, rather than the value that originally created the problem event.
This behavior is different from Zabbix, where the operational data correctly reflects the value that triggered the problem event.
Steps to Reproduce
In Zabbix, the operational data column works as expected, showing the value that triggered the problem event. Grafana, however, displays the latest item value in the operational data, which may not accurately represent the problem.
Upon inspecting the API calls in the browser's developer mode, I noticed that the calls being made are 'trigger.get' and 'problem.get'. The first one obtains the operational data correctly, but the second one obtains only the last value of the item.
I suppose that's the problem, use the last value of the item obtained with the problem.get method instead the operational data obtained with the trigger.get call.
Note: If you enable the operational data column in the Zabbix problems panel, it will correctly display the operational data.
Software versions
The text was updated successfully, but these errors were encountered: