2. RE: Monitoring templates, commands in Zenoss 6

For commands, can you define them as a user command? Rather than run them as a shell script on the host, can you run them within Zenoss itself by defining them in Advanced -> Commands -> Define Commands?

3. RE: Monitoring templates, commands in Zenoss 6

I have Zenoss commands. They invoke a shell script on the host. Something like:sh issue_command.sh ${device/id} <command_name>

This shell script in turn inserts a record in a mysql db (this table holds which devices have an upcoming command to run). The actual running of the command is completely outside Zenoss and is very custom.

In any case, this is custom business logic and is not going to change.

For commands, can you define them as a user command? Rather than run them as a shell script on the host, can you run them within Zenoss itself by defining them in Advanced -> Commands -> Define Commands?

4. RE: Monitoring templates, commands in Zenoss 6

So, I think you are saying that your extra mysql database is on your "local" Zenoss 4 server, along with the commands that communicate with the target devices?

It's clunky but can you create some ssh scripts in the zencommand container that uses ssh to drive the existing scripts on the base Zenoss system? That way, at least you leave your existing mechanism unchanged on the base box. Importing stuff into a container, updating it, protecting it from Zenoss 6 updates, etc may be a big pain. Effectively, you just treat the base box as a "remote" target.

Do you know that anything in a container under /var/zenoss is "DFS" storage and appears on the base box under /opt/serviced/var/volumes/<tenant-id>/var-zenpacks - I use this to hold stuff that I need accessible by all containers and the base.

So, I think you are saying that your extra mysql database is on your "local" Zenoss 4 server, along with the commands that communicate with the target devices?

It's clunky but can you create some ssh scripts in the zencommand container that uses ssh to drive the existing scripts on the base Zenoss system? That way, at least you leave your existing mechanism unchanged on the base box. Importing stuff into a container, updating it, protecting it from Zenoss 6 updates, etc may be a big pain. Effectively, you just treat the base box as a "remote" target.

Do you know that anything in a container under /var/zenoss is "DFS" storage and appears on the base box under /opt/serviced/var/volumes/<tenant-id>/var-zenpacks - I use this to hold stuff that I need accessible by all containers and the base.

6. RE: Monitoring templates, commands in Zenoss 6

Uou might look at the concept of cProperties (custom properties). They work just like zProperties but you can create them through the GUI - you don't need to write a ZenPack. You create them at a device class level from DETAILS -> Custom Schema and can set a default value at the class level but you can override for an individual device. So you might create a cDomain cProperty...

So, I think you are saying that your extra mysql database is on your "local" Zenoss 4 server, along with the commands that communicate with the target devices?

It's clunky but can you create some ssh scripts in the zencommand container that uses ssh to drive the existing scripts on the base Zenoss system? That way, at least you leave your existing mechanism unchanged on the base box. Importing stuff into a container, updating it, protecting it from Zenoss 6 updates, etc may be a big pain. Effectively, you just treat the base box as a "remote" target.

Do you know that anything in a container under /var/zenoss is "DFS" storage and appears on the base box under /opt/serviced/var/volumes/<tenant-id>/var-zenpacks - I use this to hold stuff that I need accessible by all containers and the base.