Disable automatic tracing for command

[ptondereau]

I have a use case when my Symfony command are some kinds of worker.
In this context, I want to avoid waiting for my command to finish and only trace the part I want to.
WDYT?

[cawolf]

Hi @ptondereau ,
we also have this use case and kind of worked around it by just ignoring the wrapping command traces and just ensuring, that the "inner" spans (which are linked to other parent traces from different services) are flushed to the tracer. We are using the internal Auxmoney\OpentracingBundle\Internal\Opentracing interface to get access to the OpenTracing\Tracer instance and flush after each span manually.

However, we can imagine having this as a "regular" feature, maybe by decorating a long running command with a marker interface and querying for this interface in the appropriate event subscribers.

Currently, we are focusing primarily on upgrading the bundle, and are looking for help with implementing new features. Would you yourself like to take a shot? If not, any help is welcome. :)

[ujwaldhakal]

are these handle by this File ?
For me I had to listen to these events manually & finish the active span from my Symfony code

[cawolf]

Yes, @ujwaldhakal , this subscriber opens the root span for each Command. The FinishCommandSpanSubscriber is its counterpart.

[pronata]

Hi @cawolf

What if add in subscribers some filter function by command name not to begin trace automatically?

[pronata]

I found the solution through decorators (decorating StartCommandSpanSubscriber and FinishCommandSpanSubscriber by adding exclusions there).