tegmentum
The problem
New Relic Plug handler fails to process certain telemetry events due to a :badkey error. This results in the handler being detached and further telemetry collection disrupted. I am using Bandit v1.5
Logs
Log: [error] Handler {:new_relic, :plug} has failed and has been detached. Class=:error
Reason: {:badkey, :conn,
%{
telemetry_span_context: #Reference<0.1763085910.242745346.37981>,
connection_telemetry_span_context: #Reference<0.1763085910.242745346.7102>
}}
Stacktrace:
[
{NewRelic.Telemetry.Plug, :get_headers, 2,
[file: "lib/new_relic/telemetry/plug.ex", line: 272]},
{NewRelic.Telemetry.Plug, :handle_event, 4,
[file: "lib/new_relic/telemetry/plug.ex", line: 102]},
{:telemetry, :"execute/3-fun-0", 4,
[file: "/app/deps/telemetry/src/telemetry.erl", line: 167]},
{:lists, :foreach_1, 2, [file: "lists.erl", line: 1686]},
{Bandit.Telemetry, :start_span, 3, [file: "lib/bandit/telemetry.ex", line: 168]},
{Bandit.Pipeline, :run, 4, [file: "lib/bandit/pipeline.ex", line: 53]},
{Bandit.HTTP1.Handler, :handle_data, 3,
[file: "lib/bandit/http1/handler.ex", line: 12]},
{Bandit.DelegatingHandler, :handle_data, 3,
[file: "lib/bandit/delegating_handler.ex", line: 18]}
]
Environment
(elixir: "~> 1.14",){:phoenix, "~> 1.7.14"}{:new_relic_agent, "~> 1.30.0"}{:new_relic_oban, "~> 0.0.2"}{:bandit, "~> 1.5"}
Is there to gracefully handle that scenario ? Is there more logging that we need to figure this out ?
Any help would be much appreciated ![]()
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex











Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
This seems like a bug to me, you should open a issue on the project repo.
tegmentum
I did, but didn’t get a response. this is a desperation move
D4no0
Are you handling the telemetry events in your application code or this is some kind of under the hood thing the library does?
If yes, then you can just wrap your handle code in a
try/catchblock. I guess you could do the same with the library, fork it and wrap it in the same way, it will avoid at least detaching of the handler.tegmentum
it is a under the hood the lib does, weirdly enough it happens at random times every once in a while, I will enable debug logs and try to see if there’s a specific request format that’s causing this.
If all else fails, I’ll probably go back to using Cowboy, or fork the lib
Thanks!
dimitarvp
Your best would probably be to fork and then make a PR after you make it work properly.
binaryseed
FYI this was fixed with Handle when Bandit was unable to create a conn by binaryseed · Pull Request #449 · newrelic/elixir_agent · GitHub