The number of different values running around out there for an event's source has become mind-boggling. To my understanding, this field was meant to have a relatively small set of values ("Trapd", "EventTranslator", "perl-send-event"...) in normal use while not excluding the use of arbitrary values ("zekes-custom-event-generator") when needed.
What I've been seeing doesn't line up at all with that expectation. Values seem to be all over the map, with some OpenNMS daemons using "OpenNMS.DaemonName", others just "DaemonName", and Threshd being a totally odd duck in that it concatenates "Threshd." with the ds-name or expression whose evaluation resulted in the event in question.
If my expectation is totally out of line with the actual intent of this field, then somebody please WONTFIX this bug, but I'd like to know of a predictable way to know which component created a given event. This knowledge is important when making decisions about which events to forward in a multi-node installation of OpenNMS.
If we're going to clean this up, I think before 1.8 is a good time to do it.
The number of different values running around out there for an event's source has become mind-boggling. To my understanding, this field was meant to have a relatively small set of values ("Trapd", "EventTranslator", "perl-send-event"...) in normal use while not excluding the use of arbitrary values ("zekes-custom-event-generator") when needed.
What I've been seeing doesn't line up at all with that expectation. Values seem to be all over the map, with some OpenNMS daemons using "OpenNMS.DaemonName", others just "DaemonName", and Threshd being a totally odd duck in that it concatenates "Threshd." with the ds-name or expression whose evaluation resulted in the event in question.
If my expectation is totally out of line with the actual intent of this field, then somebody please WONTFIX this bug, but I'd like to know of a predictable way to know which component created a given event. This knowledge is important when making decisions about which events to forward in a multi-node installation of OpenNMS.
If we're going to clean this up, I think before 1.8 is a good time to do it.