feat(dashboard): set Stop Matching visualization to Bar Gauge

[anant-shipit]

Fixes #105

Design Decisions Summary

Grouping & Panel Choice:
Grouped under "Matching Quality", the default timeseries made it difficult to quickly rank or triage which agencies were experiencing the worst stop mismatch degradation.

Visualization Rationale:
I chose a horizontal Bar Gauge. A ranking bar gauge sorted by worst agencies first allows operators to immediately triage the most problematic feeds. The gradient color (green to red thresholds) makes it visually obvious which stops need immediate attention.

Go Metric Modifications:
No Go metric types were modified.

[coderabbitai]

Warning

Review limit reached

@anant-shipit, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5bcf139d-2dc9-498a-91c1-6c66fe8a8649

📥 Commits

Reviewing files that changed from the base of the PR and between af77c99 and 1bf0b9d.

📒 Files selected for processing (1)

• grafana/dashboards/watchdog_metrics_dashboard.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coveralls]

coverage: 51.344%. remained the same — anant-shipit:feat/issue-105-stop-matching into OneBusAway:main

[0xaboomar]

Thanks for simplifying the panel by focusing on the stop match ratio it definitely makes the visualization cleaner.

I noticed that the panel description still says it shows all three metrics, while the query now only returns the ratio. The description should be updated to reflect the current behavior.