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.

Sign up for GitHub

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

Jump to bottom

[Metrics] Views API Tracking Issue #1477

Closed
dyladan opened this issue Aug 28, 2020 · 1 comment
Closed

[Metrics] Views API Tracking Issue #1477

dyladan opened this issue Aug 28, 2020 · 1 comment
Labels
waiting-for-spec

Comments

@dyladan
Copy link
Member

dyladan commented Aug 28, 2020

Ok thank you. I think this question may be closed now.
But please consider creating tracking issue for views api implementation

Originally posted by @morigs in #1465 (comment)

API OTEP: open-telemetry/oteps#89
SDK OTEP: open-telemetry/oteps#128
@AndrewGrachov AndrewGrachov mentioned this issue Oct 27, 2020
Closed
@legendecas
Copy link
Member

Closing as the metrics SDK has been refactored with the new metrics spec.

pichlermarc added a commit to dynatrace-oss-contrib/opentelemetry-js that referenced this issue Dec 15, 2023
@trentm @pichlermarc
test(instrumentation-aws-sdk): skip failing tests of @aws-sdk/client-…
196aa2d 
…sqs ReceiveMessage context handling (open-telemetry#1847)

In `@aws-sdk/client-sqs` v3.316 the SQS client methods became async. This breaks
the `utils.bindPromise` usage that attempts to propagate the SQS ReceiveMessage
span context to the user's handler for the method's returned promise.
Fixing that propagation is for open-telemetry#707 or another issue.

This change is a workaround that skips the testing of that span context
propagation feature.

Fixes: open-telemetry#1477
Refs: open-telemetry#707
Co-authored-by: Marc Pichler <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
waiting-for-spec
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dyladan @legendecas