AlertOps and LibreNMS
AlertOps’ alert management system can be integrated with SQL Monitor to receive and respond to all (predefined status mappings) alerts through email, SMS, push notification or phone alerts. AlertOps would ensure that the alert/job status would reach the appropriate team by using proper workflows, escalation policies and schedules. Based on your ruleset, incidents can be automatically opened and closed, depending on what kind of alert LibreNMS reports.
The above scenario and scope for integration is due to the fact that AlertOps has a very flexible and simple API/Webhook configuration feature that can be leveraged with LibreNMS' alert and Transport capabilities.
AlertOps - Inbound Integration
We can define rulesets in AlertOps so that LibreNMS can send out alerts to the AlertOps platform. AlertOps would ensure based on these notifications received, that it would always reach out and assign to the correct person/team by utilizing its escalation policies, schedules, and workflow features.
AlertOps provides Inbound Integrations to integrate with numerous monitoring, chat and ITSM tools. You can configure an inbound integration for LibreNMS.
At a high level this is how the flow looks like, you define an API integration in the AlertOps platform by defining settings like Integration Name, Escalation rules, recipient users/groups. Once an integration is defined, a unique API URL is generated. This acts as webhook or the gateway through which notifications from LibreNMS reach AlertOps and thus an incident/alert is created correspondingly. The API can be defined with various settings like URL mappings, filters, escalations etc. as required. LibreNMS has to be defined with a API Transport
To configure an Inbound Integration in AlertOps to receive alerts from LibreNMS,
Under 'Integrations' select 'Inbound Integrations', select the category 'API' and then select add 'Add API Integration'
There are numerous integration options available in AlertOps, select LibreNMS (else select Custom)
Once you selected the integration, you can then specify basic settings like the integration name, escalation policy, names of the recipients/groups for which the alerts must be assigned to.
Once you click save, the API Integration will be created, and you will be given a unique URL which acts as the access point and needs to be configured at the source (in this case LibreNMS), to send alerts. You can find the integration you just created, and you can give advanced settings and define various configurations for the alerts to be received and processed. For example, you can define when to open and close alerts based on the payload obtained from the API call, filters etc.
Make a note of the API URL, which will be used in LibreNMS, so it calls a HTTP POST request to this URL with the body in JSON format containing the alert specific information. AlertOps automatically creates an alert when the status variable (state) contains '1'. The incident will also be closed automatically when the status '0' is received from LibreNMS.
You can similarly define URL mappings as you want, owing to the flexibility provided by AlertOps’ OpenAPI/Plug-and-Play integrations. You can provide other filters and match with regex expressions as well. You can also test the generated URL with the sample data provided.
Configuration of LibreNMS for the integration,
Transports are located within
LibreNMS/Alert/Transport/and can be configured within the WebUI under Alerts -> Alert Transports.Or you can find the API transport under 'Settings' (settings gear icon) > 'Alert Settings'
Configure the API Method as POST and for API URL, paste the AlertOps Inbound Integration API URL
Under API Body, paste the following custom payload, (Template Syntax can be modified and mapped in AlertOps however you would want)
{
"deviceId":"{{ $device_id }}",
"hostname":"{{ $hostname }}",
"sysDesc":"{{ $sysDescr }}",
"type":"{{ $type }}",
"ip":"{{ $ip }}",
"uptime":"{{ $uptime }}",
"desc":"{{ $description }}",
"notes":"{{ $notes }}",
"alertNotes":"{{ $alert_notes }}",
"titleAlert":"{{ $title }}",
"alertId":"{{ $id }}",
"uniqueId":"{{ $uid }}",
"state":"{{ $state }}",
"severity":"{{ $severity }}",
"rule":"{{ $rule }}",
"ruleName":"{{ $name }}",
"url":"{{ $proc }}",
"timestamp":"{{ $timestamp }}",
"transportName":"{{ $transport_name }}"
}
If the above method of adding the JSON does not work, you can add the following to the Options field
deviceId={{ $device_id }}
hostname={{ $hostname }}
sysDesc={{ $sysDescr }}
type={{ $type }}
ip={{ $ip }}
uptime={{ $uptime }}
desc={{ $description }}
notes={{ $notes }}
alertNotes={{ $alert_notes }}
titleAlert={{ $title }}
alertId={{ $id }}
uniqueId={{ $uid }}
state={{ $state }}
severity={{ $severity }}
rule={{ $rule }}
ruleName={{ $name }}
url={{ $proc }}
timestamp={{ $timestamp }}
transportName={{ $transport_name }}You can leave the other fields as it is (blank)
Save and Test.
Thats it! You have configured an API Transport channel. Any alert will be sent to AlertOps for incident management.
Message logs, alert specific information can be viewed in the “Inbound Log” section in AlertOps Dashboard. Alerts can be viewed in the ‘Alerts’ tab as well.
Alert Triggering Information:
AlertOps will automatically create an incident when a new alert is received from LibreNMS when the state contains "1".
If an alert with status "1" matches an existing Open Alert, AlertOps will recognize the new alert as a duplicate and ignore the alert.
The alert will be recorded in the Inbound Messages table as “Mapped Appended.”
AlertOps will automatically close the same incident when an alert with state contains "0".
References