Re: [grpc-io] [gRPC-Python] tracing for retries

Hi Kyle, The gRFC you mentioned above was not implemented in Python yet. We have a new gRFC for OpenTelemtry Tracing in progress which will be implemented in Python once it's finished. Our `grpcio-observability` package currently only works for

[grpc-io] TCP_USER_TIMEOUT configuration and logging

I'm concerned that I'm seeing an issue similar to this old one , so I want to verify that `TCP_USER_TIMEOUT` is set to something reasonable. To configure that value, it sounds like gRPC keepalive must be enabled, but there are concerns this is

[grpc-io] [gRPC-Python] Configuring TCP_QUICKACK?

Is it possible to configure TCP_QUICKACK when using grpc with Python? It appears that all TCP configuration (e.g. for TCP_USER_TIMEOUT) is done by the grpc library itself, but I can't find any mention of quickack in the code, in other issues, or in the mailing list archives. I ask because

Re: [grpc-io] [gRPC-Python] tracing for retries

Okay, thank you for explaining. On Thursday, April 25, 2024 at 4:01:43 PM UTC-6 Xuan Wang wrote: > Hi Kyle, > > The gRFC you mentioned above was not implemented in Python yet. We have a new > gRFC for OpenTelemtry Tracing > in progress which will be

[grpc-io] gRFC A80: gRPC TCP connection metrics

I've published a gRFC for TCP connection metrics in gRPC. https://github.com/grpc/proposal/pull/428 The metrics will utilize the metrics framework outlined in [A79]: gRPC Non-Per-Call Metrics Framework .

[grpc-io] gRFC: A80 gRPC Metrics For TCP Connection

I've published a gRFC for TCP connection metrics in [A80]: gRPC Metrics For TCP Connection . The metrics will utilize the metrics framework outlined in [A79]: gRPC Non-Per-Call Metrics Framework

[grpc-io] L116: C++-Core: Loosen behavior of GRPC_ARG_HTTP2_MAX_PINGS_WITHOUT_DATA

Hey all, https://github.com/grpc/proposal/pull/429 is a proposal to modify the behavior GRPC_ARG_HTTP2_MAX_PINGS_WITHOUT_DATA to throttle pings to a frequency of 1 minute instead of completely blocking pings when too many pings have been sent without data/header frames being sent. Comments

[grpc-io] [gRPC-Python] tracing for retries

How can I enable tracing for retries in Python? The retry-stats gRFC, A46, says : > The gRPC tracing module should create a tracing span for each call from the perspective of the application, and create a child span for

Re: [grpc-io] [gRPC-Python] grpcio-observability compatibiltiy with OTEL SDK 1.22.0+

Hi Kyle, We actually do support versions higher than 1.21.0, we'll remove the version ping in the next release. As for api vs sdk, we do need sdk to create MeterProvider in the example .

Re: [grpc-io] [gRPC-Python] grpcio-observability compatibiltiy with OTEL SDK 1.22.0+

Excellent, thank you! -- Kyle J Strand Senior Software Engineer (Pronouns: he/him) kstr...@rigetti.com rigetti.com Confidentiality Note: This message is for the intended recipient only and may contain proprietary, privileged, or confidential information. The use, copying or distribution of

Re: [grpc-io] Since which version, gRPC stack started supporting TLS 1.3?

Hi Shikha, Which language are you using? Note, you should be using a recent version, which version are you using? Thanks, Larry On Wed, Apr 24, 2024 at 2:37 PM Shikha Chowdhary < shikhachowdhar...@gmail.com> wrote: > - All working well with TLS 1.2 but intermittently failed when using TLS >