diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 1fccad2db..7e7e5c91e 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -8,7 +8,7 @@ body: Before filling a bug report it would be great to [upgrade](https://docs.victoriametrics.com/#how-to-upgrade) to [the latest available release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest) and verify whether the bug is reproducible there. - It's also recommended to read the [troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html) first. + It's also recommended to read the [troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/) first. - type: textarea id: describe-the-bug attributes: diff --git a/.github/ISSUE_TEMPLATE/question.yml b/.github/ISSUE_TEMPLATE/question.yml index 384307234..5fa598b0d 100644 --- a/.github/ISSUE_TEMPLATE/question.yml +++ b/.github/ISSUE_TEMPLATE/question.yml @@ -24,7 +24,7 @@ body: label: Troubleshooting docs description: I am familiar with the following troubleshooting docs options: - - label: General - https://docs.victoriametrics.com/Troubleshooting.html + - label: General - https://docs.victoriametrics.com/troubleshooting/ required: false - label: vmagent - https://docs.victoriametrics.com/vmagent/#troubleshooting required: false diff --git a/README.md b/README.md index 05345425d..bb1ca2fb3 100644 --- a/README.md +++ b/README.md @@ -399,7 +399,7 @@ Query history can be navigated by holding `Ctrl` (or `Cmd` on MacOS) and pressin Multi-line queries can be entered by pressing `Shift-Enter` in query input field. When querying the [backfilled data](https://docs.victoriametrics.com/#backfilling) -or during [query troubleshooting](https://docs.victoriametrics.com/Troubleshooting.html#unexpected-query-results), +or during [query troubleshooting](https://docs.victoriametrics.com/troubleshooting/#unexpected-query-results), it may be useful disabling response cache by clicking `Disable cache` checkbox. VMUI automatically adjusts the interval between datapoints on the graph depending on the horizontal resolution and on the selected time range. @@ -2181,7 +2181,7 @@ VictoriaMetrics exposes currently running queries and their execution times at [ VictoriaMetrics exposes queries, which take the most time to execute, at [`top queries` page](#top-queries). See also [VictoriaMetrics Monitoring](https://victoriametrics.com/blog/victoriametrics-monitoring/) -and [troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html). +and [troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/). ## TSDB stats @@ -2384,7 +2384,7 @@ and [cardinality explorer docs](#cardinality-explorer). See also: - [Snapshot troubleshooting](#snapshot-troubleshooting). -- [General troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html). +- [General troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/). ## Push metrics diff --git a/dashboards/vm/vmalert.json b/dashboards/vm/vmalert.json index f83270c06..f6a548721 100644 --- a/dashboards/vm/vmalert.json +++ b/dashboards/vm/vmalert.json @@ -1271,7 +1271,7 @@ "type": "victoriametrics-datasource", "uid": "$ds" }, - "description": "Missed evaluation means that group evaluation time takes longer than the configured evaluation interval. \nThis may result in missed alerting notifications or recording rules samples. Try increasing evaluation interval or concurrency for such groups. See https://docs.victoriametrics.com/vmalert/#groups\n\nIf rule expressions are taking longer than expected, please see https://docs.victoriametrics.com/Troubleshooting.html#slow-queries.\"", + "description": "Missed evaluation means that group evaluation time takes longer than the configured evaluation interval. \nThis may result in missed alerting notifications or recording rules samples. Try increasing evaluation interval or concurrency for such groups. See https://docs.victoriametrics.com/vmalert/#groups\n\nIf rule expressions are taking longer than expected, please see https://docs.victoriametrics.com/troubleshooting/#slow-queries.\"", "fieldConfig": { "defaults": { "color": { diff --git a/dashboards/vmalert.json b/dashboards/vmalert.json index d91714719..0fca1823d 100644 --- a/dashboards/vmalert.json +++ b/dashboards/vmalert.json @@ -1270,7 +1270,7 @@ "type": "prometheus", "uid": "$ds" }, - "description": "Missed evaluation means that group evaluation time takes longer than the configured evaluation interval. \nThis may result in missed alerting notifications or recording rules samples. Try increasing evaluation interval or concurrency for such groups. See https://docs.victoriametrics.com/vmalert/#groups\n\nIf rule expressions are taking longer than expected, please see https://docs.victoriametrics.com/Troubleshooting.html#slow-queries.\"", + "description": "Missed evaluation means that group evaluation time takes longer than the configured evaluation interval. \nThis may result in missed alerting notifications or recording rules samples. Try increasing evaluation interval or concurrency for such groups. See https://docs.victoriametrics.com/vmalert/#groups\n\nIf rule expressions are taking longer than expected, please see https://docs.victoriametrics.com/troubleshooting/#slow-queries.\"", "fieldConfig": { "defaults": { "color": { diff --git a/deployment/docker/alerts-vmalert.yml b/deployment/docker/alerts-vmalert.yml index a67de956b..bae602201 100644 --- a/deployment/docker/alerts-vmalert.yml +++ b/deployment/docker/alerts-vmalert.yml @@ -62,7 +62,7 @@ groups: The group evaluation time takes longer than the configured evaluation interval. This may result in missed alerting notifications or recording rules samples. Try increasing evaluation interval or concurrency of group \"{{ $labels.group }}\". See https://docs.victoriametrics.com/vmalert/#groups. - If rule expressions are taking longer than expected, please see https://docs.victoriametrics.com/Troubleshooting.html#slow-queries." + If rule expressions are taking longer than expected, please see https://docs.victoriametrics.com/troubleshooting/#slow-queries." - alert: RemoteWriteErrors expr: increase(vmalert_remotewrite_errors_total[5m]) > 0 diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index 91dee6035..ab4811724 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -350,7 +350,7 @@ See more details about cardinality limiter in [these docs](https://docs.victoria [rolling restarts and configuration updates](https://docs.victoriametrics.com/cluster-victoriametrics/#updating--reconfiguring-cluster-nodes), then see [these docs](#improving-re-routing-performance-during-restart). -[Troubleshooting docs for single-node VictoriaMetrics](https://docs.victoriametrics.com/Troubleshooting.html) apply to VictoriaMetrics cluster as well. +[Troubleshooting docs for single-node VictoriaMetrics](https://docs.victoriametrics.com/troubleshooting/) apply to VictoriaMetrics cluster as well. ## Readonly mode diff --git a/docs/FAQ.md b/docs/FAQ.md index 99acb4176..b3a6e65c5 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -373,7 +373,7 @@ See [this article](https://valyala.medium.com/how-to-optimize-promql-and-metrics VictoriaMetrics also provides [query tracer](https://docs.victoriametrics.com/#query-tracing) and [cardinality explorer](https://docs.victoriametrics.com/#cardinality-explorer), which can help during query optimization. -See also [troubleshooting slow queries](https://docs.victoriametrics.com/Troubleshooting.html#slow-queries). +See also [troubleshooting slow queries](https://docs.victoriametrics.com/troubleshooting/#slow-queries). ## Which VictoriaMetrics type is recommended for use in production - single-node or cluster? diff --git a/docs/README.md b/docs/README.md index 930cf6f3d..3df2ce1c4 100644 --- a/docs/README.md +++ b/docs/README.md @@ -402,7 +402,7 @@ Query history can be navigated by holding `Ctrl` (or `Cmd` on MacOS) and pressin Multi-line queries can be entered by pressing `Shift-Enter` in query input field. When querying the [backfilled data](https://docs.victoriametrics.com/#backfilling) -or during [query troubleshooting](https://docs.victoriametrics.com/Troubleshooting.html#unexpected-query-results), +or during [query troubleshooting](https://docs.victoriametrics.com/troubleshooting/#unexpected-query-results), it may be useful disabling response cache by clicking `Disable cache` checkbox. VMUI automatically adjusts the interval between datapoints on the graph depending on the horizontal resolution and on the selected time range. @@ -2184,7 +2184,7 @@ VictoriaMetrics exposes currently running queries and their execution times at [ VictoriaMetrics exposes queries, which take the most time to execute, at [`top queries` page](#top-queries). See also [VictoriaMetrics Monitoring](https://victoriametrics.com/blog/victoriametrics-monitoring/) -and [troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html). +and [troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/). ## TSDB stats @@ -2387,7 +2387,7 @@ and [cardinality explorer docs](#cardinality-explorer). See also: - [Snapshot troubleshooting](#snapshot-troubleshooting). -- [General troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html). +- [General troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/). ## Push metrics diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 6ab92f4d4..c69c89408 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -410,7 +410,7 @@ Query history can be navigated by holding `Ctrl` (or `Cmd` on MacOS) and pressin Multi-line queries can be entered by pressing `Shift-Enter` in query input field. When querying the [backfilled data](https://docs.victoriametrics.com/#backfilling) -or during [query troubleshooting](https://docs.victoriametrics.com/Troubleshooting.html#unexpected-query-results), +or during [query troubleshooting](https://docs.victoriametrics.com/troubleshooting/#unexpected-query-results), it may be useful disabling response cache by clicking `Disable cache` checkbox. VMUI automatically adjusts the interval between datapoints on the graph depending on the horizontal resolution and on the selected time range. @@ -2192,7 +2192,7 @@ VictoriaMetrics exposes currently running queries and their execution times at [ VictoriaMetrics exposes queries, which take the most time to execute, at [`top queries` page](#top-queries). See also [VictoriaMetrics Monitoring](https://victoriametrics.com/blog/victoriametrics-monitoring/) -and [troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html). +and [troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/). ## TSDB stats @@ -2395,7 +2395,7 @@ and [cardinality explorer docs](#cardinality-explorer). See also: - [Snapshot troubleshooting](#snapshot-troubleshooting). -- [General troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html). +- [General troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/). ## Push metrics diff --git a/docs/vmagent.md b/docs/vmagent.md index 799713491..f16a1115a 100644 --- a/docs/vmagent.md +++ b/docs/vmagent.md @@ -1230,7 +1230,7 @@ See also: - [debugging scrape targets](#debugging-scrape-targets) - [relabel debug](#relabel-debug) -- [general troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html) +- [general troubleshooting docs](https://docs.victoriametrics.com/troubleshooting/) ## Calculating disk space for persistence queue