Attention: ADOT Collector v0.41.0 breaking changes - third party exporter deprecation

[vasireddy99]

What is changing?

Last year we shared out intention to unify egress using the OpenTelemetry Protocol (OTLP) exporter. Now, we’re starting to implement this: the AWS Distro for OpenTelemetry (ADOT) collector will start deprecating third party exporters starting from v0.39.0 . The OTLP Exporter helps standardize how data can be exported from ADOT, ensuring minimal security risks and providing the reliable support that you expect from ADOT.

What do I need to do if I’m using third party components?

You are affected if you are using one of the following exporters present in the ADOT collector:

• logzio
• sapm
• signalfx

You can enable the functionality behind the feature gate, you can pass the --feature-gates=-adot.exporter.<component-name>.deprecation in the command line parameter.

In ADOT Collector v0.39.0, the feature gate is disabled by default. In the Collector v0.40.0, this feature gate will be enabled by default. Starting from v0.41.0 of the ADOT Collector, third-party exporters will be deprecated.

The Datadog exporter is also behind a feature gate, and this feature gate is disabled by default in v0.39.0. However, it won't be moved to the next stages of deprecation in v0.40.0 at this point.

[eduardoasantana]

Is the ADOT team aware of any breaking changes in v0.39.0 that would affect third party exporters not listed here?

We are instrumenting our ECS services with the ADOT collector sidecar and using the Datadog exporter to send APM metrics and traces to Datadog.

When we updated some of our services from v0.38.2 to v0.39.0, the collector stopped sending APM metrics to Datadog entirely. Traces were still being sent successfully however.

We didn't get any errors logged from the aws-otel-collector sidecar container. The sidecar started up without issue as well

[Aneurysm9]

When we updated some of our services from v0.38.2 to v0.39.0, the collector stopped sending APM metrics to Datadog entirely. Traces were still being sent successfully however.

We didn't get any errors logged from the aws-otel-collector sidecar container. The sidecar started up without issue as well

Can you please create a support case so that you can confidentially share configuration and log information with us.