We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe your environment
Steps to reproduce See documents for gRPC instrumentation
What is the expected behavior? For client instrumentation example, I would see either of the followings:
GrpcInstrumentorClient().instrument()
GrpcInstrumentorClient()
instrument()
What is the actual behavior?
I see the following example codes.
In the Usage Client section:
instrumentor = GrpcInstrumentorClient().instrument()
And in the GrpcInstrumentorClient class document:
grpc_client_instrumentor = GrpcInstrumentorClient() grpc.client_instrumentor.instrument()
where 2nd line is calling non existing package. It should be typo of the variable defined in 1st line.
Additional context
I was trying implement the code to fix #373 and found this issue, so I created separate issue here. I'll create a PR for this shortly.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe your environment
Steps to reproduce
See documents for gRPC instrumentation
What is the expected behavior?
For client instrumentation example, I would see either of the followings:
GrpcInstrumentorClient().instrument()
is called without return value assignment.GrpcInstrumentorClient()
and callinstrument()
method of it.What is the actual behavior?
I see the following example codes.
In the Usage Client section:
And in the GrpcInstrumentorClient class document:
where 2nd line is calling non existing package. It should be typo of the variable defined in 1st line.
Additional context
I was trying implement the code to fix #373 and found this issue, so I created separate issue here. I'll create a PR for this shortly.
The text was updated successfully, but these errors were encountered: