Data Queries - "Suggested Values" working intermittently

[zeero22]

Hi,

I am trying to set a graph title using the "Suggested Values" section of my Data Query. The suggest value is not being accepted and the text "|query_class|" is used instead. The strange thing is that the title gets set correctly for some routers but not others. By comparing a verbose query on a working and non-working device I cannot determine any differences or the reason for the failure. How can I troubleshoot why the suggested value is not being processed?

Here are my system details:
CentOS 6.3
RRDtool 1.4.7
MySQL 5.1.61
Cacti 0.8.8a

Create Graphs:


Suggested Values:


Verbose Query:


Thanks

[zeero22]

Hey guys,

Does anyone have any idea why this is happening? Any help would be appreciated. I have read the documentation for using suggested values and I can't see where I am going wrong. Should I open a bug for this?

Thanks
Zee

[zeero22]

Some more info ... as per the attachment, the field_name in the SQL database remains consistent between the working device and non-working device. Possible cacti bug?

[BSOD2600]

does the 'reapply suggested names' function work?
Using spine or cmd.php?

[zeero22]

Hi,

Thanks for responding.
I am using cmd.php
Unfortunately using the 'reapply suggested names' function still returns "|query_class|" as the graph title.

[BSOD2600]

It shouldn't matter but try: |query_Class|

Look in the poller cache for that device. do you see those Class names? What about after clicking the green circle (invokes a manual requery)?

[zeero22]

Hi,

Unfortunately still no luck with this. Is there anyway to debug the 'back-end' of cacti to understand how it is interpreting these variables?
- The poller cache was blank/empty for this device
- Using an uppercase 'C' in |query_Class| had no effect
- Clicking on the green circle in the devices tab (to initiate a manual query) yielded the same results

[BSOD2600]

yet the Verbose Query output still returns the Class info? That's really weird.

This the only script you're having problems with?
Any errors in the technical support page?

[zeero22]

Hi,

Yes, it is strange that the verbose query returns the class info and yet cacti fails to interpret the query string. It is also strange that the query works for some routers and not others. There are two things I noticed between a working router and a non-working router:
- The query takes significantly longer on a non-working router (25secs) in comparison to the same query on a working router (5 secs) despite the query results being very similar in size and structure.
- When selecting the 'class name' to graph under the "Create graphs for this host" heading, the working router always 'greys out' the selection after it has been submitted, whilst with a non-working router the selections are never "greyed out" and can be selected again.
I am not having issues with any of my other scripts, only this one.
There are no visible errors on the technical support page.

Cheers
Zee

[gandalf]

On a reindex trigger, cacti will poll all information used by the related XML file. This will take time and may overload the target device. So, the data required for your |query_*| variables may not be provided, hence the faulty display and the long polling time for "unresponsive" devices.
R.

[zeero22]

On a reindex trigger, cacti will poll all information used by the related XML file. This will take time and may overload the target device. So, the data required for your |query_*| variables may not be provided, hence the faulty display and the long polling time for "unresponsive" devices.
R.

Thanks Gandalf, is it possible to extend the query timeout?

[gandalf]

Not that I'm aware of. My hint was meant as a possible approach. You will first have to verify, if I'm correct or if different magic is happening here.
R.