2. RE: No alerts received since last four days

Are you collecting data? I would check graphs to make sure you are getting data. Also check any threshold to ensure they are enabled. There could be mutlipe reasons why your not getting alerts. Do you have triggers and notifications configured and enabled? I would go through the event pipeline and verify each step is working. From collection to rabbit queues, to console and trigger/notification process.

3. RE: No alerts received since last four days

Is it really "alerts" ie notifications, probably email, that you are not getting? Or is it "events" that are missing ie. no updates in the event console?

As Devon says, check that events are actually being generated from the different sources and check your rabbit queues - need to be root user to run:

rabbitmqctl -p /zenoss list_queuesrawevents is the queue of incoming eventszenevents are events that have been processed by zeneventdthe signal queue are events that are queued for notifications

In general, all queues are likely to be 0 unless you are in the middle of an event storm. Any queue that is consistently above 0 suggests that a daemon has stopped for some reason.

zeneventd is the daemon that takes "raw" events and processes them so that they eventually appear in the event console. zenactiond is the daemon that then looks at processed events, checks them against all your active triggers and then generates any matching notifications. Check the log files for each daemon (in /opt/zenoss/log and, if you are running Zenoss 5 or 6, you will need to have attached to the relevant container to see entries in the log file).

Original Message:Sent: 12-16-2018 07:37 AMFrom: Jane CurrySubject: No alerts received since last four days

Is it really "alerts" ie notifications, probably email, that you are not getting? Or is it "events" that are missing ie. no updates in the event console?

As Devon says, check that events are actually being generated from the different sources and check your rabbit queues - need to be root user to run:

rabbitmqctl -p /zenoss list_queuesrawevents is the queue of incoming eventszenevents are events that have been processed by zeneventdthe signal queue are events that are queued for notifications

In general, all queues are likely to be 0 unless you are in the middle of an event storm. Any queue that is consistently above 0 suggests that a daemon has stopped for some reason.

zeneventd is the daemon that takes "raw" events and processes them so that they eventually appear in the event console. zenactiond is the daemon that then looks at processed events, checks them against all your active triggers and then generates any matching notifications. Check the log files for each daemon (in /opt/zenoss/log and, if you are running Zenoss 5 or 6, you will need to have attached to the relevant container to see entries in the log file).