TECHZEN Zenoss User Community ARCHIVE  
FORUMS / ZenPacks, JSON API, and Integrations / DISCUSSION

Dynamic component modeling

Subject: Dynamic component modeling
Author: Bharat Kumar Kobagana
Posted: 2019-04-05 06:06

Hi Team,

We have a Linux device, when we model the device ZenOSS discovered all the component as below:
Hard Drives:
File Systems:
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.
------------------------------

Subject: RE: Dynamic component modeling
Author: Jane Curry
Posted: 2019-04-05 11:07

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
------------------------------

Subject: RE: Dynamic component modeling
Author: Jay Stanley
Posted: 2019-04-05 14:33

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
------------------------------

Subject: RE: Dynamic component modeling
Author: Bharat Kumar Kobagana
Posted: 2019-04-06 08:52

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
------------------------------


< Previous
API change zparemeter fails 		  Next
Extend Monitoring Templates in child device classes 		>