{"action":"created","issue":{"url":"https://api.github.com/repos/grpc/grpc/issues/1743","labels_url":"https://api.github.com/repos/grpc/grpc/issues/1743/labels{/name}","comments_url":"https://api.github.com/repos/grpc/grpc/issues/1743/comments","events_url":"https://api.github.com/repos/grpc/grpc/issues/1743/events","html_url":"https://github.com/grpc/grpc/issues/1743","id":80543665,"number":1743,"title":"RPC stats","user":{"login":"fta1","id":8408002,"avatar_url":"https://avatars.githubusercontent.com/u/8408002?v=3","gravatar_id":"","url":"https://api.github.com/users/fta1","html_url":"https://github.com/fta1","followers_url":"https://api.github.com/users/fta1/followers","following_url":"https://api.github.com/users/fta1/following{/other_user}","gists_url":"https://api.github.com/users/fta1/gists{/gist_id}","starred_url":"https://api.github.com/users/fta1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fta1/subscriptions","organizations_url":"https://api.github.com/users/fta1/orgs","repos_url":"https://api.github.com/users/fta1/repos","events_url":"https://api.github.com/users/fta1/events{/privacy}","received_events_url":"https://api.github.com/users/fta1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-05-25T13:51:14Z","updated_at":"2015-05-25T15:09:56Z","closed_at":null,"body":"I'm trying to expose the time to 1st byte of my RPC calls, along with the total time (round trip). I achieved the latter with an extra ping/pong RPC, that I can also turn into a decorator on any call in the client side (my clients are in Python), but for the former, it is difficult. Also, it sort of clutters the code as it forces every single call to be wrapped (and in a microservice environment, that could mean touching a lot of code living in different places, and possibly several languages). It would be nice if that was collected by gRPC itself, and exposed via the various language APIs.\r\nI'm not really expecting one-way measurements, as that would mean enforcing ntp synced boxes (or worse)... yet, that would be extra nice to have.\r\n\r\nIf that also counts the number of calls, even better. The server should be able to expose that per client, while the client should probably only show the server it is connected to (per stub).\r\n"},"comment":{"url":"https://api.github.com/repos/grpc/grpc/issues/comments/105249393","html_url":"https://github.com/grpc/grpc/issues/1743#issuecomment-105249393","issue_url":"https://api.github.com/repos/grpc/grpc/issues/1743","id":105249393,"user":{"login":"ctiller","id":10120821,"avatar_url":"https://avatars.githubusercontent.com/u/10120821?v=3","gravatar_id":"","url":"https://api.github.com/users/ctiller","html_url":"https://github.com/ctiller","followers_url":"https://api.github.com/users/ctiller/followers","following_url":"https://api.github.com/users/ctiller/following{/other_user}","gists_url":"https://api.github.com/users/ctiller/gists{/gist_id}","starred_url":"https://api.github.com/users/ctiller/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ctiller/subscriptions","organizations_url":"https://api.github.com/users/ctiller/orgs","repos_url":"https://api.github.com/users/ctiller/repos","events_url":"https://api.github.com/users/ctiller/events{/privacy}","received_events_url":"https://api.github.com/users/ctiller/received_events","type":"User","site_admin":false},"created_at":"2015-05-25T15:09:56Z","updated_at":"2015-05-25T15:09:56Z","body":"We have some ongoing work to bring our statistics and tracong code open source. I don't have the exact plan at my fingertips, but it is coming.\r\n\r\n@aveitch may be able to provide some further colour."}}