-
Notifications
You must be signed in to change notification settings - Fork 5k
Fix default scan_frequency to 60s #44304
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
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
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.
Thank you for catching this 🙌
@Mergifyio backport 8.17 8.18 8.19 9.0 |
✅ Backports have been created
|
(cherry picked from commit b6ce2c1)
(cherry picked from commit b6ce2c1)
(cherry picked from commit b6ce2c1)
(cherry picked from commit b6ce2c1)
Proposed commit message
This PR is to fix the
scan_frequency
default value to 1 minute. It was set to10s
by mistake while all documentations said the default is1m
. For example: https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-aws-cloudwatch#_scan_frequencyThis PR also added some debug entries around start time and end time for API calls.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
I dont think so.