From a418ea774fe8c1167ac765c8915624d0d8c3350c Mon Sep 17 00:00:00 2001 From: Namanl2001 Date: Fri, 18 Dec 2020 21:35:50 +0530 Subject: [PATCH] fixed broken links --- docs/integrations.md | 8 ++++---- docs/quick-tutorial.md | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/integrations.md b/docs/integrations.md index d8c377cc9f0..5e80794cbab 100644 --- a/docs/integrations.md +++ b/docs/integrations.md @@ -9,9 +9,9 @@ menu: thanos ## StoreAPI [StoreAPI](https://github.com/thanos-io/thanos/blob/master/pkg/store/storepb/rpc.proto) is a common proto interface for gRPC component -that can connect to [Querier](components/query.md) in order to fetch the metric series. -Natively Thanos implements [Sidecar](components/sidecar.md) (local Prometheus data), -[Ruler](components/rule.md) and [Store gateway](components/store.md). +that can connect to [Querier](../components/query.md) in order to fetch the metric series. +Natively Thanos implements [Sidecar](../components/sidecar.md) (local Prometheus data), +[Ruler](../components/rule.md) and [Store gateway](../components/store.md). This solves fetching series from Prometheus or Prometheus TSDB format, however same interface can be used to fetch metrics from other storages. @@ -29,5 +29,5 @@ Although OpenTSDB is able to aggregate the data, it's not supported by Geras at [thanos-remote-read](https://github.com/G-Research/thanos-remote-read) is another StoreAPI integration from our friends at G-Research. -It's a proxy, that allows exposing any Thanos service (or anything that exposes gRPC StoreAPI e.g. [Querier](components/query.md)) via Prometheus [remote read](https://github.com/prometheus/prometheus/blob/38d32e06862f6b72700f67043ce574508b5697f0/prompb/remote.proto#L27) +It's a proxy, that allows exposing any Thanos service (or anything that exposes gRPC StoreAPI e.g. [Querier](../components/query.md)) via Prometheus [remote read](https://github.com/prometheus/prometheus/blob/38d32e06862f6b72700f67043ce574508b5697f0/prompb/remote.proto#L27) protocol. This means that you can connect Thanos and expose its data to any remote-read compatible applications including [Prometheus itself.](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_read) diff --git a/docs/quick-tutorial.md b/docs/quick-tutorial.md index d1fe5a4a322..80faa669a69 100644 --- a/docs/quick-tutorial.md +++ b/docs/quick-tutorial.md @@ -114,7 +114,7 @@ global: ### [Querier/Query](components/query.md) -Now that we have setup the Sidecar for one or more Prometheus instances, we want to use Thanos' global [Query Layer](components/query.md) to evaluate PromQL queries against all instances at once. +Now that we have setup the Sidecar for one or more Prometheus instances, we want to use Thanos' global [Query Layer](../components/query.md) to evaluate PromQL queries against all instances at once. The Query component is stateless and horizontally scalable and can be deployed with any number of replicas. Once connected to the Sidecars, it automatically detects which Prometheus servers need to be contacted for a given PromQL query. @@ -224,7 +224,7 @@ _NOTE: The compactor must be run as a **singleton** and must not run when manual ### [Ruler/Rule](components/rule.md) -In case of Prometheus with Thanos sidecar does not have enough retention, or if you want to have alerts or recording rules that requires global view, Thanos has just the component for that: the [Ruler](components/rule.md), +In case of Prometheus with Thanos sidecar does not have enough retention, or if you want to have alerts or recording rules that requires global view, Thanos has just the component for that: the [Ruler](../components/rule.md), which does rule and alert evaluation on top of a given Thanos Querier.