Instrumentation scope attributes support in exporters

[jade-guiton-dd]

Context

As part of improving the Collector's internal telemetry, we are planning to make use of instrumentation scope attributes to help users identify which component instance produced a metric stream, log record, or span. (See tracking issue for more context.)

Compared to resource and item-level attributes, instrumentation scope attributes have seen little use until now, so we expect many community exporters to lack support for ingesting them and making them visible to users on the backend. This issue is meant to track the current status of instrumentation scope attribute support among the exporters in opentelemetry-collector-contrib.

If you are a code owner, feel free to ping me so I can update the status of your exporter and link to any relevant issues/PRs.

Exporter status

	Meaning
🟥	Not planned
🟪	Planned / In progress
🟧	Partial support (eg. only some signals)
🟩	Supported

Exporter	Status	Notes / Relevant links
datadog	🟩	Logs: supported since v0.125 Metrics: supported since v0.125 (toggled by instrumentation_scope_metadata_as_tags option, which defaults to true since v0.126) Traces: supported since v0.128
elasticsearch	🟩	Supported in default "mapping mode" (ElasticSearch document schema)
zipkin	🟪	Contrib issue for traces

[axw]

The Elasticsearch exporter supports scope attributes in its default "mapping mode" (Elasticsearch document schema). e.g.

I don't think there's a specific issue/PR to link.