Skip to content
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

Improve Debug Logging #59

Closed
robbavey opened this issue Sep 21, 2021 · 1 comment · Fixed by #61
Closed

Improve Debug Logging #59

robbavey opened this issue Sep 21, 2021 · 1 comment · Fixed by #61

Comments

@robbavey
Copy link
Contributor

Determining the source of any connection errors in this plugin is tricky, due to the lack of debugging in the plugin, with little to no debug logging to understand where issues are happening.

As well as a lack of plugin level logging, this plugin does not provide any ability to provide wire level tracing via passing additional_settings through to the underlying library that is used to connected to SQS - see https://www.elastic.co/guide/en/logstash/current/plugins-inputs-s3.html#plugins-inputs-s3-additional_settings for an example.

By including additional_settings, the user is able to change the log level of the AWS SDK, and also set http_wire_trace to track the requests to/from AWS. See https://docs.aws.amazon.com/sdk-for-ruby/v2/api/Aws/SQS/Client.html#initialize-instance_method for details of applicable additional_settings

@andsel
Copy link
Contributor

andsel commented Feb 14, 2022

Fixed with v3.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants