[elastic_agent] Map fields for OpenTelemetry collector identifying telemetry in logs

[cmacknz]

• Relates [OTel] Include receiver-specific fields in ingested Beats documents beats#45177

{"otelcol.component.id": "filebeatreceiver", "otelcol.component.kind": "receiver", "otelcol.signal": "logs"

In https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.125.0 these fields will be added by default. If we want to query or visualize them, we will have to update our mappings for elastic agent logs to include them.

Link for OTel telemetry attributes: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/component-universal-telemetry.md#receivers

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[swiatekm]

Moving this to M2, as it's not necessary for M1.

[mauri870]

Edited the issue description to fix otelcol.component.kind that is now lowercase and also add a link to the documentation for OTel telemetry attributes.

[cmacknz]

I don't think we want to do this anymore, I think we instead want to disable these fields by default or potentially just remove them.

We'd have to map these everywhere by default, and we have no use for them in their current form. This by itself isn't a reason to remove them, but our performance comparisons have shown they have a performance cost which is a reason to not use these until they are needed:

Quoting https://github.com/elastic/ingest-dev/issues/5823#issuecomment-3510800283

After disabling processors, there was still a ~10% difference in presets in benchmark results. The uncompressed request size for beatreceiver was ~1.55 MB and for standalone beats is ~1.4 MB. This difference comes from injecting receiver specific fields here.

[cmacknz]

Closing in favor of elastic/beats#47600