Conflict for field kafka.partition between filebeat and metricbeat

[robin13]

Describe the enhancement:

Currently the template mapping for the field kafka.partition is different between filebeat (long) and metricbeat (object).

Describe a specific use case for the enhancement or feature:

With these two different types for the same field name it makes it difficult to create visualisations over filebeat and metricbeat indices on this. It would be good to standardise this (e.g. Elastic Common Schema) so that the fields are the same for both.

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[faec]

Unassigning to re-triage; this would be a breaking change and might be better routed to the integrations team at this point.

[elasticmachine]

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

[jlind23]

@masci as mentionned by @faec maybe it is worth taking it on your side WDYT?

[botelastic[bot]]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!