Opsview
Send monitoring events from OpsView to BigPanda.
| Supported Versions | Type | Authentication Type |
|---|---|---|
| Nagios-compatible versions (Version 5 and older). - For previous versions, an Action Script version of the integration is available. | Agent | Org Bearer Token |
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.
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
| Tag | Description | Attributes |
|---|---|---|
host | Name of the monitored host. | Primary Property. |
check | Name of the service being checked on the host. | Secondary Property. |
hostgroups | List of groups where the host is configured as a member. To enable this tag, provide access to the objects.cache file then contact BigPanda support and request a product change. | |
servicegroups | List of groups where the service is configured as a member. To enable this tag, provide access to the objects.cache file then contact BigPanda support and request a product change. | |
acknowledge | Indicator of whether the alert has been acknowledged in Nagios. | |
flapping | Indicator of whether the monitor is flapping. | |
maintenance | Indicator of whether the monitor is scheduled for downtime. |
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.
- 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.
- Remove the integration from the agent configuration file by running the following command.
sudo bigpanda-config -r <INTEGRATION APP KEY>
- 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 from BigPanda
- In BigPanda, navigate to the Integrations tab and select the desired integration from the list.
- In the integration details on the right, click Delete Integration. A support message opens, pre-populated with a request to delete the selected integration.
- Press Enter to send the request.
- The BigPanda support team will remove the integration from the UI.
️
This procedure does not remove any data from BigPanda or the integrated system. As needed, remove data from each system before deleting the integration.
Updated about 1 month ago