-
Notifications
You must be signed in to change notification settings - Fork 392
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
[google_workspace] Fix pagination and filters for Report API data streams. #4982
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
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.
Has this been tested against a real endpoint?
# Use this value to be able to resume from an interrupted pagination cycle. | ||
value: '[[.last_response.url.params.Get "startTime"]]' | ||
next_start_date: | ||
# The API returns records sorted from newest to oldest, |
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.
Do we have a way to catch a change in this behaviour in the API if it happens?
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.
Opened this #5009 to not forget about doing that
Yes I tested with an environment of our own and I am waiting for confirmation from another one with more activity to validate bigger event numbers scenarios. |
Package google_workspace - 2.2.1 containing this change is available at https://epr.elastic.co/search?package=google_workspace |
What does this PR do?
Checklist
changelog.yml
file.Closes #4796