Justin

+1 I just spent the last few hours struggling with this. I am not super experienced with Helm but I find this chart is unlike many others I have seen...

I am also interested in this behavior for the same reasons mentioned above. I am running the Jaeger Collector inside a Kubernetes cluster but need to allow Agents from outside...

> Was there any progress on this? I am in the same boat as @js8080 I ended up defining my own Ingress (I use NGINX as an Ingress Controller). Hopefully...

@ilhaan I am not sure what the issue is. Are you sending from the Jaeger Agent to the Collector or is your traced client attempting to send directly to the...

@ilhaan I use a docker-compose file to run my agent: ```yaml version: "3" services: jaeger-agent: image: jaegertracing/jaeger-agent hostname: jaeger-agent command: [ "--reporter.grpc.host-port=jaeger-collector.mycontainer-dev.myhostname.com:443", "--reporter.grpc.tls.enabled=true", # Enable TLS when talking to the...

Aren't we really risking the robustness of the specification by allowing _anything_ in the Context element? Isn't there a risk that CDS Hooks services (or clients) will put things in...

> OK - I just wouldn't invest too much time in this library. If you run into issues/things you don't like with this, I'd try to switch to OpenTelemetry. There's...

Ah, thank you for that info! Does the OpenTelemetry-dotnet library have the ability to bypass the Jaeger Agent and push directly to the Collector (via gRPC for example)?

That's an excellent question and I'm in the process of digging up info on how to instrument SignalR. I will follow-up with what I find.

@cwe1ss - check out [Add EventSource/EventCounter tracing and metrics for SignalR and WebSockets #2461](https://github.com/dotnet/aspnetcore/issues/2461) (aspnetcore github). Sounds like there is no `DiagnosticSource` in the ASP.NET Core SignalR code so a...