-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Traces] Study if there is a way to track container start phases #12740
Comments
@garagatyi Does you PR #12655 covered something from this issue list? |
This information would best come from openshift itself. |
@skabashnyuk no, but I have an idea how to implement this and where the exact location of the code to change. I wanted to do this as part of my PR but since it was my own cleanups and improvements that wasn't planned for my team I ended up cutting this part from the PR as unfinished. @fche yes, we watch pod events on workspace start, so we could add traces when we detect events mentioned in the issue description. |
@garagatyi Agreed on watching pod events -- for the timing stuff from awhile ago I did similar and it worked fairly well. |
We were not able to take this issue in our Sprint 164 Backlog. |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
out of date |
Description
Study if there is a way to track container start phases and report it to Jaeger.
Interesting phases:
The text was updated successfully, but these errors were encountered: