You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SemconvStability still reflects the older semconv declarative config shape, while newer declarative semconv config support has landed upstream.
This should be aligned first, separately from the broader ConfigPropertiesUtil / library-instrumentation cleanup.
Recommendation
Update SemconvStability to support the newer declarative semconv config model.
For 3.0, remove the legacy semconv declarative shape from SemconvStability for domains covered by the newer declarative model (db, code, rpc, messaging).
Keep flat-property fallback for compatibility for now.
Summary
SemconvStabilitystill reflects the older semconv declarative config shape, while newer declarative semconv config support has landed upstream.This should be aligned first, separately from the broader
ConfigPropertiesUtil/ library-instrumentation cleanup.Recommendation
SemconvStabilityto support the newer declarative semconv config model.SemconvStabilityfor domains covered by the newer declarative model (db,code,rpc,messaging).service.peerseparately in Decide how service.peer semconv should map to declarative config #18933.Why separate from #15810
This is not really a library-instrumentation cleanup item; it is semconv config evolution / alignment work.