Thanos provides a global query view, high availability, data backup with historical, cheap data access as its core features in a single binary.
Those features can be deployed independently of each other. This allows you to have a subset of Thanos features ready for immediate benefit or testing, while also making it flexible for gradual roll outs in more complex environments.
In this quick-start guide, we will explain:
Thanos will work in cloud native environments as well as more traditional ones. Some users run Thanos in Kubernetes while others on the bare metal.
Thanos aims for a simple deployment and maintenance model. The only dependencies are:
You can find the latest Thanos release here.
We also perform minor releases every 6 weeks.
During that, we build tarballs for major platforms and release docker images.
See release process docs for details.
Thanos is built purely in Golang, thus allowing to run Thanos on various x64 operating systems.
If you want to build Thanos from source you would need a working installation of the Go 1.15+ toolchain (
Thanos can be downloaded and built by running:
go get github.com/thanos-io/thanos/cmd/thanos
thanos binary should now be in your
$PATH and is the only thing required to deploy any of its components.
Contributions are very welcome! See our CONTRIBUTING.md for more information.
Thanos is an open source project and we value and welcome new contributors and members of the community. Here are ways to get in touch with the community:
Thanos is not tied to Kubernetes. However, Kubernetes, Thanos and Prometheus are part of the CNCF so the most popular applications are on top of Kubernetes.
Our friendly community maintains a few different ways of installing Thanos on Kubernetes. See those below:
If you want to add yourself to this list, let us know!
We don’t recommend running Thanos on a single node on production. Thanos is designed and built to run as a distributed system. Vanilla Prometheus might be totally enough for small setups.
However, in case you want to play and run Thanos components on a single node, we recommend following the port layout:
|Receive||gRPC (store API)||10907|
|Receive||HTTP (remote write API)||10908|
You can see example one-node setup here