[Bug][Grafana/Dashboards] Multi-AI Tool Comparison dashboard omits Claude Code and has incomplete panel layout
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 68/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- grafana
- Bereich
- data-visualization
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
- Vorherrschende Sprache
- Go
- Sterne
- 3.1k
- Forks
- 812
- Ø Merge
- 2 T. 8 Std.
- Gemergte PRs (30 T.)
- 50
Entwicklungsumgebung
Die Einrichtungsdateien dieses Projekts haben wir noch nicht geprüft. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus apache/devlake
-
type/bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 95/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug][jenkins] Incremental collection skips the stages of builds that finish after the next syncOffen
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 76/100
apache/devlake#9177 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Feature][Plugins] Add YouTrack pluginEvtl. vergeben @tpam28 hat das vor 2 Tagen übernommen. Offen
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 32/100
apache/devlake#9168 · 1 Kommentar · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug][Jira/DORA] Extra JQL does not isolate projects sharing the same Jira boardEvtl. vergeben @veetmoradiya3628 hat das vor 8 Tagen übernommen. Offen
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 35/100
apache/devlake#9151 · 2 Kommentare · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 1 Tag
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
gruntwork-io/boilerplate#329 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
prime-radiant-inc/evener#3291 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Netcracker/qubership-apihub-backend#582 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
Maintainer antworten meist innerhalb von 1 Tag