Thanos vs Kiali: What are the differences?
Developers describe Thanos as "Highly available Prometheus setup with long term storage capabilities". Thanos is a set of components that can be composed into a highly available metric system with unlimited storage capacity. It can be added seamlessly on top of existing Prometheus deployments and leverages the Prometheus 2.0 storage format to cost-efficiently store historical metric data in any object storage while retaining fast query latencies. Additionally, it provides a global query view across all Prometheus installations and can merge data from Prometheus HA pairs on the fly. On the other hand, Kiali is detailed as "Service mesh observability and configuration". It is an observability console for Istio with service mesh configuration capabilities. It helps you to understand the structure of your service mesh by inferring the topology, and also provides the health of your mesh.
Thanos and Kiali can be primarily classified as "Monitoring" tools.
Some of the features offered by Thanos are:
- Global querying view across all connected Prometheus servers
- Deduplication and merging of metrics collected from Prometheus HA pairs
- Seamless integration with existing Prometheus setups
On the other hand, Kiali provides the following key features:
- Weighted Routing Wizard
- Matching Routing Wizard
- Suspend Traffic Wizard
Thanos is an open source tool with 4.1K GitHub stars and 479 GitHub forks. Here's a link to Thanos's open source repository on GitHub.
What is Kiali?
What is Thanos?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Kiali?
Why do developers choose Thanos?
What are the cons of using Kiali?
What are the cons of using Thanos?
Sign up to get full access to all the companiesMake informed product decisions
We recently implemented Thanos alongside Prometheus into our Kubernetes clusters, we had previously used a variety of different metrics systems and we wanted to make life simpler for everyone by just picking one.
Prometheus seemed like an obvious choice due to its powerful querying language, native Kubernetes support and great community. However we found it somewhat lacking when it came to being highly available, something that would be very important if we wanted this to be the single source of all our metrics.
Thanos came along and solved a lot of these problems. It allowed us to run multiple Prometheis without duplicating metrics, query multiple Prometheus clusters at once, and easily back up data and then query it. Now we have a single place to go if you want to view metrics across all our clusters, with many layers of redundancy to make sure this monitoring solution is as reliable and resilient as we could reasonably make it.
If you're interested in a bit more detail feel free to check out the blog I wrote on the subject that's linked.