Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-users
1951 Views 7 Replies Latest reply: Nov 8, 2011 2:35 AM by Erik Itland RSS
Erik Itland Rank: White Belt
Erik Itland
9 posts since
Apr 26, 2010
Currently Being Moderated

Nov 3, 2011 9:17 AM

What decides how often a collector is run?

I've been trying to reconfigure the cycle time of a performance collector (zenperfsql) a few times and for some reason or another some of the hosts seem to be polled according to the old configuration while other hosts are polled according to the new configuration. How I found out was by grepping for "changing state from RUNNING to SQLC_QUERY" in zenperfsql.log.

 

It seems to me that the configuration is stashed away in a cache somewhere, maybe in the object database or somewhere (have been looking for .pickle and .zec files to no avail though).

 

Does anyone know?

Tags: collector, interval, cycle
  • jmp242 ZenossMaster
    jmp242
    4,060 posts since
    Mar 7, 2007
    Currently Being Moderated
    1. Nov 3, 2011 9:22 AM (in response to Erik Itland)
    Re: What decides how often a collector is run?

    Have you restarted all the collectors, or use push configuration changes ...?

     

    --

    James Pulver

    ZCA Member

    LEPP Computer Group

    Cornell University

    Have you restarted all the collectors or used push configuration changes ...

  • Erik Itland Rank: White Belt
    Erik Itland
    9 posts since
    Apr 26, 2010
    Currently Being Moderated
    2. Nov 3, 2011 10:16 AM (in response to jmp242)
    Re: What decides how often a collector is run?

    I have restarted zenoss completely a couple of times.

     

    When you mention pushing configuration changes, - did you mean by going to the devices in question and choose "Push changes"?

  • jmp242 ZenossMaster
    jmp242
    4,060 posts since
    Mar 7, 2007
    Currently Being Moderated
    3. Nov 3, 2011 10:28 AM (in response to Erik Itland)
    Re: What decides how often a collector is run?

    Yes.

     

    --

    James Pulver

    ZCA Member

    LEPP Computer Group

    Cornell University

  • Erik Itland Rank: White Belt
    Erik Itland
    9 posts since
    Apr 26, 2010
    Currently Being Moderated
    4. Nov 3, 2011 10:51 AM (in response to jmp242)
    Re: What decides how often a collector is run?

    Have tried it on one of the notorious offenders. Just got a second collection in less than 30 mins but I guess I should give it another hour.

  • Erik Itland Rank: White Belt
    Erik Itland
    9 posts since
    Apr 26, 2010
    Currently Being Moderated
    5. Nov 3, 2011 1:41 PM (in response to jmp242)
    Re: What decides how often a collector is run?

    Still the same.

  • jcurry ZenossMaster
    jcurry
    1,021 posts since
    Apr 15, 2008
    Currently Being Moderated
    6. Nov 4, 2011 8:21 AM (in response to Erik Itland)
    Re: What decides how often a collector is run?

    The reason you can't trivially find the cycle interval for zenperfsql is that it is part of Egor's ZenPack, rather than a standard daemon with Zenoss Core.  The version I have is ZenPacks.community.SQLDataSource 1.96 and this has a sqlPerfConfig.py file under the services directory of the ZenPack.  In my version, the comments say that the polling interval is taken from the WinCycleInterval (default 60 sec) though the actual code looks like it is picking up the snmp cycle interval of 300 secs.  There is a TODO note in my version that suggests he may be looking at making this interval configurable.

     

    Hope that helps!

     

    Cheers,

    Jane

  • Erik Itland Rank: White Belt
    Erik Itland
    9 posts since
    Apr 26, 2010
    Currently Being Moderated
    7. Nov 8, 2011 2:35 AM (in response to jcurry)
    Re: What decides how often a collector is run?

    I have already unpacked the Zenpack, tested a few changes and this in one in zenperfsql.py was the one I hoped would fix it:

    self.cycleInterval = 5 * 60 # seconds

    self.configCycleInterval = 20 # minutes

     

    Some days ago I updated the code to read like

     

    self.cycleInterval = 4 * 60 * 60 # seconds

    self.configCycleInterval = 12 * 60 # minutes

     

    The problem is that some of the servers are now polled every 4 hours while others are still consistently being polled multiple times an hour instead of every 4 hours as I would expect.

     

    While looking at it now I'm wondering if the configCycleInterval in zenperfsql.py might be the same thing as the configCycleInterval in sqlPerfConfig.py under services and if those are the ones that Matt Ray mentioned here: message/27768

    The "config cycle interval" is how often some of the daemons will reload their configuration unless it has been updated asynchronously in the interim.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points