> For the complete documentation index, see [llms.txt](https://cueobserve.cuebook.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cueobserve.cuebook.ai/settings.md).

# Settings

## Slack

CueObserve can send two types of Slack alerts:

1. Anomaly alerts are sent when an anomaly is detected
2. App Monitoring alerts are sent when an anomaly detection job fails

To get these alerts, enter your Slack Bot User OAuth Access Token. To create a Slack Bot User OAuth Access Token, follow the steps outlined in [Slack documentation](https://api.slack.com/messaging/webhooks).

1. Create a slack app.
2. Once you create the app, you will be redirected to your app’s `Basic Information` screen. In `Add features and functionality`, click on `Bots`.
3. On the next screen, click on `add a scope` and you will be redirected to OAuth & Permissions page.
4. On the next screen, go to Scopes section, click on `Add on OAuth Scope` and  add `files:write` and `chat:write` permissions, now click on `Install to Workspace` to create the `Bot User OAuth Token` .
5. Copy `Bot User OAuth Token` and paste it in the CueObserve Settings screen.

Next, create two channels in Slack. Add the app to these two channels. 

1. To find your Slack channel's ID, right-click the channel in Slack and then click on `Open channel details` . You'll find the channel ID at the bottom. Copy and paste it in the CueObserve Settings screen.
2. Click on the `Save` button.

## Email

1. Make sure you have enabled email alert while installation.
2. Add email Id to `Send Email To` input field, If you have to add more than one email Id, make it comma separated in input field as shown below.

![](/files/-Mi1PSSqEj7rtPlG0oWP)

## Webhook URL

CueObserve supports Webhook URL for receiving alert messages. There are two type of alerts :

1. Anomaly alerts, which are sent when an anomaly is detected in data. The response will have json data (as below) and *base64* encoded image.

   ```
   {
     "subject": subject,
     "message": message,
     "details": details,
     "AnomalyDefinitionId": anomalyDefId,
     "AnomalyId": anomalyId,
   }
   ```
2. App Monitoring alerts, which are sent when an anomaly detection job fails. The response will have json data as formatted:

   ```
   {
     "subject": subject,
     "message": message
   }
   ```

To subscribe to these alerts, configure your Webhook URL in CueObserve *settings screen*.


---

# 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://cueobserve.cuebook.ai/settings.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.