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
Tracing support #704
Comments
/milestone v0.4.0 |
@matzew: You must be a member of the knative/knative-milestone-maintainers github team to set the milestone. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
a bit late for v0.3.0 😄 |
@Harwayne think you might be able to update this for Broker/Trigger model for the Tuesday release? |
/milestone v0.5.1 |
/milestone v0.6.0 |
/milestone v0.7.0 |
The components that are involved:
|
Documentation is now tracked in knative/docs#1515. Closing this one. |
We should have a How-To guide for how to debug events flowing through the system and understand where things went wrong and how. Istio gives good tracing capabilities, but they can be a bit tricky to understand what they actually mean, a simple Readme would go a long way to prevent the user having to go digging through the logs, or at least point them to the actual logs that are necessary to look at to figure out what went wrong and why.
@Harwayne assigning to you given that you spent a good chunk of time working through what tracing capabilities are available out of Istio and how to decode them.
The text was updated successfully, but these errors were encountered: