Closed curtis closed 1 week ago
Sorry for the trouble. I think I see the issue, which looks like it is masking another issue, so this will be a double bonus. Thanks for the library info; we'll try to get a repro going.
@curtis The first fix to properly handle this exception is now on master
. If it is reasonable to pull the gem from there, I invite you to give it a try. Otherwise we will cut a release shortly.
I could not reproduce the issue with getting the endpoint name, unfortunately, but this should at least log more information related to the request so that we can diagnose and fix that issue as well. We can take another look with additional information from those logs.
We're seeing an exception with one of our Grape endpoints after adding Scout APM. This exception does not happen in the development environment, when
SCOUT_MONITOR
is false, or when Grape instruments are disabled inscout_apm.yml
. For now, we have followed the instructions to disable Grape instrumentation as noted in this issue.Gem Versions
Rails 6.1.7.8 Grape 2.1.3 Scout 5.3.8
Backtrace