timescale · atovpeko · Mar 25, 2026 · Mar 24, 2026 · Mar 24, 2026 · Mar 24, 2026
diff --git a/_partials/_azure-monitor-data-exporter.md b/_partials/_azure-monitor-data-exporter.md
@@ -15,7 +15,9 @@
 
     [Learn where to find][connection-string] your connection string. 
 
-1.  **Click `Create exporter`**
+1. **Export additional metrics**
+
+   Optionally tick `PostgreSQL metrics` to export [additional metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/#postgres-metrics), then click `Create exporter`.
 
 Your exporter is created and added to the list of already existing exporters. 
 

diff --git a/_partials/_cloudwatch-data-exporter.md b/_partials/_cloudwatch-data-exporter.md
@@ -127,7 +127,9 @@
 
     </Tabs> 
 
-1. Select the AWS Region your CloudWatch services run in, then click `Create exporter`.
+1. Select the AWS Region your CloudWatch services run in.
+
+1. Optionally tick `PostgreSQL metrics` to export [additional metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/#postgres-metrics), then click `Create exporter`.
 
 </Procedure>
 

diff --git a/_partials/_datadog-data-exporter.md b/_partials/_datadog-data-exporter.md
@@ -10,7 +10,11 @@
 
     The AWS region must be the same for your $CLOUD_LONG exporter and the Datadog provider.
 
-1.  **Set `Site` to your Datadog region, then click `Create exporter`**
+1.  **Set `Site` to your Datadog region**
+
+1. **Export additional metrics**
+
+   Optionally tick `PostgreSQL metrics` to export [additional metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/#postgres-metrics), then click `Create exporter`.
 
 </Procedure>
 

diff --git a/_partials/_prometheus-integrate.md b/_partials/_prometheus-integrate.md
@@ -30,7 +30,7 @@ To export your data, do the following:
 
 <Procedure>
 
-To export metrics from a $SERVICE_LONG, you create a dedicated Prometheus exporter in $CONSOLE, attach it to your $SERVICE_SHORT, then configure Prometheus to scrape metrics using the exposed URL. The Prometheus exporter exposes the metrics related to the $SERVICE_LONG like CPU, memory, and storage. To scrape other metrics, use Postgres Exporter as described for $SELF_LONG. The Prometheus exporter is available for [$SCALE and $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
+To export metrics from a $SERVICE_LONG, you create a dedicated Prometheus exporter in $CONSOLE, attach it to your $SERVICE_SHORT, then configure Prometheus to scrape metrics using the exposed URL. See [Exported metrics][exported-metrics] for the full list of default and additional metrics you can export. The Prometheus exporter is available for [$SCALE and $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
 
 1. **Create a Prometheus exporter**
 
@@ -42,10 +42,12 @@ To export metrics from a $SERVICE_LONG, you create a dedicated Prometheus export
 
    1. Choose the region for the exporter. Only $SERVICE_SHORTs in the same project and region can be attached to this exporter.
 
-   1. Name your exporter. 
+   1. Name your exporter.
 
    1. Change the auto-generated Prometheus credentials, if needed. See [official documentation][prometheus-authentication] on basic authentication in Prometheus.
 
+   1. Optionally tick `PostgreSQL metrics` to export [additional metrics][exported-metrics], then click `Create exporter`.
+
 1. **Attach the exporter to a $SERVICE_SHORT**
 
    1. Select a $SERVICE_SHORT, then click `Operations` > `Exporters`. 
@@ -177,6 +179,7 @@ You can further [visualize your data][grafana-prometheus] with Grafana. Use the
 [create-a-prometheus-exporter-in-tiger]: https://assets.timescale.com/docs/images/tiger-cloud-console/tiger-console-create-prometheus-exporter.png
 [create-service]: /getting-started/:currentVersion:/services/
 [enable-timescaledb]: /self-hosted/:currentVersion:/install/
+[exported-metrics]: /use-timescale/:currentVersion:/metrics-logging/exported-metrics/#postgres-metrics
 [grafana-prometheus]: https://grafana.com/docs/grafana-cloud/send-data/metrics/metrics-prometheus/
 [grafana]: /integrations/:currentVersion:/grafana/
 [install-exporter]: https://grafana.com/oss/prometheus/exporters/postgres-exporter/?tab=installation

diff --git a/about/changelog.md b/about/changelog.md
@@ -14,6 +14,8 @@ All the latest features and updates to $CLOUD_LONG.
 
 You can now enable the export of database metrics such as replication, cache usage, and background activity to Amazon CloudWatch, Datadog, and Prometheus by selecting `PostgreSQL metrics` when creating or modifying an exporter in Tiger Console. Additionally, system-level disk metrics such as IO and throughput are now being exported by default.
 
+See [Exported metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/) for the full list of default and additional metrics, and [Metrics and logging](/use-timescale/:currentVersion:/metrics-logging/) for how to create exporters.
+
 ## Support cases in Tiger Console
 <Label type="date">March 23, 2026</Label>
 

diff --git a/use-timescale/metrics-logging/aws-cloudwatch.md b/use-timescale/metrics-logging/aws-cloudwatch.md
@@ -15,10 +15,9 @@ import ExporterRegion from "versionContent/_partials/_iam-oidc-exporter-region.m
 
 # Export telemetry data to AWS Cloudwatch
 
-You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to [Amazon CloudWatch][cloudwatch]. Available metrics include CPU usage, RAM usage, and storage. This integration is available for [$SCALE or $ENTERPRISE][pricing-plan-features]
-$PRICING_PLANs.
+You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to [Amazon CloudWatch][cloudwatch]. See [Exported metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/) for the full list of default and additional metrics you can export. 
 
-This page shows you how to create an Amazon CloudWatch exporter in $CONSOLE, and manage the lifecycle of data exporters.
+This page shows you how to create an Amazon CloudWatch exporter in $CONSOLE, and manage the lifecycle of data exporters. This integration is available for [$SCALE or $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
 
 ## Prerequisites
 

diff --git a/use-timescale/metrics-logging/azure-monitor.md b/use-timescale/metrics-logging/azure-monitor.md
@@ -14,9 +14,9 @@ import NotSupportedAws from "versionContent/_partials/_not-supported-for-aws.mdx
 
 # Export telemetry data to Azure Monitor
 
-You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to [Azure Monitor][azure-monitor]. Available metrics include CPU usage, RAM usage, and storage. This integration is available for [$SCALE or $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
+You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to [Azure Monitor][azure-monitor]. See [Exported metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/) for the full list of default and additional metrics you can export.
 
-This page shows you how to create an Azure Monitor exporter in $CONSOLE, and manage the lifecycle of data exporters.
+This page shows you how to create an Azure Monitor exporter in $CONSOLE, and manage the lifecycle of data exporters. This integration is available for [$SCALE or $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
 
 ## Prerequisites
 

diff --git a/use-timescale/metrics-logging/datadog.md b/use-timescale/metrics-logging/datadog.md
@@ -10,13 +10,12 @@ tags: [telemetry, monitor]
 import DataDogExporter from "versionContent/_partials/_datadog-data-exporter.mdx";
 import PrereqsCloud from "versionContent/_partials/_prereqs-cloud-no-connection.mdx";
 import ManageDataExporter from "versionContent/_partials/_manage-a-data-exporter.mdx";
-import ExporterRegion from "versionContent/_partials/_iam-oidc-exporter-region.mdx";
 
 # Export telemetry data to Datadog
 
-You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to [Datadog][datadog]. The available metrics include CPU usage, RAM usage, and storage. This integration is available for [$SCALE or $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
+You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to [Datadog][datadog]. See [Exported metrics](/use-timescale/:currentVersion:/metrics-logging/exported-metrics/) for the full list of default and additional metrics you can export.
 
-This page shows you how to create a Datadog exporter in $CONSOLE, and manage the lifecycle of data exporters.
+This page shows you how to create a Datadog exporter in $CONSOLE, and manage the lifecycle of data exporters. This integration is available for [$SCALE or $ENTERPRISE][pricing-plan-features] $PRICING_PLANs.
 
 ## Prerequisites
 
@@ -35,9 +34,6 @@ This section shows you how to attach, edit, and delete a data exporter.
 
 <ManageDataExporter />
 
-## Reference
-
-<ExporterRegion />
 
 [datadog]: https://www.datadoghq.com
 [pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan