👍

Opsview v6+ and the Open Integration Manager

The Open Integration Manager is available for use with Opsview v6+. For more information, see the Open Integration Manager documentation. To use OIM with Opsview v6+, v10.2 of the BigPanda Agent must be installed.

Customers using Opsview v6+ should select the Opsview v6+ integration tile in BigPanda when installing the integration. See the Opsview v6+ instructions for more information.

The BigPanda agent parses these files to correlate all the alerts that Opsview generates:

• The log file—enables real-time synchronization of Opsview alerts to BigPanda.
• The status.dat file—enables a full sync of all open alerts to ensure all current data is available in BigPanda within minutes of first installing the integration. Also, enriches each alert with state information that normally is not available in the log file.
• The objects.cache file—keeps BigPanda in sync with the objects in your infrastructure. For example, if you remove a host that has open alerts, BigPanda closes the alerts automatically. Also, allows BigPanda to enrich alerts with host-groups and service-groups as well as custom information. For custom enrichments, contact BigPanda Support.

❗

️Payload Size

Alert payloads must be 6MB or smaller. Larger payloads will fail to process with BigPanda. We recommend reviewing your configurations to ensure that only actionable, useful information is being sent to BigPanda.

Key Features

• Integrates BigPanda with Opsview by using the Opsview log files.
• Ensures that all relevant alerts are correlated, regardless of the notification profiles configured in Opsview.
• Provides complete visibility into the infrastructure that Opsview is monitoring.

Schedule Downtime For Maintenance

You can schedule downtime in Opsview for a maintenance window.

After receiving the start event for scheduled downtime, BigPanda handles subsequent alerts from objects in maintenance as follows:

• Does not show new incidents in the incident feed.
• Correlates alerts to existing incidents, if applicable, and marks the alerts in Maintenance status (indicated in grey).
• Does not send AutoShare notifications for incidents where all associated alerts are in maintenance.

After receiving the end event for the scheduled downtime, BigPanda resumes normal processing for subsequent alerts from the objects.

📘

Which Alerts are in Maintenance

BigPanda handles scheduled downtime according to the options you select when configuring the downtime. For example, if you configure a host to be in maintenance but not the services on that host, then alerts for those services do not change to maintenance status in BigPanda.

Install the Integration

Administrators can install the integration by following the on-screen instructions in BigPanda.

Opsview Data Model

BigPanda normalizes alert data from Opsview 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 deduplication and correlation processes.

Standard Tags

Opsview v6+

The Opsview v6 update introduced changes to the way the platform works with Nagios variables. BigPanda has updated the installation process to align with Opsview v6+.

The Opsview notification script ships with the BigPanda Agent. To get started, install the BigPanda Agent.

Install the Integration

Administrators can install the integration by following the on-screen instructions in BigPanda. Select the Opsview v6+ integration tile.

Usage

The notify_by_bigpanda notification script works in conjunction with the bigpanda-agent to send event to BigPanda. The following is the output of the script's usage:

usage: notify_by_bigpanda [-h] [-d] [-v] [-n NAGIOS_VARS [NAGIOS_VARS ...]] [-t] [-l LOG] [-q QUEUE]

Opsview notifications script for bigpanda.io.

options:
-h, --help            show this help message and exit
-d, --debug           prints stderr to log file (default: False)
-v, --verbose         all logging modules print to log file (default: False)
-n NAGIOS_VARS [NAGIOS_VARS ...], --nagios-vars NAGIOS_VARS [NAGIOS_VARS ...]
                        List of Nagios ENV Variables to add to the payload in the format 'var=nagios_env_var' (default: None)
-t, --send-test       Sends a test payload to BigPanda (default: False)
-l LOG, --log LOG     Alternate log file location (default: /var/log/bigpanda/Opsview.log)
-q QUEUE, --queue QUEUE
                        BigPanda alerts queue (default: /var/lib/bigpanda/queue)

Deactivate the Integration in BigPanda

If you want to stop sending data to BigPanda but don’t want to delete your integration, you can temporarily deactivate it.

To deactivate an integration:

1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list. This will open integration details on the right side of the window.
2. At the top of the integration details, click the Active/Inactive toggle next to the application name to change the status of the integration.

🚧

Alert Resolution for Inactive Integrations

Any active alerts belonging to an inactive integration must be manually resolved or they will stay in the system until the auto-resolve window is reached.

Uninstall Opsview

Deleting an integration requires changes to both the integrated system and BigPanda. You must uninstall the integration on the integrated system and then delete the integration from BigPanda.

🚧

When replacing an existing integration with a new tool or system, we recommend configuring the new integration first to ensure no data is lost.

Before You Start

• 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 Opsview integration or supports multiple BigPanda integrations.

• Determine the OS on the server.

Uninstall Agent

If the agent supports only the Opsview 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 Opsview integration from the agent.

Remove the Opsview 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

❗️

Replace the app key with the corresponding value in BigPanda.

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

sudo bigpanda-config -r <INTEGRATION APP KEY>

3. 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

Delete the Integration in BigPanda

1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list.
2. In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will then be removed immediately.

👍

Alert Resolution for Deleted Integrations

All active alerts from the integration will be resolved after deletion.

❗

️Data Removal

This procedure does not remove any data from the integrated system.