Skip to content

feat(dashboard): set Unmatched Stop Clusters visualization to Geomap - #125

Open
anant-shipit wants to merge 1 commit into
OneBusAway:mainfrom
anant-shipit:feat/issue-109-unmatched-stop-clusters
Open

feat(dashboard): set Unmatched Stop Clusters visualization to Geomap#125
anant-shipit wants to merge 1 commit into
OneBusAway:mainfrom
anant-shipit:feat/issue-109-unmatched-stop-clusters

Conversation

@anant-shipit

Copy link
Copy Markdown

Fixes #109

Design Decisions Summary

Grouping & Panel Choice:
Grouped under "Deep Diagnostics", the default timeseries failed to leverage the geographic nature of the data.

Visualization Rationale:
I chose a Geomap. Stop cluster mismatches are geographical problems. Rendering them on a map instantly reveals spatial patterns (e.g., an entire transit corridor failing to match due to bad GTFS data).

Go Metric Modifications:
No Go metric types were modified, but the PromQL query was changed. I changed the dashboard query from oba_unmatched_stop_cluster_count to oba_unmatched_stop_location. This was necessary because rendering a Geomap strictly requires latitude and longitude labels, which the original counter metric did not provide, but the location metric did.

@coderabbitai

coderabbitai Bot commented Jul 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 45 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: d62f5e0f-7511-4bad-bae8-354a9c39b409

📥 Commits

Reviewing files that changed from the base of the PR and between af77c99 and 3780bff.

📒 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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unmatched Stop Clusters

1 participant