-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Collect Events.* fields for telemetry #107976
Conversation
@rw-access while this approach (using capital E Is there another custom fieldset name we could use that would cause less potential confusion? |
Hey @MikePaquette in my opinion, I think a new field name would actually cause more confusion. I'd rather avoid making up a new word, and right now since these alerts are EQL-based under the hood, we have consistency with the Elasticsearch EQL API response (see |
@@ -464,6 +464,7 @@ const allowlistProcessFields: AllowlistFields = { | |||
args: true, | |||
name: true, | |||
executable: true, | |||
code_signature: true, |
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.
Thanks for adding this!
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.
🚢 ⚓ 🚀 📦
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
events: allowlistBaseEventFields, | ||
// behavioral protection re-nests some field sets under Events.* (>=7.15) | ||
Events: allowlistBaseEventFields, |
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.
Looks good. Please help out with data engineering by keeping the data dictionary up to date in our pro cloud repo.
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 ✨ 🚀 🌔
* Collect Events.* fields for telemetry * Add process.code_signature
💔 Backport failed
Successful backport PRs will be merged automatically after passing CI. To backport manually run: |
That's fine RE 7.16 branch - it hasn't been cut yet. |
Summary
Collect
Events.*
fields alongsideevents.*
.We're switching this field for 7.15, because it's an Endpoint field that's not ECS, so this is historically our way of handling that to avoid potentially breaking issues down the line.
Checklist
Delete any items that are not applicable to this PR.