Skip to content
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

Cherry-pick #17220 to 7.6: Fix CEF processor mapping exception #17229

Merged
merged 1 commit into from
Mar 24, 2020

Conversation

adriansr
Copy link
Contributor

@adriansr adriansr commented Mar 24, 2020

Cherry-pick of PR #17220 to 7.6 branch. Original message:

Extensions spriv/dpriv were mapped to {source|destination}.user.group instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that used those extensions.

Fixes #17216

What does this PR do?

Fixes the CEF decoder mapping of spriv/dpriv extensions to {source|destination}.user.groupinstead of{source|destination}.user.group.name`.

Why is it important?

This caused a mapping exception when attempting to ingest CEF logs that used those extensions.

Checklist

  • [ ] My code follows the style guidelines of this project
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works

Related issues

Fixes #17216

Extensions spriv/dpriv were mapped to {source|destination}.user.group
instead of {source|destination}.user.group.name.

This caused a mapping exception when attempting to ingest CEF logs that
used those extensions.

Fixes elastic#17216

(cherry picked from commit 99f483e)
Copy link
Contributor

@leehinman leehinman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@adriansr adriansr merged commit 6c7567c into elastic:7.6 Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants