Skip to content

Conversation

@dreamorosi
Copy link
Contributor

Description of your changes

After some feedback raised by a user we have realised that it's not exactly explicit that Active Tracing should be enabled in your Lambda function in order to see traces in X-Ray. This PR adds a sentence to the already existing note about permission to make this detail explicit in an effort to reduce confusion for future users who might not be familiar with the service.

How to verify this change

See the diff, only added a sentence.

Related issues, RFCs

N/A

PR status

Is this ready for review?: YES
Is it a breaking change?: NO

Checklist

  • My changes meet the tenets criteria
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • The code coverage hasn't decreased
  • New and existing unit tests pass locally and in Github Actions
  • The PR title follows the conventional commit semantics

Breaking change checklist

N/A


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

@dreamorosi dreamorosi added documentation Improvements or additions to documentation tracer This item relates to the Tracer Utility labels Jun 30, 2022
@dreamorosi dreamorosi requested review from flochaz and saragerion June 30, 2022 12:15
@dreamorosi dreamorosi self-assigned this Jun 30, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jun 30, 2022

📊 Package size report   No changes

File Before After
Total (Includes all files) 140.7 kB 140.7 kB
Tarball size 139.6 kB 0%↑139.6 kB
Unchanged files
File Size
aws-lambda-powertools-commons-0.11.1-rc.0.tgz 6.5 kB
aws-lambda-powertools-logger-0.11.1-rc.0.tgz 23.8 kB
aws-lambda-powertools-metrics-0.11.1-rc.0.tgz 17.5 kB
aws-lambda-powertools-tracer-0.11.1-rc.0.tgz 21.5 kB
commons-bundle.zip 7.1 kB
logger-bundle.zip 24.3 kB
metrics-bundle.zip 18.1 kB
tracer-bundle.zip 22.0 kB

🤖 This report was automatically generated by pkg-size-action
(options hash: 83ccbc11cd1ec7ebc4fec007747c81b1)

!!! note
Before your use this utility, your AWS Lambda function [must have permissions](https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html#services-xray-permissions) to send traces to AWS X-Ray.
Before your use this utility, your AWS Lambda function must have
[Active Tracing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

new lines ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, fixed in the latest commit

Screenshot 2022-07-04 at 10 53 06

@dreamorosi dreamorosi requested a review from flochaz July 4, 2022 08:54
@github-actions
Copy link
Contributor

github-actions bot commented Jul 4, 2022

📊 Package size report   No changes

File Before After
Total (Includes all files) 140.7 kB 140.7 kB
Tarball size 139.5 kB 0.02%↑139.6 kB
Unchanged files
File Size
aws-lambda-powertools-commons-0.11.1-rc.0.tgz 6.5 kB
aws-lambda-powertools-logger-0.11.1-rc.0.tgz 23.8 kB
aws-lambda-powertools-metrics-0.11.1-rc.0.tgz 17.5 kB
aws-lambda-powertools-tracer-0.11.1-rc.0.tgz 21.5 kB
commons-bundle.zip 7.1 kB
logger-bundle.zip 24.3 kB
metrics-bundle.zip 18.1 kB
tracer-bundle.zip 22.0 kB

🤖 This report was automatically generated by pkg-size-action
(options hash: 8d7ba95184e17420bc12570dde3c4ae2)

@dreamorosi dreamorosi merged commit 7561afc into main Jul 5, 2022
@dreamorosi dreamorosi deleted the docs/clarify_active_tracing branch July 5, 2022 10:18
dreamorosi added a commit that referenced this pull request Aug 2, 2022
* docs: added note about active tracing

* fix: extra lines
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation tracer This item relates to the Tracer Utility

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants