prometheus/docs
1
0
Fork 0
mirror of https://github.com/prometheus/docs.git synced 2026-02-05 15:45:27 +01:00
Code Issues Releases Activity

Update content/docs/specs/remote_write_spec_2_0.md

Browse Source 
Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com>
This commit is contained in:
Bartlomiej Plotka
2024-07-11 11:40:59 +01:00
committed by GitHub
parent b9dac08b62
commit 8139da7253
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/docs/specs/remote_write_spec_2_0.md
View File

@@ -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.