-
Notifications
You must be signed in to change notification settings - Fork 792
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
merge base into api #968
Labels
Discussion
Issue or PR that needs/is extended discussion.
Comments
I think those can be moved into |
core works fine too |
pichlermarc
pushed a commit
to dynatrace-oss-contrib/opentelemetry-js
that referenced
this issue
Dec 15, 2023
…pen-telemetry#968) * test(instrumentation-aws-sdk): make sure that message id attribute is set on send command * fix(instrumentation-aws-sdk): set message id on send command * style(instrumentation-aws-sdk): lint fixes * chore(instrumentation-aws-sdk): use optional chaining in case data is null * test(instrumentation-aws-sdk): cover sdk v2 sqsResponseHook messaging attributes * style: lint fix * test(instrumentation-aws-sdk): make sure correct http status code is used * test(instrumentation-aws-sdk): rename test to inlcude sendMessage Co-authored-by: Amir Blum <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the package
base
has just one constant andExportResult
which is a bit weird to be a standalone package, should we simply include this intoapi
?The text was updated successfully, but these errors were encountered: