Hello,
With the AWS Custom Logs you can get your custom logs from S3 buckets both by using polling mode or in combination with SQS queues, like many other integrations.
On Elastic Agent 8.16, there was a change in the input code that made the setting Maximum Concurrent SQS Messages to be ignored and have no effect, to change the number of messages that the agent needs to consume the user now needs to use the internal setting number_of_workers which is exposed in the UI as Number of Workers
This caused multiple issues in multiple integrations as this change was not reflected on the integrations, this was fixed in multiple PRs, like #13350 and #13346, but the AWS Custom Logs integration was not included.
Changing the setting Number of Workers does not have any effect, the integration still starts using the default number of 5 workers for the SQS input.
Hello,
With the AWS Custom Logs you can get your custom logs from S3 buckets both by using polling mode or in combination with SQS queues, like many other integrations.
On Elastic Agent 8.16, there was a change in the input code that made the setting Maximum Concurrent SQS Messages to be ignored and have no effect, to change the number of messages that the agent needs to consume the user now needs to use the internal setting
number_of_workerswhich is exposed in the UI as Number of WorkersThis caused multiple issues in multiple integrations as this change was not reflected on the integrations, this was fixed in multiple PRs, like #13350 and #13346, but the AWS Custom Logs integration was not included.
Changing the setting
Number of Workersdoes not have any effect, the integration still starts using the default number of 5 workers for the SQS input.