From 2978d8c6e34e97194993e58a57d0fa29cbaab275 Mon Sep 17 00:00:00 2001 From: Bruno Teixeira Date: Thu, 21 Nov 2024 20:03:45 +0000 Subject: [PATCH] feat/Update exporter/prometheusremotewriteexporter/README.md Co-authored-by: Arthur Silva Sens --- exporter/prometheusremotewriteexporter/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/exporter/prometheusremotewriteexporter/README.md b/exporter/prometheusremotewriteexporter/README.md index 43b30ba4bb20..f612fffda4fc 100644 --- a/exporter/prometheusremotewriteexporter/README.md +++ b/exporter/prometheusremotewriteexporter/README.md @@ -154,14 +154,14 @@ sum by (namespace) (app_ads_ad_requests_total) **DISCLAIMER**: This snippet applies only to Prometheus, other remote write destinations using Prometheus Protocol (ex: Thanos/Grafana Mimir/VictoriaMetrics) may have different settings. -By default, Prometheus tipically expects samples to be ingested sequentially, in temporal order. +By default, Prometheus expects samples to be ingested sequentially, in temporal order. -When multiple consumers are enabled, the temporal ordering the samples written to the target destination is not deterministic and temporal ordering can no longer be garanteed. Example: one worker may be pushing a sample for `t+30s` and a second worker may push an additional sample but for `t+15s`. +When multiple consumers are enabled, the temporal ordering of the samples written to the target destination is not deterministic, and temporal ordering can no longer be guaranteed. For example, one worker may push a sample for `t+30s`, and a second worker may push an additional sample but for `t+15s`. -Vanilla Prometheus configurations will reject these unordered samples. You will find similar error to this `Error on ingesting out-of-order samples`. +Vanilla Prometheus configurations will reject these unordered samples and you'll receive "out of order" errors. -For enabling multiple consumers, it is necessary to enable out-of-order support in Prometheus. -This can be done by using the `tsdb.out_of_order_time_window: 10m` settings. Please choose an appropriate time window to support pushing the worst case scenarios of a "queue" build up on the sender side. +Out-of-order support in Prometheus must be enabled for multiple consumers. +This can be done by using the `tsdb.out_of_order_time_window: 10m` settings. Please choose an appropriate time window to support pushing the worst-case scenarios of a "queue" build-up on the sender side. See for more info: - https://prometheus.io/docs/prometheus/latest/configuration/configuration/#tsdb