-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add client request to telemetry metadata #324
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this. Could you add some assertions to one of the tests at test/grpc/integration/client_interceptor_test.exs showing the new metadata?
You can see the use of the custom attach_events
helper there and follow the same pattern.
5eca7e3
to
d197e81
Compare
@polvalente I added some asserts as you suggested. Though I only asserted some of the fields, specially for the stream. If you have something specific in mind, I can add it. |
d197e81
to
e448ce1
Compare
Just checking up, is there anything else I can do to move this forward? |
e448ce1
to
403752b
Compare
Hi, any chance to get a second look at this? It would be great to have this included. |
Hi @polvalente @sleipnir , thanks for the approvals! Just for my information, is there anything else that needs to happen before this gets merged? |
ping @polvalente |
This is on my to-do list :) |
@polvalente I apologize if I'm being pushy, but are there any news on this? |
403752b
to
556f666
Compare
Description
Having the actual client request in the telemetry event can be useful to cover more use cases, e.g. if you want to log specifics of the requests you are doing.
NOTE: Not sure if this was considered and discarded already so I just went ahead and created the PR as this would be helpful for my use case.