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
This was, at the time, a decision made to prevent an explosion of fields early in Agent/Fleet's product lifecycle. Today, we have mechanisms like dynamic field limits, and can rely on ECS templates for much of the field mappings for logging data streams.
We should explore removing dynamic: false from the Elastic Agent integration's data stream mappings as an act of technical debt cleanup.
The text was updated successfully, but these errors were encountered:
Previously, we set
dynamic: false
in the mappings for the Elastic Agent integration's data streams, e.g.integrations/packages/elastic_agent/data_stream/filebeat_logs/manifest.yml
Lines 1 to 7 in 98a8e95
This was, at the time, a decision made to prevent an explosion of fields early in Agent/Fleet's product lifecycle. Today, we have mechanisms like dynamic field limits, and can rely on ECS templates for much of the field mappings for logging data streams.
We should explore removing
dynamic: false
from the Elastic Agent integration's data stream mappings as an act of technical debt cleanup.The text was updated successfully, but these errors were encountered: