Opsview alert integration

Opsview supports custom notification methods: when it notifies, it runs the script you installed and hands the alert content over in environment variables that start with NAGIOS_ (NAGIOS_HOSTNAME, NAGIOS_SERVICEDESC, NAGIOS_NOTIFICATIONTYPE and so on). A script pushes that content to Flashduty in the Standard Alert Event format: problem notifications trigger alerts and recovery notifications close them.

Configure in Opsview

Create the notification script on the Orchestrator

Where: Opsview Orchestrator server › notify_by_flashduty

Item	Value
File	Create `notify_by_flashduty` and make it executable (`chmod +x`)
First argument (required)	`{integration_url}`; the push URL is passed as the script’s first argument instead of being written into the script
Dependency	The script uses `curl`; if the notification method runs on a Collector, that Collector also needs `curl` and access to `api.flashcat.cloud`

#!/bin/sh
# Opsview custom notification method: forward host/service notifications to a
# Flashduty Standard Alert Event integration. The push URL is the first argument.
URL="$1"
[ -n "$URL" ] || exit 1

case "$NAGIOS_NOTIFICATIONTYPE" in
  PROBLEM|RECOVERY) ;;
  *) exit 0 ;;   # ignore acknowledgements, flapping and downtime notifications
esac

if [ -n "$NAGIOS_SERVICEDESC" ]; then
  KEY="opsview:$NAGIOS_HOSTNAME:$NAGIOS_SERVICEDESC"
  STATE="$NAGIOS_SERVICESTATE"
  OUTPUT="$NAGIOS_SERVICEOUTPUT"
  CHECK="$NAGIOS_SERVICEDESC"
  TITLE="$NAGIOS_HOSTNAME - $NAGIOS_SERVICEDESC - $STATE"
else
  KEY="opsview:$NAGIOS_HOSTNAME"
  STATE="$NAGIOS_HOSTSTATE"
  OUTPUT="$NAGIOS_HOSTOUTPUT"
  CHECK="host"
  TITLE="$NAGIOS_HOSTNAME - $STATE"
fi

if [ "$NAGIOS_NOTIFICATIONTYPE" = "RECOVERY" ]; then
  STATUS=Ok
else
  case "$STATE" in
    CRITICAL|DOWN|UNREACHABLE) STATUS=Critical ;;
    WARNING)                   STATUS=Warning ;;
    OK|UP)                     STATUS=Ok ;;
    *)                         STATUS=Info ;;
  esac
fi

esc() { printf '%s' "$1" | tr '\n\r\t' '   ' | sed 's/\\/\\\\/g; s/"/\\"/g'; }

JSON=$(printf '{"title_rule":"%s","event_status":"%s","alert_key":"%s","description":"%s","labels":{"resource":"%s","check":"%s","host_address":"%s","host_alias":"%s","opsview_keywords":"%s"}}' \
  "$(esc "$TITLE")" "$STATUS" "$(esc "$KEY")" "$(esc "$OUTPUT")" "$(esc "$NAGIOS_HOSTNAME")" "$(esc "$CHECK")" \
  "$(esc "$NAGIOS_HOSTADDRESS")" "$(esc "$NAGIOS_HOSTALIAS")" "$(esc "$OPSVIEW_KEYWORDS")")

curl -fsS -m 10 -X POST -H 'Content-Type: application/json' -d "$JSON" "$URL" >/dev/null

Every environment variable the script reads is in the notification variable list of the Opsview documentation. The script handles them as follows:

Environment variable	Use
`NAGIOS_NOTIFICATIONTYPE`	Only `PROBLEM` and `RECOVERY` are handled; types such as `ACKNOWLEDGEMENT` and `FLAPPINGSTART` are ignored
`NAGIOS_SERVICEDESC`	Non-empty means a service alert, otherwise it is a host alert
`NAGIOS_HOSTNAME`, `NAGIOS_SERVICEDESC`	Alert Key: `opsview:<host name>:<service name>` for a service, `opsview:<host name>` for a host; the title is `<host name> - <service name> - <state>` or `<host name> - <state>`
`NAGIOS_SERVICESTATE`, `NAGIOS_HOSTSTATE`	Severity: `CRITICAL`, `DOWN`, `UNREACHABLE` → Critical; `WARNING` → Warning; `OK`, `UP` → recovery; anything else (`UNKNOWN`) → Info. A `RECOVERY` notification is always treated as a recovery
`NAGIOS_SERVICEOUTPUT`, `NAGIOS_HOSTOUTPUT`	Alert description
`NAGIOS_HOSTADDRESS`, `NAGIOS_HOSTALIAS`, `OPSVIEW_KEYWORDS`	Labels `host_address`, `host_alias`, `opsview_keywords`; `NAGIOS_HOSTNAME` is written to the label `resource`

Import the script on the Orchestrator and apply changes

Where: Terminal of the Opsview Orchestrator server; Opsview › Configuration › Apply ChangesOn the Orchestrator, import the script as the opsview user:

sudo -u opsview /opt/opsview/orchestrator/bin/orchestratorimportscripts notifications /path/to/notify_by_flashduty

Then go to Configuration › Apply Changes to finish installing the script.

Add the notification method in Opsview

Where: Opsview › Configuration › Notification Methods › Add New

Field	Value
Name (required)	`Flashduty`
Enable	Tick
Run On (required)	Choose the Orchestrator or the Collector
Command (required)	`notify_by_flashduty {integration_url}` (scripts are read from `/opt/opsview/monitoringscripts/notifications` by default, and arguments follow the script name)

After saving, go to Configuration › Apply Changes again to activate the new notification method.

Add the method to a user's notification profile

Where: Opsview › Configuration › Users and Roles › Users › edit the user › Notification Profiles › Add NewOpsview notifications are driven by each user’s Notification Profile, so every user who should receive Flashduty notifications must select this method (you can also open My Profile from your username at the top right):

Field	Value
Alert me by	`Flashduty`
During	The active time period
Host and Services	Select the host groups and service checks to notify about and tick the states to notify on; include both the problem states and the recovery states, otherwise Flashduty receives no recovery notification

Click Update, then Submit Changes, and finally go to Configuration › Apply Changes to make it live.You can also create a shared profile under Shared Notification Profiles and assign it to several users.

Test the script with test_notifications and confirm a real alert

Where: Terminal of the Opsview Orchestrator serverOpsview provides a test_notifications tool that simulates the environment variables Nagios Core sets at notification time; use it to test the script:

# Host problem
sudo -u opsview /opt/opsview/coreutils/utils/test_notifications hostproblem /path/to/notify_by_flashduty '{integration_url}'
# Service problem
sudo -u opsview /opt/opsview/coreutils/utils/test_notifications serviceproblem /path/to/notify_by_flashduty '{integration_url}'

The test sends a real event to Flashduty; once the alert appears, close it manually in Flashduty. The integration shows Latest event time, which means the script and push URL are correct. The test bypasses the notification method and the Notification Profile, so it does not prove they work: make a monitored object in Opsview actually leave the OK state and then recover, and confirm both the problem and recovery notifications reach Flashduty. If no alert appears, use “Troubleshooting” below to see the environment variables the script actually receives.

If the notification method is set to run on a Collector, test the script on the Collector servers as well.

Recovery and deduplication

A host or service always uses the same Alert Key, so repeated problem notifications (for example from Opsview’s re-notification interval) only update the same alert, and the RECOVERY notification recovers it
When a service goes from WARNING to CRITICAL, the severity is updated on the same alert
Acknowledgement (ACKNOWLEDGEMENT), flapping (FLAPPING*) and downtime (DOWNTIME*) notifications are ignored by the script and produce no event in Flashduty

Troubleshooting

No alert arrives: confirm the Notification Profile selects Flashduty and Apply Changes was run; check in Opsview’s Notifications View whether the notification was sent; test the script on its own with test_notifications
The test works but real alerts are not pushed: in a real notification the script reads the environment variables Opsview passes; add { date; echo "Called with $@"; env; echo; } >> /tmp/env.txt to the top of the script (the debugging method given in the Opsview documentation) to see what it actually receives
The alert does not recover: confirm the Notification Profile ticks the recovery states; Nagios only sends a recovery notification after a problem notification was sent
Flashduty returns a parameter error: confirm the push URL in Command is complete, including integration_key

For more details, see the Opsview documentation Custom Notification Methods and Notification Profiles.

Quick Start

Product Comparison

Channels

Incident Management

Post-Mortem

Status Page

Analytics

Integration Settings

Configuration

Advanced

Integrations

Best Practices

In Flashduty On-call

Use a dedicated integration

Use a shared integration

Configure in Opsview

Recovery and deduplication

Troubleshooting