OpenCensus metric exporter bridge #1444
Merged
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.
Fixes #93
This allows wrapping an OpenTelemetry exporter so that it can be used with OpenCensus. This is useful to facilitate migrations from OpenCensus to OpenTelemetry, as it would allow using a mix of OpenCensus and OpenTelemetry APIs in code (and libraries), while sending all telemetry to a single exporter.
Everything was straightforward to map, except the data points themselves. To do that, I ended up having to implement custom
Aggregation
s based on the data point type.I also need to do an audit of OpenCensus functionality that is "dropped" when using the bridge and document it. Thus far, I know it drops
Summary
data points, exemplars, and some types of metric descriptors. I might do that in a follow-up.