ubuntu/opentelemetry-collector repository overview

ubuntu/opentelemetry-collector is a rock for opentelemetry-collector maintained by Canonical⁠.

The OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data. In addition, it removes the need to run, operate and maintain multiple agents/collectors in order to support open-source telemetry data formats (e.g. Jaeger, Prometheus, etc.) to multiple open-source or commercial back-ends.

[Learn more about opentelemetry-collector⁠]

⁠Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels⁠.

⁠Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble⁠]

⁠Inspect

To view the Pebble services⁠ and checks⁠ defined in this rock:

docker run --rm ubuntu/opentelemetry-collector:0.141-24.04_stable plan

⁠Run

To run this rock, use any of the usual container runtimes, for example, docker:

docker run --name opentelemetry-collector-container \
    -p 4318:4318 \
    ubuntu/opentelemetry-collector:0.141-24.04_stable

Access the OpenTelemetry Collector instance at http://localhost:4318.

⁠Get logs

To view the logs of the running container, run:

docker exec opentelemetry-collector-container pebble logs

Or, for a specific service:

docker exec opentelemetry-collector-container pebble logs <service>

⁠Monitor health checks

Rocks may have predefined health checks that you can list by running:

docker exec opentelemetry-collector-container pebble checks

The overall health of your container can be inspected via:

docker exec opentelemetry-collector-container pebble health

⁠Configuration

⁠Environment variables

⁠Volumes

⁠Ports

[Report a bug⁠] [Contribute⁠]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy⁠.