Bob Weinand

Hey all, I wanted to ask whether the issue still exists with 1.7.2? There have been quite a bunch of bugfixes by now on the sidecar side.

We started working on mitigating this error. This needs some refactors though and will take a bit of time.

Hey @j-fulbright, We have two sources of crashes identified within 1.4.1 (and also some with 1.4.0) and we've just released 1.4.2. Could you please confirm whether these crashes are still...

@j-fulbright Awesome, then I suppose I may close this issue?

So, if I understand it right, the goal is to specifically not trace that specific span, right? ``` \DDTrace\install_hook('Symfony\Component\Console\Application::doRun', function(\DDTrace\HookData $hook) { $hook->data = \DDTrace\install_hook('DDTrace\Integrations\Exec\ExecIntegration::createSpan', function(DDTrace\HookData $hook) { $hook->suppressCall(); });...

hook_method will also work, I'm mostly using install_hook to stuff the hook id into the $data property to remove_hook it afterwards. But suppressCall is specific to install_hook.

@orlandothoeny Ah, I see, I did not check what exactly the method is here :-) It encompasses everything, so yeah. But in that case wouldn't it be simpler to just...

It's unexpected that multiple datadog-ipc-helpers are active. At least assuming they all use the same dd-trace-php version. There is supposed to be one datadog-ipc-helper per user (as in linux uid)...

@mrtus I meant checking tcpdump and watching the payloads within a 5 second timeframe being sent to the agent (assuming you don't use the unix socket, but tcp to port...

Yes, exactly that. Part of these requests are: ``` service":"bar-deploy-worker-events","extra_services":[],"env":"prd","app_version":"8a4c567cb38fc72211608515f361389d773db68c" ``` and do these service/env/app_version tuples repeat, or is it distinct for all request within a ~5 second window? Also...