OpenTelemetry endpoint URL requirements

When you enable OpenTelemetry (OTEL) export through the spec.otel block in the AutomationOrchestrator custom resource, audit events and application logs are forwarded to the configured OpenTelemetry Protocol (OTLP) endpoint.

See Installation reference for the full spec.otel field descriptions.

Important:

Telemetry data collection in automation orchestrator is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product capabilities, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

The endpoint URL must meet the following requirements:

  • HTTPS endpoints are always accepted.
  • HTTP is accepted only for loopback addresses (localhost, 127.0.0.1, ::1) and Kubernetes cluster-internal service DNS names in the format service.namespace.svc.cluster.local.
  • All other HTTP endpoints are rejected to prevent plaintext transmission of log data.

For example, to connect to an in-cluster OpenTelemetry collector:

http://ao-otel-collector.automation-orchestrator.svc.cluster.local:4318/v1/logs

For a remote endpoint outside the cluster:

https://collector.example.com:4318/v1/logs