-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distributed tracing on data plane #48
Comments
@alexsnaps @adam-cattermole for the sake of gh issue hygiene, and assuming at this time there are no issues in this epic progressing, how about closing this out with the tasks that were completed & marking this as Done? |
Sure, I think that makes sense - breaking out the pieces / decisions around how we expose tracing at the kuadrant level |
As request come into the cluster, it'd be nice to enable distributed traces from the Gateway onward, throughout the different Kuadrant components and eventually to the user's application fronted by Kuadrant.
--tracing-service-insecure
authorino-operator#167Add some global way (in theMoved to Add some global way (in the Kuadrant CR?) to configure the underlying components for them to push spans to the OTLP collector kuadrant-operator#731Kuadrant
CR?) to configure the underlying components for them to push spans to the OTLP collector.Have us (within wasm, e.g. pre auth RL?) start the trace and is there a way to have envoy propagate that traceparent to ext`-auth?Moved to Have us (within wasm, e.g. pre auth RL?) start the trace and is there a way to have envoy propagate that traceparent to ext-auth? wasm-shim#59Look into adding "well-known" fields into our span to "trace" them back to the user's domain: RLP, AP, …Moved to RFC: Tracing Sampling Strategy Rules #96The text was updated successfully, but these errors were encountered: