Page 1 of 1
data not graphing properly in pnp4nagios
Posted: Wed Dec 30, 2015 11:09 am
by linuser
I am trying to track the number of unique DNS queries that are hitting our server. I was able to modify the check_bind.sh script and it works nicely. Here is the output I get:
Code: Select all
Bind9 is running. 2 successfull requests, 0 referrals, 2 nxdomains since last check. | 'success'=2 'referral'=0 'nxrrset'=2 'nxdomain'=2 'recursion'=0 'failure'=0 'duplicate'=0 'dropped'=0 'unique'=165161
My problem now is that I want to view this in pnp4nagios but it looks like this:
What do I need to do in order to produce a nice graph like the others?
Re: data not graphing properly in pnp4nagios
Posted: Wed Dec 30, 2015 11:28 am
by linuser
If I change the DS # to one that exist in BIND.rrd it will then show in graph format but at the next check interval pnp4nagios changes it back to 9 and looks like the pic again.
Re: data not graphing properly in pnp4nagios
Posted: Wed Dec 30, 2015 11:36 am
by Box293
If you have updated the script and additional datasources have been added after the initial creation of the RRD, this is the cause of the error.
When RRD files are first created, they are created with X amount of datasources (whatever data is being pushed in the first time).
If more datasources are added later, they are ignored as the RRD is not created to accommodate them.
You have two solutions:
1) Delete the RRD file and let it be created automatically again. You will lose all historic data.
2) This script for Nagios XI can update the RRD file with the correct amount of datasources.
ICMP and Ping Checks Stopped Graphing After XI 2014 Upgrade
http://support.nagios.com/wiki/index.ph ... 14_Upgrade
It is a basic perl script so it should work, but because you're not using XI I cannot guarantee it will.
Re: data not graphing properly in pnp4nagios
Posted: Wed Dec 30, 2015 11:47 am
by linuser
Ok, tested the file deletion method and that worked. Thanks for the help!
Re: data not graphing properly in pnp4nagios
Posted: Wed Dec 30, 2015 3:36 pm
by rkennedy
Glad to see this fixed! I'll go ahead and close this thread out now, but if you need any assistance in the future feel free to open a new one.