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
For those of us that use gRPC it would be nice to have the encoder support handling spans from the brave-grpc instrumentation.
I wonder if there is some abstraction we can add so we don't have to keep manually implementing these things as new RPC mechanisms are instrumented in brave, obviously HTTP is fairly well understood and the tags are standarized
The text was updated successfully, but these errors were encountered:
On Thu, 29 Mar 2018 05:02 Brian Devins, ***@***.***> wrote:
For those of us that use gRPC it would be nice to have the encoder support
handling spans from the brave-grpc instrumentation.
I wonder if there is some abstraction we can add so we don't have to keep
manually implementing these things as new RPC mechanisms are instrumented
in brave, obviously HTTP is fairly well understood and the tags are
standarized
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#73>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD6129XQIuB679BJ2s8PDARUsDrIToBks5ti_pbgaJpZM4S_XAC>
.
For those of us that use gRPC it would be nice to have the encoder support handling spans from the brave-grpc instrumentation.
I wonder if there is some abstraction we can add so we don't have to keep manually implementing these things as new RPC mechanisms are instrumented in brave, obviously HTTP is fairly well understood and the tags are standarized
The text was updated successfully, but these errors were encountered: