After deciding on the right location for a monitoring template should then decide where it should be bound. Remember that to cause the template to be used it must be bound. Binding templates using zDeviceTemplates is only applicable for monitoring templates that should be bound to devices. See Classes and Relationships for information on how monitoring templates are bound to components. To add a monitoring template to zenpack.
Then within this device class entry you must add a templates field. It also shows that template being bound to the device class by setting zDeviceTemplates. Many different entry types are shown in the above example. See the references below for more information on each. Python module name to which this template is intended to be bound. For example, a defined Device-replacement template will replace the existing Device template on a device class.
A defined Device-addition template will be applied in addition to the existing Device template on a device class. Datasources also allow other ad-hoc options to be added not referenced in the above list.
This is because datasources are an extensible type in Zenoss, and depending on the value of type , other fields may be valid. The following datasource types are valid on any Zenoss system.
They are the default types that are part of the platform. This list is not exhaustive as datasources types are commonly added by ZenPacks. The Built-in datasource type performs no collection. It assumes associated data will be populated by an external mechanism. ZSD Help. HTTP Monitor. Open Source. Organization: Zenoss, Inc. Name: ZenPacks.
Releases Version 3. Update notes. Zenoss API. Action service. Trigger resources. Data receiver service. User management service. On this page Creating templates Copying templates Renaming templates Template binding Device templates Binding a device template Resetting bindings Component templates Interface templates. Monitoring templates Collection Zone stores performance configuration data in templates. You can define a template anywhere in the device class hierarchy or on an individual device.
Templates are divided among three types: Device Component Interface Creating templates You can create an empty template to customize to your needs. Click the "add a monitoring template" button "plus" icon, lower-left corner.
Click Submit. Copying templates You can create a template by overriding an existing template. To override a template: Navigate to the template you want to copy. From the Action menu, select View and Edit Details. In the Edit Template Details dialog box, enter a new name. Template binding The determination of which templates apply to what objects is called binding.
Device templates Device templates are applied to devices, one to each device. However, there are some extra considerations and steps required to package your configuration in a ZenPack.
Commands in this section should be run on the host as the zenoss user unless otherwise noted. We should also restart at least Zope after installing the ZenPack so that we can work with it in the web interface. To support our new NetBotz environmental sensor device we will want to create a new device class. This will give us full control over how these types of devices are modeled and monitored.
Use the following steps to add a new device class. The new NetBotz device will now be selected. The modeler plugins are what model information about the device. We should see a list something like the following. This allows us to know that regardless of what the user sets their default modeler plugins to in the system that NetBotz appliances will be collected using the set of modeler plugins we configure here.
There are a lot of configuration properties. However, some will be critical to monitoring NetBotz appliances. Find the zSnmpMonitorIgnore property and set its value to true. While the system default is to have SNMP monitoring enabled, a user could easily disable it globally and cause our NetBotz monitoring to stop working. Adding a device class to your ZenPack causes all settings in that device class to be added to the ZenPack. This includes modeler plugin configuration, configuration property values and monitoring templates.
You can add a the device through the web interface, or on the command line using zendisc as follows:.
0コメント