Integrations

Set up links to third-party tools

You can export cluster metrics and logs to third-party tools for analysis and customization. Exporting data is a two-stage process:

  1. Create an export configuration. A configuration defines the sign in credentials and settings for the tool that you want to export to.
  2. Use the configuration to export data from a cluster. While the connection is active, metrics or logs are automatically streamed to the tool.

Currently, you can export data to the following tools:

Exporting cluster metrics and logs counts against your data transfer allowance. This may incur additional costs for network transfer, especially for cross-region and internet-based transfers, if usage exceeds your cluster allowance. Refer to Data transfer costs.

For information on how to export metrics and logs from a cluster using an integration, refer to Export metrics and Export logs.

Configure integrations

Create and manage export configurations on the Integrations page.

Integrations

The page lists the configured and available third-party integrations.

Manage integrations

You can add and delete export configurations for the following tools. You can't delete a configuration that is assigned to a cluster.

The Datadog integration requires the following:

To create an export configuration, do the following:

  1. On the Integrations page, click Configure for the Datadog provider or, if a configuration is already available, Add Configuration.
  2. Enter a name for the configuration.
  3. Enter your Datadog API key.
  4. Choose the Datadog site to connect to, or choose Self-hosted and enter your URL.
  5. Optionally, click Download to download the Datadog dashboard template. You can import this JSON format template into your Datadog account and use it as a starting point for visualizing your cluster data in Datadog.
  6. Click Test Configuration to make sure your connection is working.
  7. Click Create Configuration.

The Grafana Cloud integration requires the following:

  • Grafana Cloud account and stack. For best performance and lower data transfer costs, deploy your stack in the region closest to your cluster. For a list of supported regions, see the Grafana Cloud documentation.
  • Access policy token. You need to create an Access policy with metrics:write scope, and then add a token. For more information, see Grafana Cloud Access Policies in the Grafana documentation.

To create an export configuration, do the following:

  1. On the Integrations page, click Configure for the Grafana Cloud provider or, if a configuration is already available, Add Configuration.
  2. Enter a name for the configuration.
  3. Enter your organization name. This is displayed in the URL when you connect to your Grafana Cloud Portal (for example, https://grafana.com/orgs/<organization-name>).
  4. Enter your Grafana Cloud Access policy token.
  5. Enter your Grafana Cloud instance ID and zone. Obtain these by navigating to the Grafana Cloud portal, selecting your stack, and on the Grafana tile, clicking Details. They are displayed under Instance Details.
  6. Optionally, click Download to download the Grafana Cloud dashboard template. You can import this JSON format template into your Grafana account and use it as a starting point for visualizing your cluster data in Grafana. The dashboard is also available from the Grafana Dashboards page.
  7. Click Test Configuration to make sure your connection is working.
  8. Click Create Configuration.

The Sumo Logic integration requires the following:

To create an export configuration, do the following:

  1. On the Integrations page, click Configure for the Sumo Logic provider or, if a configuration is already available, Add Configuration.
  2. Enter a name for the configuration.
  3. Enter your installation token, access ID, and access key.
  4. Optionally, click Download to download the Sumo Logic dashboard template. After you install the YugabyteDB app (coming soon) in your Sumo Logic account, you can import this JSON format template and use it as a starting point for visualizing your cluster data.
  5. Click Test Configuration to make sure your connection is working.
  6. Click Create Configuration.

Prometheus integration is TP and only available for clusters deployed on AWS.

The Prometheus integration requires the following:

  • Prometheus instance

    • deployed in a VPC on AWS

    • OLTP Receiver feature flag enabled

    • publically-accessible endpoint URL that resolves to the private IP of the Prometheus instance; the DNS for the endpoint must be in a public hosted zone in AWS.

    • VPC hosting the Prometheus instance has the following Inbound Security Group rules:

      • Allow HTTP inbound traffic on port 80 for Prometheus endpoint URL (HTTP)
      • Allow HTTPS inbound traffic on port 443 for Prometheus endpoint URL (HTTPS)

      See Control traffic to your AWS resources using security groups in the AWS documentation.

  • YugabyteDB Aeon cluster from which you want to export metrics

    As each region of a cluster deployed in AWS has its own VPC, make sure that all the VPCs are peered and allow inbound access from Prometheus; this also applies to regions you add or change after deployment, and to read replicas. For information on VPC networking in YugabyteDB Aeon, see VPC network overview.

To create an export configuration, do the following:

  1. On the Integrations page, click Configure for the Prometheus provider or, if a configuration is already available, Add Configuration.

  2. Enter a name for the configuration.

  3. Enter the endpoint URL of the Prometheus instance.

    The URL must be in the form

    http://<prometheus-endpoint-host-address>/api/v1/otlp

  4. Click Create Configuration.

VictoriaMetrics integration is TP and only available for clusters deployed on AWS.

The VictoriaMetrics integration requires the following:

  • VictoriaMetrics instance

    • deployed in a VPC on AWS

    • publically-accessible endpoint URL that resolves to the private IP of the VictoriaMetrics instance; the DNS for the endpoint must be in a public hosted zone in AWS. The URL must be in the form as described in How to use OpenTelemetry metrics with VictoriaMetrics.

    • VPC hosting the VictoriaMetrics instance has the following Inbound Security Group rules:

      • Allow HTTP inbound traffic on port 80 for VictoriaMetrics endpoint URL (HTTP)
      • Allow HTTPS inbound traffic on port 443 for VictoriaMetrics endpoint URL (HTTPS)

      See Control traffic to your AWS resources using security groups in the AWS documentation.

  • YugabyteDB Aeon cluster from which you want to export metrics

    As each region of a cluster deployed in AWS has its own VPC, make sure that all the VPCs are peered and allow inbound access from VictoriaMetrics; this also applies to regions you add or change after deployment, and to read replicas. For information on VPC networking in YugabyteDB Aeon, see VPC network overview.

To create an export configuration, do the following:

  1. On the Integrations page, click Configure for the VictoriaMetrics provider or, if a configuration is already available, Add Configuration.

  2. Enter a name for the configuration.

  3. Enter the endpoint URL of the VictoriaMetrics instance.

    The URL must be in the form

    http://<victoria-metrics-endpoint-host-address>/opentelemetry

  4. Click Create Configuration.

To view the configurations, click the View button for the provider.

To delete a configuration, click View and choose Delete.

Note that you can't modify an existing integration configuration. If you need to change an integration (for example, to replace or update an API key) for a particular tool, do the following:

  1. Create a new configuration for the provider with the updated information.
  2. Assign the new configuration to your clusters.
  3. Unassign the old configuration from clusters.
  4. Delete the old configuration.