mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 12:31:07 +01:00
docs/Single-server-VictoriaMetrics.md: update victoria-metrics -help
output after e7fdea5953
This commit is contained in:
parent
e7fdea5953
commit
3be0e6b087
@ -1758,6 +1758,8 @@ Pass `-help` to VictoriaMetrics in order to see the list of supported command-li
|
|||||||
The maximum time the request waits for execution when -search.maxConcurrentRequests limit is reached; see also -search.maxQueryDuration (default 10s)
|
The maximum time the request waits for execution when -search.maxConcurrentRequests limit is reached; see also -search.maxQueryDuration (default 10s)
|
||||||
-search.maxStalenessInterval duration
|
-search.maxStalenessInterval duration
|
||||||
The maximum interval for staleness calculations. By default it is automatically calculated from the median interval between samples. This flag could be useful for tuning Prometheus data model closer to Influx-style data model. See https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness for details. See also '-search.maxLookback' flag, which has the same meaning due to historical reasons
|
The maximum interval for staleness calculations. By default it is automatically calculated from the median interval between samples. This flag could be useful for tuning Prometheus data model closer to Influx-style data model. See https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness for details. See also '-search.maxLookback' flag, which has the same meaning due to historical reasons
|
||||||
|
-search.maxStatusRequestDuration duration
|
||||||
|
The maximum duration for /api/v1/status/* requests (default 5m0s)
|
||||||
-search.maxStepForPointsAdjustment duration
|
-search.maxStepForPointsAdjustment duration
|
||||||
The maximum step when /api/v1/query_range handler adjusts points with timestamps closer than -search.latencyOffset to the current time. The adjustment is needed because such points may contain incomplete data (default 1m0s)
|
The maximum step when /api/v1/query_range handler adjusts points with timestamps closer than -search.latencyOffset to the current time. The adjustment is needed because such points may contain incomplete data (default 1m0s)
|
||||||
-search.maxTagKeys int
|
-search.maxTagKeys int
|
||||||
|
@ -1758,6 +1758,8 @@ Pass `-help` to VictoriaMetrics in order to see the list of supported command-li
|
|||||||
The maximum time the request waits for execution when -search.maxConcurrentRequests limit is reached; see also -search.maxQueryDuration (default 10s)
|
The maximum time the request waits for execution when -search.maxConcurrentRequests limit is reached; see also -search.maxQueryDuration (default 10s)
|
||||||
-search.maxStalenessInterval duration
|
-search.maxStalenessInterval duration
|
||||||
The maximum interval for staleness calculations. By default it is automatically calculated from the median interval between samples. This flag could be useful for tuning Prometheus data model closer to Influx-style data model. See https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness for details. See also '-search.maxLookback' flag, which has the same meaning due to historical reasons
|
The maximum interval for staleness calculations. By default it is automatically calculated from the median interval between samples. This flag could be useful for tuning Prometheus data model closer to Influx-style data model. See https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness for details. See also '-search.maxLookback' flag, which has the same meaning due to historical reasons
|
||||||
|
-search.maxStatusRequestDuration duration
|
||||||
|
The maximum duration for /api/v1/status/* requests (default 5m0s)
|
||||||
-search.maxStepForPointsAdjustment duration
|
-search.maxStepForPointsAdjustment duration
|
||||||
The maximum step when /api/v1/query_range handler adjusts points with timestamps closer than -search.latencyOffset to the current time. The adjustment is needed because such points may contain incomplete data (default 1m0s)
|
The maximum step when /api/v1/query_range handler adjusts points with timestamps closer than -search.latencyOffset to the current time. The adjustment is needed because such points may contain incomplete data (default 1m0s)
|
||||||
-search.maxTagKeys int
|
-search.maxTagKeys int
|
||||||
|
Loading…
Reference in New Issue
Block a user