Open aselder opened 2 years ago
We are experiencing the same thing. Latest versions of all the hexes, and the router_dispatch is the one the error gets attached to.
We are experiencing this too. Have reverted library upgrade until this is addressed
The same. Can we expect some fixes?
I'm using Phoenix 1.6 and the latest version all spandex stuff.
With the new telemetry setup, if I have an error occur inside the router_dispatch span, this span is correctly marked as having an error, but this does not propogate up the top level span, so DataDog doesn't mark the overall request as an error case:
Notice that the top span at the end the span list has
error: 0
. A failure should cascade up and make the entire request as an error.