# Alerting Integrations

## Pre-requisites

The alerting integration needs to be properly configured. The default installation provides the required ConfigMaps, and in case of errors please refer to the [production installation guide](/seldon-enterprise-platform/production-environment/observability-alerting/alerting.md).

## Firing a test alert

The Seldon Enterprise Platform alerting integration is built with a flexible architecture and allows users to monitor and define [SLAs, SLOs, and SLIs](https://www.atlassian.com/incident-management/kpis/sla-vs-slo-vs-sli) for their models and the operation of the platform. Prometheus metrics exposed by Enterprise Platform and the models form the basis of SLIs and defined alerts form the SLOs.

In this example, we'll demonstrate how to push a test alert manually through the API to provide intuition on what would happen if SLO is breached.

1. **Using the API to fire a test alert**

   You can use the API to fire a test alert. If you have configured Alertmanager correctly this will then show up in the Enterprise Platform frontend.

   You can make an authorized curl request as below, getting a token using the [API auth guide](/seldon-enterprise-platform/product-tour/api.md).

   `curl http://<ENTERPRISE_PLATFORM_IP>/seldon-deploy/api/v1alpha1/alerting/test -X POST -H "Authorization: Bearer $TOKEN"`
2. **Alert shows in notifications drawer**

   The test alert will send a notification to the Enterprise Platform frontend within seconds, along with informing any other receivers (Pagerduty/Opsgenie/Slack/Email) that you may have configured.

   ![Unresolved notification](/files/U59svAEcBBacHEKUTRXX)
3. **Alert shows on alerts page**

   Click on `View All Firing Alerts` in the alerts tray and, you will see the test alert along with any other currently firing alerts. This allows you to diagnose and fix any issues you may have missed when away from the Enterprise Platform UI.

   ![Alerts page](/files/UCQKw4L6jxugvSzr6jBP)
4. **Alert removed from alerts page**

   The test alert will resolve after 1 minute and will no longer be visible on the alerts page once refreshed.
5. **Resolution notification**

   Once the alert is resolved, after some time the frontend will be notified about the resolution. If you use the default configuration this will be after 5 minutes, but otherwise depends on Alertmanager's `resolve_timeout`.

   This test alert only relies on Alertmanager, but real alerts will send resolution notifications as soon as Prometheus reports the alert as resolved.

   ![Resolved notification](/files/4SHyCCxrDxpyna1fxlC5)


---

# Agent Instructions: 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:

```
GET https://docs.seldon.ai/seldon-enterprise-platform/demos/general/alerting-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
