-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Critical
-
None
-
Affects Version/s: 4.0.4
-
Component/s: Frontend (F)
-
None
-
Environment:Debian 9 como servidor e agente monitorado.
Steps to reproduce:
- Create a simple map ...
- Add a host...
- Create the host, set up a label with triggers...
- Created 3 ntp, http and ssh status triggers in the label...
- Update the map and check the ok status of the 3 services...
- After stopping the http service, check for failure, ok...
- Then stop the ntp serviec, check the map failure and ok...
- I have a problem with ntp, but I have a problem with ntp...
- It was tested more tjan once, it was verified that after about 5 minutes, the ntp alert comes out, even in recent data and dashboard it is already being solved.