@esk having used sidekiq before I’d say drop them and/or heavily sample them if you can. It should just be Sidekiq looking for jobs in sorted order. It’s something that would be nice to have a metric for to know if it’s starting to bog down workers or something, but a span for them all is a bit much IMO.

Also yay Honeycomb!!

@esk Are they part of a trace, and/or do they have a parent span?
I think they are Sidekiq workers polling Redis and trying to see if there are any jobs to process, in which case they can be filtered (but maybe not all ZSCANs?). If thats the case, we should probably filter them out directly in our instrumentation, or better sample them heavily.
For mastodon.social we only keep 1% of traces, except for errors where we keep 100% of them.