2. Introduction
• Status quo reporting
• Why a reporting engine?
• How does it work?
• Realworld examples
• Alternatives
• Conclusion and perspectives
• Resources - Q&A
User Conference Europe 2009
3. Status quo reporting
• A lot of data in OpenNMS
• Performancedata in RRD/JRB-Flatfiles
• Nodes, events, alarms, notifications, outages,
thresholds, assets
stored in SQL-Database
User Conference Europe 2009
4. Status quo reporting
• Performancedata
• KSC Reports
• Customized Resource Graphs
• Statistics Reports
• Outages
• Availability Reporting
• SLA-Reporting
User Conference Europe 2009
6. Why a reporting engine?
• Easier customized availability reports
• Providing scheduling, history, mail
• Easier deployment and maintaining
• Easier to keep OpenNMS up-to-date
• A lot of use cases in the realworld
User Conference Europe 2009
7. Why a reporting engine?
• Good tools - Rich Client Application
• Playing within boundaries
• Build and maintain report-packages
• It´s easy to deploy reports to customer
• Report other applications with SQL
(OTRS, RT, CMDBs ...)
User Conference Europe 2009
8. How does it work?
• We uselicense model Shareware/OpenCore)
(Hybrid
JasperServer with iReport
• We use JasperServer community edition
(GNU Public License)
• We use JasperServer Webservice API
User Conference Europe 2009
14. Conclusion and
perspectives
• It´s the entering wedge
• It would be nice to put the basic reporting
stuff to the OpenNMS webapplication
• Provide a platform for reporting
• Create report-packages in the community
• Cool stuff for reporting in the pipeline
WMI-Support, RANCID, Inventory scanner
User Conference Europe 2009
15. Resources - Q&A
• OpenNMS Wiki - Integration
• Bugzilla sourcepatch for 1.6.2
• JasperServer 3.0 Web-Services guide
• OpenNMS SVN - feature-jasper
• OpenNMS Mailinglist
• IRC: irc://irc.freenode.org/#opennms
User Conference Europe 2009
