From 2b870b1116b62aa71e173b3a1c378170e8ad1af4 Mon Sep 17 00:00:00 2001 From: Artem Navoiev Date: Fri, 26 Jan 2024 20:30:29 +0100 Subject: [PATCH] docs: fix key concepts image and links Signed-off-by: Artem Navoiev --- docs/keyConcepts.md | 23 +++++------------------ 1 file changed, 5 insertions(+), 18 deletions(-) diff --git a/docs/keyConcepts.md b/docs/keyConcepts.md index 597b0b9ce1..a500cc2a2d 100644 --- a/docs/keyConcepts.md +++ b/docs/keyConcepts.md @@ -475,7 +475,7 @@ The basic monitoring setup of VictoriaMetrics and vmagent is described in the [example docker-compose manifest](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/deployment/docker). In this example vmagent [scrapes a list of targets](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/prometheus.yml) and [forwards collected data to VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/9d7da130b5a873be334b38c8d8dec702c9e8fac5/deployment/docker/docker-compose.yml#L15). -VictoriaMetrics is then used as a [datasource for Grafana](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/provisioning/datasources/datasource.yml) +VictoriaMetrics is then used as a [datasource for Grafana](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/deployment/docker/provisioning/datasources) installation for querying collected data. VictoriaMetrics components allow building more advanced topologies. For example, vmagents can push metrics from separate datacenters to the central VictoriaMetrics: @@ -537,12 +537,8 @@ foo_bar 4.00 1652170560000 # 2022-05-10 10:16:00 The data above contains a list of samples for the `foo_bar` time series with time intervals between samples ranging from 1m to 3m. If we plot this data sample on the graph, it will have the following form: -

- - - -

- + + To get the value of the `foo_bar` series at some specific moment of time, for example `2022-05-10 10:03:00`, in VictoriaMetrics we need to issue an **instant query**: @@ -575,12 +571,7 @@ In response, VictoriaMetrics returns a single sample-timestamp pair with a value we'll see that there is no raw sample at `2022-05-10 10:03`. When there is no raw sample at the requested timestamp, VictoriaMetrics will try to locate the closest sample before the requested timestamp: -

- - - -

- + The time range in which VictoriaMetrics will try to locate a replacement for a missing data sample is equal to `5m` by default and can be overridden via the `step` parameter. @@ -712,11 +703,7 @@ see that it contains only 13 raw samples. What happens here is that the range qu an [instant query](#instant-query) executed `1 + (start-end)/step` times on the time range from `start` to `end`. If we plot this request in VictoriaMetrics the graph will be shown as the following: -

- - - -

+ The blue dotted lines in the figure are the moments when the instant query was executed. Since the instant query retains the ability to return replacements for missing points, the graph contains two types of data points: `real` and `ephemeral`.