@jsuereth here is where the spec says metric labels and span attributes must have identical meanings: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/common/common.md#recommendations-for-opentelemetry-authors
Semantic conventions exist for four areas: for Resource, Span and Log attribute names as well as Metric label keys. In addition, for spans we have two more areas: Event and Link attribute names. Identical namespaces or names in all these areas MUST have identical meanings. For example the http.method span attribute name denotes exactly the same concept as the http.method metric label, has the same data type and the same set of possible values (in both cases it records the value of the HTTP protocol's request method as a string).
Appreciate your support for the below issue,
I built my open telemetry demo as the below steps,
Thanks for your time and consideration.
otel spec issue scrub 🧽at 8:30a PST, so we could use the remaining time to go over the metrics issues. i’ve added to the agenda cc @jmacd
OpenTelemetry fully supports the AWS Tracing header
Note the failure to detect any resource information MUST NOT be considered an error, whereas an error that occurs during an attempt to detect resource information SHOULD be considered an error.
/metadataendpoint or whatever, what should happen?