You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a healtcheck in our app, which checks Redis connectivity using the PING command. It is very uninteresting to trace, and spams our trace storage so much that we cannot currently use the RedisInstrumentor for our application.
Other instrumentor libraries, such as the requests one and the gRPC one, check for this flag when deciding whether or not to start a new trace. The same solution could be applied here.
Same issue in gRPC client instrumentor: #559
Nice illustration of the exact way to fix it for the Redis instrumentor:
We have a healtcheck in our app, which checks Redis connectivity using the PING command. It is very uninteresting to trace, and spams our trace storage so much that we cannot currently use the RedisInstrumentor for our application.
Other instrumentor libraries, such as the requests one and the gRPC one, check for this flag when deciding whether or not to start a new trace. The same solution could be applied here.
Same issue in gRPC client instrumentor: #559
Nice illustration of the exact way to fix it for the Redis instrumentor:
opentelemetry-python-contrib/instrumentation/opentelemetry-instrumentation-requests/src/opentelemetry/instrumentation/requests/__init__.py
Lines 129 to 131 in b6d77f1
I've already implemented and verified a fix for this, just waiting for internal approval to submit it.
Steps to reproduce
What is the expected behavior?
No trace
What is the actual behavior?
Trace
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: