You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a plan to migrate the ecs mappings template provided by ElasticSearch. As one of the tasks once the templates are added the ecs.yml would be removed as mentioned in Step 4.
When the ecs.yml is removed in metrics datastream, it can be an issue since there are many fields in ecs which are dimensions field.
We need a plan on how to handle these dimensions field.
The text was updated successfully, but these errors were encountered:
As one of the tasks once the templates are added the ecs.yml would be removed as mentioned in #8542.
I think we shouldn't do that step for metric integrations. At least, we shouldn't remove fields that are marked as dimensions from the ecs/field yml files for metric integrations.
For OTel-based integrations, we can just rely on the default mappings and mark all fields in *attributes.* as a dimension.
Therefore, I don't feel like there's any urgency to come up with a solution to completely remove all field definitions for our existing metric integrations.
There is a plan to migrate the ecs mappings template provided by ElasticSearch. As one of the tasks once the templates are added the ecs.yml would be removed as mentioned in Step 4.
When the ecs.yml is removed in metrics datastream, it can be an issue since there are many fields in ecs which are dimensions field.
We need a plan on how to handle these dimensions field.
The text was updated successfully, but these errors were encountered: