[Bug][Grafana/Dashboards] Multi-AI Tool Comparison dashboard omits Claude Code and has incomplete panel layout
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 68/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- grafana
- Domínio
- data-visualization
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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
- Linguagem predominante
- Go
- Estrelas
- 3.1k
- Forks
- 812
- Merge médio
- 2d 8h
- PRs com merge (30d)
- 51
Preparar o ambiente
Ainda não verificamos os arquivos de configuração deste projeto. Comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de apache/devlake
-
type/bug
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 95/100
Mantenedores costumam responder em até 1 dia
-
[Bug][jenkins] Incremental collection skips the stages of builds that finish after the next syncAberta
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 1 dia
-
[Feature][Plugins] Add YouTrack pluginTalvez já em andamento @tpam28 assumiu há 2 dias. Aberta
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 32/100
apache/devlake#9168 · 1 comentário · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
[Bug][Jira/DORA] Extra JQL does not isolate projects sharing the same Jira boardTalvez já em andamento @veetmoradiya3628 assumiu há 8 dias. Aberta
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
apache/devlake#9151 · 2 comentários · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
type/bug
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 52/100
apache/devlake#9150 · 3 comentários ·
Mantenedores costumam responder em até 1 dia
Todas as issues de apache/devlake
Issues semelhantes
-
bug
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 92/100
open-telemetry/opentelemetry-go-compile-instrumentation#1417 ·
Mantenedores costumam responder em até 2 dias
-
agent-research-finding agent-research-recommend chore ready-for-agent
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
jordansmall/spindrift#4068 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Type/Task
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
OpenNSW/nsw-srilanka#537 ·
Mantenedores costumam responder em até 1 dia
-
security
Dificuldade 2/5 1-2 dias Facilidade para iniciantes 62/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 90/100
Mantenedores costumam responder em até 1 dia