Performance template zenoss

CPU Utilization Report. Alias Formula Evaluation. Reverse Polish Notation. Using Python in Alias Formulas. Adding a Data Point Alias. Navigate to a data source on a template. Select a data point.

From the page menu, select Add DataPoint Alias. Add Data Point Alias. Note If the data point returns values in the desired units, then leave the value for formula blank.

Data Point Alias Dialog. Zenoss Reports That Use Aliases. The Add a New Threshold dialog appears. Enter an ID for the new threshold, and then click OK. Add a Threshold. Data Points - Select one or more data points to which this threshold will apply. Enabled - Select True to enable the threshold, or False to disable it. Performance Graphs. Navigate to a performance template whose data you want represented in a graph.

From the Graph Definitions table menu, select Add Graph. The Add a New Graph dialog appears. Enter the name of the graph, and then click OK. The Graph Definition page appears. Enter information or select values to define the graph: Name - Optionally edit the name of the graph you entered in the Add a New Graph dialog. Height - Enter the height of the graph, in pixels.

Width - Enter the width of the graph, in pixels. Units - Enter a label for the graph's vertical axis. Graph Definition.

Graph Points. Select values for the graph point, and then click OK. The new graph point appears on the Graph Definition page. Note Thresholds are always drawn before other graph points.

Re-sequencing Graph Points. DataPoint Graph Points. Adding DataPoint Graph Points. The GraphPoint dialog appears. Click OK to add the graph point.

Editing DataPoint Graph Points. Line Width - Enter the pixel width of the line. Editing Threshold Graph Points. Threshold Graph Points. Select Add Threshold from the Graph Points table menu.

The Add GraphPoint dialog. Custom Graph Points. Custom Graph Definition. Graph Commands. Changing Graph Display Order. Navigate to a device. Click Create Local Copy. Click the name of the template. In the Graphs area of the page, use the Seq options to order the graphs. Prev Up Next 1. Availability Monitoring Home 3. Monitoring Using ZenCommand. Having page size and load time graphs can be helpful ways to quickly see whether your site is responding slowly for users over time, when, etc.

Aside from just knowing if your site is up or down, it is also helpful to know when it is performing outside of ranges you find acceptable. For example, if your homepage takes around 2 seconds to load, you may wish to set a threshold of 4 seconds. Then you could get alerts when your site is taking abnormally long to load and go find out why. Pertaining to webserver vs website monitoring Also, how to setup multiple website monitors that resolve to the same IP. This will be covered in a future article.

Basically, you add multiple httpmonitor datasources in a single local template. Archived community. Search for:. Welcome, Guest Login Register Username:? Remember Me. Up to Documents in Configuration. 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. A monitoring template must be created to perform periodic collection of data, associate thresholds with that data, or define how that data should be graphed. Two important concepts in understanding how monitoring templates are used are location and binding.

Location is the device class in which a monitoring template is contained. Binding is the device class, device or component to which a monitoring template is bound.

Zenoss will attempt to find a monitoring template named WidgeterHealth in the following places in the following order. The first template that matches by name will be used for the device.

No template will be bound if no matching template is found in any of these locations. 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.