Nagios Support Forum

Now that I'm collecting rrd data and can graph service performance data (and I' m soo happy with that), I'm wondering how to keep data from only selected services.

It seems unnecessary to have rrd collect and process this data for all monitored hosts and every service that returns a valid data string. But maybe the overhead is so small, my concern is unwarranted.

BTW, most of our config will be in the "static" directory, and managed as text files, rather than through the XI interface.

Thanks...Lyle

Put this directive in any config/template where you don't want performance data processing.
The performance difference from this is based purely on the quantity of checks. Performance data processing is necessary for most users, but if you don't need it, it will free up a decent amount of CPU to turn it off. If you turn it off for 20 services, you probably won't notice. If you turn it off for 2000, you most certainly will see a difference.

Thanks. I thought there might be an simple answer.

...Lyle

Just post again if you have any questions or issues and we would be happy to help

In the interest of performance, I I want to only process & keep performance data for some services on some hosts, all manually defined in the static directory.

Setting process_perf_data=1 in the service definitions is no problem. But would I set process_perf_data=0 in the 4 occurrences in hosttemplates.cfg and servicetemplates.cfg in /usr/local/nagios?

So far, I have considered anything other than the static directory as "off limits". I'm not sure about what XI is maintaining, or what future XI releases might write over.

Thanks...Lyle

Update: Looks like I do this through the XI Core Config Manager, changing the template settings. I assume it survives upgrades etc, right?

You are correct, the upgrades will not touch your object configs or the Core Config Manager DB info. Maintaining configs through the CCM is how most XI users prefer to manage their configurations, as opposed to manual configurations in the static directory. Although some users have automation in place that require the manual maintenance.