This report analyse OpenNMS events. Events are displayed by source like Syslogd, Trapd or perl_send_event. To see how many events are processed in OpenNMS, a statistical overview about the average daily events per hour will be displayed. For diagnosis there are some different Top25 lists to identify eventstorms or generic enterprise trap issues.
This report requires enhancement in bug#4060 to upgrade JasperReports to 3.7.4. To calculate the events per hour there is Postgres function
generate_series(start_timestamp, end_timestamp)
used. This function is available in Postgres 8.4+. If somebody has an idea to solve this issue with a more compatible statement, don't hestitate to drop me a message, you're welcome.
Environment
Operating System: All
Platform: PC
URL: http://www.open-factory.org
Acceptance / Success Criteria
None
Attachments
5
Lucidchart Diagrams
Activity
Show:
Markus von Rüden October 9, 2015 at 2:51 AM
The Event Analysis report is working fine. Closing...
David Hustace March 22, 2011 at 6:43 AM
Ronny has 2 accounts. One has 3 recent login attempts and 3 failures. Changing issues to his indigo account.
Donald Desloge February 8, 2011 at 3:02 PM
Ronny,
I am having trouble running this report. Seems to be the events_eph dataset that keeps having trouble.
This report analyse OpenNMS events. Events are displayed by source like Syslogd, Trapd or perl_send_event. To see how many events are processed in OpenNMS, a statistical overview about the average daily events per hour will be displayed. For diagnosis there are some different Top25 lists to identify eventstorms or generic enterprise trap issues.
This report requires enhancement in bug#4060 to upgrade JasperReports to 3.7.4. To calculate the events per hour there is Postgres function
generate_series(start_timestamp, end_timestamp)
used. This function is available in Postgres 8.4+. If somebody has an idea to solve this issue with a more compatible statement, don't hestitate to drop me a message, you're welcome.