Map unmapped fields in ES monitoring template

[philippkahr]

Closes:

• elasticsearch.node.stats.indices.shard_stats.total_count missing in ES monitoring template #114470

1. I run a 8.19 cluster in cloud
2. Activated monitoring
3. Waited a bit and checked the unmapped fields in Kibana which was over ~60 fields.
4. Turned on dynamic mapping with a strings as keyword dynamic template.
5. Rolled over and waited a bit.
6. Copied the created template, cleaned it up from unnecessary fields [1]
7. Copied the created template over the .monitoring-es-mb template.
8. Deleted all the data streams
9. Watch data come in.
10. Kibana reports a total of 580 fields mapped [2]

[1]: Per default there will be a new object created for each node id. Thus an unnecessary field such as elasticsearch.cluster.stats.state.nodes. <node-id>.attributes.logical_availability_zone will be mapped.
[2]:

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• If submitting code, have you built your formula locally prior to submission with gradle check?
• If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
• If submitting code, have you checked that your submission is for an OS and architecture that we support?
• If you are submitting this code for a class then read our policy for that.

[elasticsearchmachine]

@philippkahr please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.