From 8139da7253df774e1ea848785b8cb4838ddcff0d Mon Sep 17 00:00:00 2001 From: Bartlomiej Plotka Date: Thu, 11 Jul 2024 11:40:59 +0100 Subject: [PATCH] Update content/docs/specs/remote_write_spec_2_0.md Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com> Signed-off-by: Bartlomiej Plotka --- content/docs/specs/remote_write_spec_2_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/specs/remote_write_spec_2_0.md b/content/docs/specs/remote_write_spec_2_0.md index 94ea4756..afdb4c0b 100644 --- a/content/docs/specs/remote_write_spec_2_0.md +++ b/content/docs/specs/remote_write_spec_2_0.md @@ -157,7 +157,7 @@ Senders MAY use those headers to confirm which parts of data were successfully w On the 2xx HTTP status code, Senders CAN assume that a missing write response header means that no such a piece of data was written by the Receiver (count of `0`). value. One exception is that Senders MUST NOT assume the same (empty header means zero) when using the deprecated `prometheus.WriteRequest` Protobuf Message in the request. -Senders MUST NOT assume what Remote Write specification version the Receiver implements from the remote write response headers. +Senders MUST NOT assume what Remote Write specification version the Receiver implements the remote write response headers. More (optional) headers might come in the future, e.g. when more entities or fields are added and worth confirming.