Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
nagios.cfg
# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed. These commands are executed only if the
# enable_performance_data option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on performance data.
nagios.cfg
# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
# enable_performance_data option (above) is set to 1.
The above two quotes lead to double-saving the service performance data; the data are saved twice at the following locations:
/opt/perfdata/service-perfdata &
/var/log/nagios/service-perfdata.out
Is it safe to disable "process-service-perfdata" command ?
Each file is 26GB in size!! Is any way to reduce their size by loosing historical data before a specific time (ex. 2012) ?
Is there a reason why you are spooling all your perfdata into 1 file? Are you running pnp4nagios/npcd or any other reapers? What is the use case for this?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
amprantino wrote:I don't know if nagios use these data for reporting.
It is not. It only holds performance data and is usually only used by the graphing add ons (unless you rolled out something custom the relies on them).
amprantino wrote:Is any way to purge the info before a specific date? (for example before 2012)
Most likely, though it depends on their format. Could you post a few lines from each file?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Yep, that does seem to do the trick. Though I still wonder what you are even using these files for . . . .
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Is it possible to add an auto-purge parameter: for example nagios to purge all historical data that is older that a specific time, for example 1 or 2 years?
It looks like you already have an awk command for cleanup. You could set it to run with cron. Is that what you are doing now, or are you just running it manually?
If you'd like to see something more built-in, I'd suggest a feature request at https://github.com/NagiosEnterprises/nagioscore/issues . The devs will decide when/if the feature goes in. Of course, since it is open source, you could build it, and then the devs could potentially merge your code in.