---

Subject:	!ZenPackSpec is an artifact
Author:	Chet Luther
Posted:	2015-08-04 14:48

!ZenPackSpec is an artifact of the YAML export process. It's not needed, and safe to remove from your zenpack.yaml.

You add monitoring templates to /Devices the same way you'd add them to your own custom device classes. The default value for a device classes' "remove" property is False, which means that using the following syntax your monitoring template will be create in /Devices, but /Devices won't be removed when you remove the ZenPack.

zenpack: ZenPacks.example.Example

device_classes:
/Devices:
templates:
MyTemplate:
...

The indentation above will be broken, but hopefully you get the idea.

---

Subject:	I do, thanks Chet.
Author:	Jay Stanley
Posted:	2015-08-04 15:44

I do, thanks Chet.

Is there a list of ZP's that use ZPL That we could use for reference

Right now I am using OpenStackInfrastructure, I was using Ceph, but it went away today

How should I build a relationship to Device
class_relationships:
- zenpacklib.Device 1:MC new_component

Is there any plans to add event classes, transforms, mappings to ZPL any time soon

---

Subject:	Seems like:
Author:	Jay Stanley
Posted:	2015-08-04 16:13

Seems like:

class_relationships:
- Products.ZenModel.Device.Device 1:MC new_component

would be the correct way

---

Subject:	Some ZenPacks that use
Author:	Jay Stanley
Posted:	2015-08-06 07:33

Some ZenPacks that use zenpacklib:
https://github.com/vholer/ZenPacks.CERIT_SC.LinuxMonitorAdvanced/tree/ma...
https://github.com/zenoss/ZenPacks.zenoss.OpenStackInfrastructure/
Ent Customers can look at APIC and HP.Proliant

Can also search for them on github. Looking for zenpacklib, zenpacklib.py or zenpack.yaml
https://github.com/searchutf8=%E2%9C%93&q=zenpacklib&type=Code&ref=sear...