From 291aafa2c9ee3d58b43ee2da24ba86eff19227e4 Mon Sep 17 00:00:00 2001 From: bwplotka Date: Mon, 10 Jun 2024 08:56:23 +0100 Subject: [PATCH] Proposed wording changes after Tom Wilkie's feedback. Signed-off-by: bwplotka --- content/docs/concepts/remote_write_spec_2_0.md | 2 +- content/docs/specs/remote_write_spec.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/content/docs/concepts/remote_write_spec_2_0.md b/content/docs/concepts/remote_write_spec_2_0.md index 25629ffa..4f269c36 100644 --- a/content/docs/concepts/remote_write_spec_2_0.md +++ b/content/docs/concepts/remote_write_spec_2_0.md @@ -26,7 +26,7 @@ The Remote-Write protocol is designed to make it possible to reliably propagate -The Remote-Write protocol is designed to make stateless implementations of the server possible; as such there are little-to-no inter-message references. As such the protocol is not considered "streaming." To achieve a streaming effect multiple messages should be sent over the same connection using e.g. HTTP/1.1 or HTTP/2. "Fancy" technologies such as gRPC were considered, but at the time were not widely adopted, and it was challenging to expose gRPC services to the internet behind load balancers such as an AWS EC2 ELB. +The Remote-Write protocol is designed to be stateless; there is strictly no inter-message communication. As such the protocol is not considered "streaming." To achieve a streaming effect multiple messages should be sent over the same connection using e.g. HTTP/1.1 or HTTP/2. "Fancy" technologies such as gRPC were considered, but at the time were not widely adopted, and it was challenging to expose gRPC services to the internet behind load balancers such as an AWS EC2 ELB. The Remote-Write protocol contains opportunities for batching, e.g. sending multiple samples for different series in a single request. It is not expected that multiple samples for the same series will be commonly sent in the same request, although there is support for this in the Proto Message. diff --git a/content/docs/specs/remote_write_spec.md b/content/docs/specs/remote_write_spec.md index aa2bad26..d24aaab3 100644 --- a/content/docs/specs/remote_write_spec.md +++ b/content/docs/specs/remote_write_spec.md @@ -19,8 +19,7 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S The remote write protocol is designed to make it possible to reliably propagate samples in real-time from a sender to a receiver, without loss. -The remote write protocol is designed to make stateless implementations of the server possible; as such there are little-to-no inter-message references. As such the protocol is not considered "streaming." To achieve a streaming effect multiple messages should be sent over the same connection using e.g. HTTP/1.1 or HTTP/2. "Fancy" technologies such as gRPC were considered, but at the time were not widely adopted, and it was challenging to expose gRPC services to the internet behind load balancers such as an AWS EC2 ELB. - +The Remote-Write protocol is designed to be stateless; there is strictly no inter-message communication. As such the protocol is not considered "streaming. To achieve a streaming effect multiple messages should be sent over the same connection using e.g. HTTP/1.1 or HTTP/2. "Fancy" technologies such as gRPC were considered, but at the time were not widely adopted, and it was challenging to expose gRPC services to the internet behind load balancers such as an AWS EC2 ELB. The remote write protocol contains opportunities for batching, e.g. sending multiple samples for different series in a single request. It is not expected that multiple samples for the same series will be commonly sent in the same request, although there is support for this in the protocol.