feat: add status reporting to S3#45748
Merged
joecompute merged 65 commits intoelastic:mainfrom Aug 20, 2025
Merged
Conversation
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Contributor
Author
|
run docs-build |
joecompute
commented
Aug 6, 2025
be527cc to
af85abf
Compare
joecompute
commented
Aug 8, 2025
joecompute
commented
Aug 8, 2025
Contributor
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
1511f9f to
a3acf1c
Compare
Contributor
Kavindu-Dodan
left a comment
There was a problem hiding this comment.
Overall looks good 🙌 , I will defer my approval till we verify the concern of this comment https://github.com/elastic/beats/pull/45748/files#r2273745257
cf37ec7 to
a6f8da9
Compare
mergify bot
pushed a commit
that referenced
this pull request
Aug 20, 2025
* Add health status reporting * Move status reporter helper from CloudWatch status reporting to libbeat * Enhance status reporter helper * Fix linting issues, esp related to logging (cherry picked from commit 3ec4a35) # Conflicts: # x-pack/filebeat/input/awss3/input_benchmark_test.go # x-pack/filebeat/input/awss3/sqs_s3_event_test.go # x-pack/filebeat/input/awss3/sqs_test.go
mergify bot
pushed a commit
that referenced
this pull request
Aug 20, 2025
* Add health status reporting * Move status reporter helper from CloudWatch status reporting to libbeat * Enhance status reporter helper * Fix linting issues, esp related to logging (cherry picked from commit 3ec4a35)
This was referenced Aug 20, 2025
kaisecheng
pushed a commit
to kaisecheng/beats
that referenced
this pull request
Aug 20, 2025
* Add health status reporting * Move status reporter helper from CloudWatch status reporting to libbeat * Enhance status reporter helper * Fix linting issues, esp related to logging
joecompute
pushed a commit
that referenced
this pull request
Aug 21, 2025
* Add health status reporting * Move status reporter helper from CloudWatch status reporting to libbeat * Enhance status reporter helper * Fix linting issues, esp related to logging
joecompute
pushed a commit
that referenced
this pull request
Aug 21, 2025
* Add health status reporting * Move status reporter helper from CloudWatch status reporting to libbeat * Enhance status reporter helper * Fix linting issues, esp related to logging
6 tasks
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
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
Adds Status reporting for AWS s3 inputs (via SQS and without SQS), and moves the proxy state reporter from the awscloudwatch package out into a common package.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
None - Status reports are utilized by the Agent. In standalone mode, logs are added in Debug level
How to test this PR locally
S3 input status updated:orS3 via SQS input status updated:prefix for status changesStartup and configuration
S3 via SQS: Starting, configuring, running messages
S3 without SQS: Startup and configuration, plus with failure/stop via expired token
More degraded scenarios
S3 via SQS: Expired token
S3 without SQS: Network fault
S3 via SQS: Network fault
Related issues