grafana/docker-otel-lgtm - Open Source PR Review Scorecard

An OpenTelemetry backend in a Docker container image

C-Rank Grade: A (Welcoming) - 60/100

External PR Merge Rate: 82%

Response Time: 1d

First Timer Success: 100%

Frequently Asked Questions

Is grafana/docker-otel-lgtm welcoming to first-time open-source contributors?

grafana/docker-otel-lgtm has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in grafana/docker-otel-lgtm respond to incoming external pull requests in approximately 30.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 60.4 C-Rank™ score (A Tier) represent?

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.4 places grafana/docker-otel-lgtm in the A tier.

What is the external contributor pull request merge rate for grafana/docker-otel-lgtm?

The external contributor pull request merge rate for grafana/docker-otel-lgtm is 81.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in grafana/docker-otel-lgtm?

grafana/docker-otel-lgtm does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

grafana
grafana/docker-otel-lgtmA•Welcoming2.0k
GitHub
Back to Explorer
grafana

grafana/docker-otel-lgtm

2,047
InactiveA•Welcoming(60/100)Shell

An OpenTelemetry backend in a Docker container image

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
9.2/10
Patience Score
9.0/10
Nitpick Rate
25%

Highly welcoming maintainers in grafana/docker-otel-lgtm. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
81.8%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
7 core
Highly collaborative maintainer core
Diagnostic Health HUD
81.8%
Merge Gauge
100.0%
1st-Timer
Community Vibe70/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for grafana/docker-otel-lgtm
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/grafana/docker-otel-lgtm)](https://getmerged.abhishekco.de/grafana/docker-otel-lgtm?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

There appear to be two issues with the current healthcheck.sh implementation. 1. All services can be skipped immediately after startup Immediately after the container starts, it is possible that none of the components are listening on their respective ports yet. In this case, every curl returns exit code 7 (connection refused), and check_service() skips every service: Grafana not running (skipping) Loki not running (skipping) Tempo not running (skipping) Mimir not running (skipping) OTel Collector not running (skipping) All running services healthy Since check_service() does not fail when a service is skipped, the script eventually exits with 0. This means the Docker healthcheck can report the container as healthy even though the LGTM stack is still starting up. Since /tmp/ready is already used to indicate that the stack has completed its initialization, it seems appropriate to check this before checking the individual services: if [ ! -f /tmp/ready ]; then echo "LGTM stack is not

📅 Opened Sep 3, 2026💬 1 comment
Quality: 50/100Contribute
Looking for more Shell beginner tasks?Explore Shell GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for grafana/docker-otel-lgtm

When evaluating whether to contribute to grafana/docker-otel-lgtm, 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 grafana/docker-otel-lgtm acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.8% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to grafana/docker-otel-lgtm

01

Is grafana/docker-otel-lgtm welcoming to first-time open-source contributors?

grafana/docker-otel-lgtm has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 60.4 C-Rank™ score represent?

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.4 places grafana/docker-otel-lgtm in the Welcoming tier.

04

What is the external contributor pull request merge rate for grafana/docker-otel-lgtm?

The external pull request merge rate is 81.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in grafana/docker-otel-lgtm?

grafana/docker-otel-lgtm does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for grafana/docker-otel-lgtm 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.