-
Notifications
You must be signed in to change notification settings - Fork 489
[ECS] Cleaning up incorrect invalid ECS field usages at root-level #7965
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
Conversation
🌐 Coverage report
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Package azure_frontdoor - 1.3.2 containing this change is available at https://epr.elastic.co/search?package=azure_frontdoor |
Package carbonblack_edr - 1.14.1 containing this change is available at https://epr.elastic.co/search?package=carbonblack_edr |
Package cisco_meraki - 1.15.1 containing this change is available at https://epr.elastic.co/search?package=cisco_meraki |
Package juniper_srx - 1.16.1 containing this change is available at https://epr.elastic.co/search?package=juniper_srx |
Package netflow - 2.15.1 containing this change is available at https://epr.elastic.co/search?package=netflow |
What does this PR do?
Removing the unused and incorrect ECS field usages at the root-level for the following packages:
Note: this is purely a docs change
Checklist
changelog.yml
file.Related issues