Skip to content

Commit

Permalink
fixed broken links
Browse files Browse the repository at this point in the history
Signed-off-by: Namanl2001 <namanlakhwani@gmail.com>
  • Loading branch information
Namanl2001 committed Dec 18, 2020
1 parent 4723967 commit 6225861
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
8 changes: 4 additions & 4 deletions docs/integrations.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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)
4 changes: 2 additions & 2 deletions docs/quick-tutorial.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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.


0 comments on commit 6225861

Please sign in to comment.