Feel free to check the free, in-browser interactive tutorial as Katacoda Thanos Course We will be progressively updating our Katacoda Course with more scenarios.
On top of this feel free to go through our tutorial presented here:
Thanos is based on Prometheus. With Thanos you use more or less Prometheus features depending on the deployment model, however Prometheus always stays as integral foundation for collecting metrics and alerting using local data.
Thanos bases itself on vanilla Prometheus (v2.2.1+). We plan to support all Prometheus version beyond this version.
NOTE: It is highly recommended to use Prometheus 2.13 (available in next Prometheus release) due to Prometheus remote read improvements.
Always make sure to run Prometheus as recommended by Prometheus team, so:
We recommend using Thanos when you need to scale out your Prometheus instance.
Following the KISS and Unix philosophies, Thanos is made of a set of components with each filling a specific role.
See those components on this diagram:
Thanos integrates with existing Prometheus servers through a Sidecar process, which runs on the same machine or in the same pod as the Prometheus server.
The purpose of the Sidecar is to backup Prometheus data into an Object Storage bucket, and give other Thanos components access to the Prometheus metrics via a gRPC API.
The Sidecar makes use of the
reload Prometheus endpoint. Make sure it’s enabled with the flag
The following configures the sidecar to write Prometheus' data into a configured object storage:
thanos sidecar \ --tsdb.path /var/prometheus \ # TSDB data directory of Prometheus --prometheus.url "http://localhost:9090" \ # Be sure that the sidecar can use this url! --objstore.config-file bucket_config.yaml \ # Storage configuration for uploading data
The format of YAML file depends on the provider you choose. Examples of config and up-to-date list of storage types Thanos supports is available here.
Rolling this out has little to zero impact on the running Prometheus instance. It is a good start to ensure you are backing up your data while figuring out the other pieces of Thanos.
If you are not interested in backing up any data, the
--objstore.config-file flag can simply be omitted.
The Sidecar component implements and exposes a gRPC Store API. The sidecar implementation allows you to query the metric data stored in Prometheus.
Let’s extend the Sidecar in the previous section to connect to a Prometheus server, and expose the Store API.
thanos sidecar \ --tsdb.path /var/prometheus \ --objstore.config-file bucket_config.yaml \ # Bucket config file to send data to --prometheus.url http://localhost:9090 \ # Location of the Prometheus HTTP server --http-address 0.0.0.0:19191 \ # HTTP endpoint for collecting metrics on the Sidecar --grpc-address 0.0.0.0:19090 # GRPC endpoint for StoreAPI
Prometheus allows the configuration of “external labels” of a given Prometheus instance. These are meant to globally identify the role of that instance. As Thanos aims to aggregate data across all instances, providing a consistent set of external labels becomes crucial!
Every Prometheus instance must have a globally unique set of identifying labels. For example, in Prometheus’s configuration file:
global: external_labels: region: eu-west monitor: infrastructure replica: A
Now that we have setup the Sidecar for one or more Prometheus instances, we want to use Thanos' global Query Layer 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.
Query also implements Prometheus’s official HTTP API and can thus be used with external tools such as Grafana. It also serves a derivative of Prometheus’s UI for ad-hoc querying and stores status.
Below, we will set up a Query to connect to our Sidecars, and expose its HTTP UI.
thanos query \ --http-address 0.0.0.0:19192 \ # HTTP Endpoint for Query UI --store 184.108.40.206:19090 \ # Static gRPC Store API Address for the query node to query --store 220.127.116.11:19090 \ # Also repeatable --store dnssrv+_grpc._tcp.thanos-store.monitoring.svc # Supports DNS A & SRV records
Go to the configured HTTP address that should now show a UI similar to that of Prometheus. If the cluster formed correctly you can now query across all Prometheus instances within the cluster. You can also check the Stores page to check up on your stores.
The Query component is also capable of deduplicating data collected from Prometheus HA pairs. This requires configuring Prometheus’s
global.external_labels configuration block (as mentioned in the External Labels section) to identify the role of a given Prometheus instance.
A typical choice is simply the label name “replica” while letting the value be whatever you wish. For example, you might set up the following in Prometheus’s configuration file:
global: external_labels: region: eu-west monitor: infrastructure replica: A # ...
In a Kubernetes stateful deployment, the replica label can also be the pod name.
Reload your Prometheus instances, and then, in Query, we will define
replica as the label we want to enable deduplication to occur on:
thanos query \ --http-address 0.0.0.0:19192 \ --store 18.104.22.168:19090 \ --store 22.214.171.124:19090 \ --query.replica-label replica # Replica label for de-duplication --query.replica-label replicaX # Supports multiple replica labels for de-duplication
Go to the configured HTTP address, and you should now be able to query across all Prometheus instances and receive de-duplicated data.
The only required communication between nodes is for Thanos Querier to be able to reach gRPC storeAPIs you provide. Thanos Querier periodically calls Info endpoint to collect up-to-date metadata as well as checking the health of given StoreAPI. The metadata includes the information about time windows and external labels for each node.
There are various ways to tell query component about the StoreAPIs it should query data from. The simplest way is to use a static list of well known addresses to query. These are repeatable so can add as many endpoint as needed. You can put DNS domain prefixed by
dnssrv+ to have Thanos Query do an
SRV lookup to get all required IPs to communicate with.
thanos query \ --http-address 0.0.0.0:19192 \ # Endpoint for Query UI --grpc-address 0.0.0.0:19092 \ # gRPC endpoint for Store API --store 126.96.36.199:19090 \ # Static gRPC Store API Address for the query node to query --store 188.8.131.52:19090 \ # Also repeatable --store dns+rest.thanos.peers:19092 # Use DNS lookup for getting all registered IPs as separate StoreAPIs
Read more details here.
As the sidecar backs up data into the object storage of your choice, you can decrease Prometheus retention and store less locally. However we need a way to query all that historical data again. The store gateway does just that by implementing the same gRPC data API as the sidecars but backing it with data it can find in your object storage bucket. Just like sidecars and query nodes, the store gateway exposes StoreAPI and needs to be discovered by Thanos Querier.
thanos store \ --data-dir /var/thanos/store \ # Disk space for local caches --objstore.config-file bucket_config.yaml \ # Bucket to fetch data from --http-address 0.0.0.0:19191 \ # HTTP endpoint for collecting metrics on the Store Gateway --grpc-address 0.0.0.0:19090 # GRPC endpoint for StoreAPI
The store gateway occupies small amounts of disk space for caching basic information about data in the object storage. This will rarely exceed more than a few gigabytes and is used to improve restart times. It is useful but not required to preserve it across restarts.
A local Prometheus installation periodically compacts older data to improve query efficiency. Since the sidecar backs up data as soon as possible, we need a way to apply the same process to data in the object storage.
The compactor component simple scans the object storage and processes compaction where required. At the same time it is responsible for creating downsampled copies of data to speed up queries.
thanos compact \ --data-dir /var/thanos/compact \ # Temporary workspace for data processing --objstore.config-file bucket_config.yaml \ # Bucket where to apply the compacting --http-address 0.0.0.0:19191 # HTTP endpoint for collecting metrics on the Compactor
The compactor is not in the critical path of querying or data backup. It can either be run as a periodic batch job or be left running to always compact data as soon as possible. It is recommended to provide 100-300GB of local disk space for data processing. It is recommended to provide 100-300GB of local disk space for data processing.
NOTE: The compactor must be run as a singleton and must not run when manually modifying data in the bucket.
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, which does rule and alert evaluation on top of a given Thanos Querier.