Deprecate the exporters and related artifacts#441
Conversation
psx95
force-pushed
the
release-minor-version
branch
from
6d7912b to
6507068
Compare
psx95
changed the title
psx95
force-pushed
the
release-minor-version
branch
from
50e8f0d to
ab54b0d
Compare
There was a problem hiding this comment.
This seems duplicative of https://docs.cloud.google.com/trace/docs/migrate-to-otlp-endpoints
do we need both ?
There was a problem hiding this comment.
The trace one is, but this document has a little more information. Eventually we plan to update https://docs.cloud.google.com/trace/docs/migrate-to-otlp-endpoints and have that as single source of truth.
psx95
force-pushed
the
release-minor-version
branch
from
5ab431e to
a3d1df2
Compare
| } | ||
| ``` | ||
|
|
||
| #### 4. Adding Attributes |
There was a problem hiding this comment.
Not sure some of these points are neccessary. Why do we need to tell people how to add attributes?
There was a problem hiding this comment.
This is assuming the people migrating are not familiar with OpenTelemetry API and so the guide walks through some of the common usages.
It also serves as pre-cursor to resource attributes which is an important concept for a successful export.
3 participants
This PR marks the public APIs of the artifacts released from this repository as deprecated and also emits deprecation warnings during runtime in form of logs in case any of these artifacts are used in an application.
The PR also adds a migration guide, which will hold instructions for users to follow while moving from the OpenTelemetry Google Cloud Monitoring and Trace exporters to OpenTelemetry OTLP exporters.