Technology
TigerData
Monitor Tiger services for database performance, query execution, and resource utilization. Track connection pools, disk usage, replication lag, and database health. and health
Overview
Overview
Tiger is the fastest Postgres cloud, powered by TimescaleDB. It enhances Postgres to handle time series, events, real-time analytics, and vector search—all in a single database alongside transactional workloads.
TimescaleDB is an open-source Postgres extension designed for running real-time analytics on time-series data. It is engineered up from Postgres and maintains full SQL support.
You get one system that handles live data ingestion, late and out-of-order updates, and low latency queries, with the performance, reliability, and scalability your app needs. Ideal for IoT, crypto, finance, SaaS, and a myriad other domains, Tiger enables you to build data-heavy, mission-critical apps while retaining the familiarity and reliability of Postgres.
Use Cases
- Monitor database connection pools and active sessions
- Track query execution time and slow queries
- Analyze disk usage and table statistics
- Monitor replication lag and streaming replication health
- Track transaction rates, commits, and rollbacks
- Monitor buffer cache efficiency and I/O operations
Setup
Overview
A Tiger service is a single optimised Postgres instance extended with innovations such as TimescaleDB in the database engine, and a cloud infrastructure that delivers speed without compromise. A Tiger service instance is 10-1000x faster at scale!
Tiger services expose comprehensive metrics through built-in statistics views that can be collected using the OpenTelemetry Collector's TimescaleDB receiver. This integration provides deep visibility into database performance, query execution, connection management, and resource utilization.
Prerequisites
Before you setup monitoring for Tiger services:
-
Create a target Tiger service with time-series and analytics enabled.
You need your connection details. This procedure also works for self-hosted TimescaleDB.
-
Deploy the OpenTelemetry Collector Contrib distribution in your environment
Configure your Tiger service for Dash0 integration
-
Connect to your Tiger service
In Tiger Console open an SQL editor. You can also connect to your Tiger service using psql.
-
Enable the
pg_stat_statementsextension in your servicesqlCREATE EXTENSION IF NOT EXISTS pg_stat_statements; -
Create a dedicated user for monitoring
Security best practice is to create a dedicated monitoring user with the built-in
pg_monitorrole:sql-- Create monitoring user CREATE USER dash0_monitor WITH PASSWORD 'secure_password'; -- Grant the pg_monitor role for comprehensive monitoring access GRANT pg_monitor TO dash0_monitor; -- If using pg_stat_statements for top query collection CREATE EXTENSION IF NOT EXISTS pg_stat_statements; GRANT SELECT ON pg_stat_statements TO dash0_monitor;
Configure the OpenTelemetry Collector
The OpenTelemetry Collector uses the Postgres receiver to collect metrics from the TimescaleDB statistics views.
-
Update the following Postgres receiver with your Tiger service connection details
yamlreceivers: TimescaleDB: endpoint: <host>:<port> databases: - tsdb username: dash0_monitor password: <secure_password> # Use ${env:POSTGRES_PASSWORD} in production! collection_interval: 10s tls: insecure: true insecure_skip_verify: true initial_delay: 1sThe
endpointitem looks like<service_id>.<project_id>.tsdb.cloud.timescale.com:12345 -
Add the Postgres receiver to your collector configuration
For more options see the Postgres receiver documentation
Collector Deployment
Deploy the OpenTelemetry Collector with the Postgres receiver configuration for your Tiger service. For detailed deployment instructions, see our other integrations for deploying the OpenTelemetry Collector:
Verification
After configuring the collector, verify that metrics are being collected:
- Check the collector logs for successful connections to TimescaleDB
- Navigate to the Metrics Explorer in Dash0
- Search for metrics with prefix
TimescaleDB.* - Confirm connections and capacity metrics are visible:
TimescaleDB.backends(active connections)TimescaleDB.connection.max(configured max connections)TimescaleDB.db_size(database size in bytes)TimescaleDB.commits(transaction commits)TimescaleDB.rollbacks(transaction rollbacks)