You can export telemetry data from your Timescale Cloud Time Series and Analytics services to third-party monitoring tools such as Datadog or AWS CloudWatch. Available metrics include CPU usage, RAM usage, and storage. Third-party monitoring is available for Scale or Enterprise Timescale Projects.
This page shows you how to securely connect a data exporter to a monitoring tool, and manage the lifecycle of data exporters.
To export telemetry data you:
- Create a data exporter - configure a Timescale Cloud data exporter to securely communicate with an external monitoring tool.
- Attach the exporter to a Timescale Service - connect the exporter to a Timescale Cloud Service.
A data exporter sends telemetry data from a Timescale Cloud Service to a third-party monitoring tool. You attach each Timescale Cloud Service to a single data exporter. Each data exporter must be in the same AWS region as the Timescale Cloud Service you are attaching it to. If your Timescale Cloud Project has multiple services running in different regions, create an exporter for each region.
To send telemetry data to an external monitoring tool, you attach the data exporter to a Timescale Cloud Service. Each data exporter must be in the same AWS region as the Timescale Cloud Service you are attaching it to.
Each Timescale Cloud Service has one exporter only. The exporter sends telemetry data from that service to the monitoring provider.
- In Timescale Portal > Services, choose the service to monitor.
- Click
Operations, thenIntegrations. - Select an exporter, then click
Attach exporter.
Warning
You need to restart the Timescale Cloud Services when you attach a first Logs data type exporter.
You can now monitor your service metrics from the metrics explorer in Datadog, or query them from the CloudWatch metrics page in AWS Console. For more information, see the Datadog or CloudWatch documentation.
Use the following metrics to check the service is running correctly:
timescale.cloud.system.cpu.usage.millicorestimescale.cloud.system.cpu.total.millicorestimescale.cloud.system.memory.usage.bytestimescale.cloud.system.memory.total.bytestimescale.cloud.system.disk.usage.bytestimescale.cloud.system.disk.total.bytes
Additionally, use the following tags to filter your results.
| Tag | Example variable | Description |
|---|---|---|
host | us-east-1.timescale.cloud | |
project-id | ||
service-id | ||
region | us-east-1 | Timescale region |
role | replica or primary | For services with replicas |
node-id | For multi-node services |
To update a data exporter:
- In Timescale Console, open Integrations.
- Beside the exporter you want to edit, click the menu button. Click
Edit. - Edit the exporter fields and save your changes.
You cannot change fields such as the provider or the AWS region.
To remove a data exporter that you no longer need:
Disconnect the data exporter from your Timescale Cloud Services:
For each Timescale Cloud Services the data exporter is connected to:
- In Timescale Console, open Services, then select the Timescale Cloud Service to update.
- Click
Operations, then clickIntegrations. - Click the trash can icon.
The data exporter is removed from this service. However, it still exists in your Timescale Cloud project.
In Timescale Console, open Integrations.
Beside the exporter you want to delete, click the menu button, then click
Delete.Confirm that you want to delete the data exporter.
When you create the IAM OIDC provider, the URL must match the region you create the exporter in. It must be one of the following:
| Region | Zone | Location | URL |
|---|---|---|---|
ap-southeast-1 | Asia Pacific | Singapore | irsa-oidc-discovery-prod-ap-southeast-1.s3.ap-southeast-1.amazonaws.com |
ap-southeast-2 | Asia Pacific | Sydney | irsa-oidc-discovery-prod-ap-southeast-2.s3.ap-southeast-2.amazonaws.com |
ap-northeast-1 | Asia Pacific | Tokyo | irsa-oidc-discovery-prod-ap-northeast-1.s3.ap-northeast-1.amazonaws.com |
ca-central-1 | Canada | Central | irsa-oidc-discovery-prod-ca-central-1.s3.ca-central-1.amazonaws.com |
eu-central-1 | Europe | Frankfurt | irsa-oidc-discovery-prod-eu-central-1.s3.eu-central-1.amazonaws.com |
eu-west-1 | Europe | Ireland | irsa-oidc-discovery-prod-eu-west-1.s3.eu-west-1.amazonaws.com |
eu-west-2 | Europe | London | irsa-oidc-discovery-prod-eu-west-2.s3.eu-west-2.amazonaws.com |
sa-east-1 | South America | São Paulo | irsa-oidc-discovery-prod-sa-east-1.s3.sa-east-1.amazonaws.com |
us-east-1 | United States | North Virginia | irsa-oidc-discovery-prod.s3.us-east-1.amazonaws.com |
us-east-2 | United States | Ohio | irsa-oidc-discovery-prod-us-east-2.s3.us-east-2.amazonaws.com |
us-west-2 | United States | Oregon | irsa-oidc-discovery-prod-us-west-2.s3.us-west-2.amazonaws.com |
Keywords
Found an issue on this page?Report an issue or Edit this page in GitHub.