Background
There is no published view of which fields of the OpenTelemetry declarative configuration schema the Python implementation currently supports. This makes it hard to:
- Define "most use cases covered" for a 1.0 recommendation.
- Communicate gaps to users and vendors.
- Compare coverage against other languages (Go, Java, JS).
JS just published its matrix in open-telemetry/opentelemetry-js#6846 (tracked via open-telemetry/opentelemetry-js#6809). Python should produce the equivalent.
Proposal
A new markdown doc under opentelemetry-sdk/src/opentelemetry/sdk/_configuration/ (or docs/sdk/) mapping config schema sections — resource, propagator, tracer_provider (sampler, limits, processors, exporters), meter_provider, logger_provider, attribute_limits, etc. — to supported / partial / unsupported, with links to tracking issues for the gaps.
Sources of truth to cross-check each row against:
Output
- A
spec-conformance.md doc with the tri-state matrix.
- The SDK config README links to the matrix.
- A changelog entry under Documentation.
Part of #3631.
Background
There is no published view of which fields of the OpenTelemetry declarative configuration schema the Python implementation currently supports. This makes it hard to:
JS just published its matrix in open-telemetry/opentelemetry-js#6846 (tracked via open-telemetry/opentelemetry-js#6809). Python should produce the equivalent.
Proposal
A new markdown doc under
opentelemetry-sdk/src/opentelemetry/sdk/_configuration/(ordocs/sdk/) mapping config schema sections —resource,propagator,tracer_provider(sampler, limits, processors, exporters),meter_provider,logger_provider,attribute_limits, etc. — to supported / partial / unsupported, with links to tracking issues for the gaps.Sources of truth to cross-check each row against:
opentelemetry-sdk/src/opentelemetry/sdk/_configuration/schema.json(vendored schema)opentelemetry-sdk/src/opentelemetry/sdk/_configuration/_*.pyid_generator(feat(config): wire id_generator from declarative configuration to TracerProvider #5334),OTEL_PYTHON_*interaction (feat(config): decide OTEL_PYTHON_* env-var behaviour when OTEL_CONFIG_FILE is set #5335), metric producer (feat(config): add metric producer support to declarative config #5073), schema v1.1.0 bump (feat(config): bump declarative configuration schema to v1.1.0 #5333), env-var-to-config adapter / Phase 2 (feat(config): unify declarative and env-var configuration through a shared SDK orchestrator #5126)Output
spec-conformance.mddoc with the tri-state matrix.Part of #3631.