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

Add support to show problems #495

Closed
1 of 3 tasks
fpaternot-zz opened this issue Dec 6, 2017 · 6 comments
Closed
1 of 3 tasks

Add support to show problems #495

fpaternot-zz opened this issue Dec 6, 2017 · 6 comments

Comments

@fpaternot-zz
Copy link

I'm submitting a ...

  • Bug report
  • Feature requestdd
  • Question / Support request

Currently it seems that trigger.get is the only way to retrieve trigger information.

If the trigger uses the PROBLEM event generation in multi mode (https://www.zabbix.com/documentation/3.4/manual/config/triggers/trigger#configuration), events are omitted and not shown. This mimics the behavior of Monitoring->Triggers.

However, it would be great to add the possibility to show the same of Monitoring->Problems as well. I realize this feature is not a very popular one, but for large environments it is used quite a bit.

@adtsys-suporte
Copy link

I need this too.
I have to show all resolved triggers and the count of them, and if I use the Zabbix Triggers, it shows only the unresolved triggers and does not obey the time shift.

@LeHigh75
Copy link

+1 on this one, it would be very useful for us

@bcarlsson
Copy link

+1 Please add this

@partosXP
Copy link

+1
It's the main reason for not using Grafana with this plugin as main dashboard of zabbix data instead of zabbix interface... its impossible to ignore history of problems.

@jsenicourt-adeo
Copy link

+1
We use IT services to calculate SLA.
We have to know which trigger affect SLA rate in history
thx for your work

@mjtrangoni
Copy link
Contributor

+1

@alexanderzobnin alexanderzobnin added this to the 3.11 milestone Jan 28, 2020
@alexanderzobnin alexanderzobnin modified the milestones: 3.11, 3.12 Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants