OpenTelemetry Support in Weik.io

This page describes how to enable and configure OpenTelemetry support for Weik.io agents.

Enabling OpenTelemetry#

Enable OpenTelemetry support by setting the following configuration:

Weikio:
  Agent:
    Otel:
      IsEnabled: true

Configuration options#

Environment variables#

The following OpenTelemetry environment variables can be configured:

Example configuration#

Weikio:
  Agent:
    Otel:
      IsEnabled: true
      ServiceName: my-integration-service
      Endpoint: http://otel-collector:4317

Integration flow telemetry#

When you enable OpenTelemetry:

• All Camel routes are automatically instrumented
• Traces capture route processing, endpoints, and component operations
• Metrics log route timings and message counts
• Logs are correlated with traces

Weik.io automatically downloads and configures the OpenTelemetry Java agent when you enable OpenTelemetry support. This provides:

• Automatic instrumentation of Camel routes and components
• Distributed tracing without additional configuration
• Metric collection for monitoring route performance
• Log correlation with trace context

Technical details#

Weik.io downloads the OpenTelemetry Java agent from Maven Central and stores it in the agent’s data directory under {AgentDataPath}/{AgentName}/Otel/. Each agent instance keeps its own copy of the agent, which avoids conflicts when multiple agents run on the same machine.

Configuration options#

The OpenTelemetry Java agent version can be configured through IntegrationRunnerOptions.OtelAgentVersion (default: 1.32.1).

Default ports#

The default OTLP ports are:

• gRPC: 4317
• HTTP: 4318

These can be configured through the OTEL_EXPORTER_OTLP_ENDPOINT environment variable.