mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 12:31:07 +01:00
docs: sync with cluster branch after 97b41e727c
This commit is contained in:
parent
a8b8e23d68
commit
3f4cb9a142
@ -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,
|
- `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.
|
which is returned in the response.
|
||||||
- `api/v1/status/top_queries` - for listing the most frequently executed queries and queries taking the most duration.
|
- `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://<vmselect>:8481/select/<accountID>/graphite/<suffix>`, where:
|
- URLs for [Graphite Metrics API](https://graphite-api.readthedocs.io/en/latest/api.html#the-metrics-api): `http://<vmselect>:8481/select/<accountID>/graphite/<suffix>`, where:
|
||||||
- `<accountID>` is an arbitrary number identifying data namespace for query (aka tenant)
|
- `<accountID>` is an arbitrary number identifying data namespace for query (aka tenant)
|
||||||
|
@ -446,6 +446,8 @@ See also [useful tips for target relabeling](#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.
|
* 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
|
The specific sets of labels per each supported service discovery option are listed
|
||||||
[here](https://docs.victoriametrics.com/sd_configs.html#prometheus-service-discovery).
|
[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
|
## 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.
|
* 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.
|
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,
|
* All the target-level labels are automatically added to all the metrics scraped from targets,
|
||||||
|
Loading…
Reference in New Issue
Block a user