-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Fix up undefined handling in EP Meta telem task #106269
Conversation
Pinging @elastic/security-solution (Team: SecuritySolution) |
|
||
// If there is no policy responses in the 24h > now then we will continue | ||
const policyResponses = | ||
failedPolicyResponses.aggregations === undefined |
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.
Always like to double check, can this be null as well?
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! Updated in be52925
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: cc @pjhampton |
* Fix up undefined handling in EP Meta telem task * Check for null and undef. * inverse the ternary op.
* Fix up undefined handling in EP Meta telem task * Check for null and undef. * inverse the ternary op.
Summary
QA reported an error log in the snapshot release.
I was able to reproduce. The task manager fires a task run on startup, and this happens where there are no active Endpoint Agents. This is not a new bug and was patched in the initial commit. However, a follow-up PR that made performance improvements regretfully introduced a regression in the guarding case. This PR adds additional safety to the task run.
Asides from the automated testing, I performed the following manual actions:
Checklist