Zenoss add monitoring template

For these standard interfaces when a Collection Zone cannot locate a template that matches the interface type, then it uses the ethernetCsmacd template. Some vendors provide expanded monitoring capabilities on their interfaces. In some cases, ZenPacks provide custom templates specific to those types that can override this default behavior.

A common example would be the Ethernet Interfaces interface type built to monitor these expanded capabilities for Cisco network interfaces. In this case the template's target class is used to bind the EthernetInterface template. For more information about these expanded interface capabilities, refer to the Cisco Monitor ZenPack page. Skip to content. Zenoss Cloud Documentation Get started. Get started. How-to procedures. Reference pages.

Smart View. Trigger queries. Events beta. Streaming data. StatsD agent. Data Access. Collection Zones. Installing collectors. Managing devices. Process monitoring. Event management. Triggers and notifications. User management. UI reference. Reports reference. Cisco UCS Reports. Enterprise Reports. Graph Reports.

Multi-Graph Reports. User access. Client access. Update notes. Zenoss API. Action service. Trigger resources. 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. Some datasource and datapoint types are provided by a particular ZenPack and only available if that ZenPack is installed. These types often have unique parameters that control their function.

ZenPackLib allows the specification of these parameters, but the degree of documentation for each varies. As a result, designing YAML templates using these requires a bit of investigation. The available properties depend on the datasource or datapoint type being used. Currently, examination of the related source code is a good way to investigate them, but an alternative is given below. CalculatedPerformance ZenPack. Please note that the datasource properties used are not documented below, since they are provided by the CalculatedPerformance ZenPack.

First, we want to determine a list of available parameters, and we can use ZenDMD to display them as follows:. Further experimentation is required to determine proper values for these properties, and creating templates manually using the Zenoss GUI is a good way to do so. Datapoints also allow other ad-hoc options to be added not referenced in the above list. Thresholds also allow other ad-hoc options to be added not referenced in the above list. The following threshold types are valid on any Zenoss system.

This list is not exhaustive as additional threshold types can be added by ZenPacks. The MinMaxThreshold threshold type creates an event if values are below or above specified limits. The ValueChangeThreshold threshold type creates an event if the value is different than last time it was collected. The following graphpoint types are valid on any Zenoss system. This list is not exhaustive as additional graphpoint types can be added by ZenPacks. Cloud Docs. ZSD Help. Monitoring Templates Monitoring templates are containers for monitoring configuration.

Location and Binding Two important concepts in understanding how monitoring templates are used are location and binding. On the widgeter1 device. Must be a valid Zenoss object ID.

Widgeter no string "" empty string is equivalent to Products. Device datasources Datasources to add to the template. See Datasource Types.