-
Notifications
You must be signed in to change notification settings - Fork 452
symantec_endpoint: ensure that event.duration is mapped as a long #11504
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
6f40c7c
to
e1b3f42
Compare
The event.duration field does not get mapped as a long, even when there is a convert processor in place, potentially resulting in a mapping conflict. So add back a field definition for the field.
e1b3f42
to
dda6b15
Compare
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
History
cc @efd6 |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Package symantec_endpoint - 2.16.2 containing this change is available at https://epr.elastic.co/search?package=symantec_endpoint |
…astic#11504) The event.duration field does not get mapped as a long, even when there is a convert processor in place, potentially resulting in a mapping conflict. So add back a field definition for the field.
…astic#11504) The event.duration field does not get mapped as a long, even when there is a convert processor in place, potentially resulting in a mapping conflict. So add back a field definition for the field.
Proposed commit message
The event.duration field does not get mapped as a long, even when there is a convert processor in place, potentially resulting in a mapping conflict. So add back a field definition for the field.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots