Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Opentelemetry for scheduler

See original GitHub issue

Description

I am using quarkus-scheduler and quarkus-opentelemetry. Right now, a scheduler invocation does not create a new span.

@Scheduled(every = "1s")
    void schedule() {
        Log.info(Span.current().getSpanContext().getSpanId());
    }

This outputs 2022-11-19 17:44:16,006 INFO [org.acm.Sched] (vert.x-worker-thread-0) 0000000000000000, which is an invalid span id - no span is open at that point.

Can this please be added?

Implementation ideas

No response

Issue Analytics

State:
Created 10 months ago
Comments:7 (4 by maintainers)

Top GitHub Comments

3reactions

Postremuscommented, Nov 21, 2022

@mkouba

which version of quarkus do you use?

2.14.1.Final

Using @WithSpan works, I get a proper SpanId (like 95d38a815ef4498c).

@syr I am not using reactive code (for now), so not too woried about that. Might come in useful though when integrating some custom (company internal) components with otel. Thank you for linking that thread.!

1reaction

mkoubacommented, Nov 21, 2022

I believe that since 2.14.0.CR1 we execute the scheduled methods using the managed thread pool (for both quarkus-scheduler and quarkus-quartz).

@Postremus which version of quarkus do you use?