Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Top repositories
OneUptime’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside OneUptime’s account where OneUptime opened or reviewed pull requests in the past 365 days.
Who noticed OneUptime
Everyone who starred or forked OneUptime’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories OneUptime owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
🔗 Repositorio oficial y código: OneUptime/oneuptime 📌 Guarda este post para tu próxima auditoría de costos SRE.
I built an open-source alternative to Datadog, PagerDuty, and Statuspage I’m building OneUptime (oneuptime/oneuptime) an open-source observability platform that brings monitoring, alerting, incident management, status pages, logs, metrics, and traces into one place. Self-host it on your own infrastructure or use our cloud. Free and open source under Apache 2.0. Our goal is simple: help teams build more reliable software and avoid paying the observability tax to Datadog / NewRelic / etc. Let me know what you think!