sourceability / instrumentation Goto Github PK

Hi :)

I'm struggling to give meaning to how data goes to Datadog. Traces & spans seems to mix the messenger:consume command, and the individual consumed messages

Here's an example :

You can see individual messages around a ~2-5s, but the first consumed one is always -5-7minutes, which is likely to be the worker process restart time (10 min),

My config is the following:

# config/sourceability_instrumentation.yaml
sourceability_instrumentation:
  profilers:
    datadog:
      enabled: true

  listeners:
    command:
      enabled: true

    messenger:
      enabled: true

#config/messenger.yaml
framework:
    messenger:
        buses:
            messenger.bus.default:
                middleware:
                    - Sourceability\Instrumentation\Messenger\ProfilerMiddleware

Am I doing something wrong? Are the messenger listener & messenger middlewares stepping on each others toes?

Symfony currently develops built-in console profiling support:

symfony/symfony#47416

To avoid confusion/conflict i think this library should warn the user if symfony 6.4 (TBD) or up is installed

This would auto-remind us to swap/cleanup this library when it's relevant

https://blackfire.io/docs/php/integrations/sdk