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.

Sign up for GitHub

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

Jump to bottom

Investigate tracing of wsmaster tomcat server shutdown #11946

Closed
metlos opened this issue Nov 15, 2018 · 1 comment
Closed

Investigate tracing of wsmaster tomcat server shutdown #11946

metlos opened this issue Nov 15, 2018 · 1 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.

Comments

@metlos
Copy link
Contributor

metlos commented Nov 15, 2018

Description

Tomcat shutdown was identified as one of the areas that would potentially benefit from tracing to help us understand what is the time being spent on and why it sometimes seemingly hangs.

Before blindly adding tracing though, we should first discuss whether this area is really something that is worth investing into. We should only add traces to areas that are really needed to not overload the tracing server with unneeded data points.

Reproduction Steps

N/A

OS and version:
N/A

Diagnostics:
N/A
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels Nov 15, 2018
@yarivlifchuk yarivlifchuk mentioned this issue Jan 28, 2019
Closed
20 tasks
@skabashnyuk skabashnyuk added the severity/P2 Has a minor but important impact to the usage or development of the system. label Mar 6, 2019
@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2019
@che-bot
Copy link
Contributor

che-bot commented Sep 7, 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 closed this as completed Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@metlos @skabashnyuk @che-bot