|
|
| Subject: | Where would a heartbeat for something called myApplication be originating? |
| Author: | Larry Virden |
| Posted: | 2016-05-04 10:24 |
An alert is appearing that says it is mydevice|myApplication|/Status/Heartbeat|4|mydevice myApplication heartbeat failure .
How can I find out what exactly this is
I don't see much doc about the alert heartbeats. I would like to configure the operations view of alerts so they don't see them. But for some reason, the "okay, here's another heartbeat" alert is not an info alert but a warning.
Weird.
Any tips on dealing with events that operators do not need to see
| Subject: | more info |
| Author: | Larry Virden |
| Posted: | 2016-05-05 11:11 |
I tried searching through all of zenhub for "mydevice" and found hits here:
/opt/zenoss/Products/ZenEvents/tests/testDeviceIdentification.py
/opt/zenoss/Products/ZenModel/tests/testDevice.py
Anyone have any idea what might be set or triggered to cause references to "mydevice" to start being monitored
| Subject: | /Status/Heartbeat events are |
| Author: | Jay Stanley |
| Posted: | 2016-05-31 09:17 |
/Status/Heartbeat events are from the daemons.
Daemons will send heartbeats to zenhub, which then get processed by zeneventserver.
If zeneventserver does not see a heartbeat in X minutes an event will be created.
Usually means the daemon is down or having some sort of issue
| < |
Previous What command line can I use to obtain all properties of a specific event? |
Next TimeZone in Container |
> |