VictoriaMetrics: fast, cost-effective monitoring solution and time series database
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 70%
Response Time: 3d
First Timer Success: 60%
VictoriaMetrics/VictoriaMetrics has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in VictoriaMetrics/VictoriaMetrics respond to incoming external pull requests in approximately 73.6 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 59.9 places VictoriaMetrics/VictoriaMetrics in the A tier.
The external contributor pull request merge rate for VictoriaMetrics/VictoriaMetrics is 69.8%, based on public PR activity from non-core contributors.
VictoriaMetrics/VictoriaMetrics currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (75% critical review signals). Ensure PRs strictly follow guidelines before requesting review in VictoriaMetrics/VictoriaMetrics.
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/VictoriaMetrics/VictoriaMetrics?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~48 hours (87% approval). Large PRs (>500 lines) take ~353 hours (31% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe Currently, vmui relies on the /admin/tenants API to determine whether it should render the tenant selector at the top of the UI. If vmui can access this endpoint and it returns tenant data, the selector is displayed. However, in typical multitenant deployments, vmauth is placed in front of the VictoriaMetrics cluster and restricts each user to their own tenant. The /admin/* endpoints are intended for admin users with access to all tenants and are usually not exposed through vmauth. As a result, regular users may not see which tenant they are currently working with in vmui. It can create some confusion as in #11634. Describe the solution you'd like VictoriaLogs already exposes tenant information via /select/tenant_ids. It would be useful to align VictoriaMetrics with this behavior and make the tenant information available through a non-admin API. The proposed behavior: vmsingle should support /select/tenant_ids and always re
Is your feature request related to a problem? Please describe We moved a MinIO service to a new server and changed the DNS A record for its HTTPS endpoint. The old server stayed online. We use vmagent v1.138.0 with a static scrape target, a 60s scrape interval, and a 20s scrape timeout. After the DNS change: DNS queries inside the vmagent container returned the new address. A fresh HTTPS request returned metrics from the new server. vmagent continued to collect metrics from the old server. The target stayed up, with no scrape errors. We identified the old server by its capacity metrics. This continued for about six hours. Metrics switched to the new server after the vmagent pod was replaced. In this version, IdleConnTimeout is twice the scrape interval. Regular scrapes reuse the connection before that timeout expires. This matches the keep-alive behavior described in #1822 and #2868. Describe the solution you'd like Please add an optional maximum lifetime for scrape connections, conf
Is your feature request related to a problem? Please describe vmalert can read config files from AWS and Google Cloud - see https://docs.victoriametrics.com/vmalert.html#reading-rules-from-object-storage But vmbackup/vmrestore components additionally can integrate with Azure. See comparison list here https://docs.victoriametrics.com/guides/connecting-vm-components-to-cloud-storage/ Describe the solution you'd like It will be great for consistency sake add Azure support for vmalert as well. Describe alternatives you've considered No response Additional information Low priority.
Describe the bug VictoriaMetrics crashes when running in a Windows container which is using Process isolation AND when the storageDataPath is in a Docker volume. The crash occurs right after VictoriaMetrics has started up and began scraping from a Blackbox Exporter. panic: FATAL: cannot move temporary file "C:\\victoria\\victoria-metrics-data\\data\\small\\2026_03\\parts.json.tmp.7" to "C:\\victoria\\victoria-metrics-data\\data\\small\\2026_03\\parts.json": rename C:\victoria\victoria-metrics-data\data\small\2026_03\parts.json.tmp.7 C:\victoria\victoria-metrics-data\data\small\2026_03\parts.json: The system cannot find the path specified. [recovered, repanicked] It seems that the crash doesn't occur when the container is using HyperV isolation. To Reproduce The problem occurs when I'm testing VictoriaMetrics in a Windows container (Docker). The container starts a renamed victoria-metrics-windows-amd64-prod.exe executable and it's using a testing prometheus.yml config that has ICMP jobs
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 VictoriaMetrics/VictoriaMetrics, 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 VictoriaMetrics/VictoriaMetrics acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.8% were successfully merged into the primary branch.
VictoriaMetrics/VictoriaMetrics has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 59.9 places VictoriaMetrics/VictoriaMetrics in the Welcoming tier.
The external pull request merge rate is 69.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, VictoriaMetrics/VictoriaMetrics currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for VictoriaMetrics/VictoriaMetrics 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.