Our application uses open telemetry grpc (logs metrics and traces) which causes fiddler ui to spam server reflection calls when the server does not support server reflection.
Ofter only a short time of capturing there are huge volumes of server reflection calls to the same endpoint making the fiddler UI
Fiddler should:
* Allow bypass of traffic initiated from fiddler.UI (my current workaround is a rule to not show the traffic, but it makes the application flicker since it seems to be displayed and then later removed)
* Allow Server Reflection to be turned off
* Server reflection needs a circuit breaker, if the server do not support reflection DONT retry as fast as you can. at most retry with a few minutes between and only if the server is likely to start supporting it
Also: It would be nice (LOW PRIORITY) if you included default .proto files for opentelemetry opentelemetry-proto/opentelemetry/proto at main ยท open-telemetry/opentelemetry-proto so it could just work.
Current problems:
* 100 000s of "server reflection calls" making application unresponsive and taking up many GB or RAM