feat: add Instana propagator #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
basti1302
force-pushed
the
propagator-instana
branch
2 times, most recently
from
5206ce7 to
53499ca
Compare
basti1302
commented
Jul 5, 2022
basti1302
force-pushed
the
propagator-instana
branch
from
53499ca to
432c7fa
Compare
kirrg001
reviewed
Jul 5, 2022
propagators/opentelemetry-propagator-instana/src/InstanaPropagator.ts
Outdated
Show resolved
Hide resolved
basti1302
force-pushed
the
propagator-instana
branch
2 times, most recently
from
8f093a1 to
3d23dd6
Compare
basti1302
force-pushed
the
propagator-instana
branch
from
3d23dd6 to
ad52250
Compare
kirrg001
approved these changes
Jul 5, 2022
|
The actual PR for upstream is here now: open-telemetry#1081. Closing this as the review is completed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: THIS PR IS JUST FOR INTERNAL REVIEW PURPOSES. We do not intend to merge this PR into the main branch in this forked repo. Instead, we will open a PR on the upstream repository.
Which problem is this PR solving?
Short description of the changes
Checklist
npm run test-all-versionsfor the edited package(s) on the latest commit if applicable.