Some events have Log Messages that are more verbose than Description
Description
I guess the logmsg field should be the short title of an event, correct? If so, there are a some events in opennms.events.xml which aren't configured correctly.
For example nodeLostService. There is the parm[eventReason] in logmsg which can blow up you "title".
Postgres outage identified on interface 10.10.7.48 with reason code: JDBC service is not responding on: NODE, 08001, org.postgresql.util.PSQLException: Connection to NODE:5004 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connection.
I looked at some other events and noticed, that often the descr field is filled with more information. Maybe it makes sense to audit the events in opennms.events.xml.
If you think it is a good idea, I would do this job
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Show:
Seth Leger May 5, 2017 at 1:40 PM
PR merged, marking as fixed.
commit 1747ae051d6cda0efe3152dc5c8c540f5c95da86
Seth Leger April 19, 2017 at 10:11 AM
Hi , that sounds perfect. I thought my phrase sounded a little awkward since it says "poller detected" and we "detect" with provisioning so I'm glad you improved it.
I'll review the PR as soon as I can.
Marcel Fuhrmann April 19, 2017 at 3:15 AM
I've choosen the phrase "... because of the following condition: %parm[eventReason]%" Please review it again.
Seth Leger April 13, 2017 at 12:09 PM
Can you replace the "Reason code: " phrase by integrating it into the previous sentence instead? To me, the entire phrase "reason code" is not good because it's not really a "code" (ie. number or other mnemonic), but a terse phrase indicating the problem. I would prefer to rephrase it like:
I guess the logmsg field should be the short title of an event, correct?
If so, there are a some events in opennms.events.xml which aren't configured correctly.
For example nodeLostService. There is the parm[eventReason] in logmsg which can blow up you "title".
I looked at some other events and noticed, that often the descr field is filled with more information.
Maybe it makes sense to audit the events in opennms.events.xml.
If you think it is a good idea, I would do this job