GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||
GeezerVison is showing github.com — feat(aws-lambda): Add span streaming support to AWS Lambda integration by ericapisani · Pull Request #6498 · getsentry/sentry-python Conversation
Member
feat(aws-lambda): Add span streaming support to AWS Lambda integration When span streaming is enabled via the trace_lifecycle experiment, use Also adds CLOUD_PLATFORM.AWS_LAMBDA constant and updates the test server Depends on getsentry/sentry-conventions#414 being Fixes PY-2307
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
When span streaming is enabled via the trace_lifecycle experiment, use sentry_sdk.traces.start_span instead of start_transaction so the function span is emitted as a span envelope item with OTel-compatible attributes (cloud.provider, cloud.platform, faas.*, aws.lambda.*). Also adds CLOUD_PLATFORM.AWS_LAMBDA constant and updates the test server helper to route span envelope items into a separate span_items list so tests can assert on streamed spans independently of error envelopes. Depends on getsentry/sentry-conventions#414 being shipped first as it introduces a number of the conventions used here Fixes PY-2307 Fixes #6005 All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Member
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ✅ Bugbot reviewed your changes and found no new issues! Comment Reviewed by Cursor Bugbot for commit 5bef11c. Configure here.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
Codecov Results 📊✅ 88442 passed | ⏭️ 6022 skipped | Total: 94464 | Pass Rate: 93.63% | Execution Time: 299m 30s 📊 Comparison with Base Branch
All tests are passing successfully. ❌ Patch coverage is 22.22%. Project has 2492 uncovered lines. Files with missing lines (1)
Coverage diff@@ Coverage Diff @@ ## main #PR +/-## ========================================== - Coverage 89.38% 89.31% -0.07% ========================================== Files 192 192 — Lines 23285 23308 +23 Branches 8002 8012 +10 ========================================== + Hits 20811 20816 +5 - Misses 2474 2492 +18 - Partials 1309 1309 — Generated by Codecov Action |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…hich they're coming in
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM! But we need to wait for the conventions PR before merging 😴
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Just merged the conventions so merging this now 😄 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
getsentry#6498) When span streaming is enabled via the trace_lifecycle experiment, use sentry_sdk.traces.start_span instead of start_transaction so the function span is emitted as a span envelope item with OTel-compatible attributes (cloud.provider, cloud.platform, faas.*, aws.lambda.*). Also adds CLOUD_PLATFORM.AWS_LAMBDA constant and updates the test server helper to route span envelope items into a separate span_items list so tests can assert on streamed spans independently of error envelopes. Depends on getsentry/sentry-conventions#414 being shipped first as it introduces a number of the conventions used here Fixes PY-2307 Fixes getsentry#6005
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Migrate aws_lambda to span first
There was an error while loading. Please reload this page.