-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[AI-5441] DDS: ESET Protect: Integration v1.0.0 #20349
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
[AI-5441] DDS: ESET Protect: Integration v1.0.0 #20349
Conversation
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.
Suggesting some minor documentation edits
eset_protect/assets/dashboards/eset_protect_filtered_websites_events.json
Outdated
Show resolved
Hide resolved
Review from sarah-witt is dismissed. Related teams and files:
- agent-integrations
- eset_protect/README.md
- eset_protect/assets/dashboards/eset_protect_audit_events.json
- eset_protect/assets/dashboards/eset_protect_filtered_websites_events.json
- eset_protect/assets/dashboards/eset_protect_overview.json
- eset_protect/assets/dashboards/eset_protect_threat_events.json
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. Just a couple of non-blocking questions
targetType: attribute | ||
preserveSource: false | ||
overrideOnConflict: false | ||
- type: pipeline |
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.
Just asking to better understand the intention here; not a blocking comment.
- Did you create a sub-processor to skip logs with empty user attributes while running the attribute mapper?
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.
Yes, if any user-related fields are null or empty, we will skip the usr.name
mapping.
- type: grok-parser | ||
name: Parsing the `occured` attribute to convert it into milliseconds | ||
enabled: true | ||
source: occured |
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.
just want to make sure that the source field is intentionally occured
not occurred
.
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.
In the live logs, we are getting field named occured
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 applying those changes. I've flagged a typo in the new content, and also left a couple of small suggestions that make the troubleshooting section a bit easier to visually parse. Otherwise this LGTM
* Add ESET Protect integration with assets * adding codeowners and labeler * Adding datadog checks and configuration files * Updated log pipeline * Updating log pipeline * Updating about file version * Updating log pipeline for 1 sample * Updating code owner details * Updating dashboard and pipeline * Updating log pipeline * updating logs result * Updating versions as per suggestion * Resolved review comments and updated content * Readme suggested changes --------- Co-authored-by: Kirolos Shahat <kashahat@gmail.com> 94a10ce
What does this PR do?
This is a initial release PR of ESET Protect integration including all the required assets.
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged