> 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/solarwinds-observability-saas-swo.md).

# SolarWinds Observability SaaS (SWO)

[SolarWinds Observability SaaS](https://www.solarwinds.com/solarwinds-observability) delivers unified and comprehensive visibility for cloud-native, on-premises, and hybrid custom and commercial applications to help ensure optimal service levels and user satisfaction with key business services.

Route detailed alerts from SolarWinds Observability SaaS to the right users in SolarWinds Incident Response.

### Using SolarWinds Observability SaaS as an Alert Source

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

<figure><img src="/files/27aQ9otDXAFUSX8FKLR8" alt=""><figcaption></figcaption></figure>

Select **SolarWinds** **Observability SaaS.** Copy the displayed **Webhook URL** to configure it within **SolarWinds** **Observability SaaS.** Finish by clicking **Add Alert Source** -> **Done.**

<figure><img src="/files/UaM2e0UgKgVQayXcwUcC" alt=""><figcaption></figcaption></figure>

### Adding SolarWinds Incident Response Webhook in SolarWinds Observability SaaS

### Setup a Notification Service

Navigate to **Settings** in the sidebar, select **Notification Services** and select **SolarWinds Incident Response.**

<figure><img src="/files/TPSSOG4UoPHqlEa4uTkf" alt=""><figcaption></figcaption></figure>

Paste the copied alert source webhook URL from SolarWinds Incident Response under **Destination URL**.

<figure><img src="/files/VPkBIQjQMLcypEuaWHZq" alt=""><figcaption></figcaption></figure>

You can choose to receive a test notification by clicking **Notification Test** and then proceed to create the webhook notification service for SolarWinds Incident Response.

### Setup an Alert

Navigate to **Alerts**, select **Alert Settings** and create a new alert.

You can set up the alert with:

a. Any Severity option - Critical, Warning, Info

<figure><img src="/files/ehonTibaXffaowQuWEGJ" alt=""><figcaption></figcaption></figure>

b. Select Metrics (Entity or Metric Group), Logs or Events (Kubernetes or Database) condition. Please note we do not support Anomaly condition alerts.

<figure><img src="/files/KCfirmKlMPmbSDG9cBs9" alt=""><figcaption></figcaption></figure>

c. Add the previously setup Notification Service so that incidents get triggered in SolarWinds Incident Response for triggered alerts.

Ensure you **enable the toggle for receiving an additional notification when the alert is cleared** in order for this integration to support auto-resolution.

<figure><img src="/files/kEbkDybutTq9SCRfyTB0" alt=""><figcaption></figcaption></figure>

That's it, you are good to go! Your SolarWinds Observability SaaS integration is now complete. Whenever SolarWinds Observability SaaS fires an alert through **Alerts > Notification Services**, an incident will be created in SolarWinds Incident Response for it. Also, when an alert has been **cleared** in SolarWinds Observability SaaS, the corresponding incident gets **auto-resolved** in SolarWinds Incident Response.

{% hint style="info" %}
If you have any feedback for us on this integration, do reach out to our support for assistance.
{% endhint %}

*Have any 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/solarwinds-observability-saas-swo.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.