Create a utility to automatically wire-up Open Telemetry to the Google Cloud Observability suite. #380
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.
Reduce friction to set up Open Telemetry with Google Cloud backends.
As can be seen with
tests/test_automatic.sh
, this enables auto-instrumentation like:And with manual instrumentation, it enables very simple logic like:
Compare this with the much more complicated (and incomplete/confusing) instructions found here:
Note that in addition to reducing setup friction, this provides a means of unifying configuration steps across different environments as well as across future changes in the ingestion landscape. For example, if the preferred means of ingestion were to change, the API interface here could stay the same, while changing the core implementation logic. (For implementation logic that could break clients, that could come with a change in major version, even though the code interface did not change (making it still very easy for clients to upgrade to the new ingestion path).