Open MalKeshar opened 1 year ago
That would be a welcome addition.
@MalKeshar would you be able to share the query you have used in your workaround?
That would be a welcome addition.
@MalKeshar would you be able to share the query you have used in your workaround?
It depends on the database you are using. We are using PostgreSQL. If you need this one I can check our query later
That would be a welcome addition.
@MalKeshar would you be able to share the query you have used in your workaround?
It depends on the database you are using. We are using PostgreSQL. If you need this one I can check our query later
Yes please. We are also using Postgres in our setup.
That would be a welcome addition. @MalKeshar would you be able to share the query you have used in your workaround?
It depends on the database you are using. We are using PostgreSQL. If you need this one I can check our query later
Yes please. We are also using Postgres in our setup.
I'm afraid, I am lost testing dash with this data. We not yet pushed this workaround into production. Sorry. Eventulally I'm gonna look into it once again, but not in the nearest future :-(
Is your feature request related to a problem? Please describe. We are using grafana annotations from zabbix events. Currently is not possible to understand easily the time impact of event. Problem event and OK event are separeted events, don't related in any way.
Describe the solution you'd like For instance we also using mysql database as a source of another custom annotations. With them time impact is clearly understandable. Please take a look at attached screenshots.
Our suggestion - to implement "timeEnd" annotation based (if it exist) on OK event.
Workaround for whose, who suffer with same issue: use direct datasource of zabbix db for such customization.
Additional context Screenshots: