[Bug][Grafana/Dashboards] Multi-AI Tool Comparison dashboard omits Claude Code and has incomplete panel layout
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- grafana
- Área
- data-visualization
Línea de trabajo
Start with the MySQL and PostgreSQL multi-ai-comparison.json dashboards and compare the existing Copilot, Kiro, and Cursor panels, variables, queries, and grid coordinates. Review the Claude Code tables named in the issue and verify their available fields, then test both dashboards in Grafana with cursor and claude_code data. Done means both variants include Claude Code metrics, filters, documentation, and a filled Assistant Activity slot without layout gaps.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Search before asking
- I had searched in the issues and found no similar issues.
What happened
The Multi-AI Tool Comparison dashboard (multi-ai-comparison.json)
benchmarks AI tool adoption and activity across organizations. In
PR #9017, the dashboard was expanded from Copilot and Kiro to
also include Cursor (Multi-AI Tool Comparison: Copilot vs Kiro vs
Cursor).
However, Claude Code (introduced in PR #8808 via
backend/plugins/claude_code) is completely missing from this
multi-tool comparison dashboard:
- Missing Metrics & Tool Incomplete Comparison:
• Weekly Active Users: Compares Kiro, Copilot, and Cursor,
but omits Claude Code active users (which are collected in
_tool_claude_code_activity_summary and
_tool_claude_code_user_activity).
• Lines of Code (LOC) Added: Aggregates Kiro returned lines,
Copilot LOC added, and Cursor LOC added, but omits Claude
Code cc_lines_added.
• Acceptance Rate Comparison: Compares Copilot and Cursor
acceptance rates, but does not include Claude Code tool
action acceptance rate ((edit + write + multiedit accepted) /
total).
• Connection & Scope Variables: Templating list lacks
variables for Claude Code connections and scopes. - Unbalanced Grid Layout:
• In the Assistant Activity row, panel 13 (Cursor: Tab
Completions) is assigned grid position {h: 8, w: 12, x: 0, y:
21}.
• The adjacent right grid position {h: 8, w: 12, x: 12, y:
21} is left completely empty, resulting in a blank gap in the
dashboard before the next row begins at y: 29. - Dashboard Parity:
• In addition, the PostgreSQL version
(multi-ai-comparison.json) was never updated when Cursor was
added, so it remains out of sync and lacks both Cursor and
Claude Code.
What do you expect to happen
- multi-ai-comparison.json (both MySQL and PostgreSQL variants)
should include Claude Code metrics alongside Copilot, Kiro, and
Cursor:
• WAU: Include Claude Code active users from
_tool_claude_code_user_activity or
_tool_claude_code_activity_summary.
• Assistant Activity: Fill the empty slot at {x: 12, y: 21,
w: 12, h: 8} with a panel for Claude Code tool activity (e.g.
Claude Code: Tool Actions (Accepted vs Rejected) or Sessions
& Tool Modifications).
• Lines of Code Added: Include SUM(cc_lines_added) from
_tool_claude_code_user_activity.
• Acceptance Rate: Include Claude Code tool acceptance rate
(edit_tool_accepted, write_tool_accepted, etc. vs rejected).
• Templating Variables: Add claude_code_connection_id and
claude_code_scope_id template dropdowns. - The "Semantic boundary" documentation at the top of the
dashboard should be updated to clarify the boundary for Claude
Code (i.e. agentic tool actions and CLI sessions vs. inline IDE
autocompletions).
How to reproduce
- Deploy DevLake with both cursor and claude_code plugins
enabled and collect data for both. - Open Grafana and navigate to the Multi-AI Tool Comparison
dashboard (/d/multi_ai_comparison). - Notice that:
• There are no connection/scope filters or panels for Claude
Code.
• There is a 12-column empty gap to the right of the Cursor
Tab Completions panel in the Assistant Activity row.
Anything else
No response
Version
main (commit a18194b96b5b332a60a74b23d51bacbb4262234d)
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
- Lenguaje dominante
- Go
- Estrellas
- 3.1k
- Forks
- 812
- Merge medio
- 2 d 8 h
- PR fusionados (30 d)
- 51
Preparar el entorno
Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/devlake
-
type/bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
Los mantenedores suelen responder en 1 día
-
[Bug][jenkins] Incremental collection skips the stages of builds that finish after the next syncAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
[Feature][Plugins] Add YouTrack pluginPosiblemente ocupada @tpam28 la tomó hace 2 días. Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 32/100
apache/devlake#9168 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
[Bug][Jira/DORA] Extra JQL does not isolate projects sharing the same Jira boardPosiblemente ocupada @veetmoradiya3628 la tomó hace 7 días. Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
apache/devlake#9151 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
type/bug
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
apache/devlake#9150 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de apache/devlake
Issues similares
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
DataDog/dd-trace-go#5469 ·
Los mantenedores suelen responder en 1 día
-
bug tests
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
l3montree-dev/devguard#3101 ·
Los mantenedores suelen responder en 1 día
-
area:*of bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
oapi-codegen/oapi-codegen#2593 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
DaoCloud/DaoCloud-docs#7432 ·
Los mantenedores suelen responder en 1 día