Skip to content

chore(monitor-snapshot/master): update files from upstreams #1267

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

Merged
ti-chi-bot merged 1 commit into from
Nov 10, 2026
Merged

chore(monitor-snapshot/master): update files from upstreams #1267

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified monitor-snapshot/master/ansible-monitor.tar.gz
View file
Open in desktop
Binary file not shown.
27 changes: 11 additions & 16 deletions monitor-snapshot/master/operator/dashboards/tidb_resource_control.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,7 @@
"dashLength": 10,
"dashes": false,
"datasource": "tidb-cluster",
"description": "The max request unit cost for resource groups during in a period(20s).",
"description": "Maximum combined read and write RU/s of one natural second in a 60-second rolling window ending about 30 seconds before the point, summed over clients. Under normal reporting a peak is visible for about a minute and a scrape interval of at most 60 seconds does not miss it; data that arrives late, is retried, or follows a leader change is visible only from its arrival until the window ends and can be missed. A peak may span two adjacent points at a 1-minute step; the two ends of a queried range can be off by up to about 60 seconds. Compare with RU, which shows average consumption rates. RU is attributed to the second in which the client settles it, so a long request concentrates its RU in its settlement second; covers the foreground RU that TiDB confirms by second; excludes TiFlash and background task RU, SQL CPU RU and RUv2.",
"fill": 1,
"fillGradient": 0,
"gridPos": {
Expand All @@ -255,11 +255,12 @@
"y": 0
},
"id": 5,
"interval": "1m",
"legend": {
"alignAsTable": true,
"avg": false,
"current": true,
"max": false,
"max": true,
"min": false,
"rightSide": true,
"show": true,
Expand All @@ -282,24 +283,18 @@
"steppedLine": false,
"targets": [
{
"expr": "sum(resource_manager_resource_unit_read_request_unit_max_per_sec{k8s_cluster=\"$k8s_cluster\", tidb_cluster=\"$tidb_cluster\", resource_group=~\"$resource_group\"}) by (resource_group)",
"expr": "max by (keyspace_name, resource_group) (max_over_time(resource_manager_resource_unit_peak_per_second_rolling_60s{k8s_cluster=\"$k8s_cluster\", tidb_cluster=\"$tidb_cluster\", resource_group=~\"$resource_group\"}[$__interval]))",
"format": "time_series",
"intervalFactor": 2,
"legendFormat": "{{resource_group}}-read",
"interval": "1m",
"intervalFactor": 1,
"legendFormat": "{{resource_group}}",
"refId": "A"
},
{
"expr": "sum(resource_manager_resource_unit_write_request_unit_max_per_sec{k8s_cluster=\"$k8s_cluster\", tidb_cluster=\"$tidb_cluster\", resource_group=~\"$resource_group\"}) by (resource_group)",
"format": "time_series",
"intervalFactor": 2,
"legendFormat": "{{resource_group}}-write",
"refId": "B"
}
],
"thresholds": [ ],
"timeFrom": null,
"timeShift": null,
"title": "RU Max(Max Cost During 20s Period)",
"title": "Peak RU/s",
"tooltip": {
"shared": true,
"sort": 0,
Expand All @@ -317,17 +312,17 @@
{
"format": "short",
"label": null,
"logBase": 10,
"logBase": 1,
"max": null,
"min": null,
"min": 0,
"show": true
},
{
"format": "short",
"label": null,
"logBase": 1,
"max": null,
"min": null,
"min": 0,
"show": true
}
]
Expand Down
Loading