Do I need to do anything to transform exceptions' error messages? #716
Replies: 1 comment 3 replies
-
|
Are you calling You've swapped out Spandex maybe? Did those exceptions show up right in datadog? |
Beta Was this translation helpful? Give feedback.
-
|
Using instrumentation libraries. I was assuming that any exceptions that occurred after the router would show up with correct error info in the And you're exactly correct, we swapped from Spandex. Those exceptions were showing up correctly in datadog. |
Beta Was this translation helpful? Give feedback.
-
|
Good to know this is an area we are lacking in parity with Spandex. Can you open an issue in https://github.com/open-telemetry/opentelemetry-erlang-contrib |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hello!
I recently experimented with adding open telemetry to one of the apps my team owns. It's been over a week now since I made the swap and we've had a few exceptions. However, they all show up in DataDog with no stacktrace info and this message:
exit:{{#{'__exception__' => true,...},[...]},{'Elixir.MyAppWeb.Endpoint',...}}. Do I need to add some transformation logic? I haven't seen this mentioned anywhere else really, so I'm wondering if maybe I misconfigured something. I would appreciate any help!Beta Was this translation helpful? Give feedback.
All reactions