My project will be developing the Zipkin Exporter for the OpenTelmetry Rust client library. OpenTelemetry aims to fix an annoying problem: monitoring framework lock-in. Agreeing on a single spec for how we should think about and represent metrics and traces makes it so that we can instrument our application and not worry about being forever-tied to a single backend. That spec is detailed here. Pretty much gives you what a standard normally gives you: portability guarantees.
Maintaining idiomatic client libraries for all the supported languages is a huge and expensive undertaking though (made more difficult by the fact that the spec tells us somewhat rigidly how the client library APIs should look and be structured, despite the fact that you'd expect an idiomatic Java API to look pretty