Performance Graphs downloads naming for NRPE/NSCLIENT

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
dlukinski
Posts: 1130
Joined: Tue Oct 06, 2015 9:42 am

Performance Graphs downloads naming for NRPE/NSCLIENT

Post by dlukinski »

Hello Nagios XI support

Wehn we generate PErfoamnce Graph download for SNMP-based checks, we get JPG file named correctly such as
[email protected]_usage.jpg

But in case of NRPE, NCPA or NSclient checks we only get chart.jpg, chart2.jpg and so one.

We sometimes need dozens of such downloads done in a short period of time. Renaming them manually could be too long.
How to fix Nagios to make it generate correct file-names for non-SNMP checks?

Thank you,
Dimitri
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Performance Graphs downloads naming for NRPE/NSCLIENT

Post by lmiltchev »

I don't believe this issue has anything to do with the type of checks (SNMP, NRPE, NCPA, etc.). It is a problem with escaping spacial characters.

I was able to recreate the issue when trying to save a chart as JPEG of a service named "/Disk Usage". In this case, the "/" was causing the issue, and the chart was saved as "chart.jpg". I already filed an internal bug report on the issue (task_id=13118).

Our developers have been notified, and will be fixing the issue as soon as they can.

Thank you!
Be sure to check out our Knowledgebase for helpful articles and solutions!
dlukinski
Posts: 1130
Joined: Tue Oct 06, 2015 9:42 am

Re: Performance Graphs downloads naming for NRPE/NSCLIENT

Post by dlukinski »

lmiltchev wrote:I don't believe this issue has anything to do with the type of checks (SNMP, NRPE, NCPA, etc.). It is a problem with escaping spacial characters.

I was able to recreate the issue when trying to save a chart as JPEG of a service named "/Disk Usage". In this case, the "/" was causing the issue, and the chart was saved as "chart.jpg". I already filed an internal bug report on the issue (task_id=13118).

Our developers have been notified, and will be fixing the issue as soon as they can.

Thank you!
Please close the case
Locked