Skip to content

Revert "v8.5: remove VictoriaMetrics guide" #21678

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
merged 1 commit into from
Aug 28, 2025
Merged

Revert "v8.5: remove VictoriaMetrics guide" #21678

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
3 changes: 1 addition & 2 deletions maintain-tidb-using-tiup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,7 +283,7 @@ The destroy operation stops the services and clears the data directory and deplo
tiup cluster destroy ${cluster-name}
```

<!-- ## Switch from Prometheus to VictoriaMetrics
## Switch from Prometheus to VictoriaMetrics

In large-scale clusters, Prometheus might encounter performance bottlenecks when handling a large number of instances. Starting from TiUP v1.16.3, TiUP supports switching the monitoring component from Prometheus to VictoriaMetrics (VM) to provide better scalability, higher performance, and lower resource consumption.

Expand Down Expand Up @@ -433,4 +433,3 @@ After confirming that the old metrics have expired, you can perform the followin
```bash
rm -rf /tidb-data/prometheus-8249
```
-->
Loading