# InfluxDB Integration

InfluxDB is a high-performance time series database purpose-built for storing metrics, events, and real-time analytics. Its built-in Checks & Notifications system lets you define threshold conditions on your time series data and push alert notifications directly to external HTTP endpoints — making it straightforward to route those alerts into ITOC360.

### In ITOC360

Go to Sources, click **Create Source**, and select **InfluxDB** from the list. Once the source is created, copy the webhook URL and token from the source detail page — you will need these when configuring InfluxDB.

### In InfluxDB

In the left sidebar, hover over the bell icon to expand the navigation and click **Alerts**.<br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FygwhmwQ3ulWECe6vov4h%2Fimage.png?alt=media&#x26;token=a58b53b2-f345-4e9d-8f86-2d40dcc147e4" alt=""><figcaption></figcaption></figure>

#### Step 1 — Create a Notification Endpoint

On the Alerts page, click **Notification Endpoints**, then click **+ Create** in the top right corner.<br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FJveYGf4dCVp9xoCxJG9j%2Fimage.png?alt=media&#x26;token=a050e215-077b-42d8-9d49-3e90f2ca0412" alt=""><figcaption></figcaption></figure>

From the **Destination** dropdown, select **HTTP** and give the endpoint a name. Under **HTTP Options**, make sure the method is set to **POST** and the auth method is **none**. Paste your ITOC360 webhook URL into the URL field, appending your source token as a query parameter:

```
https://<your-url>?token=<your-token>
```

Click **Create Notification Endpoint** to save.

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FmmPcuK2nKsr48OQTTdWZ%2FEkran%20Resmi%202026-03-31%2014.23.52.png?alt=media&#x26;token=77762f63-383f-4446-82bc-41bf5c4e6bd7" alt=""><figcaption></figcaption></figure>

#### Step 2 — Create a Check

Click the **Checks** tab on the Alerts page, then click **+ Create** and select **Threshold Check**.

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FKKWkXXOT9wiuR6RUIeew%2Fimage.png?alt=media&#x26;token=24aad648-9286-4798-a8e0-472f9b1899b6" alt=""><figcaption></figcaption></figure>

In the query builder, select your bucket from the **FROM** column, choose a measurement, and select the field you want to monitor. Click **Submit** to preview the data on the chart.

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2F1ZYQOssCfS6zjVEsp60o%2Fimage.png?alt=media&#x26;token=6b32ef0a-1001-4076-8ca7-a138fb5e20aa" alt=""><figcaption></figcaption></figure>

Switch to the **2. Configure Check** tab. In the **Thresholds** section on the right, click **+ CRIT** and enter the value above which the check should fire as critical. You can optionally add a **WARN** threshold for a lower severity level. Give the check a descriptive name at the top, then click the checkmark button in the top right corner to save.\ <br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FaHUw2ozLf0dk81fGbTrg%2Fimage.png?alt=media&#x26;token=8a2f55d4-1e26-4a3e-9880-665c55f893bd" alt=""><figcaption></figcaption></figure>

#### Step 3 — Create Notification Rules

Click the **Notification Rules** tab. InfluxDB requires a separate rule for each status level, so you will need to create two rules — one for when the check fires and one for when it recovers.

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2FMgze0mhxOwdw2tsdqUkx%2Fimage.png?alt=media&#x26;token=6af6fa13-cea2-4aac-96fe-53c07fb5264c" alt=""><figcaption></figcaption></figure>

Click **+ Create**. Give the rule a name and set the condition to `When status is equal to CRIT`. Under **Notification Endpoint**, select the endpoint you created in Step 1. Click **Create Notification Rule** to save.\ <br>

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2Fbir8MMZ4BKayzlZlYwkz%2Fimage.png?alt=media&#x26;token=9e7c3977-8928-4910-9b6c-51266a4d8445" alt=""><figcaption></figcaption></figure>

Then create a second rule in the same way, this time setting the condition to `When status is equal to OK` and selecting the same endpoint. This second rule is what allows itoc360 to automatically resolve alerts when your metric returns to normal.

### Notes

* InfluxDB runs notification rules on a schedule (default: every 1 minute). There may be a short delay between a threshold breach and the alert appearing in ITOC360.
* The CRIT rule and the OK rule must point to the same notification endpoint so that ITOC360 can correctly match each alert to its resolution.
* If you have multiple checks, each one should have its own pair of notification rules.
