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

The active connection is not accurate enough #38871

Closed
Yui-Song opened this issue Nov 3, 2022 · 0 comments · Fixed by #38873
Closed

The active connection is not accurate enough #38871

Yui-Song opened this issue Nov 3, 2022 · 0 comments · Fixed by #38873
Assignees
@Yui-Song
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@Yui-Song
Copy link
Contributor

Yui-Song commented Nov 3, 2022

Enhancement

It would be more accurate to calculate the active connections and DB time with the following promeQL: sum(tidb_server_tokens{k8s_cluster="$k8s_cluster",tidb_cluster="$tidb_cluster"})
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Yui-Song Yui-Song

Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

metrics: update active connection promeQL and add metric: miss plan cache Yui-Song/tidb
1 participant
@Yui-Song