> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/grafana/grafana-integration.md).
# Grafana Integration
Create alerts in ilert from Grafana alerts.
{% hint style="info" %}
Are you using Grafana v9.x or higher? Please refer our [Grafana Integration (v 9.x)](/integrations/inbound-integrations/grafana/grafana-integration-v-9.x.md) guide.
{% endhint %}
## In ilert: Create a Grafana alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Grafana**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In Grafana: Add ilert Webhook as Alerting Channel
1. In the sidebar, go to **Alerting** → **Notification channels** and click on the **New channel** button.
2. Select **Type** webhook and in the field **URL** insert the webhookurl generated in ilert. Set the HTTP Method to **POST**.
3. Optionally test the integration by cliking on the **Send Test** button. Click on **Save**
4. Check if an alert has been created in ilert.
5. After the Notification Channel has been created in Grafana, add it to one or more **graph alerts**.
6. Switch to any dashboard of your Grafana installation and edit a graph.
7. In the edit view, open the **Alert** section via the left sidemenu and click on the green **Create Alert** button.
8. Fill in the desired **condition** and select the relevant ilert **Notification channel** under **Notifications → Send to** you created in steps 2 and 3. Do not forget to save the dashboard afterwards (in the upper right Navibar).
9. The integration is now set up!
## FAQ
**Will alerts in ilert be resolved automatically?**
Yes, as soon as an alert with "ok" has been resolved in Grafana, the associated alert in ilert will be resolved automatically.
**What happens when an alert is paused in Grafana, is the associated alert also accepted in ilert?**
Yes.
**Can I link Grafana to multiple alert sources in ilert?**
Yes, create a **Notification Channel** per alert source in Grafana.
---
# 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://docs.ilert.com/integrations/inbound-integrations/grafana/grafana-integration.md?ask=&goal=
```
`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.
