Infer resource type based on conventions for export to Google Cloud Monitoring (Stackdriver) #581
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.
Description:
Reverse mapping from OpenTelemetry's semantic conventions to OpenCensus resource type.
Since OpenTelemetry has switched to using semantic conventions over explicit resource types, the resource type may now be missing when converted to OpenCensus resource.
In that case we will try to infer the resource type based on documented conventions.
Link to tracking Issue:
The issue has been originally discussed in open-telemetry/opentelemetry-python#951 (comment), pointing to inconsistency between OpenCensus and OpenTelemetry which needs to be addressed.
Testing: Unit tests added for new functionality
Documentation: No documentation needed, we may just refer to the already documented semantic conventions.
/cc @james-bebbington @aabmass