From a656d10bdf274b1c5ec3c39ec9eb3ce2cb4cb624 Mon Sep 17 00:00:00 2001 From: Andrew Kroh Date: Thu, 16 Sep 2021 18:38:16 -0400 Subject: [PATCH] Fix logger statement in aws-s3 input (#27982) It should have used Warnw instead of Warn because it included structured data. (cherry picked from commit a3f09763ac2a370d09df1545a43a4211c616213d) --- x-pack/filebeat/input/awss3/sqs_s3_event.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/filebeat/input/awss3/sqs_s3_event.go b/x-pack/filebeat/input/awss3/sqs_s3_event.go index e42b78e28e85..aba2c777739a 100644 --- a/x-pack/filebeat/input/awss3/sqs_s3_event.go +++ b/x-pack/filebeat/input/awss3/sqs_s3_event.go @@ -173,7 +173,7 @@ func (p *sqsS3EventProcessor) keepalive(ctx context.Context, log *logp.Logger, w // Renew visibility. if err := p.sqs.ChangeMessageVisibility(ctx, msg, p.sqsVisibilityTimeout); err != nil { - log.Warn("Failed to extend message visibility timeout.", "error", err) + log.Warnw("Failed to extend message visibility timeout.", "error", err) } } }