From 6197ed63d86a591eba72ff27fa11871d4e73c102 Mon Sep 17 00:00:00 2001 From: Oleg Zaytsev Date: Thu, 15 Dec 2022 16:57:44 +0100 Subject: [PATCH] Remove comments from the remote read docs I think these are not intended to be here. Signed-off-by: Oleg Zaytsev --- docs/querying/remote_read_api.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/querying/remote_read_api.md b/docs/querying/remote_read_api.md index aae8e5d1b..30073c3e2 100644 --- a/docs/querying/remote_read_api.md +++ b/docs/querying/remote_read_api.md @@ -65,8 +65,6 @@ Note: Names of query parameters that may be repeated end with `[]`. This API provides data read functionality from Prometheus. This interface expects [snappy](https://github.com/google/snappy) compression. The API definition is located [here](https://github.com/prometheus/prometheus/blob/master/prompb/remote.proto). -/// Can you clarify what you mean by this? -/// https://github.com/prometheus/prometheus/pull/7266#discussion_r426456791 Can we talk a little bit how negotiation works of sampled vs streamed ? Request are made to the following endpoint. ``` @@ -74,12 +72,10 @@ Request are made to the following endpoint. ``` ### Samples -/// Does it return a message that includes a list, or does it return a list of raw samples? This returns a message that includes a list of raw samples. ### Streamed Chunks -/// This is a little much detail, the relevant point is they're the internal implementation of the chunks. These streamed chunks utilize an XOR algorithm inspired by the [Gorilla](http://www.vldb.org/pvldb/vol8/p1816-teller.pdf) compression to encode the chunks. However, it provides resolution to the millisecond instead of to the second.