[microsoft_defender_endpoint] ensure page_size configuration is preserved in CEL evaluation responses - #15467
Merged
brijesh-elastic merged 2 commits intoSep 26, 2025
Conversation
…rrectly formatted in vulnerability data stream
brijesh-elastic
added
Integration:microsoft_defender_endpoint
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Contributor
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
machine_action |
6944.44 | 4739.34 | -2205.1 (-31.75%) | 💔 |
vulnerability |
1972.39 | 1669.45 | -302.94 (-15.36%) | 💔 |
To see the full report comment with /test benchmark fullreport
efd6
changed the title
efd6
reviewed
Sep 25, 2025
Contributor
There was a problem hiding this comment.
These changes are handled in #15471. So let's back them out here.
Comment on lines
+4
to
+9
| - description: Ensure large `$skip` API parameter values are correctly formatted in `vulnerability` data stream. | ||
| type: bugfix | ||
| link: https://github.com/elastic/integrations/pull/1 | ||
| - description: 'Enhanced error handling in the CEL program for API calls to prevent "no such key: page_size" errors in the machine data stream.' | ||
| type: bugfix | ||
| link: https://github.com/elastic/integrations/pull/1 |
Contributor
There was a problem hiding this comment.
Suggested change
| - description: Ensure large `$skip` API parameter values are correctly formatted in `vulnerability` data stream. | |
| type: bugfix | |
| link: https://github.com/elastic/integrations/pull/1 | |
| - description: 'Enhanced error handling in the CEL program for API calls to prevent "no such key: page_size" errors in the machine data stream.' | |
| type: bugfix | |
| link: https://github.com/elastic/integrations/pull/1 | |
| - description: 'Ensure `page_size` configuration is preserved in CEL evaluation responses.' | |
| type: bugfix | |
| link: https://github.com/elastic/integrations/pull/15467 |
This is not really an error handing issue, this is a invariant correctness issue.
brijesh-elastic
changed the title
💚 Build Succeeded
History
|
|
Contributor
|
Package microsoft_defender_endpoint - 3.1.2 containing this change is available at https://epr.elastic.co/package/microsoft_defender_endpoint/3.1.2/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally