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

feat: option to disallow tracer to capture response as metadata #128

Conversation

heitorlessa
Copy link
Contributor

@heitorlessa heitorlessa commented Aug 22, 2020

Issue #, if available: #128

Description of changes:

  • Add capture_response parameter in both capture_lambda_handler and capture_method decorators, by default True for backward compatibility reasons
  • Docstrings clean up
  • Correct internal loggers to debug messages to a minimum (no responses)

Checklist

Added examples in the doc, and warning upfront

image

Breaking change checklist

RFC issue #:

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@codecov-commenter
Copy link

codecov-commenter commented Aug 22, 2020

Codecov Report

Merging #128 into develop will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##           develop      #128   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           24        24           
  Lines          697       701    +4     
  Branches        64        66    +2     
=========================================
+ Hits           697       701    +4     
Impacted Files Coverage Δ
aws_lambda_powertools/tracing/tracer.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ad00a92...91c05e6. Read the comment docs.

* develop:
  chore: clarify changelog bugfix vs breaking change
  chore: remove/correct unnecessary debug logs
  chore: fix debug log adding unused obj
  improv: explicitly assert not having ColdStart metric
  chore: grammar
  chore: add metrics fix description
  fix: update cold_start doc to reflect #125
  fix: split ColdStart metric to its own EMF blob #125
  chore: correct typos
@heitorlessa heitorlessa force-pushed the feat/tracer-disallow-response-metadata branch from 59c228d to adfee49 Compare August 22, 2020 19:03
@heitorlessa
Copy link
Contributor Author

heitorlessa commented Aug 23, 2020

Done - Lemme know if I missed anything else, and whether the docs are explicit enough :) @michaelbrewer

@heitorlessa heitorlessa self-assigned this Aug 23, 2020
@heitorlessa heitorlessa merged commit 3f74b03 into aws-powertools:develop Aug 23, 2020
@heitorlessa heitorlessa deleted the feat/tracer-disallow-response-metadata branch August 23, 2020 14:57
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.

3 participants