Yes. Gather ALL the context
* your env
* language internals
* your infra
* any request parameters passed in
* latency, request for all outbound queries & http reqs
* raw query, normalized, hints
append it all to the arbitrarily-wide structured blob, ONE per request per service
Think of it as reconstructing strace across network hops. ☺️
Pass the full context of the request along with the request. using the single arbitrarily-wide structured data blob per request per hop will ensure that **everything is kept together**.
this is key. SEEING everything together doesn't matter, it's being able to QUERY everything together that matters.
preserving the connective tissue of the request is what enables you to perform correlations and wizardry. that connective shit gets discarded by statsd/DD metrics.
You can follow @mipsytipsy.
Tip: mention @threader_app on a Twitter thread with the keyword “compile” to get a link to it.
Enjoy Threader? Sign up.
Since you’re here...
... we’re asking visitors like you to make a contribution to support this independent project. In these uncertain times, access to information is vital. Threader gets 1,000,000+ visits a month and our iOS Twitter client was featured as an App of the Day by Apple. Your financial support will help two developers to keep working on this app. Everyone’s contribution, big or small, is so valuable. Support Threader by becoming premium or by donating on PayPal. Thank you.