You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Datadog exporter currently parses the status description to determine if an exception was raised, yet the specification requires these to be recorded as events (and the python code already does this), so the Datadog exporter should read this data from the event list instead of hoping the description is properly formatted.
The current code does say that span events are not supported , and while that would suggest that reporting events are not supported, we could certainly parse them for this data.
I'll probably tackle this, I'm already working on #154. Also mentioned in #236, where I worked around the current behavior.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this @alertedsnake! Your suggestion makes sense. If you end up tackling this, just give a heads up here and I'll check in before giving it a go myself.
@alertedsnake no worries, only one of us gets time during their day job to do this 🙃 . May ask for a review as my python is quite rusty, will ping on PR
The Datadog exporter currently parses the status description to determine if an exception was raised, yet the specification requires these to be recorded as events (and the python code already does this), so the Datadog exporter should read this data from the event list instead of hoping the description is properly formatted.
The current code does say that span events are not supported , and while that would suggest that reporting events are not supported, we could certainly parse them for this data.
I'll probably tackle this, I'm already working on #154. Also mentioned in #236, where I worked around the current behavior.
The text was updated successfully, but these errors were encountered: