-
Notifications
You must be signed in to change notification settings - Fork 442
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
[watchguard_firebox] Support email addresses in 2500-0000 and 2500-0001 events #12909
[watchguard_firebox] Support email addresses in 2500-0000 and 2500-0001 events #12909
Conversation
…01 events - Support email addresses in 2500-0000 and 2500-0001 events and append email address to related.user
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
🚀 Benchmarks reportTo see the full report comment with |
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.
why add the user_email
field? couldn't you just rename that to user.email
? i'm just curious
Oh I see what I missed, one moment.. new change coming. |
Okay, so I had forgotten to add |
|
💚 Build Succeeded
History
|
Package watchguard_firebox - 1.2.0 containing this change is available at https://epr.elastic.co/package/watchguard_firebox/1.2.0/ |
Proposed commit message
Checklist
changelog.yml
file.[ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesHow to test this PR locally
Related issues