Official Elastic connectors for third-party data sources
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 82%
Response Time: 7h
First Timer Success: 78%
elastic/connectors has a recorded first-timer success rate of 77.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in elastic/connectors respond to incoming external pull requests in approximately 7.3 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 69.9 places elastic/connectors in the A tier.
The external contributor pull request merge rate for elastic/connectors is 82.0%, based on public PR activity from non-core contributors.
elastic/connectors currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in elastic/connectors. Prompt code reviews with positive guidance for new contributors.
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/elastic/connectors?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 Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Problem Description Connectors contain logic here that collects documents to bulk operations and then sends batches into Elasticsearch. There is a todo in the code: # TODO: retry 429s for individual items here It is possible that the whole request will return 200, but individual items within this request will be marked as failed - e.g. you've sent 500 items and 3 of them returned 429 because EIS or ML node was unable to process them. So we need to add logic that collects all items that failed ingestion in the batch and retry them a couple times. Actual implementation of this needs to be discusssed. Proposed Solution When bulk request returns successful status but individual items are not successful these items need to be retried - either combined with more items from the queue or just these items alone. If after a couple attempts ingestion fails these items should be dropped with a log line. Additional Context Be mindful of Error Monitor in _process_bulk_response - it counts failed it
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 elastic/connectors, 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 elastic/connectors acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.0% were successfully merged into the primary branch.
elastic/connectors has a recorded first-timer success rate of 77.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 69.9 places elastic/connectors in the Welcoming tier.
The external pull request merge rate is 82.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, elastic/connectors currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for elastic/connectors 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.