-
Notifications
You must be signed in to change notification settings - Fork 466
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
Elastic-Agent CEF Integration Mapping missing event.* fields #2805
Comments
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
I was trying to figure out how we missed this sort of issue in so many integrations. I tracked it to this line https://github.com/elastic/elastic-package/blob/a4a0b19d768eee14582acfb58a816823110a8980/internal/fields/validate.go#L266 which skips checks on
|
Relates: elastic/elastic-package#147 |
Also found
|
Several event field mappings were missing (tests do not validate event.* as per elastic/elastic-package#147). After adding those mappings some of the data types didn't match so I added a few convert processors. I modified the pipeline tests to use simulated data from the Beats decode_cef processor. Fixes: elastic#2805
PR to fix: #2808 |
Several event field mappings were missing (tests do not validate event.* as per elastic/elastic-package#147). After adding those mappings some of the data types didn't match so I added a few convert processors. I modified the pipeline tests to use simulated data from the Beats decode_cef processor. Fixes: #2805
Several event field mappings were missing (tests do not validate event.* as per elastic/elastic-package#147). After adding those mappings some of the data types didn't match so I added a few convert processors. I modified the pipeline tests to use simulated data from the Beats decode_cef processor. Fixes: elastic#2805
The CEF integration for Elastic-Agent is missing several event.(kind, id, start, & end) fields. Without this mapping, conflicts occur within the logs-* data view
The text was updated successfully, but these errors were encountered: