Why is the OpenTelemetry Quartz package still in beta after so many years?

[sharpzilla]

Could you please kindly clarify what exactly the package is still missing or lacking in order to finally graduate from beta to a stable production-ready release? Also, would it be possible to share whether there is any official roadmap or timeline available regarding when we might expect the Quartz instrumentation for OpenTelemetry to become fully stable?"

[martincostello]

Originally posted here: open-telemetry/opentelemetry-dotnet#7070 (comment)

The OpenTelemetry.Instrumentation.Quartz package is in a different repository, but I'll answer the question here.

Typically, there are two reasons for a package not to have a stable version yet:

1. It's in active development still - it isn't "done" (for example our OpAMP client)
2. It implements a Semantic Convention that itself is not yet stable (for example, the OpenTelemetry.Instrumentation.Wcf which implements the non-stable RPC semantic conventions).

Looking at the CHANGELOG, my guess is that it could be both - it doesn't look like any major feature development has happened to the package since it was added.

If the Quartz instrumentation is lacking features and/or needs to be stabilised, feel free to contribute to that effort if it's something that's important to you. Alternatively you could create an issue requesting that in the repository that code lives in, and someone else who is invested in improving that situation might be interested in contributing it.

TL;DR - there's no official roadmap or timeline for this package to become stable.