You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're actively using our Racecar instrumentation on production, it captures what we need in terms of grouped spans into transactions.
There's a difficulty looking into a specific consumer's code performance on apps that have multiple consumers/producers. That is due to the fact that the instrumentation does transaction naming as follows: process_batch, process_message, deliver_message
The ideal scenario for transaction naming in that instrumentation would be to include the class that called those methods, in a similar way as what we currently have on controller's instrumentation. Something on the lines of "#{klass}#process_batch" i.e: DopeConsumer#process_batch or DopeProducer#deliver_message
The text was updated successfully, but these errors were encountered:
We're actively using our Racecar instrumentation on production, it captures what we need in terms of grouped spans into transactions.
There's a difficulty looking into a specific consumer's code performance on apps that have multiple consumers/producers. That is due to the fact that the instrumentation does transaction naming as follows:
process_batch
,process_message
,deliver_message
The ideal scenario for transaction naming in that instrumentation would be to include the class that called those methods, in a similar way as what we currently have on controller's instrumentation. Something on the lines of
"#{klass}#process_batch"
i.e:DopeConsumer#process_batch
orDopeProducer#deliver_message
The text was updated successfully, but these errors were encountered: