tegmentum
New Relic Plug handler fails to process certain telemetry events due to a :badkey error
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
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Sta...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New
Other Trending Topics
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance










First 6 of 6 Posts
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