Zenoss Export Monitoring Templates

Posted By admin On 26/04/18
Zenoss Export Monitoring Templates Average ratng: 4,6/5 1499reviews

Applies To Zenoss 4.x Summary Custom properties allow you to define arbitrary properties for devices or device classes that you can use for a variety of purposes. A custom property is created with a default value chosen by the administrator. It will only be used once it is referred to by some other part of Zenoss subsequent to its creation.

Online Export Monitoring System

Build the Monitoring Template; Test Monitoring Template; Export. That Zenoss was monitoring the uptime. Of the Device monitoring template in the. Zenoss monitoring templates (referred to as templates) are collections of data points, often with corresponding thresholds (data point limits) and graphs, that are.

Important: The default (or manually entered) values for the custom properties inherit down the device class tree, enabling administrators to make a change to a subset of device classes (and thereby to devices within those device classes). The best way to illustrate custom properties is to explore a particular use case. Consider a scenario in which a Zenoss administrator needs to use a different threshold for CPU idle percentage for the /Server/Linux class and for every subclass of /Server/Linux. One option would be to copy the /Server/Linux device template to each individual class and to modify the template accordingly; however, that method would be labor intensive and difficult to audit for accuracy. An alternative approach would be to create a custom property for the idle percentage threshold by editing the value of that property for the /Server/Linux class. Since the values of custom properties inherit down the device class tree, the new threshold would automatically be applied to all sub-classes of /Server/Linux. Procedure Note: Many of the steps outlined in this Procedure section apply to this specific use case only.

This article explains those steps required to create any custom property and those that are specific to this example. The steps outlined apply to Zenoss 3.x and above. Although the methods for completing this procedure on versions of Zenoss prior to 3.x will differ, the underlying concepts remain the same.

• Signed in to Zenoss. • Select the Infrastructure tab from the top navigation bar. Make sure that Devices is highlighted in the device class tree on the left. Notice that on the right side of the Devices button a forward slash (/) displays. The slash indicates that you are at the root level of the device class tree.

Important: The ability to create a new custom property is only available at this root level of the device class tree. The step outlined above applies to the creation of any custom property. • Click the Details arrow. This step also applies to the creation of any custom property. Important: The list of Custom Properties is titled Custom Schema when you are editing the properties of a device class, but is titled Custom Properties when you are editing the properties of a particular device.

Although the title differs, content of the page that loads (a list of custom properties) is the same. • Select Custom Schema from the left navigation bar. A two-part page appears.

Download Tv Program Radio Televizije Krusevac Software. In the upper half, a list of existing custom properties is shown. In the lower half, a form entitled Add Property displays. This step applies to the creation of any custom property. • To create your new custom property, enter cPercentFree in the label and name fields.

The label and name values are arbitrary; the cPercentFree label is specific to this example. Important: When entering the name value, ensure the first letter of the name is lowercase c and that the second letter is capitalized. • From the Type drop down menu, select int. This value is specific to this example. • In the Default field enter 2 for the value. This value is specific to this example; in the default template for /Server/Linux, the threshold for CPU idle is 2%. By choosing this default value, you can later refer to this custom property and keep the default value constant except for those specific classes or devices where you wish to change it.