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
I find myself missing having a tool that can trace through the whole RPC call-graph for a given session. Really nice for debugging and understanding the broader system as a newbie by inspecting requests/responses.
It sounds like Datadog APM may be able to do similar things? Any limitations/differences to be aware of?
At a glance it seems like the use cases are a bit different. Datadog APM shows the latencies, but I can't find request/response payloads. Looks like it runs on every request, so it can't log everything. I didn't use Dapper much but maybe that's closer to what Datadog APM does - low-overhead performance monitoring.
xsds/sherlog was opt-in just for a given session and seemed to be geared at debugging specifically. It was great when you had just found a repro and could record a full trace to reference for anything unusual downstream. With Datadog APM it looks like I'd have to use the right filters to get to the right trace.
The text was updated successfully, but these errors were encountered:
I find myself missing having a tool that can trace through the whole RPC call-graph for a given session. Really nice for debugging and understanding the broader system as a newbie by inspecting requests/responses.
It sounds like Datadog APM may be able to do similar things? Any limitations/differences to be aware of?
At a glance it seems like the use cases are a bit different. Datadog APM shows the latencies, but I can't find request/response payloads. Looks like it runs on every request, so it can't log everything. I didn't use Dapper much but maybe that's closer to what Datadog APM does - low-overhead performance monitoring.
xsds/sherlog was opt-in just for a given session and seemed to be geared at debugging specifically. It was great when you had just found a repro and could record a full trace to reference for anything unusual downstream. With Datadog APM it looks like I'd have to use the right filters to get to the right trace.
The text was updated successfully, but these errors were encountered: