On 11.07.2014 14:09, Antonio Fernández Pérez wrote:
The core does not care about these written files processed by an external application (npcd, ingrapd, graphios, etc). Similar to the ido db backend - it may be cleaned from historical entries, only the web and reporting are affected by that.
1) monitor your icinga host, graph the trends 2) usually log files (icinga.log archives) and if a db is used, the size 3) debug logs and not processed performance data files (the latter leads into funny inode problems [0]) regards, Michael [0] http://www.legendiary.at/2013/09/27/the-inode-problem/
-- Michael Friedrich, DI (FH) Application Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | michael.friedr...@netways.de ** Open Source Backup Conference 2014 - September - osbconf.org ** ** Puppet Camp Duesseldorf 2014 - Oktober - netways.de/puppetcamp ** ** OSMC 2014 - November - netways.de/osmc ** ** OpenNebula Conf 2014 - Dezember - opennebulaconf.com ** |
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users