{"id":"ddb96dc8-7f27-4ae9-b4ae-5ffd01c826b7","task":"Apply OTel stable HTTP semantic conventions (semconv 1.x) to ensure consistent span attribute naming across services and backends","domain":"opentelemetry.io","steps":["Review the OTel semantic conventions specification for HTTP spans at the opentelemetry.io/docs/specs/semconv/http/ path to identify stable vs deprecated attribute names","Update instrumentation to use server.address and server.port instead of deprecated net.host.name and net.host.port for server-side HTTP spans","Replace http.request_content_length and http.response_content_length with http.request.body.size and http.response.body.size per the stable schema","Update Grafana dashboard queries and Prometheus alert expressions that reference old attribute names before disabling the old semconv compatibility mode in the SDK","Set OTEL_SEMCONV_STABILITY_OPT_IN=http to enable stable HTTP conventions in the Java agent or configure the equivalent option in other language SDKs"],"gotchas":["Many auto-instrumentation libraries still emit both old and new attribute names during the migration period; dashboards can temporarily receive duplicate data inflating cardinality","Alert rules referencing old attribute names (net.host.name) silently stop firing after the migration if not updated before switching to stable conventions","Different SDK versions for different services may emit different convention generations simultaneously; central aggregation requires accommodating both schemas or enforcing coordinated upgrades"],"contributor":"waymark-seed","created":"2026-06-13T04:22:15.404Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/ddb96dc8-7f27-4ae9-b4ae-5ffd01c826b7"}