warren830 opened a new pull request, #8786: URL: https://github.com/apache/incubator-devlake/pull/8786
## Summary - **New logging fields**: Add `CodeReferenceCount`, `WebLinkCount`, `HasFollowupPrompts` to chat_log and `LeftContextLength`, `RightContextLength` to completion_log, aligned with [Kiro prompt logging docs](https://kiro.dev/docs/enterprise/monitor-and-track/prompt-logging/) - **Dashboard separation**: Create dedicated `qdev_feature_metrics` dashboard for legacy `by_user_analytic` data; reorganize `qdev_executive` with Row dividers clearly labeling each data source (`_tool_q_dev_chat_log`, `_tool_q_dev_user_report`, cross-source) - **Dashboard enrichment**: Add Chat Trigger Type Distribution, Response Enrichment Breakdown, Completion Context Size Trends, and Response Enrichment Trends panels to logging dashboard - **SQL fixes**: Fix `only_full_group_by` incompatibility in Weekly Active Users and New vs Returning Users queries; fix Steering Adoption stat returning string instead of numeric - **E2E tests**: Add Playwright test suite covering full pipeline flow (connection → scope → blueprint → pipeline → Grafana dashboard verification) ## Dashboard Overview | Dashboard | Data Source | Purpose | |---|---|---| | Kiro Usage Dashboard | `_tool_q_dev_user_report` | New format: credits, messages, subscriptions | | Kiro Legacy Feature Metrics (NEW) | `_tool_q_dev_user_data` | Legacy: feature-level metrics | | Kiro AI Activity Insights | `chat_log` + `completion_log` | Prompt logging | | Kiro Executive Dashboard | Cross-source | KPIs with clear data source labels | ## Test plan - [x] `go build ./plugins/q_dev/...` passes - [x] `go test ./plugins/q_dev/...` passes - [x] Playwright E2E: 13/13 tests pass (connection, scope, blueprint, pipeline, 4 dashboards) - [x] All dashboard panels render with data (verified via screenshots) - [ ] Review migration script for production safety 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
