You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/components/query.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ menu: components
6
6
7
7
# Querier/Query
8
8
9
-
The Querier component (also known as "Query") implements the [Prometheus HTTP v1 API](https://prometheus.io/docs/prometheus/latest/querying/api/) to query data in a Thanos cluster via PromQL.
9
+
The `thanos query` command (also known as "Querier") implements the [Prometheus HTTP v1 API](https://prometheus.io/docs/prometheus/latest/querying/api/) to query data in a Thanos cluster via PromQL.
10
10
11
11
In short, it gathers the data needed to evaluate the query from underlying [StoreAPIs](../../pkg/store/storepb/rpc.proto), evaluates the query and returns the result.
12
12
@@ -15,7 +15,7 @@ Querier is fully stateless and horizontally scalable.
15
15
Example command to run Querier:
16
16
17
17
```bash
18
-
$ thanos query \
18
+
thanos query \
19
19
--http-address "0.0.0.0:9090" \
20
20
--store "<store-api>:<grpc-port>" \
21
21
--store "<store-api2>:<grpc-port>"
@@ -81,7 +81,7 @@ This also hides gaps in collection of a single data source.
81
81
If we configure Querier like this:
82
82
83
83
```
84
-
$ thanos query \
84
+
thanos query \
85
85
--http-address "0.0.0.0:9090" \
86
86
--query.replica-label "replica" \
87
87
--store "<store-api>:<grpc-port>" \
@@ -106,7 +106,7 @@ WITHOUT this replica flag (deduplication turned off), we will get 3 results:
106
106
* Prometheus + sidecar "A" in different cluster: `cluster=2,env=2,replica=A,replicaX=A`
Copy file name to clipboardExpand all lines: docs/components/rule.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ _**NOTE:** It is recommended to keep deploying rules inside the relevant Prometh
10
10
11
11
_The rule component should in particular not be used to circumvent solving rule deployment properly at the configuration management level._
12
12
13
-
The rule component evaluates Prometheus recording and alerting rules against chosen query API via repeated `--query` (or FileSD via `--query.sd`). If more than one query is passed, round robin balancing is performed.
13
+
The `thanos rule` command evaluates Prometheus recording and alerting rules against chosen query API via repeated `--query` (or FileSD via `--query.sd`). If more than one query is passed, round robin balancing is performed.
14
14
15
15
Rule results are written back to disk in the Prometheus 2.0 storage format. Rule nodes at the same time participate in the system as source store nodes, which means that they expose StoreAPI and upload their generated TSDB blocks to an object store.
16
16
@@ -20,7 +20,7 @@ The data of each Rule node can be labeled to satisfy the clusters labeling schem
20
20
Read more about Ruler in HA [here](rule.md#ruler-ha)
Copy file name to clipboardExpand all lines: docs/components/sidecar.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ menu: components
6
6
7
7
# Sidecar
8
8
9
-
The sidecar component of Thanos gets deployed along with a Prometheus instance. This allows sidecar to optionally upload metrics to object storage and allow [Queriers](./query.md) to query Prometheus data with common, efficient StoreAPI.
9
+
The `thanos sidecar` command runs a component that gets deployed along with a Prometheus instance. This allows sidecar to optionally upload metrics to object storage and allow [Queriers](./query.md) to query Prometheus data with common, efficient StoreAPI.
0 commit comments