> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/pt-br/development-cycle/dashboards/alerts/how-to-edit-an-alert.md).

# Como editar um alerta

Aprenda como editar um alerta.

Nesta página, você pode editar as configurações globais dos seus alertas. Edite as informações necessárias e revise-as cuidadosamente antes de salvar. Dessa forma, você garante a compatibilidade com os requisitos necessários.

Siga estas etapas para editar um alerta:

1. Na página inicial da Plataforma, clique em **Monitor**
2. No menu superior da página, clique em **Configuração de alertas**.
   * Você também pode clicar em **Configurações** e clicar em **Alertas** no menu à esquerda.
3. Na tabela, localize o alerta que deseja editar.
4. Clique no **ícone de lápis**, localizado na última coluna, para editar o alerta.
5. Edite as informações necessárias.
6. Clique em **Salvar**.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkqXsI0cPgzRnwxNhnH%2Fuploads%2FSLE8UKAUkgaSEGjFn1qE%2FEditar_Alertas_PT%20-%20Made%20with%20Clipchamp.mp4?alt=media&token=eb219c34-9183-4ed9-87cd-fef753485f33>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/developer-guide/pt-br/development-cycle/dashboards/alerts/how-to-edit-an-alert.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.