Chris Schneider

I thought I wrote a piece about ActiveJob in another issue, but I can't locate it now. The gist of it is: ActiveJob doesn't give us the information needed to...

That would be fine - we've mostly not looked into instrumentation hooks because we have to support back to before the hooks existed, so we need a specialized monkey patch...

Hi @walidvb - we fixed the interaction with View instruments and jb in the latest release. Can you update to 2.4.24 and try again?

Sorry, but we can't use or look at Skylight's code due to licensing.

I will be looking at Sequel support soon though, I think basic instrumentation shouldn't be too hard.

I've started looking at Sequel, but haven't formalized it into a proper instrument yet. I'll see if I can find time this week to get it released.

Could you try downgrading to scout apm 2.6.7 temporarily. I fixed another issue with Sidekiq, and I wonder if this is an unintended side effect.

@hmatic Are you using ActiveJob, or "run-later" functionality in sidekiq? Trying to narrow down the situation you're seeing. Are you seeing this issue newly on an upgraded Rails? Which version...

Thank you for the report - something must have changed in the ActiveJob payload between the ... patch releases... of Rails. I'll take a look.

@hmatic I am not able to reproduce this locally. I have a new Rails 6.0.3.2, with ActiveJob set to sidekiq, and Sidekiq 5.0.0. We capture the job name from Sidekiq's...