OpenSearch Data Prepper is a component of the OpenSearch project that accepts, filters, transforms, enriches, and routes data at scale.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 70%
Response Time: 3d
First Timer Success: 62%
opensearch-project/data-prepper has a recorded first-timer success rate of 62.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in opensearch-project/data-prepper respond to incoming external pull requests in approximately 66.0 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 60.9 places opensearch-project/data-prepper in the A tier.
The external contributor pull request merge rate for opensearch-project/data-prepper is 70.4%, based on public PR activity from non-core contributors.
opensearch-project/data-prepper currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in opensearch-project/data-prepper.
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/opensearch-project/data-prepper?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~43 hours (88% approval). Large PRs (>500 lines) take ~317 hours (32% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. It would be nice to be able to specify an S3-compatible storage solution as a DLQ. Currently, you can only specify Amazon S3. Describe the solution you'd like I'd like to be able to specify a custom endpoint to use an S3 storage solution that isn't on AWS (such as Minio, Ceph, Garage...).
We are encountering an issue in Data Prepper when trying to access or manipulate JSON fields whose key names contain spaces. Example Input { "Computer Name": "xyz" } Attempt 1: add_entries with value_expression - add_entries: entries: - key: cloud/provider value_expression: "/Computer Name" Observed behavior: Using add_entries with value_expression results in a runtime error: Error adding entry to record ... value_expression [/Computer Name] When using add_entries with format instead of value_expression, no error is thrown, but the resulting value is null. Attempt 2: rename_keys and copy_values Both processors fail when referencing the same key with a space. Observed errors: java.lang.IllegalArgumentException: key Computer Name must contain only alphanumeric chars with .-_@/ and must follow JsonPointer (ie. 'field/to/key') And during pipeline validation: Parameter "entries.null.from_key" for plugin "rename_keys" is invalid: key Computer Name must contain only
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 opensearch-project/data-prepper, 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 opensearch-project/data-prepper acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.4% were successfully merged into the primary branch.
opensearch-project/data-prepper has a recorded first-timer success rate of 62.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 60.9 places opensearch-project/data-prepper in the Welcoming tier.
The external pull request merge rate is 70.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, opensearch-project/data-prepper currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for opensearch-project/data-prepper 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.