We’ve just released a new version of RepoSquirrel, focused on deeper insights into both development activity and operational incidents.
This release adds:
New visualizations showing workload distribution per subsystem over time
Faster and more accurate code analysis by replacing cloc with Tokei
A new PagerDuty integration that connects incidents directly to Git users and repositories
With the PagerDuty integration you can visualize things like:
Open incidents and open/resolve trends
Incident frequency by severity
Incidents per hour (time-of-day patterns)
Severity over time and averages
Who is resolving and assigning incidents
Per-responder views of what they’re handling and when
Arbitrary incident searches (e.g. customer-specific incidents) with visualizations
Documentation (with screenshots) for the PagerDuty integration is here: https://github.com/reposquirrel/reposquirrel/blob/main/docs/...
One thing I’d love help with: since I only have limited demo data that I can publish publicly, I’m very interested in screenshots from real-world systems (anonymized, of course). If you’re using PagerDuty and RepoSquirrel and are willing to share how it looks in practice, that would be hugely appreciated.
Happy to answer questions or dive deeper into how any of this works.