Marco Costa
Marco Costa
Seems like a more than reasonable request, @benrbrook. I'll add it to our roadmap. Given how small the required changes seem to be, I expect that we'll be able to...
GC cannot be attributed to a single Ruby thread because it's a global VM event. This means that we can attribute it to a specific trace: affects all traces active...
Thank you for this issue report, @mkigikm. > Since they are not prefixed with 'HTTP_', the parsing code misses them. This sounds spot on. I'll schedule for us to tackle...
👋 @jeffblake and @wasabigeek, as @jeffblake pointed out, `job_logger` is invoked before any middleware are processed: 1. `job_logger` is invoked here: https://github.com/mperham/sidekiq/blob/v5.2.9/lib/sidekiq/processor.rb#L126 2. Middleware are invoked here: https://github.com/mperham/sidekiq/blob/v5.2.9/lib/sidekiq/processor.rb#L137 ([which invokes...
For some more context: what information are we missing today because of the lack of trace-logs correlation at the job logger level? Is it only these three ("start", "done", "fail")...
👋 @jorgemanrubia and @rgrey, thank you for patience here! I was trying to find any possible points where `ddtrace` holds on to memory by simply running large Ruby applications (I...
👋 @agirlnamedsophia, `orm_service_name` only affected `active_record.instantiation` spans. We removed this configuration because ActiveRecord object instantiation is part of the host application workload, thus in v1.0.0 the service for `active_record.instantiation` is...
👋 @adrys-lab @zackse @muzfuz, we have a prerelease gem published that will fix this issue and we'd like anyone experiencing this problem to try it out. The build is based...
🙌 thank you so much @lyricsboy!
Version [1.4.1](https://github.com/DataDog/dd-trace-rb/releases/tag/v1.4.1) has been released with this fix. Thank you all for your patience and cooperation in solving this issue. 🙇 If the problem still persists please let us know!