-
We currently use a simple HTTP/JSON protocol for the scaler to communicate with the interceptor. Because this protocol is just request/response, it has limitations on latency that can cause very slow …
-
### Is your feature request related to a problem? Please describe.
As far as I can tell, unit testing a gRPC server with its interceptors is not possible.
**This leads to 2 issues :**
- It is not…
-
# Bug Report
### OTel packages:
OpenTelemetry V1.6.0
OpenTelemetry.Api V1.6.0
OpenTelemetry.Api.ProviderBuilderExtensions V1.6.0
OpenTelemetry.Exporter.Console V1.6.0
OpenTelemetry.Exporter.Op…
-
Malformed or inconsistent JSON can cause parsing errors. When values have inconsistent data types, the parser may fail—for instance, if a certain key is expected to be a number but occasionally appear…
-
https://github.com/grpc/proposal/blob/master/A72-open-telemetry-tracing.md
-
### Problem description
We experience intermittent connection reset errors migrating to grpc-js version "1.3.2". We are creating the Grpc client instance every time when message is processed.
On the…
-
gRPC clients via `@grpc/grpc-js` bring their own interceptors. Letting the user choose from multiple interceptor mechanisms available seems overcomplicated.
This could be solved by moving intercep…
-
We use the GRPC interceptor functionality to add authentication information to the metadata of the request.
When I add an `UnaryInterceptor` to the client it works fine for unary RPCs, however onl…
-
I’ve been using this package for a while and it works great, thank you @d5h!
And because all of our code is typed I was wondering if you’d agree to tightening the type hints in this package a littl…
-
**Description**
Documentation issue
In Zeebe 8.4+ (probably earlier versions too), the interceptor documentation has some outdated information https://docs.camunda.io/docs/8.4/self-managed/zeebe…