Describe the feature request
Dynatrace is transitioning to use the OpenTelemetry tracer in Envoy to collect spans from Envoy. The reason for this is: our integration with Envoy today rely on the OpenTracing tracer, which is deprecated and will be removed soon.
Dynatrace supports ingesting OpenTelemetry Protocol data (OTLP) only over HTTP. As a prerequisite for this transition, I worked on getting a HTTP exporter in Envoy. The HTTP exporter is merged and will be part of Envoy version 1.28 . So now, Dynatrace customers can send Envoy spans to Dynatrace via HTTP.
The majority of our customers though uses Envoy "via" Istio. As part of this transition we would be glad if we could introduce a Dynatrace Tracing Extension to Istio.
Our proposal is to Introduce a new tracing extension that "wraps" and uses the OpenTelemetry tracer under the hood. The reason for going this route is to make the configuration easier for our customers. For example, to send spans to Dynatrace they need to configure the correct URL and Authorization API token as a header, which can be error prone and cumbersone. With our extension, we can hide all this complexity from our customers and let them focus on the minimal parts (their SaaS URL + access token).
There is already precedence in Istio for such approach, with the Lightstep extension wrapping the OTel tracer.
Additionally, we are also working on extra extensions on Envoy's OpenTelemetry tracer to be able to configure Resource Detectors and a Sampler. These are concepts that exist in OpenTelemetry and further allow for proper enrichment/correlation of data + allowing them to better configure the volume of data exported, which is crucial for cost management.
With our Dynatrace extension in Istio, we can then also configure for our customers the Dynatrace resource detector + Sampler. If we would rely purely on the OTel extension in Istio, our customers would have to configure all of this themselves, which is not optimal.
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
Opening this official issue as discussed on Slack with Jianpeng He.
Describe the feature request
Dynatrace is transitioning to use the OpenTelemetry tracer in Envoy to collect spans from Envoy. The reason for this is: our integration with Envoy today rely on the OpenTracing tracer, which is deprecated and will be removed soon.
Dynatrace supports ingesting OpenTelemetry Protocol data (OTLP) only over HTTP. As a prerequisite for this transition, I worked on getting a HTTP exporter in Envoy. The HTTP exporter is merged and will be part of Envoy version 1.28 . So now, Dynatrace customers can send Envoy spans to Dynatrace via HTTP.
The majority of our customers though uses Envoy "via" Istio. As part of this transition we would be glad if we could introduce a Dynatrace Tracing Extension to Istio.
Our proposal is to Introduce a new tracing extension that "wraps" and uses the OpenTelemetry tracer under the hood. The reason for going this route is to make the configuration easier for our customers. For example, to send spans to Dynatrace they need to configure the correct URL and Authorization API token as a header, which can be error prone and cumbersone. With our extension, we can hide all this complexity from our customers and let them focus on the minimal parts (their SaaS URL + access token).
There is already precedence in Istio for such approach, with the Lightstep extension wrapping the OTel tracer.
Additionally, we are also working on extra extensions on Envoy's OpenTelemetry tracer to be able to configure Resource Detectors and a Sampler. These are concepts that exist in OpenTelemetry and further allow for proper enrichment/correlation of data + allowing them to better configure the volume of data exported, which is crucial for cost management.
With our Dynatrace extension in Istio, we can then also configure for our customers the Dynatrace resource detector + Sampler. If we would rely purely on the OTel extension in Istio, our customers would have to configure all of this themselves, which is not optimal.
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
Opening this official issue as discussed on Slack with Jianpeng He.