[Enhancement]: Propose how to "reimplement" `global_labels` we had in APM Classic with OTEL Resource attributes

[lucabelluccini]

Type of issue

Missing information

What documentation page is affected

https://www.elastic.co/docs/reference/opentelemetry/edot-sdks/

What happened?

Our Classic APM Agents offer global_labels to add custom fields to all events (e.g. Java).

We should mention how to "reproduce" the same also with EDOT SDKs.
I think the common practice for this would be using the resource attributes.

To check with engineering:

• Are the resource attributes kept in ALL the documents stored or only some of them?
• How to filter them on Kibana applications?

Users often use this attributes to separate data and use DLS to grant access to documents only to documents having a specific field:value pair.

Additional info

FYI @hegerchr

[jackshirazi]

https://www.elastic.co/docs/reference/opentelemetry/edot-sdks/java/migration#global_labels

[lucabelluccini]

Thank you @jackshirazi ! I didn't look in the migration (was quite obvious 🤦 ). And search was failing me...
I see it is in all the SDKs which supported it... We can consider this closed I think...