Semantic Conventions

Spring Boot applications instrumented with the Micrometer APIs can export telemetry data adopting specific semantic conventions. Semantic conventions define a standard set of attributes and naming rules for observations, ensuring consistency across different observability backends.

Arconia provides support for the following semantic conventions:

Auto-Activation

Convention modules auto-activate when their dependency is added to the classpath. No additional configuration property is required.

If multiple convention modules are present on the classpath, Arconia will detect the conflict at startup and fail with an actionable error message. In that case, set the arconia.observations.conventions.type property to select which convention to use.

Table 1. Observation Configuration Properties
Property	Default	Description
`arconia.observations.conventions.type`	-	When set, only the convention module matching this value activates (e.g., `opentelemetry`). When not set, convention modules auto-activate based on classpath detection.

Custom Convention Modules

You can create your own convention module by implementing the ObservationConventionsProvider interface and registering it as a Spring bean. This enables Arconia to auto-discover your module and detect conflicts with other convention modules.

@Bean
ObservationConventionsProvider myConventionsProvider() {
    return () -> "my-conventions";
}