-
Notifications
You must be signed in to change notification settings - Fork 458
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
Trigger Counts and Single Stat #726
Comments
Same Issue for upgrading from 4.0.4 to 4.0.7 Seems like Zabbix changed the API Count Output Datafield in the last Update. Object ############# if you disable the Queries->"Count" value (eq countOutput:true) and set the Severity in Visualisation->Column to the correct Severity then you get the correct value back |
Yes, now Zabbix returns |
Can the commit be released in a 3.10.3 update? Seems like it just missed out on 3.10.2. |
Hello Guys Software Version Zabbix Grafana Zabbix-Grafana-Plugin |
Well, but its explained here for Sys Admins -> you cant fix it until the next update is released, because its a bug in the current version, in cause of the change in the latest Zabbix Version you running. |
@alexanderzobnin 2 months have passed since the patch was committed to master. Could a new release be pushed out so that this plugin will work with current versions of Zabbix? |
I am tested new pre release verison zabbix 4.2.2rc1, still has problem |
Describe the bug
The Single Stat plugin doesn't appear to render trigger counts correctly after upgrading to Zabbix to 4.0.x and Grafana and this Zabbix plugin to the latest available. I either see a blank panel or 'undefined' depending on the browser.
Other Single Stat panels backed on to Zabbix (not showing counts, but specific metrics) don't appear to be affected and are working as before the upgrades.
Expected behavior
Previously the Single Stat plugin would show the count of the number of triggers returned by the query.
Screenshots
Network data
This is the return data of one of two affected queries.
Other Notes
I've tried deleting the panel and adding it back in again but see the same results.
The text was updated successfully, but these errors were encountered: