Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.
C-Rank Grade: A (Welcoming) - 55/100
External PR Merge Rate: 82%
Response Time: 3d
First Timer Success: 56%
influxdata/telegraf has a recorded first-timer success rate of 55.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in influxdata/telegraf respond to incoming external pull requests in approximately 83.9 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 55.4 places influxdata/telegraf in the A tier.
The external contributor pull request merge rate for influxdata/telegraf is 82.2%, based on public PR activity from non-core contributors.
influxdata/telegraf currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in influxdata/telegraf. Maintains strict focus on technical quality and test standards.
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/influxdata/telegraf?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 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~55 hours (96% approval). Large PRs (>500 lines) take ~403 hours (37% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
The official Go client for Elasticsearch
Idempotent schema management for MySQL, PostgreSQL, SQLite, and SQL Server
High-performance lightweight proxy and load balancer for LLM infrastructure. Intelligent routing, automatic failover and unified model discovery across local and remote inference backends.
Use Case Our current telemetry pipeline is: Telegraf -> Apache NiFi -> Kafka Telegraf collects and enriches the metrics. Apache NiFi then serializes the Kafka message key and value using Avro and publishes the messages to Kafka. The source systems and Kafka are located in different network zones. Using Avro is important because it reduces the amount of data transferred between these zones. We want to remove Apache NiFi and use Telegraf as the only component in the pipeline: Telegraf -> Kafka This would allow Telegraf to collect, enrich, serialize, and publish the metrics directly to Kafka. Expected behavior The outputs.kafka plugin should support Avro serialization for both: the Kafka message key; the Kafka message value. The serialized key and value should use binary Avro encoding and the Confluent wire format. The key and value should preferably support separate Avro schemas and schema IDs, since they may use different schemas. The Avro schema is defined once and reused for seria
Use Case Monitoring laptop batteries and batteries of connected peripherals. Upower is the standard way of reporting battery information in Linux. UPS devices might also report their level using upower but I'm not sure if it's common, I don't have any UPSs to test with. Expected behavior Batteries can be monitored using a upower input plugin. Actual behavior None, batteries need to be monitored using manual workarounds like the exec input plugin. Additional info No response
Use Case Hello and thank you for an excellent product! I would like to have an output plugin for sending data to ClickHouse. With support for sending different metrics to different tables. PS. I know about the existence of the SQL plugin and HTTP plugin. Using these plugins and some “crutches” you can send data to ClickHouse. But this is extremely inconvenient and has very limited settings. Expected behavior easy use native plugin Actual behavior “crutches” Additional info No response
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 influxdata/telegraf, 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 influxdata/telegraf acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.2% were successfully merged into the primary branch.
influxdata/telegraf has a recorded first-timer success rate of 55.9%. 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 55.4 places influxdata/telegraf in the Welcoming tier.
The external pull request merge rate is 82.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, influxdata/telegraf 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 influxdata/telegraf 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.