Whether to follow the existing Jenkins semantic conventions, the OpenTelemetry semantic conventions or both. Default: Jenkins

⚠️ Stability Warning

The OpenTelemetry semantic conventions for CI/CD are currently at Development stability level. This means these conventions may change in future OpenTelemetry releases, potentially introducing breaking changes to attribute names and values. Monitor OpenTelemetry releases carefully and be prepared to update your observability backend configurations accordingly.

Options

Jenkins: Use only custom Jenkins-specific semantic conventions.
Jenkins + OpenTelemetry: Use both Jenkins and OpenTelemetry conventions (results in duplicate attributes). Use this option in a transition phase before switching to OpenTelemetry.
OpenTelemetry: Use only standard OpenTelemetry semantic conventions.

Jenkins metrics, spans and attributes for which no corresponding OpenTelemetry convention exists remain unchanged by these options.