-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filebeat system visualisation do not use ECS #11859
Comments
I agree the searches and visualizations should still use the custom fields. Here's what happened. My initial PR #9138 to migrate the system module did migrate this field to the ECS field But later, we decided to use a few of the event fields for guided categorization, and We should indeed address this for the next patch release, should be straightforward to fix. |
Hmmm, it seems like the ecs-migration.yml file doesn't contain this incorrect mapping anymore. I'll fix the dashboards directly. |
Fix for master is up: #11936. I'll backport to 7.0 as soon as it's merged. The incorrect entry is no longer in ecs-migration.yml, as already mentioned. The list of breaking changes doesn't seem to contain this incorrect migration either. So I only really had to fix the dashboard itself. |
Thanks for the fix Mat. |
@webmat Not sure why this was reopend? Both PR's are merged. |
Hmmm, it got auto-closed by my first merge to master, which was incorrect. I reopened temporarily, but I assumed the merge of the backport would close it again. Looks like it didn't :-) Closing now |
With 7.0, some Filebeat system visualisation do not work, as they do not use proper ECS fields.
Specifically the visualisation:
These visualisations should filter on field
system.auth.ssh.event
rather thanevent.action
.The text was updated successfully, but these errors were encountered: