Page MenuHomePhabricator

[identity] Add gRPC request tracing span
ClosedPublic

Authored by bartek on May 10 2024, 6:32 AM.
Tags
None
Referenced Files
F3572158: D11985.id40106.diff
Sat, Dec 28, 11:10 AM
F3572155: D11985.id40067.diff
Sat, Dec 28, 11:10 AM
F3572131: D11985.id.diff
Sat, Dec 28, 11:09 AM
F3572124: D11985.diff
Sat, Dec 28, 11:09 AM
Unknown Object (File)
Nov 21 2024, 2:21 AM
Unknown Object (File)
Nov 21 2024, 2:21 AM
Unknown Object (File)
Nov 8 2024, 9:21 PM
Unknown Object (File)
Nov 8 2024, 4:19 PM
Subscribers

Details

Summary

Way of improving logs. We have this pattern in Blob Service where each HTTP request has its unique ID. This way, we can trace logs for specific RPC call by filtering by this ID.
It doesn't decrease users' anonymity level - it doesn't introduce any fields that could let us trace user actions at level higher than a single RPC call.

Example of when such log IDs greatly improved debugging experience here

Test Plan

Example screenshot here:

Screenshot 2024-05-10 at 15.35.59.png (1×2 px, 1 MB)

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable