NH-9150 Use oboe_api functions for no default timestamp #13
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
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.
Change custom Exporter to use oboe_api functions for no default timestamp, added in this oboe PR: https://github.com/librato/oboe/pull/889 This is so Python custom-distro can report events with the timestamps calculated by OTel.
Distributed test trace was successfully exported to AO prod: https://my.appoptics.com/apm/123092/services/django-app-b-ot/traces/BF810AC1D84519621647B5D0983F022C00000000/graph
This PR is pointed at
add-custom-propagatorbranch for now, until that one's merged tomain.