ZenPacks and JSON API

Expand all | Collapse all

Dynamic component modeling

  • 1.  Dynamic component modeling

    Posted 19 days ago
    Hi Team,

    We have a Linux device, when we model the device ZenOSS discovered all the component as below:
    Hard Drives:
    • /dev/sda
    • /dev/sdb
    • /dev/sdc
    File Systems:
    • /home
    • /var
    • /opt
    And ZenOSS started monitoring each component's (hard drive and file system) heath like free disk space, io rate, etc.

    But if we add a new Hard Drive (/dev/sdd) or created a new file system (/tmp), then, when ZenOSS will start monitoring new components?
    1. From the next device modeling cycle? (default is for every 12 hours)
    2. Is there a way to configure ZenOSS to detect new component more frequently. (Like for every 10 or 15 minutes).

    Please help us in resolving this issue. Thanks in advance.

    ------------------------------
    Bharat Kumar Kobagana
    Aptira Pty Ltd.
    ------------------------------


  • 2.  RE: Dynamic component modeling

    Posted 19 days ago
    So, you are quite right, new components are discovered by the modeler cycle which runs every 12 hours by default.  However, if a device has changed you can always do a manual remodel of the device from the GUI.

    If there are lots of devices getting lots of new components for some reason then you could write a little script to run zenmodeler. Use "zenmodeler help" to get all the options but the obvious candidates are "-d <device" and maybe "--collect <modeler plugin>" to restrict the modeler to particular components.  If you change lots of devices under a particular device class then the "-p <device class" will remodel all devices under the given class, including subclasses.

    Cheers,
    Jane

    ------------------------------
    Jane Curry
    Skills 1st United Kingdom
    jane.curry@skills-1st.co.uk
    ------------------------------



  • 3.  RE: Dynamic component modeling

    Posted 19 days ago
    You can increase modeling time, but I wouldn't recommend modeling all devices every 10-15 minutes. Would create too much db churn.

    Instead, I would have users model devices from the UI after doing maintenance to a machine. Or create a new datasource/event that looks for new stuff and if found create an event. This event could be used to kick off a new model of the device using trigger/notification or zProps.

    ------------------------------
    jstanley
    ------------------------------



  • 4.  RE: Dynamic component modeling

    Posted 18 days ago
    Thanks, Jane and Stanley, for the provided solutions. Will create a new data source to raise an event when new components are added to the devices.

    ------------------------------
    Bharat Kumar Kobagana
    Visakhapatnam
    ------------------------------