Is your feature request related to a problem? Please describe.

Quartz is being instrumented by the OpenTelemetry Java Agent 2.18.1, but the spans created for job executions do not contain attributes identifying the trigger, job, scheduler or instance.

Describe the solution you'd like

It would be nice if the Quartz instrumentation for job executions would set the messaging attributes described in https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/:

• messaging.client.* appears to fit a Quartz instance.
• messaging.message.* could fit the Quartz trigger.
• messaging.destination.* would fit for the Quartz job.
• messaging.destination.subscription.* might fit for the Quartz scheduler?

Describe alternatives you've considered

Use the span name alone. This is not very convenient.

Additional context

This issue was focussing on job execution, which is already instrumented in principle, but is in my opinion lacking some information. I also created #14628 about installing instrumentation into additional Quartz listener hooks to provide even more information on Quartz internals.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}