diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index f6ce1a22d..0f9bb11d2 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -323,6 +323,7 @@ See [troubleshooting docs](https://docs.victoriametrics.com/Troubleshooting.html - `api/v1/status/active_queries` - for currently executed active queries. Note that every `vmselect` maintains an independent list of active queries, which is returned in the response. - `api/v1/status/top_queries` - for listing the most frequently executed queries and queries taking the most duration. + - `metric-relabel-debug` - for debugging [relabeling rules](https://docs.victoriametrics.com/relabeling.html). - URLs for [Graphite Metrics API](https://graphite-api.readthedocs.io/en/latest/api.html#the-metrics-api): `http://:8481/select//graphite/`, where: - `` is an arbitrary number identifying data namespace for query (aka tenant) diff --git a/docs/relabeling.md b/docs/relabeling.md index 1b295a63a..3e5df86a6 100644 --- a/docs/relabeling.md +++ b/docs/relabeling.md @@ -446,6 +446,8 @@ See also [useful tips for target relabeling](#useful-tips-for-target-relabeling) ## Useful tips for target relabeling +* Target relabelig can be debugged by clicking the `debug` link for the needed target on the `http://vmagent:8429/target` + or on the `http://vmagent:8429/service-discovery` pages. See [these docs](https://docs.victoriametrics.com/vmagent.html#relabel-debug). * Every discovered target contains a set of meta-labels, which start with `__meta_` prefix. The specific sets of labels per each supported service discovery option are listed [here](https://docs.victoriametrics.com/sd_configs.html#prometheus-service-discovery). @@ -462,6 +464,8 @@ See also [useful tips for target relabeling](#useful-tips-for-target-relabeling) ## Useful tips for metric relabeling +* Metric relabeling can be debugged at `http://vmagent:8429/metric-relabel-debug` page. + See [these docs](https://docs.victoriametrics.com/vmagent.html#relabel-debug). * All the labels, which start with `__` prefix, are automatically removed from metrics after the relabeling. So it is common practice to store temporary labels with names startigh with `__` during metrics relabeling. * All the target-level labels are automatically added to all the metrics scraped from targets,