--- title: "Manage export configurations" url: "https://docs.yugabyte.com/stable/yugabyte-platform/alerts-monitoring/anywhere-export-configuration/" --- # Manage export configurations Set up links to third-party tools in YugabyteDB Anywhere. Set up links to third-party tools You can export universe metrics and logs to third-party tools for analysis and customization. To export either metrics or logs from a universe: 1. [Create an export configuration](#configure-integrations "Create an export configuration") for the integration you want to use. A configuration defines the sign in credentials and settings for the tool that you want to export to. 2. Using the configuration you created, connect your cluster. - [Export metrics](/stable/yugabyte-platform/alerts-monitoring/anywhere-metrics-export/ "Export metrics") - [Export logs](/stable/yugabyte-platform/alerts-monitoring/universe-logging/ "Export logs") While the connection is active, metrics or logs are automatically streamed to the tool. To export logs or metrics from Kubernetes universes, install the [OpenTelemetry Operator](https://opentelemetry.io/docs/platforms/kubernetes/operator/#getting-started "OpenTelemetry Operator"). Metrics export on Kubernetes requires YugabyteDB v2026.1.2.0 or later; see [Kubernetes limitations](/stable/yugabyte-platform/alerts-monitoring/anywhere-metrics-export/#limitations "Kubernetes limitations"). ## Available integrations Currently, you can export data to the following tools: | Integration | Log export | Metric export | |-------------------------------------------------------------------------------------------------------------------------|------------|---------------| | [Datadog](https://docs.datadoghq.com/ "Datadog") | Yes | Yes | | [Splunk](https://www.splunk.com/en_us/solutions/opentelemetry.html "Splunk") | Yes | | | [AWS CloudWatch](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html "AWS CloudWatch") | Yes | | | [Google Cloud Logging](https://cloud.google.com/logging/ "Google Cloud Logging") | Yes | | | [Dynatrace](#dynatrace "Dynatrace") | | Yes | | [Loki](#loki "Loki") | Yes | | | [OTLP](#otlp "OTLP") | Yes | Yes | ## Best practices To limit performance impact and control costs, locate export configurations in a region close to your universe(s). ## Manage integrations Create and manage export configurations on the **Integrations > Log & Metrics Export** page. The page lists the configured third-party integrations. To view details for a configuration, select it in the list. To delete a configuration, click the three dots, and choose **Delete configuration**. You can't delete a configuration that is assigned to a universe. Note that you can't modify an existing configuration. If you need to change an configuration (for example, to replace or update an API key) for a particular tool, do the following: 1. Create a new configuration for the integration with the updated information. 2. Assign the new configuration to your universes. 3. Unassign the old configuration from universes. 4. Delete the old configuration. ## Configure integrations You can add and delete export configurations for the following tools. You can't delete a configuration that is in use by a universe. ### Datadog The Datadog export configuration requires the following: - Datadog account - Datadog [API key](https://docs.datadoghq.com/account_management/api-app-keys/ "API key") To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **Datadog**. 4. Enter your Datadog [API key](https://docs.datadoghq.com/account_management/api-app-keys/ "API key"). 5. Choose the Datadog site to connect to, or choose Self-hosted and enter your URL. 6. Click **Create Configuration**. ### Splunk The Splunk export configuration requires the following: - Splunk access token - Endpoint URL To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **Splunk**. 4. Enter your Splunk [Access token](https://docs.splunk.com/observability/en/admin/authentication/authentication-tokens/org-tokens.html "Access token"). 5. Enter the Endpoint URL. 6. Optionally, enter the Source, Source Type, and Index. 7. Click **Validate and Create Configuration**. ### AWS The AWS CloudWatch export configuration requires the following: - Access Key ID and Secret Access Key for the AWS Service Account - The [log group and log stream](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/Working-with-log-groups-and-streams.html "log group and log stream") - The AWS region where the stream is located To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **AWS CloudWatch**. 4. Enter your access key and secret access key. 5. Enter the Log group and Log stream. 6. Enter the region. 7. Optionally, provide the ARN for the role. 8. Optionally, provide an endpoint URL. 9. Click **Validate and Create Configuration**. ### Google Cloud Logging The Google Cloud Logging export configuration requires the following: - Google Service Account with the `roles/logging.logWriter` role. - The Service Account credentials JSON key. The credentials should be scoped to the project where the log group is located. To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **GCP Cloud Logging**. 4. Optionally, provide the project name. 5. Upload the JSON file containing your Google Cloud credentials. 6. Click **Validate and Create Configuration**. ### Dynatrace The [Dynatrace](https://www.dynatrace.com "Dynatrace") integration requires the following: - Publically-accessible [OTLP endpoint URL](https://docs.dynatrace.com/docs/ingest-from/opentelemetry/otlp-api#export-to-dynatrace "OTLP endpoint URL") of your Dynatrace instance. The endpoint URL is the URL of your Dynatrace instance. For example: `https://{your-environment-id}.live.dynatrace.com/api/v2/otlp` Note that if you copy your Dynatrace environment ID from the browser address bar, make sure to remove `.apps`. - [Dynatrace Access Token](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/access-tokens#create-api-token "Dynatrace Access Token"). The access token needs to have ingest metrics, ingest logs, ingest OpenTelemetry traces, and read API tokens [scope](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/access-tokens#scopes "scope"). To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **Dynatrace**. 4. Enter the Dynatrace Endpoint URL. 5. Enter your Dynatrace Access Token. 6. Click **Validate and Create Configuration**. ### Loki [Grafana Loki](https://grafana.com/docs/loki/latest/ "Grafana Loki") is a log aggregation system designed to store and query logs. YugabyteDB Anywhere can export logs to a Loki-compatible endpoint (including self-hosted Loki and [Grafana Cloud](https://grafana.com/docs/grafana-cloud/send-data/logs/logs-with-loki/ "Grafana Cloud")). #### Prerequisites - Enable the Loki sink by setting the **Allow Loki Exporter in Telemetry Provider** Global Configuration option (config key `yb.telemetry.allow_loki`) to `true`. Refer to [Manage runtime configuration settings](/stable/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config/ "Manage runtime configuration settings"). The flag is enforced when you create or delete a Loki telemetry provider. - A reachable Loki endpoint. #### Create a Loki export configuration To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **Loki**. 4. Fill in the Loki-specific fields: - Enter the **Loki endpoint** URL. For example, `http://:`. - **Organization / Tenant ID** (optional). Organization ID is required when multi-tenancy is set up in Loki. Optional for Grafana Cloud, as the authentication reroutes requests according to scope. - **Authentication Type**: **Basic Auth** or **No Auth**. If you choose **Basic Auth**, enter a **Username** and **Password**. 5. Click **Validate and Create Configuration**. Loki configurations are immutable After you create a configuration, you cannot edit it. To change settings, create a new configuration, reassign universes, and delete the old configuration. ### OTLP YugabyteDB Anywhere supports [OTLP](https://opentelemetry.io/docs/ "OTLP") (OpenTelemetry Protocol) as a generic telemetry provider sink. An OTLP telemetry provider lets a universe stream database logs and database metrics to any OTLP-compatible receiver using the standard OpenTelemetry wire format. The OTLP sink is vendor-agnostic and works with any backend that speaks OTLP, including (but not limited to) [Cribl](https://cribl.io/ "Cribl"), [Grafana Cloud](https://grafana.com/docs/grafana-cloud/ "Grafana Cloud"), [New Relic](https://docs.newrelic.com/docs/opentelemetry/opentelemetry-introduction/ "New Relic"), [Prometheus](https://prometheus.io/docs/guides/opentelemetry/ "Prometheus") (3.0+), [VictoriaMetrics](https://docs.victoriametrics.com/guides/getting-started-with-opentelemetry/ "VictoriaMetrics"), and [Sumo Logic](https://help.sumologic.com/docs/send-data/opentelemetry-for-logs/ "Sumo Logic"). You can reuse the same OTLP telemetry provider for [query and audit logging](/stable/yugabyte-platform/alerts-monitoring/universe-logging/ "query and audit logging"), [database metrics export](/stable/yugabyte-platform/alerts-monitoring/anywhere-metrics-export/ "database metrics export"), or both. OTLP uses the same OpenTelemetry Collector and universe export workflows as other telemetry providers. #### Prerequisites - In versions earlier than v2026.1.2.0, enable the OTLP integration by setting the **OTLP Exporter for Telemetry Provider** Global Configuration option (config key `yb.telemetry.allow_otlp`) to `true`. Refer to [Manage runtime configuration settings](/stable/yugabyte-platform/administer-yugabyte-platform/manage-runtime-config/ "Manage runtime configuration settings"). Starting in v2026.1.2.0, OTLP is enabled by default. - A reachable OTLP-compatible receiver and credentials if required (Basic Auth username and password, or a bearer token). #### Create an OTLP export configuration To create an export configuration, do the following: 1. On the **Integrations** page, on the **Log & Metrics Export** tab, click **Add Configuration**. 2. Enter a name for the configuration. 3. Choose **OTLP**. 4. Fill in the OTLP-specific fields: - Enter the OTLP receiver **Endpoint URL**. - **Protocol**: gRPC (default) or HTTP. - **Authentication Type**: - **No Auth** (default): no credentials. - **Basic Auth**: username and password. - **Bearer Token** - **Logs Endpoint** (HTTP only, optional): override URL for logs (for example, `https://example.com:4318/v1/logs`). - **Metrics Endpoint** (HTTP only, optional): override URL for metrics (for example, `https://example.com:4318/v1/metrics`). - **Timeout (seconds)**: default is `5`. 5. Click **Validate and Create Configuration**. OTLP configurations are immutable After you create a configuration, you cannot edit it. To change settings, create a new configuration, reassign universes, and delete the old configuration. Concrete endpoint URLs and auth schemes vary by OTLP backend; consult your receiver vendor's documentation or [Integrations in YugabyteDB Aeon](/stable/yugabyte-cloud/cloud-monitor/managed-integrations/ "Integrations in YugabyteDB Aeon") for the correct OTLP address. #### Unsupported scenarios - Per-signal endpoint overrides (`logsEndpoint`, `metricsEndpoint`) are allowed only when **Protocol** is **HTTP**. A gRPC provider that sets either field is rejected. - For the **HTTP** protocol, when log export is enabled the OpenTelemetry Collector appends `/v1/logs` to the configured endpoint. Configure the endpoint without that suffix unless you use the explicit **Logs Endpoint** override. - Kubernetes support follows the same rules as the rest of YugabyteDB Anywhere OpenTelemetry export. See [metrics export limitations](/stable/yugabyte-platform/alerts-monitoring/anywhere-metrics-export/#limitations "metrics export limitations") and [log export prerequisites](/stable/yugabyte-platform/alerts-monitoring/universe-logging/#prerequisites "log export prerequisites"). #### REST API configuration The full OTLP request body for the REST API is documented in the YugabyteDB Anywhere OpenAPI specification under the `TelemetryProvider` model and the `OTLPConfig` schema (`POST /api/v1/customers/{cUUID}/telemetry_provider` with `config.type` = `"OTLP"`). Refer to the [YugabyteDB Anywhere REST API](/stable/yugabyte-platform/anywhere-automation/anywhere-api/ "YugabyteDB Anywhere REST API"). Be careful when using `collection_level=ALL` in the API, as it can lead to performance overhead on the database nodes. The following `OTLPConfig` fields are accepted by the REST API but are not exposed in the UI: | Field | Description | |------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| | `headers` | Map of extra HTTP headers attached to every export request. | | `compression` | Exporter compression (`gzip`, `none`, `snappy`, `zstd`). UI create requests always send `gzip`. | | `retryOnFailure` | Retry settings: `{ "initial_interval": "...", "max_interval": "...", "max_elapsed_time": "..." }` with duration strings such as `30s`, `1m`, `60m`. | #### Additional configuration | Runtime flag | Scope | Description | |----------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `yb.telemetry.skip_connectivity_validations` | Global | Skips connectivity and permission validations on create if your receiver is not reachable from YugabyteDB Anywhere at configuration time. | | `yb.universe.otel_collector_max_memory` | Universe | Hard memory limit on the OpenTelemetry Collector process (kills the process if exceeded). To apply a change on an existing universe, re-run any OpenTelemetry configure API (configure metrics export, modify audit logging, or modify query logging). | ## Next steps - [Export metrics from a universe](/stable/yugabyte-platform/alerts-monitoring/anywhere-metrics-export/ "Export metrics from a universe") - [Export logs from a universe](/stable/yugabyte-platform/alerts-monitoring/universe-logging/ "Export logs from a universe")