David Elner

> Guilty as charged :laughing: @dasch haha, you're not the only one! This is fairly common, so I figured there was decent odds. It's okay for now, especially as we...

It's available on most of our integrations, but not actively used to create coloration/groupings. Seems like a good candidate. Are there any other such tags that you think would also...

It's currently not really "in use" other than that its populated with the library name of the integration that produced it. This value is a constant e.g. `active_record`). It's a...

@nightpool Agreed on providing this additional visibility; it needs more granularity without use of `service`. Thanks for raising this point! @dasch > OK, I've thought of another use case for...

Hey @webandtech thanks for the suggestion (and sorry for the late reply!) We'll take a look at this in the coming weeks. Will let you know what develops.

@webandtech I've been told this has been moved to our backlog. Will let you know if/when that changes.

Re-reading this, it looks like the metric in question `trace.sidekiq.job.hits` is generated by the agent, not by the trace library. For that specific metric, I don't believe we have the...

Yup, we're aware of this not playing well with `before_action`/`after_action`. This is because of the class we currently patch (`ActionController::Base`) doesn't allow for this. We will likely add additional instrumentation...

We've overhauled our Rails instrumentation a bit in 0.27.0, so we should begin work on changing how we instrument controller actions soon; look for that in the near future.

I would like to work on this but its not currently on the schedule; I'll follow up with the team and see what they'd like to do about it.