Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-users
46318 Views 4 Replies Latest reply: Oct 21, 2009 4:15 AM by jcurry RSS
jcurry ZenossMaster
jcurry
1,021 posts since
Apr 15, 2008
Currently Being Moderated

Feb 2, 2009 3:16 PM

Config cycle and modeler cycle

If you use the left-hand menu and choose Collectors (which used to be called Monitors), it shows you various values including:
Config Cycle Interval (mins) 360
Modeler Cycle Interval (mins) 720

The 2.3 version of the Admin Guide, page 55, says that "By default, the system is setup to perform complete remodeling every 6 hours." - but it says this under the zenmodeler daemon.

My belief is that the zenmodeler daemon actually runs every 12 hours by default (the 720 shown above), not eveery 6 hours. Is this correct???

And just what IS the Config Cycle that runs eveery 360 mins??

Thanks,
Jane
  • Matt Ray Rank: Zen Master
    Matt Ray
    2,484 posts since
    Apr 5, 2008
    Currently Being Moderated
    1. Feb 4, 2009 5:28 PM (in response to jcurry)
    RE: Config cycle and modeler cycle
    Chet dropped some knowledge on us:

    The default modeling cycle is 720 minutes (12 hours). The documentation is wrong. The "config cycle interval" is how often some of the daemons will reload their configuration unless it has been updated asynchronously in the interim. Really the config cycle interval is something that doesn't matter much anymore since everything is asynchronously updated. By changing the "Modeler Cycle Interval (mins)" in the collector's configuration you can change the default modeling interval.

    This is going to be captured in the 2.3.3 Admin Guide update.

    Thanks,
    Matt
  • mwcotton Rank: Brown Belt
    mwcotton
    563 posts since
    Apr 23, 2008
    Currently Being Moderated
    2. Feb 4, 2009 9:11 PM (in response to Matt Ray)
    RE: Config cycle and modeler cycle
    What does " reload their configuration" mean?
    Could mean reload the configuration from the zenoss/etc/*.conf files or it could reread some magic info from the database.
  • Matt Ray Rank: Zen Master
    Matt Ray
    2,484 posts since
    Apr 5, 2008
    Currently Being Moderated
    3. Feb 10, 2009 11:11 AM (in response to mwcotton)
    Config cycle and modeler cycle
    When you make changes to the device configuration, you have to
    manually "Push Changes" if you want them to go into effect
    immediately. If not, it will wait until the next reload.

    Thanks,
    Matt Ray
    Zenoss Community Manager
    community.zenoss.com
    mray@zenoss.com



    On Feb 4, 2009, at 8:11 PM, mwcotton wrote:

     

     

    What does " reload their configuration" mean?
    Could mean reload the configuration from the zenoss/etc/*.conf files
    or it could reread some magic info from the database.







    _______________________________________________
    zenoss-users mailing list
    zenoss-users@zenoss.org
    http://lists.zenoss.org/mailman/listinfo/zenoss-users


    _______________________________________________
    zenoss-users mailing list
    zenoss-users@zenoss.org
    http://lists.zenoss.org/mailman/listinfo/zenoss-users
  • jcurry ZenossMaster
    jcurry
    1,021 posts since
    Apr 15, 2008
    Currently Being Moderated
    4. Oct 21, 2009 4:15 AM (in response to Matt Ray)
    Re: RE: Config cycle and modeler cycle

    Can we go around the "Config Cycle" question again? When Chet says "some of the daemons will reload their configuration unless it has been updated asynchronously" - which daemons?  I am struggling yet again to get consistency with IP service monitoring and process monitoring and I am wondering if these are the daemons (zenprocess and zenstatus) that may use the config cycle as I sometimes find that configuration in this sort of area suddenly "takes" overnight.

     

    The Event History, for example, has /Change/Set entries like "calling function 'setServiceClass' with '{'protocol': 'udp', 'port': 161}' on object udp_00161" after I was doing stuff with that service during the evening - the event came through at 4:09 (when I certainly wasn't doing stuff) but this time coincides with the "Last Collection" field on each device's status page (which I assumes means the last modeler poll?).

     

    Is it just the modeler poll that is triggering these /Change/Set service / process entries or does the Config Cycle have a roll here? (or anywhere now????).

     

    This is a 2.5 drop 5 beta but I believe it has not changed significantly for yonks.

     

    Cheers,

    Jane

More Like This

  • Retrieving data ...

Incoming Links