Am 30.05.2012 13:06, schrieb Wouter Depypere: > Hi, > > We have two running instances of icinga, one version 1.2 running for 3 > years and a 1.6.1 running since a few months. both have a postgres back > end and classic gui. > We are now looking into the possibilities of reporting on availability > and we have some questions. > > - (if I am correct) the standard reporting is based on log files. As > our old server has all the logs and history we would like to keep these > and migrate these to our new server. But is the format of these logs > still compatible between the versions? would it be as simple as moving > these files to the new server, reloading icinga and try the basic > reporting in the classic GUI? > > - Are these logs parsable to a database through an api/library provided? > > - We were also looking at the reporting package based on Jasper, but > from the website I understand this works only with MySQL. Is this > correct? And if so, would it be possible to setup a separate report > server based on these logs? And how easy would this be? > > > Thanks in advance, > > Wouter Depypere > - AFAIK the format of the log files hasn't changed (if you leave the option "log_external_commands_user" untouched) - please have a look at log2ido (http://docs.icinga.org/1.2/en/db_components.html#id1369416; I haven't used it so I don't know the syntax)
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
