Filter out health check request in grpc

[ymotongpoo]

Is your feature request related to a problem?
As of 0.18b1, opentelemetry-instrumentation-grpc doesn't have the feature to exclude trace propagation to the specific endpoints. Because of this, gRPC servers always send health check request traces to the backend via the exporter as you see in the screenshot below:

Describe the solution you'd like
It would be nice if opentelemetry-instrumentation-grpc could have something similar to OTEL_PYTHON_FLASK_EXCLUDED_URLS in opentelemetry-instrumentation-flask.

Describe alternatives you've considered
Each exporters support filter option to avoid sending unnecessary traces to the backend.

Additional context
Health checking is the common practice in Kubernetes and the traces for such requests sometimes pollute the Trace dashboard and leads to unnecessary costs for SaaS services.

[jan25]

I could give this a shot if not already picked up :)

[lzchen]

@jan25
Sure thing.

[rahulgupta92]

Is this feature being worked upon or has been implemented? Any suggestions/workarounds for excluding such requests?

[lzchen]

@jan25
Any updates on this?

[avzis]

@lzchen @ymotongpoo
I'm looking for a good first issue, is this still relevant?

[ymotongpoo]

@avzis Yes, I think so. I'm working on Go version in open-telemetry/opentelemetry-go-contrib#2572, and you can port it to Python.

[lzchen]

@avzis
I'll assign this to you.

[ymotongpoo]

So, is @avzis working on this now? Because open-telemetry/opentelemetry-go-contrib#2572 is merged, now I can port it to Python soon if necessary.

[lzchen]

@avzis
Are you currently working on this? I can assign it to @ymotongpoo if not.

[avzis]

hi, yes

[lzchen]

@avzis

hi, yes

Will be taking this as "yes you can assign it to someone else". Please comment if otherwise.

[avzis]

i mean "yes i'm working on it", sorry for not being clear

[ymotongpoo]

oh, I have implemented mostly in #1241 but for unit tests.

[avzis]

ok, so you finish it..
ill take another issue
good luck :)