[dev.icinga.com #1629] Daemonize AvailReportParser - Githubissues

icinga-migration commented 13 years ago

This issue has been migrated from Redmine: https://dev.icinga.com/issues/1629

Created by Anonymous on 2011-06-09 09:39:34 +00:00

Assignee: (none) Status: Rejected (closed on 2012-12-16 12:30:12 +00:00) Target Version: (none) Last Update: 2012-12-16 12:30:12 +00:00 (in Redmine)

I've tested out AvailReportParser, in the branch origin/mluebben/default. It's a very good start for the proper uptime/downtime reporting of services.

However, doing the report by hand is a bit "heavy" labour to generate logs for every service(not host).

Suggested changes:

Daemonize it, with set intervals to run at for all objects, so these can be ready for reporting, rather than a command line setup.
Change the way it works from a pregenerated report, to put the statusdata required for reporting in the database instead. (This way, the webgui to create the report from, can be used instead, and schedule it more easily, more flexible data too, using the flexibillity of the webgui).
Showcase the utility and its functions, it has a huge potential!
With the flexibility of putting all data in the database ready for reporting, retention of data ** is solved by the daemon. It should also be a lot easier to generate custom reports this way.

PS: Let me know if you want help making the daemon in Perl ;)

icinga-migration commented 13 years ago

Updated by mluebben on 2011-06-10 11:37:54 +00:00

1.)Daemonize it, with set intervals to run at for all objects, so these can be ready for reporting, rather than a command line setup.

The idea was to create cron jobs for importing the data in the database and set a flag for successfully import in the database. That be with icinga. A Daemon was a nice idea, but i have no enough experience to write a stable daemon in perl or c**.

2.) Change the way it works from a pregenerated report, to put the statusdata required for reporting in the database instead. (This way, the webgui to create the report from, can be used instead, and schedule it more easily, more flexible data too, using the flexibillity of the webgui).

I don't understand your idea. What do you mean?

icinga-migration commented 13 years ago

Updated by Anonymous on 2011-06-15 05:36:00 +00:00

1) That also works, its probably easier todo also ;)

2) Now you pregenerate the report data in the availparser, all I enter to get the report is the row index to get the report. Why does the parser generate the report? Why cant the parser just export all the data to a database, so I can make a shiny report in JasperServer instead? Like this: http://www.youtube.com/watch?v=gif-TmBF80A With that approach, its a ton easier to generate reports custom made, than using iReport or ordering it from someone ;-)

icinga-migration commented 13 years ago

Updated by mluebben on 2011-06-15 16:51:08 +00:00

2.) The JasperServer in the Video, is the JasperReports Server Professional or Enterprise Edition. In this versions can you create ad hoc reports:

http://www.jaspersoft.com/reporting-server

In the Community Edition can't you create ad hoc reports. There is a another problem, too. The data for a availability report not all in the IDO and it's very heavy to calculate this data with report time period, downtimes etc. That's why i create the parser ;-)

icinga-migration commented 13 years ago

Updated by Anonymous on 2011-06-15 17:34:56 +00:00

2) D'oh!

Keep em reports coming!

icinga-migration commented 13 years ago

Updated by mfriedrich on 2011-08-26 22:43:42 +00:00

Target Version changed from 1.5 to 1.5.1