App service
Services/OpenTelemetry Collector

OpenTelemetry Collector service

OpenTelemetry Collector service for reusable application and infrastructure workflows inside a Wodby stack.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

All services

Why teams use this service

Technical profile

Review versions, ports, source, and packaging.

Stacks that use it

See where this service fits in ready-made stacks.

Runtime wiring and defaults

See ports, links, storage, configs, and runtime behavior.

Overview

Technical profile and packaging

This page shows how OpenTelemetry Collector is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

0

Ports and protocols

4318/HTTP, 4317/TCP

Labels

opentelemetry-collector, otlp, tracing, observability

Stacks

Use it inside ready-made stacks or your own

These public stacks already include OpenTelemetry Collector as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
Grafana LokiGrafana TempoVictoriaMetrics

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

4318/HTTP, 4317/TCP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Configs

1 config can be versioned with the service.

Service links

These links define which other services can connect to OpenTelemetry Collector when it is used inside a stack.