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: CODE_OF_CONDUCT.md
+1-4
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,4 @@ face temporary or permanent repercussions as determined by other members of the
58
58
59
59
## Attribution
60
60
61
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4/)
Copy file name to clipboardExpand all lines: docs/components/rule.md
+7-1
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
---
2
+
title: Rule
3
+
type: docs
4
+
menu: components
5
+
---
6
+
1
7
# Rule (aka Ruler)
2
8
3
9
_**NOTE:** It is recommended to ma deploying rules inside the relevant Prometheus servers locally. Use ruler only on specific cases. Read details[below](rule.md#Risk) why._
@@ -13,7 +19,7 @@ You can think of Rule as a simplified Prometheus that does not require a sidecar
13
19
The data of each Rule node can be labeled to satisfy the clusters labeling scheme. High-availability pairs can be run in parallel and should be distinguished by the designated replica label, just like regular Prometheus servers.
14
20
Read more about Ruler in HA in [here](rule.md#Ruler_HA)
Copy file name to clipboardExpand all lines: docs/components/sidecar.md
+8-2
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
---
2
+
title: Sidecar
3
+
type: docs
4
+
menu: components
5
+
---
6
+
1
7
# Sidecar
2
8
3
9
The sidecar component of Thanos gets deployed along with a Prometheus instance. It implements Thanos' Store API on top of Prometheus' remote-read API and advertises itself as a data source to the cluster. Thereby queriers in the cluster can treat Prometheus servers as yet another source of time series data without directly talking to its APIs.
@@ -13,14 +19,14 @@ Prometheus servers connected to the Thanos cluster via the sidecar are subject t
13
19
The retention is recommended to not be lower than three times the block duration. This achieves resilience in the face of connectivity issues
14
20
to the object storage since all local data will remain available within the Thanos cluster. If connectivity gets restored the backlog of blocks gets uploaded to the object storage.
Copy file name to clipboardExpand all lines: docs/components/store.md
+7-1
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,15 @@
1
+
---
2
+
title: Store
3
+
type: docs
4
+
menu: components
5
+
---
6
+
1
7
# Store
2
8
3
9
The store component of Thanos implements the Store API on top of historical data in an object storage bucket. It acts primarily as an API gateway and therefore does not need significant amounts of local disk space. It joins a Thanos cluster on startup and advertises the data it can access.
4
10
It keeps a small amount of information about all remote blocks on local disk and keeps it in sync with the bucket. This data is generally safe to delete across restarts at the cost of increased startup times.
0 commit comments