This means out monitoring template should be named TemperatureSensor. You can also define monitoring templates in zenpack. See Monitoring Templates for more information. These thresholds are all setup on the test1. The next trick is to ensure that the events generated by the thresholds not the command template itself, but the threshold are different.
The trick here is that the auto-clear fingerprint the way Zenoss determines whether one event clears another is:.
Either way, eventClass and eventKey are significant note that prior to Zenoss 4 eventKey was not part of the auto-clear fingerprint, neither was component UUID. This way, only one threshold is true at any one time. Different event Classes are necessary otherwise any threshold will clear all others with a matching device, component and eventKey. I have a very small test script to use in a command template, test1.
Enterprise Reports. Graph Reports. Multi-Graph Reports. User access. Client access. 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. 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:.
0コメント