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.
I created a custom check and wanted to track performance data and i am just using PNP4nagios, which is fine for me. Some of the data gets through, but it seems like I have too many lines of data for Performance Data to manage. Is there a limit to how much data Performance Data can handle? Here is a pic to show what I mean:
You should always print something to STDOUT that tells if the service is working or why it is failing. Try to keep the output short - probably less that 80 characters. Remember that you ideally would like the entire output to appear in a pager message, which will get chopped off after a certain length.
You may be running into issues with the time-series database of choice (usually RRD):
label length is arbitrary, but ideally the first 19 characters are unique (due to a limitation in RRD). Be aware of a limitation in the amount of data that NRPE returns to Nagios
Nagios Core will only read the first 4 KB of data that a plugin returns. This is done in order to prevent runaway plugins from dumping megs or gigs of data back to Nagios Core. This 4 KB output limit is fairly easy to change if you need. Simply edit the value of the MAX_PLUGIN_OUTPUT_LENGTH definition in the include/nagios.h.in file of the source code distribution and recompile Nagios Core. There's nothing else you need to change!
It's hard for me to give a definitive answer without rather intimate details of your setup and a deep-dive, but those are some things to consider.
