[DocDB] Create a button in the Tserver UI to access the io-stack-traces #22842
Assignees
Labels
2024.1 Backport Required
area/docdb
YugabyteDB core features
kind/enhancement
This is an enhancement of an existing feature
priority/medium
Medium priority issue
Comments
rthallamko3
added
area/docdb
yugabyte-ci
added
kind/enhancement
rthallamko3
changed the title
|
|
es1024
added a commit
that referenced
this issue
Jun 27, 2024
Summary:
This diff makes the following changes to improve usability of the stack trace
tracking endpoints (/io-stack-traces, /debug-stack-traces):
1. Add a button to /utilz for /io-stack-traces:
{image uri=https://github.com/yugabyte/yugabyte-db/assets/6742815/c3db1e87-a0f2-4fb7-8aa2-bff65638220d , width=1000px}
2. Add a link to reset tracking (/reset-stack-traces).
3. Add the tracking period to the endpoints.
{image uri=https://github.com/yugabyte/yugabyte-db/assets/6742815/9de9f5f0-b63e-4618-bafb-cb89f01ea4ec}
4. Reset stack trace tracking when the track_stack_traces gflag is set.
Jira: DB-11739
Test Plan: Opened /io-stack-traces, /debug-stack-traces, /utilz, and tested toggling track_stack_traces.
Reviewers: asrivastava
Reviewed By: asrivastava
Subscribers: ybase
Differential Revision: https://phorge.dev.yugabyte.com/D36190
jasonyb
pushed a commit
that referenced
this issue
Jun 28, 2024
Summary: 9c637e2 [PLAT-14429]: Modify Troubleshooting Platform registration workflow in YBA 0a1406d [PLAT-14098]: Updating yb.runtime_conf_ui.tag_filter with appropriate tags value does not display the flags accordingly 70a87f9 [PLAT-13605][PLAT-13609]: Edit Volume controls and storage type in FULL_MOVE but not in case of UPDATE 26fbfe0 [PLAT-14515][UI] Clicking preview doesn't show the correct info and clears up the data provided while setting up the ysql_ident or ysql_hba multiline flags.- [PLAT-14514] [PLAT-14513] a07946b [#18233] Initial commit for yugabyted unit test framework. b2e8ee7 [#22842] docdb: Improve usability of stack trace tracking endpoints 508f26e [docs] Added RN 2.20.2.3-b2 (#23042) 214d44a [#22935] YSQL: Use db oid in the tserver's sequence cache entry key c47b2d9 [#22802] YSQL: Avoid renaming DocDb tables during legacy rewrite Excluded: 7c8343d [#22874] YSQL: Fix cascaded drops on columns 58c8d4e [#23046] xCluster: Remove ns_replication from the code a70681d [#22816] YSQL: Bug fixes for replication connections in ysql connection manager b239e07 Doc upgrade versions (#22988) Excluded: ec76062 [#16408] YSQL: Split TestPgRegressIndex.testPgRegressIndex Test Plan: Jenkins: rebase: pg15-cherrypicks Reviewers: jason, tfoucher Subscribers: yql Tags: #jenkins-ready Differential Revision: https://phorge.dev.yugabyte.com/D36247
es1024
added a commit
that referenced
this issue
Jul 3, 2024
…cking endpoints Summary: Original commit: b2e8ee7 / D36190 This diff makes the following changes to improve usability of the stack trace tracking endpoints (/io-stack-traces, /debug-stack-traces): 1. Add a button to /utilz for /io-stack-traces: {image uri=https://github.com/yugabyte/yugabyte-db/assets/6742815/c3db1e87-a0f2-4fb7-8aa2-bff65638220d , width=1000px} 2. Add a link to reset tracking (/reset-stack-traces). 3. Add the tracking period to the endpoints. {image uri=https://github.com/yugabyte/yugabyte-db/assets/6742815/9de9f5f0-b63e-4618-bafb-cb89f01ea4ec} 4. Reset stack trace tracking when the track_stack_traces gflag is set. Jira: DB-11739 Test Plan: Opened /io-stack-traces, /debug-stack-traces, /utilz, and tested toggling track_stack_traces. Reviewers: asrivastava Reviewed By: asrivastava Subscribers: ybase Tags: #jenkins-ready Differential Revision: https://phorge.dev.yugabyte.com/D36212
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jira Link: DB-11739
Description
Create a button in the Tserver UI to access the io-stack-traces
Also include a button to reset the io-stats /reset-stack-traces
Include a note on the timestamp, when the tracking started.
Issue Type
kind/enhancement
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: