TechZen - Zenoss User Community Forums

Just to add, if you're really concerned you can take a backup in Control Center beforehand which will contain all the images and can be restored if necessary. ------------------------------ Ryan Matte ------------------------------

If you're running Resource Manager 6 then it's guaranteed that the old 5.x images are no longer being referenced.  Docker images are stored as layers with deltas between them to conserve space.  Generally only the most recent version of an image is going ...

Hi Matt, When you add a new device Zenoss sends invalidation messages through to the hub which then propagates that info to the monitoring daemons to tell them about the new device and to get them to start monitoring it.  Sometimes those invalidations ...

It sounds like your hbase data may possibly be broken/corrupted.  You should attempt a repair and see if that helps... serviced service attach hmaster su - hbase cd /opt/hbase/bin ./hbase hbck -ignorePreCheckPermission –fixAssignments ./hbase hbck ...

To my knowledge there aren't really any simple ways to do what you're describing.  The methods you described are the ones that I typically see used to perform that type of monitoring.  Basing it on the collected uptime value is probably your best bet ...

You're not going to be able to do what you're asking because Zenoss stores it's data in a database called zodb, and then we use something called relstorage to store that zodb inside of MySQL (to improve performance).  It stores that data as binary blobs ...

Seeing that type of error generally indicates that you are running a new version of Resource Manager with an old version of Control Center.  The API between Control Center and Resource Manager which allows them to communicate with each other got updated ...

The reason you were running in to the error you were seeing is because an event without a component was hitting your transform and you weren't checking for the existence of component before proceeding with the rest of your code.  A simple "if component:" ...

blockingtimeout is for a specific use case where a plugin isn't doing what it's supposed to be and ends up blocking for a long period of time which halts all data collection for zenpython.  The blockingtimeout specifies how long a plugin should remain ...

The best way I can think of to accomplish what you're describing would be to setup a datapoint against the value that you're wanting to monitor but make it a derive instead of a gauge, which will graph the change between the current cycle and the previous ...

Hey, Just use the backup feature in Control Center after you've completed the configuration that you're wanting to do.  You can then just restore that backup to any master Control Center server and it'll load all the same config in.  You'd need to do ...

Just to add, if your issue is related to what I described in my last note then clearing any Critical events from /Status by hand (closing them) will get the devices marked as Up again until any further events like that come in.  The transform I mentioned ...