ZenPack:Duration Threshold

From Zenoss Wiki
This is the approved revision of this page, as well as being the most recent.
Jump to: navigation, search


Note: This ZenPack is available in commercial versions of Zenoss. Click here to request more information about this commercial ZenPack. Click here to see all commercial ZenPacks.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.DurationThreshold




Duration Threshold ZenPack

Adds a duration type threshold to Zenoss. Used when a value is only bad when it stays bad for some length of time.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Releases

Version 2.0.2- Download
Released on 2017/03/17
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x, Zenoss Resource Manager 5.1.x, Zenoss Resource Manager 5.x.x

Background

This ZenPack adds the DurationThreshold threshold, which will apply the threshold comparison value against specified datapoints over a specific time range, and send an event when a certain percentage of the values violate the threshold. This can be used to create an event when a condition appears and clears over a particular time range.

Gallery

Features

A new threshold DurationThreshold that allows the following to be specified:

  • Time period of how far back the values should be evaluated.
  • A percentage number that allows for the threshold to be violated a number of times before causing an exception

Note that NaN values are ignored, and so are empty RRD files in Zenoss 4.x.x.

Usage

Follow these steps to monitor the values of a datapoint collected over a period of time:

  1. Navigate to device Configuration Properties
  2. Navigate to the desired Monitoring Template.
  3. In the right-hand pane, click on the + button to add a threshold.
  4. Select the DurationThreshold option from the Type field, type in a name for the threshold and then click on the Add button.
  5. Click on the newly added threshold.
  6. Enter information into the dialog box about the threshold.
    • Datapoints: select the datapoints to which this threshold should apply.
    • Severity: choose the appropriate severity.
    • Enabled: should this threshold be used or not?
    • Minimum Value: create an event if values fall below this value
    • Maximum Value: create an event if values fall above this value
    • Event Class: What event class to which events will be associated.
    • Escalate Count: after this number of threshold events created, increase the severity by one (eg Error -> Critical). The severity does not increase further after the initial escalation.
    • Time period: provide a time period using time operators like month, weeks, day, hours, minutes, seconds, or just the number of seconds. An example: 1 hour 5 minutes 10 seconds
    • Percentage of violations to trigger an event: a number from 0 (any violation triggers an event) to 100 (all values must violate the threshold)
  7. Click on the ``Save`` button to save the changes.

Alternatively Custom Properties can be defined and used for time period and percentage of violations. Consult the Custom Properties section of Administrator Guide for details.

Zenoss 5.0.x

Follow these steps to allow Zenoss 5.0.x to collect metric data points.

  1. Log into the Zenoss master host.
  2. $ sudo serviced service edit zencommand
    • search the word 'Endpoints'. Endpoints is an array of objects. Add the following object to Endpoints:
    {
      "Name": "zproxy",
      "Purpose": "import",
      "Protocol": "tcp",
      "PortNumber": 8080,
      "PortTemplate": "",
      "VirtualAddress": "",
      "Application": "zproxy",
      "ApplicationTemplate": "zproxy",
      "AddressConfig": {
        "Port": 0,
        "Protocol": ""
      },
      "VHosts": null,
      "AddressAssignment": {
        "ID": "",
        "AssignmentType": "",
        "HostID": "",
        "PoolID": "",
        "IPAddr": "",
        "Port": 0,
        "ServiceID": "",
        "EndpointName": ""
      }
    },
    • save the file
  1. sudo serviced service restart zencommand
  2. repeat above steps for zenperfsnmp and zenvsphere.
  3. repeat above steps for all Zenoss collector hosts.

Changes

2.0.2
  • Fix error when using multiple duration thresholds on same datapoint. (ZPS-1133)
  • Support new contextMetric capability in Zenoss 5.2.3. (ZEN-27018)
2.0.1
  • Prevent excessive authorization calls slowing Zenoss UI. (ZPS-548)
  • Evaluate thresholds in real time instead of one cycle delayed.
  • Fix event summaries to no longer refer to "High Queue Latency". (ZPS-671)
  • Support multiple datapoints in the same duration threshold.
2.0.0
  • Allow Custom Properties for time period and violation threshold and their use in duration threshold UI.
  • Re-format event messages.
  • Generate event if neither maximum threshold nor minimum threshold is defined.
  • Zenoss 5.x.x compatibility.

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.DurationThreshold-*.egg
  4. Restart these services:
    $ zenoss restart


Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus