-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elixir response time missing when using Bandit #489
Comments
Thanks for the report. I don't think the two things are related. I have a hunch I'm already tracking down related to instrumenting bandit that might be related. This error is interesting though, looks like the transition completed w/o setting a Are you doing anything out of the ordinary, perhaps trying to start a web transaction manually in your app? |
Nope, I am not doing anything manually.. |
Oh I'm calling |
Will you share a link to that elixir forum post? |
I think this could happen on ignored paths.
start_transaction returns :ignore , so the attributes from the plug telemetry (including host ) never get set.
|
That wouldn't cause the error... when you call |
I was able to reproduce the error locally and have a PR to fix it: #497 The response time metric is a separate issue that I aim to track down soon |
Describe the bug
When using Bandit I am unable to see the Elixir response time in New Relic dashboard (I still see Postgres and total response time tho).
I started receiving crash reports that might be related:
Environment
Erlang/OTP 26 [erts-14.2.5] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns]
Elixir 1.17.3 (compiled with Erlang/OTP 26)
new_relic_agent 1.31.1
bandit 1.6.7
The text was updated successfully, but these errors were encountered: