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
Known 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
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp