> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/observium.md).

# Observium

[Observium](https://www.observium.org/) is a low-maintenance auto-discovering network monitoring platform supporting a wide range of device types, platforms, and operating systems, and focuses on providing a beautiful and powerful yet simple and intuitive interface to the health and status of your network.

Route detailed monitoring alerts from Observium to the right users in Squadcast.

### How to integrate Observium with Squadcast

#### In Squadcast: Using Observium as an Alert Source

1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.

![](/files/ej4AI9zpOyFu5NZJCbwC)

2\. Select **Observium.** Copy the displayed **Webhook URL** to [configure](#in-observium-create-a-squadcast-webhook) it within **Observium**. Finish by clicking **Add Alert Source** -> **Done.**

![](/files/qsDjVbVLd1Dku6uVGjoD)

{% hint style="warning" %}
**Important:**

When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}

#### In Observium: Create a Squadcast Webhook

**(1)** From the first option in the top bar, select **Contacts**

![](/files/IRKTi8a3cQDBanh3gTBM)

**(2)** Select **Add Contact** to add a Webhook

![](/files/VKIOTYxElA49sDMBCVy1)

**(3)** Fill out the details as below:

* (a) **Transport**: Select **Webhook** from the drop-down
* (b) **Description**: Give it a name, such as, *Squadcast Webhook*
* (c) **URL**: Paste the previously copied URL from Squadcast
* (d) Click on **Add Contact**

![](/files/BEMTxZMgHCUT3jxUjFbz)

**(4)** Navigate to the newly created **Contact** and associate the required *Alert Checkers* and *Syslog Rules* that should use this **Contact** to notify you for alerts

![](/files/N37D7MCBgCYW4h0mfI5z)

**(5)** Navigate to your **Alert Checkers** and enable **Send Recovery** option to send *recovery alerts* signals to Squadcast

![](/files/01VlywV7JjWFaaFsFNOU)

That is it, you are now good to go! Whenever an alert is triggered in Observium, an incident will be created automatically in Squadcast. When an alert is resolved in Observium, the corresponding **incident gets auto-resolved in Squadcast** as well.

### FAQ

**Q:** Do Syslog alerts from Observium get auto-resolved in Squadcast?

**A:** No, Observium does not send auto-resolve signals to Squadcast for Syslog alerts. Hence, Squadcast incidents for Syslog alerts should be resolved manually.

*Have any other questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/observium.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.