Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 58%
Response Time: 6h
First Timer Success: 56%
thanos-io/thanos has a recorded first-timer success rate of 55.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in thanos-io/thanos respond to incoming external pull requests in approximately 5.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.4 places thanos-io/thanos in the A tier.
The external contributor pull request merge rate for thanos-io/thanos is 57.8%, based on public PR activity from non-core contributors.
thanos-io/thanos currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/thanos-io/thanos?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Is your proposal related to a problem? (Write your answer here.) Describe the solution you'd like The Prometheus project recently offers distroless images to reduce the surface for CVEs. It would be great, if Thanos could offer distroless images as well. Describe alternatives you've considered Images with FROM scratch should works as well - Thanos binary are static go binaries. Additional context See prometheus/prometheus#8657
Is your proposal related to a problem? thanos rule supports reloading rule files via SIGHUP or POST /-/reload, but it does not automatically detect updates to files specified by --rule-file. This is particularly inconvenient in Kubernetes environments where rule files are managed via ConfigMap or Secret. Even when a mounted file is updated automatically, thanos rule does not pick up the change on its own, so users still need an external reloader sidecar just to detect the file change and call /-/reload. The --rule-file flag description itself also notes this current limitation: Note that rules are not automatically detected, use SIGHUP or do HTTP POST /-/reload to re-read them. Describe the solution you'd like It would be very helpful if thanos rule had a native auto-reload mechanism for files specified by --rule-file. For example, an optional mechanism that: watches rule files on disk detects updates automatically reloads rules without requiring an external sidecar keeps the curr
Is your proposal related to a problem? Compactor crashes with the following error: panic: cannot reduce resolution to custom buckets schema Describe the solution you'd like Compactor support downsampling of native histograms custom buckets. Describe alternatives you've considered Disabling native histograms in prometheus. Additional context Prometheus: 3.9.1 Thanos : v0.41.0 Debug log: ts=2026-02-26T18:13:18.445641724Z caller=streamed_block_writer.go:178 level=info msg="finalized downsampled block" mint=1770854400000 maxt=1772064000000 ulid=01KJDJBP3BKRF9RXC2Y7GAEQV1 resolution=300000 panic: cannot reduce resolution to custom buckets schema goroutine 3325 [running]: github.com/prometheus/prometheus/model/histogram.(*FloatHistogram).CopyToSchema(0x19c96d0eaff?, 0x0?) /go/pkg/mod/github.com/prometheus/[email protected]/model/histogram/float_histogram.go:154 +0x2e6 github.com/thanos-io/thanos/pkg/compact/downsample.(*histogramAggregator).add(0xc00146c390, {0x42d34f0?, 0xc00146c390?, 0
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to thanos-io/thanos, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of thanos-io/thanos acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.8% were successfully merged into the primary branch.
thanos-io/thanos has a recorded first-timer success rate of 55.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.4 places thanos-io/thanos in the Welcoming tier.
The external pull request merge rate is 57.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, thanos-io/thanos currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for thanos-io/thanos are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.