Tinybird Exporter
contrib
Maintainers: @mx-psi, @jordivilaseca, @MoreraAlejandro
Source: opentelemetry-collector-contrib
Supported Telemetry
Overview
Description
This exporter sends logs, metrics, and traces to Tinybird via the Events API. Tinybird is a real-time analytics platform for ingesting, transforming, and serving data with low latency and high throughput. Telemetry data sent to Tinybird can be queried and analyzed in real time using SQL.“Quick Start
Looking for a quick start? Check out our Open Telemetry Template, which provides a ready-to-use example for configuring the Tinybird OpenTelemetry Exporter.Configuration
Required settings
endpoint(no default): The Tinybird API endpoint URL (e.g.,https://api.us-east.aws.tinybird.co)token(no default): Your Tinybird API token used for authentication
Optional settings
metrics: Configuration for different metric typesgauge::datasource(default:gauge): Name of the gauge metrics data sourcesum::datasource(default:sum): Name of the sum metrics data sourcehistogram::datasource(default:histogram): Name of the histogram metrics data sourceexponential_histogram::datasource(default:exponential_histogram): Name of the exponential histogram metrics data source
traces::datasource(default:traces): Name of the traces data sourcelogs:datasource(default:logs): Name of the logs data sourcewait(default:false): Whether to wait for data to be ingested before returning a responseretry_on_failure: Configuration for retry behavior on failuressending_queue: Configuration for the sending queue
Basic Configuration
Advanced Configuration
Data Source Requirements
Before using this exporter, you need to create the corresponding data sources in your Tinybird workspace. The data source names must:- Only contain letters, numbers, and underscores
- Match the data source names specified in your configuration
Authentication
The exporter uses API token authentication. You can provide the token in several ways:-
Environment Variable (recommended):
-
Direct configuration:
Error Handling
The exporter includes built-in retry logic for handling temporary failures. You can configure retry behavior using theretry_on_failure settings:
enabled: Enable/disable retry logicinitial_interval: Initial retry intervalmax_interval: Maximum retry intervalmax_elapsed_time: Maximum total time to retry
Performance Considerations
- Use the
sending_queueconfiguration to buffer data and improve throughput - Set
wait: falsefor better performance (default behavior)
Example: Complete Pipeline Configuration
Configuration
Example Configuration
Last generated: 2026-04-13