Aside from what others have mentioned (being interop on the send and receive side of things) I find a great deal of value in the interop schema, so you don't ha

Aside from what others have mentioned (being interop on the send and receive side of things) I find a great deal of value in the interop schema, so you don't have to re-learn what every joker wants to name their special unicorn flavor of kubernetes pod name or container id or http response code when exploring metrics or making dashboards https://opentelemetry.io/docs/specs/semconv/general/attributes/#server-attributes https://opentelemetry.io/docs/specs/semconv/general/attribut... https://opentelemetry.io/docs/specs/semconv/hardware/common/ https://opentelemetry.io/docs/specs/semconv/hardware/common/ https://opentelemetry.io/docs/specs/semconv/system/container-metrics/#container-metrics https://opentelemetry.io/docs/specs/semconv/system/container... https://opentelemetry.io/docs/specs/semconv/system/k8s-metrics/#k8s-metrics https://opentelemetry.io/docs/specs/semconv/system/k8s-metri... https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#http-server https://opentelemetry.io/docs/specs/semconv/http/http-metric... https://opentelemetry.io/docs/specs/semconv/cloud-providers/aws-sdk/#common-attributes https://opentelemetry.io/docs/specs/semconv/cloud-providers/...