Skip to content
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

Closed
skabashnyuk opened this issue Feb 22, 2019 · 7 comments
Closed

[Traces] Study if there is a way to track container start phases #12740

skabashnyuk opened this issue Feb 22, 2019 · 7 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@skabashnyuk
Copy link
Contributor

Description

Study if there is a way to track container start phases and report it to Jaeger.
Interesting phases:

  • Pod assigning
  • Image pulling
  • Image pulled
  • Container starting
  • Container starter
  • etc.
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels Feb 22, 2019
@yarivlifchuk yarivlifchuk mentioned this issue Feb 22, 2019
20 tasks
@skabashnyuk
Copy link
Contributor Author

@garagatyi Does you PR #12655 covered something from this issue list?

@fche
Copy link

fche commented Feb 22, 2019

This information would best come from openshift itself.

@garagatyi
Copy link

@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.

@amisevsk
Copy link
Contributor

@garagatyi Agreed on watching pod events -- for the timing stuff from awhile ago I did similar and it worked fairly well.

@ibuziuk
Copy link
Member

ibuziuk commented Feb 27, 2019

We were not able to take this issue in our Sprint 164 Backlog.

@skabashnyuk skabashnyuk added severity/P2 Has a minor but important impact to the usage or development of the system. and removed team/osio labels Mar 6, 2019
@che-bot
Copy link
Contributor

che-bot commented Oct 1, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 1, 2019
@skabashnyuk
Copy link
Contributor Author

out of date

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants