Remove mappings from filebeat_input_logs #7753
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
When adding
filebeat_input_metrics
, another datastreamfilebeat_input_logs
was automatically added by Fleet. More information can be found here - #5077 (comment).The
filebeat_input_metrics
has undergone mapping changes such as #7179, thus making mappings undeefilebeat_input_logs
irrelevant. Since this datastream is only a placeholder and is always empty, this PR removes the mappings for it completely.Checklist
changelog.yml
file.Note:
packages/elastic_agent/data_stream/filebeat_input_logs/fields/base-fields.yml
was not removed aspackage-spec
requires atleast 1 file underfields
folder. This file contains only base datastream fieldsdata_stream.*