OpenTelemetry observations
Use supported OTEL interfaces alongside the institution’s existing instrumentation.
#Coexistence with existing OTEL
The SDK uses official OpenTelemetry dependencies and manages its own provider. It does not replace the institution’s global provider, sampler or exporter. Actual span attributes, events, links, status and dropped-item counts can be recorded.
#Observer and native context
observerContext represents Sigillum observation relationships; nativeContext represents the official provider’s actual span relationships. Different IDs are not presented as equivalent. Automatic source or tool observations do not justify inventing additional business steps.
#Enrich a span
Use set_otel_attribute, add_otel_event and add_otel_link in Python; TrySetOtelAttribute, TryAddOtelEvent and TryAddOtelLink in .NET; and the scope’s span() interface in Java. Keep exact decimal values in raw JSON when OTEL primitive types cannot represent them faithfully.
#Collector integration boundary
The SDK’s documented OTEL support does not turn every institutional Collector or exporter into an authorised Sigillum receiver. Configure any supported internal Collector integration against its delivered ingestion contract. This documentation does not invent an OTLP endpoint or a universal Collector YAML configuration.