[Internal]: EDOT Collector setups and populated data streams

[lucabelluccini]

Description

Users are inquiring:

• Why do we need to keep 2 ES Exporters in our EDOT Configurations (ecs & otel)?
• What are the data streams which get populated when using our EDOT Configurations?
• What are the data streams which get populated when using Managed OTEL Input?
• Why I see some fields being duplicated in some documents (e.g. resource.attributes.service.name and service.name)?
• Are the data streams we are using leveraging LogsDB, TSDS, other?

Resources

This is partially related to #2162

I think we should have something similar to our old APM Storage page, but for EDOT https://www.elastic.co/docs/solutions/observability/apm/data-streams#apm-data-streams-list

I would request to have this documented officially as it has to be kept in sync with the product and it is not something which can be compensated easily with a knowledge article.

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

The Data Streams populated via Managed OTel Input might differ from local EDOT Gateway.

What release is this request related to?

N/A

Serverless release

N/A

Collaboration model

The engineering team

Point of contact.

Main contact: @raultorrecilla / @AlexanderWert / @sboomsma

Sorry for the wide ping, but I struggle to route this kind of requests - please assign/reroute as necessary.