---

Subject:	Any 'active' event (Not
Author:	Jay Stanley
Posted:	2016-05-31 09:13

Any 'active' event (Not cleared or closed) will either be archived after X days (See Settings > Events) or Aged (Informational events)

All active events will stay in the event console.

---

Subject:	Green alerts seem to act differently for us in Core 5
Author:	Larry Virden
Posted:	2016-06-08 09:14

When a green (aka OK, aka severity 0) alert is sent, it never appears on our event console. And in fact, we don't see it in the archive as well.

When we change the severity/color to 1/blue, the same alert appears just fine in the event console.

We would love for it to appear in the active queue. Other software we have used would do an "aging" process so that the green would go away after 5 minutes or so.

However, the Core 5 admin guide, page 110talks about:

Auto-Clear Correlation

The auto-clearing feature is similar to the de-duplication feature. It also is based on the event's fingerprint. The difference is which event fields make up the fingerprint, and what happens when a new event matches an existing event's fingerprint.

All of the standard events created as a result of polling activities do auto-clearing by themselves. As with deduplication, you would invoke auto-clearing manually only to handle events that come from other sources, such as syslog, a Windows event log, or SNMP traps.

If a component has been identified for the event, then the auto-clear fingerprint consists of these fields:

If component UUID exists:

component UUID

eventClass (including zEventClearClasses from event class configuration properties)

eventKey (can be blank)

If component UUID does not exist:

device

component (can be blank)

eventKey (can be blank)

eventClass (including zEventClearClasses from event class configuration properties)

When a new event comes into the system with a special 0 (Clear) severity, Zenoss Core checks all active events to see if they match the auto-clear fingerprint of the new event. All active events that match the auto-clear fingerprint are updated with a Cleared state, and the clearid field is set to the UUID of the clear event. After a configurable period of time, all events in a closed state (Closed, Cleared, and Aged) are moved from the active events table to the event archive.

If an event is cleared by the clear event, it is also inserted into the active events table with a status of Closed; otherwise, it is dropped. This is done to prevent extraneous clear messages from filling your events database.

---

Subject:	make sure you have Clears
Author:	Jay Stanley
Posted:	2016-06-08 18:25

make sure you have Clears selected in your filters

---

Subject:	test from jc
Author:	Jane Curry
Posted:	2016-06-09 03:17

test from jc

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk

---

Subject:	This is a test comment. It
Author:	[Not Specified]
Posted:	2016-06-09 03:17

This is a test comment. It should be ignored.

---

Subject:	Change Zenoss Core 5 blue (cleared/up/ok) events to green events
Author:	[Not Specified]
Posted:	2016-08-16 08:57

Working with LVirden, we'd like to know if it's possible for the out of the box setting up/cleared events to be changed to show as green up/cleared events. As mentioned there is information in theadmin guide, page 110 as well as something on page 171 'Changing Events Maintenance Settings - Don't Age this Severity and Above. In this 2nd option we've changed this to 'Clear'.

But we'd still like to see the up/ok/green events as some alerts have timers and will auto clear, some alerts need to be noted when they do clear so not all up/ok events should auto clear from the event console.

---

Subject:	Again, check your filters.
Author:	Jay Stanley
Posted:	2016-09-01 09:19

Again, check your filters. Select Cleared and Closed and Severity Clear and they will show up in the event console until they archive.

<

Previous Graphing Troubles

Next Does Zenoss Core have the basics of discovery of relationships between devices, ...

>