From e50ee4d6558ccf908384b77322b951304dfd8690 Mon Sep 17 00:00:00 2001 From: bwplotka Date: Wed, 5 Jun 2024 17:45:34 +0100 Subject: [PATCH] Added Experimental status, moved to 2.0-rc.0 version. Signed-off-by: bwplotka --- content/docs/concepts/remote_write_spec_2_0.md | 8 +++++--- 1 file changed, 5 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 1aeb75a1..0786a3cf 100644 --- a/content/docs/concepts/remote_write_spec_2_0.md +++ b/content/docs/concepts/remote_write_spec_2_0.md @@ -1,14 +1,16 @@ --- -title: Prometheus Remote-Write Specification 2.0 +title: "[EXPERIMENTAL] Prometheus Remote-Write Specification 2.0" sort_rank: 4 --- # Prometheus Remote-Write Specification -* Version: 2.0 -* Status: Proposed +* Version: 2.0-rc.0 +* Status: **Experimental** * Date: May 2024 +> NOTE: This is a release candidate for Remote-Write 2.0 specification. This means that this specification is currently in an experimental state--no major changes are expected, but we reserve the rights to break the compatibility if it's absolutely necessary, based on the early adopters' feedback. The potential feedback, questions and suggestions should be added as comments to the [PR with the open proposal](https://github.com/prometheus/proposals/pull/35). + The Remote-Write specification, in general, is intended to document the standard for how Prometheus and Prometheus Remote-Write compatible senders send data to Prometheus or Prometheus Remote-Write compatible receivers. This document is intended to define a second version of the [Prometheus Remote-Write](./remote_write_spec.md) API with minor changes to protocol and semantics. This second version adds a new Proto Message with new features enabling more use cases and wider adoption on top of performance and cost savings. The second version also deprecates the previous Proto Message from a [1.0 Remote-Write specification](./remote_write_spec.md#protocol). Finally, this spec outlines how to implement backwards-compatible senders and receivers (even under a single endpoint) using existing basic content negotiation request headers. More advanced, automatic content negotiation mechanisms might come in a future minor version, if needed. For the rationales behind the 2.0 specification, see [the formal proposal](https://github.com/prometheus/proposals/pull/35).