New component: Tinybird Exporter

[jordivilaseca]

The purpose and use-cases of the new component

The Tinybird OpenTelemetry Exporter will enable the export of traces, metrics, and logs to Tinybird, a real-time data platform built over ClickHouse. This exporter is designed for developers and data teams who need to analyze OpenTelemetry data at scale and in real-time.

The OpenTelemetry exporter leverages Tinybird’s Events API to automatically handle ingestion scaling and backpressure, removing the complexity of infrastructure provisioning and management that traditionally comes with processing large volumes of observability data.

Key use cases include real-time monitoring dashboards, anomaly detection systems, performance analytics, and any application requiring immediate insights from OpenTelemetry data streams.

Example configuration for the component

exporters:
  tinybird:
    token: ${TINYBIRD_TOKEN}
    metrics_datasource: metrics
    logs_datasource: logs
    traces_datasource: traces
    endpoint: https://api.us-east.aws.tinybird.co

Telemetry data types supported

logs, traces and metrics

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

Implementation PRs will be provided by a developer of Tinybird

[VihasMakwana]

@jordivilaseca Hello!

For new components, collector SIG meetings are great place to share your idea and get feedback from maintainers. The meeting takes place on every Wednesday. Here are more details about timings of the meetings.

[VihasMakwana]

cc: @open-telemetry/collector-contrib-maintainers @open-telemetry/collector-contrib-approvers

[mx-psi]

I am going to volunteer as a sponsor for this. The main reason behind this is that, while we no longer have a rule for accepting vendor exporters, I feel like we have not fully addressed the implications of this and I want to be fair.

I have spoken with @jordivilaseca in private and believe that Tinybird's rationale for having an exporter is at least as good as any other vendor. I nonetheless encourage Tinybird to pursue an OTLP-native solution since that may be the solution in the future.