> 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/influxdb.md).
# InfluxDB Integration
The ilert InfluxDB Integration helps you to easily connect ilert with InfluxDB.
[InfluxDB](https://www.influxdata.com) is an open-source time series database designed to handle high write and query loads, ideal for storing and analyzing time-stamped data such as metrics, events, and real-time analytics. It provides features like built-in time-stamping, data retention policies, and support for various data visualization tools, making it a popular choice for monitoring applications, IoT, and performance metrics.
## In ilert: Create an InfluxDB alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **InfluxDB**, 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 InfluxDB: Add ilert Webhook as Notification Endpoint
1. On the sidebar, click **Alerts**.
2. Click **Notification Endpoints -> Create**.
3. Set HTTP as Destination and enter a Name.
4. Under **HTTP Options**, set **HTTP Method** to POST and enter the previously generated in ilert alert source URL into the **URL**.
5. Click **Create Notification Endpoint** to save.
6. Navigate to **Checks -> Create** (this documentation uses threshold checks).
7. Set a **Name** for your check.
8. Now select a metric you want to create a check for.
9. Click on **2. Configure Check** to set up the threshold.
10. Set up some thresholds.
{% hint style="info" %}
We recommend that you create a threshold for setting the check status to '**OK'** as it is necessary to resolve corresponding alerts in ilert.
{% endhint %}
11. Click on the blue tick in the top right corner to save the check.
12. Now navigate to **Notification Rules -> Create**.
13. Add the following Notification Rules:
{% tabs %}
{% tab title="CRIT" %}
{% endtab %}
{% tab title="WARN" %}
{% endtab %}
{% tab title="OK" %}
{% endtab %}
{% endtabs %}
14. Save the Notification Rule(s).
## FAQ
**Will alerts in ilert be resolved automatically?**
Yes, if you created a threshold and a notification rule for the 'OK' status, corresponding alerts will be resolved automatically.
---
# 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/influxdb.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.
