Skip to content

Conversation

@calavera
Copy link
Contributor

Issue #, if available:

Fixes #821

Description of changes:

Implement Lambda's advance logging controls:

Provide a feature that exposes a initialization function for tracing-subscriber that sets the right logging controls based on Lambda's configuration.
The feature is enabled by default, but it can be disabled if a user doesn't want to use it.

By submitting this pull request

  • I confirm that my contribution is made under the terms of the Apache 2.0 license.
  • I confirm that I've made a best effort attempt to update all relevant documentation.

Provide a feature that exposes a initialization function for `tracing-subscriber` that sets the right logging controls based on Lambda's configuration.
The feature is enabled by default, but it can be disabled if a user doesn't want to use it.

Signed-off-by: David Calavera <david.calavera@gmail.com>
@calavera calavera requested a review from bnusunny February 26, 2024 01:11
Signed-off-by: David Calavera <david.calavera@gmail.com>
@calavera calavera force-pushed the advanced_logging_controls branch from bf24a5f to 6a44953 Compare February 26, 2024 01:13
It makes logs too verbose.

Signed-off-by: David Calavera <david.calavera@gmail.com>
Signed-off-by: David Calavera <david.calavera@gmail.com>
Identify the dependency as the top dependency.

Signed-off-by: David Calavera <david.calavera@gmail.com>
Signed-off-by: David Calavera <david.calavera@gmail.com>
@aws aws deleted a comment from github-actions bot Feb 26, 2024
@calavera calavera merged commit f51589c into main Feb 26, 2024
@calavera calavera deleted the advanced_logging_controls branch February 26, 2024 03:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for lambda advanced logging controls

2 participants