# Automatic Disabling of Failing Streaming Integrations

Streaming integrations consume resources on the ThousandEyes backend. To maintain efficiency, only functional streaming integrations are supported.

## Criteria for Disabling

If a streaming integration fails to stream data for 12 consecutive hours, you receive a warning notification in the ThousandEyes platform. This notification informs you that the integration will be disabled in 12 hours if the issue is not resolved. You can find your notifications at the bell icon.

![Warning Notification](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-b1d436dcdb767898b3a108d66dfb5eeb3ca8f962%2Fproduct-documentation_integration-guides_custom-built-integrations_opentelemetry-warning-notification.png?alt=media\&token=89583230-91ee-450e-8d7b-3c2b58214e4e)

If failures continue for 12 consecutive hours, the integration is disabled automatically, and the platform notifies you again.

![Disabled Notification](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-df529b6d1d9a4a691e1fa8d9adb926a2c4dce6aa%2Fproduct-documentation_integration-guides_custom-built-integrations_opentelemetry-disable-notification.png?alt=media\&token=930a5984-1eb0-4e2e-9cb1-349145ee80e7)

Successful data export at any point resets the failure counter to zero.

## Common Failure Causes

Failures can occur due to:

* **Invalid Target URL**: The configured URL cannot receive OTLP data.
* **Invalid Target Protocol**: Incorrect protocol configuration leads to data export attempts using an incorrect protocol.
* **Invalid Authentication Headers**: Incorrect tokens in headers may lead to HTTP 401 errors, as the data export request fails authentication.
* **Invalid Content Type**: Missing or incorrect content type headers can cause data export failures.

## Re-Enabling a Disabled Integration

Streaming integrations are disabled, not deleted. You can correct configurations and re-enable them.

### Re-Enabling Via the UI

1. In the ThousandEyes platform, go to **Manage > Integrations**.
2. Click the disabled integration to open the edit window.
3. Toggle the **Integration Status** to **Enabled**.
4. Click **Save** to apply changes.

### Re-Enabling Via the API

Send a PUT HTTP request to enable the integration:

```bash
curl -i -XPUT https://api.thousandeyes.com/v7/stream/<stream_id> \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $BEARER_TOKEN" \
-d '{"enabled": "true"}'
```


---

# Agent Instructions: 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:

```
GET https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/automatic-disabling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.