Zenoss

Zenoss provides performance and availability monitoring across the entire IT infrastructure. Install this integration to correlate noisy events from Zenoss into actionable incidents in BigPanda so you can find and fix problems in your infrastructure quicker and easier.

Supported Versions:
Zenoss Core 4, 5, 6

Type:
Agent

Key Features

  • Keeps you up-to-date on the status of Zenoss events and all relevant event attributes.

  • Correlates Zenoss events into actionable incidents in BigPanda, so you can easily manage the events and the associated devices.

How It Works

  • The agent queries for all new Zenoss events and for changes in event states in real-time via the Zenoss API.

  • To ensure a full sync of all current alerts, the agent also queries for all Zenoss events at regular intervals. The query intervals are configurable. See Customizing Zenoss.

How and When Alerts are Closed

When Zenoss sends a close event for an alert, the alert is automatically closed in BigPanda. However, closing an alert manually in BigPanda does not close the alert in Zenoss.

Installing The Integration

Administrators can install the integration by following the on-screen instructions in BigPanda. For more information, see Installing an Integration.

Zenoss Data Model

BigPanda normalizes alert data from Zenoss into tags. You can use tag values to filter the incident feed and to define filter conditions for Environments. The primary and secondary properties are also used during the correlation process.

Standard Tags

device

Name of the device for which the event occurred.

check

Event key (or event class, if the event key does not exist) and component, if it exists.

For example: "/Status/Heartbeat on zenmodeler"

Secondary Property.

severity

Number representing the severity of the event, mapped to:

'0': 'Clear'
'2': 'Info'
'3': 'Warning'
'4': 'Error'
'5': 'Critical'

summary

Summary of the event.

message

Message body of the event. This value may be the same as the summary.

component

Zenoss daemon reporting the event.

event_class

Event class the event maps to.

event_key

User-defined mapping for the event.

ip_address

IP address of the device.

prod_state

Production state of the device.

systems

Names of the Zenoss system organizers for the device.

device_groups

Names of the Zenoss group organizers for the device.

device_class

Device class.

device_url

URL of the device.

location

Names of the Zenoss location organizers for the device.

monitor

Monitor for the device.

Customizing Zenoss

To ensure a full sync of all current alerts, the BigPanda agent queries for all Zenoss events at regular intervals. You can configure the query interval or disable the full sync by editing the config file for the agent.

Prerequisites

Obtain access to the server where the BigPanda agent is installed.

Configuring the Query Interval

You may want to configure the full sync to reduce the load on your Zenoss server, depending on the average volume of events Zenoss generates.

  1. Open the config file, which is located at /etc/bigpanda/bigpanda.conf.
  2. Locate the settings for the Zenoss full sync, named zenoss/fullsync.
  3. Change the value of the full_sync_interval to your preferred interval between full syncs, in seconds.The default value is 900 (15 minutes).

Disabling the Full Sync

The full sync acts as a backup to the incremental sync to ensure accuracy. Disable this feature only if you need to reduce the load on your Zenoss server.

  1. Open the config file, which is located at /etc/bigpanda/bigpanda.conf.
  2. Locate the settings for the Zenoss full sync, named zenoss/fullsync.
  3. Add the following key and value pair: "enabled": false.

Make sure you add the pair outside of the config property.

"name": "zenoss/fullsync", 
"enabled": false, 
"config": {
  "user": "BigPanda",...
  },

Uninstalling Zenoss

To stop sending Zenoss events to BigPanda, you can uninstall the agent from the server or remove the Zenoss integration from the agent.

Prerequisites

  • Manually resolve any open incidents related to the integration to remove them from your incident feed. Optionally, remove any additional data in BigPanda. For example, modify or remove any Environments or AutoShare rules that reference the integration.

  • Obtain access to the server where the BigPanda agent is installed.

  • Determine if the agent on the server supports only the Zenoss integration or supports multiple BigPanda integrations.

  • Determine the OS on the server.

Uninstalling the Agent

If the agent supports only the Zenoss integration, you can uninstall the agent from the server.

Do not uninstall the BigPanda agent if it is supporting other BigPanda integrations. In this case, remove the Zenoss integration from the agent.

Removing the Zenoss Integration from the Agent

If the agent is supporting multiple integrations, you can remove only the specific integration without disabling the other BigPanda integrations that the agent supports.

  1. Stop the BigPanda agent by running one of the following commands.

    • For RHEL 5 and 7, CentOS 5 and 7, Debian, and Ubuntu:

    sudo service bigpanda stop

    • For RHEL 6 and CentOS 6:

    sudo initctl stop bigpanda

  2. Remove the integration from the agent configuration file by running the following command.

    sudo bigpanda-config -r <INTEGRATION APP KEY>

Replace the app key with the corresponding value in BigPanda.

sudo bigpanda-config -r <INTEGRATION APP KEY>

  1. Start the BigPanda agent by running one of the following commands.

    • For RHEL 5 and 7, CentOS 5 and 7, Debian, and Ubuntu:

    sudo service bigpanda start

    • For RHEL 6 and CentOS 6:

    sudo initctl start bigpanda

Post-Requisites

Delete the integration in BigPanda to remove the Opsview integration from your UI.

Zenoss


Zenoss provides performance and availability monitoring across the entire IT infrastructure. Install this integration to correlate noisy events from Zenoss into actionable incidents in BigPanda so you can find and fix problems in your infrastructure quicker and easier.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.