Closed alienth closed 12 years ago
I should note, on the previous version of this zenpack, I had the same issue. I got around it by manually setting the cycleTime in objects.xml and reinstalling. However, I don't think that should be necessary any longer, since the datasource now has the cycleTime field.
can you enable 'debug' logging level by zenperfsql daemon? I'm pretty sure that SqlPerformanceCollectionTasks will be created with a correct scheduleIntervalSeconds values (you can check this by job name).
Despite the debug setting existing in the zenperfsql.xml, I got the following when trying to enable it in zenperfsql.conf:
INFO: Commenting out unknown option 'debug' found on line 105 in config file
Going to try to run it in command-line mode with debug enabled.
Hm, I think this might actually be happening upon 5 minute runs due to Missed_Runs. Going to close this for now while I investigate further.
Thanks, Jason
I turned my cycleTime down to 60 seconds for the pgSqlDatabase and pgSqlDatabaseStat templates. However, it appears that zenperfsql isn't honouring this, and it is sticking with a 300 second cycletime.
I've remodeled all of my devices, restarted zenoss entirely, and verified that the Database components aren't using a local template. Running on the latest HEAD of all of the related zenpacks.