Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
GreptimeTeam’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside GreptimeTeam’s account where GreptimeTeam opened or reviewed pull requests in the past 365 days.
Who noticed GreptimeTeam
Everyone who starred or forked GreptimeTeam’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 GreptimeTeam 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
We did it. Detail blog will be followed, stay tune: Thanks to the team and all the contributors!❤️ github.com/GreptimeTeam/greptimedb/releases/tag/v…
Full six-model report: rca-bench.greptime.com Code, protocols, and artifacts: GreptimeTeam/agent-rca-bench
🔗 Repositorio oficial y benchmarks: GreptimeTeam/greptimedb 📌 Guarda este post para optimizar el coste de tu almacenamiento de telemetría.
How the query interface affects LLM root cause analysis: 504 runs across six models Disclosure: I work on GreptimeDB, which sponsors this benchmark. Model, prompt and telemetry were held fixed; only the query interface changed. Correct diagnoses went from 105 (Prometheus/Loki/Tempo APIs) to 130 (SQL over one store) out of 168, with ~48% less input. 14 incidents, and the comparison changes storage, query language and tool design together. Code and artifacts: GreptimeTeam/agent-rca-bench