Capacity Planning Graphs - values not JSON compliant
Capacity Planning Graphs - values not JSON compliant
Capacity Planning graphs will not display. The following message appears
No Data to Display: out of range float values are not json compliant
No Data to Display: out of range float values are not json compliant
Re: Capacity Planning Graphs - values not JSON compliant
Is there any output in Details --> Advanced --> Performance Data? If so, can you post it?
Re: Capacity Planning Graphs - values not JSON compliant
Please see attached.
You do not have the required permissions to view the files attached to this post.
Re: Capacity Planning Graphs - values not JSON compliant
FLCUISIT, can you also tell us what is the version of the Nagios XI and the Capacity Planning Report component that you are currently using?
Admin->Manage Components
Admin->Manage Components
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Capacity Planning Graphs - values not JSON compliant
Latest Available Version: 2014R2.6
Installed Version: 2014R2.6
Last Update Check: 2015-03-09 11:52:03
Capacity Planning Report
Provides data extrapolation and capacity planning capability. Requires host authorization to view report.
Version: 2.1.9 Date: 12/29/2014 Author: Nagios Enterprises, LLC
Installed Version: 2014R2.6
Last Update Check: 2015-03-09 11:52:03
Capacity Planning Report
Provides data extrapolation and capacity planning capability. Requires host authorization to view report.
Version: 2.1.9 Date: 12/29/2014 Author: Nagios Enterprises, LLC
Re: Capacity Planning Graphs - values not JSON compliant
Hm-m, we had a bug in the past (which was fixed), where you would get a similar errors in the Capacity Planning if the "<LABEL>...</LABEL> tags were missing in the xml file.
Maybe something similar is going on here. Are you missing the <UNIT>...</UNIT> tags? Can you show us the xml file and the permissions?
Maybe something similar is going on here. Are you missing the <UNIT>...</UNIT> tags? Can you show us the xml file and the permissions?
Code: Select all
cat /usr/local/nagios/share/perfdata/hp.core.fcu/Ping.xml
ll -d /usr/local/nagios/share/perfdata/hp.core.fcu
ll /usr/local/nagios/share/perfdata/hp.core.fcuBe sure to check out our Knowledgebase for helpful articles and solutions!
Re: Capacity Planning Graphs - values not JSON compliant
Code: Select all
cat /usr/local/nagios/share/perfdata/hp.core.fcu/Ping.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<NAGIOS>
<DATASOURCE>
<TEMPLATE>check_xi_service_ping</TEMPLATE>
<IS_MULTI>0</IS_MULTI>
<DS>1</DS>
<NAME>rta</NAME>
<UNIT>ms</UNIT>
<ACT>13.366</ACT>
<WARN>3000.000</WARN>
<WARN_MIN></WARN_MIN>
<WARN_MAX></WARN_MAX>
<WARN_RANGE_TYPE></WARN_RANGE_TYPE>
<CRIT>5000.000</CRIT>
<CRIT_MIN></CRIT_MIN>
<CRIT_MAX></CRIT_MAX>
<CRIT_RANGE_TYPE></CRIT_RANGE_TYPE>
<MIN>0</MIN>
<MAX></MAX>
</DATASOURCE>
<DATASOURCE>
<TEMPLATE>check_xi_service_ping</TEMPLATE>
<IS_MULTI>0</IS_MULTI>
<DS>2</DS>
<NAME>pl</NAME>
<UNIT>%%</UNIT>
<ACT>0</ACT>
<WARN>80</WARN>
<WARN_MIN></WARN_MIN>
<WARN_MAX></WARN_MAX>
<WARN_RANGE_TYPE></WARN_RANGE_TYPE>
<CRIT>100</CRIT>
<CRIT_MIN></CRIT_MIN>
<CRIT_MAX></CRIT_MAX>
<CRIT_RANGE_TYPE></CRIT_RANGE_TYPE>
<MIN></MIN>
<MAX></MAX>
</DATASOURCE>
<DATASOURCE>
<TEMPLATE>check_xi_service_ping</TEMPLATE>
<IS_MULTI>0</IS_MULTI>
<DS>3</DS>
<NAME>rtmax</NAME>
<UNIT>ms</UNIT>
<ACT>15.083</ACT>
<WARN></WARN>
<WARN_MIN></WARN_MIN>
<WARN_MAX></WARN_MAX>
<WARN_RANGE_TYPE></WARN_RANGE_TYPE>
<CRIT></CRIT>
<CRIT_MIN></CRIT_MIN>
<CRIT_MAX></CRIT_MAX>
<CRIT_RANGE_TYPE></CRIT_RANGE_TYPE>
<MIN></MIN>
<MAX></MAX>
</DATASOURCE>
<DATASOURCE>
<TEMPLATE>check_xi_service_ping</TEMPLATE>
<IS_MULTI>0</IS_MULTI>
<DS>4</DS>
<NAME>rtmin</NAME>
<UNIT>ms</UNIT>
<ACT>12.147</ACT>
<WARN></WARN>
<WARN_MIN></WARN_MIN>
<WARN_MAX></WARN_MAX>
<WARN_RANGE_TYPE></WARN_RANGE_TYPE>
<CRIT></CRIT>
<CRIT_MIN></CRIT_MIN>
<CRIT_MAX></CRIT_MAX>
<CRIT_RANGE_TYPE></CRIT_RANGE_TYPE>
<MIN></MIN>
<MAX></MAX>
</DATASOURCE>
<RRD>
<RC>1</RC>
<TXT>/usr/local/nagios/share/perfdata/hp.core.fcu/Ping.rrd: found extra data on update argument: 15.083:12.147</TXT>
</RRD>
<NAGIOS_CHECK_COMMAND>check_xi_service_ping!3000.0!80%!5000.0!100%</NAGIOS_CHECK_COMMAND>
<NAGIOS_DATATYPE>SERVICEPERFDATA</NAGIOS_DATATYPE>
<NAGIOS_DISP_HOSTNAME>hp.core.fcu</NAGIOS_DISP_HOSTNAME>
<NAGIOS_DISP_SERVICEDESC>Ping</NAGIOS_DISP_SERVICEDESC>
<NAGIOS_HOSTNAME>hp.core.fcu</NAGIOS_HOSTNAME>
<NAGIOS_HOSTSTATE>UP</NAGIOS_HOSTSTATE>
<NAGIOS_HOSTSTATETYPE>HARD</NAGIOS_HOSTSTATETYPE>
<NAGIOS_MULTI_PARENT></NAGIOS_MULTI_PARENT>
<NAGIOS_PERFDATA>rta=13.366ms;3000.000;5000.000;0; pl=0%;80;100;; rtmax=15.083ms;;;; rtmin=12.147ms;;;; </NAGIOS_PERFDATA>
<NAGIOS_RRDFILE>/usr/local/nagios/share/perfdata/hp.core.fcu/Ping.rrd</NAGIOS_RRDFILE>
<NAGIOS_SERVICECHECKCOMMAND>check_xi_service_ping!3000.0!80%!5000.0!100%</NAGIOS_SERVICECHECKCOMMAND>
<NAGIOS_SERVICEDESC>Ping</NAGIOS_SERVICEDESC>
<NAGIOS_SERVICEOUTPUT>OK - 192.168.18.3: rta 13.366ms, lost 0%</NAGIOS_SERVICEOUTPUT>
<NAGIOS_SERVICEPERFDATA>rta=13.366ms;3000.000;5000.000;0; pl=0%;80;100;; rtmax=15.083ms;;;; rtmin=12.147ms;;;;</NAGIOS_SERVICEPERFDATA>
<NAGIOS_SERVICESTATE>OK</NAGIOS_SERVICESTATE>
<NAGIOS_SERVICESTATETYPE>HARD</NAGIOS_SERVICESTATETYPE>
<NAGIOS_TIMET>1426076773</NAGIOS_TIMET>
<NAGIOS_XMLFILE>/usr/local/nagios/share/perfdata/hp.core.fcu/Ping.xml</NAGIOS_XMLFILE>
</NAGIOS>Code: Select all
[root@localhost ~]# ll -d /usr/local/nagios/share/perfdata/hp.core.fcu
drwxrwxr-x 2 nagios nagios 4096 Mar 11 08:57 /usr/local/nagios/share/perfdata/hp.core.fcu
You have new mail in /var/spool/mail/rootCode: Select all
[root@localhost ~]# ll /usr/local/nagios/share/perfdata/hp.core.fcu
total 4208
-rwxrwxr-x 1 nagios nagios 384740 Aug 30 2011 CPU_Usage.rrd
-rw-rw-r-- 1 nagios nagios 1799 Mar 11 08:57 CPU_Usage.xml
-rwxrwxr-x 1 nagios nagios 384740 Aug 30 2011 Drive_C__Disk_Usage.rrd
-rw-rw-r-- 1 nagios nagios 1960 Mar 11 08:53 Drive_C__Disk_Usage.xml
-rwxrwxr-x 1 nagios nagios 768012 Aug 30 2011 _HOST_.rrd
-rw-rw-r-- 1 nagios nagios 3148 Mar 11 09:22 _HOST_.xml
-rwxrwxr-x 1 nagios nagios 384740 Aug 30 2011 Logon_Errors.rrd
-rw-rw-r-- 1 nagios nagios 2072 Mar 11 09:23 Logon_Errors.xml
-rwxrwxr-x 1 nagios nagios 384740 Aug 30 2011 Memory_Usage.rrd
-rw-rw-r-- 1 nagios nagios 1940 Mar 11 08:56 Memory_Usage.xml
-rwxrwxr-x 1 nagios nagios 384740 Aug 30 2011 Page_File_Usage.rrd
-rw-rw-r-- 1 nagios nagios 2050 Mar 11 08:55 Page_File_Usage.xml
-rwxrwxr-x 1 nagios nagios 768012 Aug 30 2011 Ping.rrd
-rw-rw-r-- 1 nagios nagios 3268 Mar 11 08:56 Ping.xml
-rwxrwxr-x 1 nagios nagios 384740 Aug 30 2011 Server_Work_Queues.rrd
-rw-rw-r-- 1 nagios nagios 2262 Mar 11 08:57 Server_Work_Queues.xml
-rwxrwxr-x 1 nagios nagios 384736 Jul 30 2014 Uptime.rrd
-rw-rw-r-- 1 nagios nagios 1733 Mar 11 08:56 Uptime.xmlRe: Capacity Planning Graphs - values not JSON compliant
Also, this issue occurs for multiple servers, switches and routers
Re: Capacity Planning Graphs - values not JSON compliant
Our developers are looking into this. Can you try the following (as a workaround)?
Open the "/usr/local/nagiosxi/html/includes/components/capacityplanning/backend/rrddatastore.py" file in a text editor and comment out line 100-101, so that they would look like this:
Save and exit. Let us know if this fixed your issue.
Open the "/usr/local/nagiosxi/html/includes/components/capacityplanning/backend/rrddatastore.py" file in a text editor and comment out line 100-101, so that they would look like this:
Code: Select all
# self.dataset.host = self.host
# self.dataset.service = self.serviceBe sure to check out our Knowledgebase for helpful articles and solutions!
Re: Capacity Planning Graphs - values not JSON compliant
This did not resolve the issue