-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] aws-s3: Stop calling ChangeMessageVisibility after ReceiptHandleIsInvalid #29480
[Filebeat] aws-s3: Stop calling ChangeMessageVisibility after ReceiptHandleIsInvalid #29480
Conversation
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Stop the keepalive goroutine after ErrCodeReceiptHandleIsInvalid is returned by ChangeMessageVisibility. Add `message_receipt_time` to log messages associated with processing of a given SQS message. Fix incorrect error being wrapped when ApproximateReceiveCount threshold is reached.
This pull request does not have a backport label. Could you fix it @andrewkroh? 🙏
NOTE: |
9105c79
to
8581e16
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
…9480) Stop the keepalive goroutine after ErrCodeReceiptHandleIsInvalid is returned by ChangeMessageVisibility. Add `message_receipt_time` to log messages associated with processing of a given SQS message. Fix incorrect error being wrapped when ApproximateReceiveCount threshold is reached. (cherry picked from commit a0ef4d3)
…9480) (#29485) Stop the keepalive goroutine after ErrCodeReceiptHandleIsInvalid is returned by ChangeMessageVisibility. Add `message_receipt_time` to log messages associated with processing of a given SQS message. Fix incorrect error being wrapped when ApproximateReceiveCount threshold is reached. (cherry picked from commit a0ef4d3) Co-authored-by: Andrew Kroh <[email protected]>
@Mergifyio backport 7.17 |
…9480) Stop the keepalive goroutine after ErrCodeReceiptHandleIsInvalid is returned by ChangeMessageVisibility. Add `message_receipt_time` to log messages associated with processing of a given SQS message. Fix incorrect error being wrapped when ApproximateReceiveCount threshold is reached. (cherry picked from commit a0ef4d3)
✅ Backports have been created
|
…HandleIsInvalid (backport #29480) (#29497) * Stop calling ChangeMessageVisibility after ReceiptHandleIsInvalid (#29480) Stop the keepalive goroutine after ErrCodeReceiptHandleIsInvalid is returned by ChangeMessageVisibility. Add `message_receipt_time` to log messages associated with processing of a given SQS message. Fix incorrect error being wrapped when ApproximateReceiveCount threshold is reached. (cherry picked from commit a0ef4d3) Co-authored-by: Andrew Kroh <[email protected]>
What does this PR do?
This reduced log noise and unnecessary API calls from the aws-s3 input.
message_receipt_time
to log messages associated with processing of a given SQS message.Why is it important?
ReceiptHandleIsInvalid warnings become very noisy in Filebeat logs.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.