Skip to content

Commit 8139da7

Browse files
bwplotkathampiotr
andauthored
Update content/docs/specs/remote_write_spec_2_0.md
Co-authored-by: Piotr <[email protected]> Signed-off-by: Bartlomiej Plotka <[email protected]>
1 parent b9dac08 commit 8139da7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/specs/remote_write_spec_2_0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ Senders MAY use those headers to confirm which parts of data were successfully w
157157

158158
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.
159159

160-
Senders MUST NOT assume what Remote Write specification version the Receiver implements from the remote write response headers.
160+
Senders MUST NOT assume what Remote Write specification version the Receiver implements the remote write response headers.
161161

162162
More (optional) headers might come in the future, e.g. when more entities or fields are added and worth confirming.
163163

0 commit comments

Comments
 (0)