We are converting existing Python gRPC services to the Python gRPC AsyncIO 
version (1.43.1). We currently use the py-grpc-prometheus package to 
collect/emit server and client metrics. This packages subclasses:
```
class PromServerInterceptor(grpc.ServerInterceptor): 

class PromClientInterceptor(grpc.UnaryUnaryClientInterceptor, 
grpc.UnaryStreamClientInterceptor, grpc.StreamUnaryClientInterceptor, 
grpc.StreamStreamClientInterceptor):
```
 and uses a number of other gRPC package attributes, etc.

The question is, are the blocking and asyncio classes 'compatible' when 
used in this way? If not, any suggestions on alternative ways of collecting 
server/client request/response metrics?

Thank you:)

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/b9bb6bca-efc8-4578-903a-05736f968fe4n%40googlegroups.com.

Reply via email to