thanos-io/thanos

Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on March 13th, 2022
Created on November 1st, 2017
Open Issues & Pull Requests: 879 (+0)
Number of forks: 2,353
Total Stargazers: 14,183 (+0)
Total Subscribers: 231 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.9 days
Mean response time: 329.7 days
90th percentile: 1228.5 days
Tracked items: 508

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 84% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 23 hours, while "feature request/improvement" waits about 33 months. 60% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 6% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 496
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 938 days
Stale 30+ days: 483
Stale 90+ days: 460

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 5
Events in 7 days: 8

Top labels

  • stale (533)
  • feature request/improvement (404)
  • help wanted (393)
  • bug (329)
  • good first issue (178)
  • component: query (165)
  • question (146)
  • component: store (138)

Detailed Description

Thanos is a set of components that adds highly available metric storage and querying to existing Prometheus deployments.

Thanos solves the problem of scaling Prometheus beyond a single instance while retaining historical data indefinitely. It works by leveraging Prometheus's native storage format to store metric blocks in object storage, then providing a unified query interface across multiple Prometheus servers. The system deduplicates metrics from Prometheus HA pairs on the fly and supports downsampling of historical data to accelerate queries. It can be deployed as a sidecar alongside Prometheus or as a separate receive component to handle remote write traffic, making it adaptable to different infrastructure patterns.

Teams should adopt Thanos when they need to query metrics across multiple Prometheus instances, require long-term metric retention beyond what a single Prometheus server can handle, or want to eliminate single points of failure in their monitoring stack. The tool suits organizations already running Prometheus who want to extend it without replacing their existing setup. It requires only object storage as an optional dependency, supporting any S3-compatible system or Google Cloud Storage, which keeps operational overhead minimal.

The project maintains a substantial base of real-world adopters, as evidenced by the fact that nearly all open issues come from outside users rather than the core team. Responses to issues and pull requests typically arrive within one to two weeks. Development activity concentrates on bug fixes, feature requests and improvements, with particular focus on the query component.