Added instructions on how to use the OTLP Exporter for dash0
Comment From: philwebb
Thanks for the suggestion, but I'm not sure that we should update our documentation with OpenTelemetry compatible implementations. Since it's a drop-in replacement, I think our existing OpenTelemetry documentation should be enough.
Comment From: wilkinsona
I've opened https://github.com/spring-projects/spring-boot/issues/43727 to update the docs to talk about OTLP rather than OpenTelemetry.
Comment From: CodingFabian
The alternative would be to create a dash0 metric registry and exporter. then it gets a place on the documentation page like all the others. right?
Comment From: wilkinsona
I can't speak for the Micrometer team but I think that's quite unlikely to happen when the existing OTLP registry serves the same purpose.
Comment From: CodingFabian
of course I am poking the bear here, but most of the listed vendors support OTLP too. So apparently having OTLP support doesn't rule out a custom implementation and listing
Comment From: bclozel
I guess other vendors ship proprietary data formats in addition to supporting OTLP and that explains the specific registry. If I understand correctly, dash0 markets itself as fully OpenTelemetry compliant with no proprietary format. Why require a vendor-specific registry then?
If you're looking to promote dash0, I don't think adding a code snippet in our reference documentation is going to help. Right now searching for "dash0 Spring Boot" returns zero relevant result in my search engine.
I did notice a recent spring-demo app in the dash0 org but it actually uses the paketo-buildpacks/opentelemetry, so the OpenTelemetry Java agent to instrument the application. This is not an invalid combination but it's not the one we support officially and it won't produce the observations documented in the Spring projects. I would suggest promoting this sample and other content before considering this approach.