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
{{ message }}
This repository has been archived by the owner on Aug 25, 2020. It is now read-only.
I'm trying to figure out if I'm using this gem correctly or if I'm missing something that's not mentioned in the documentation. I installed the gem, making sure to place it after grape and newrelic_rpm, and when I drill down on an API call, it points to the newrelic-grape code as the source of the most time spent on the query. When I click on GET api-locations-:locations_id-nearby on this page: http://d.pr/i/hy7Z
it takes me here: http://d.pr/i/XsKg
Does that mean that the perform_action_with_newrelic_trace(trace_options) do block is what's taking up 162 out of 193ms?
I was expecting it to show me which part of the Grape API call is taking the most time.
The text was updated successfully, but these errors were encountered:
I'm trying to figure out if I'm using this gem correctly or if I'm missing something that's not mentioned in the documentation. I installed the gem, making sure to place it after grape and newrelic_rpm, and when I drill down on an API call, it points to the newrelic-grape code as the source of the most time spent on the query. When I click on
GET api-locations-:locations_id-nearby
on this page: http://d.pr/i/hy7Zit takes me here: http://d.pr/i/XsKg
Does that mean that the
perform_action_with_newrelic_trace(trace_options) do
block is what's taking up 162 out of 193ms?I was expecting it to show me which part of the Grape API call is taking the most time.
The text was updated successfully, but these errors were encountered: