Add internal and external analytics for dwds
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Description
**We are collecting following analytics internally**
- usage of dwds
- performance of some VM calls:
- getVM
- getIsolate
- getSourceReport
- evaluate
- evaluateInFrame
- updateCompilerDependencies
- step
- user-perceived DevTools startup time (time elapsed from clicking on the debug extension icon in the browser till the debugger page is rendered in DevTools)
- DDR crashes
**Additional analytics to collect**
- dwds
- http request handling exceptions per http server
- hot restart performance
- devtools load time
- Flutter tools
- `flutter run -d chrome --debug` usage and crashes - check if they already exist somewhere
- performance of various debugging operations
- DDR
- total usage, with or without dwds
Contributor guide
Research direction
Start by locating the existing analytics paths for dwds, Flutter tools, and DDR, then compare them with the listed VM calls, HTTP exceptions, performance timings, usage, and crash signals. Done means the requested analytics scope is implemented for the listed components and operations, including any existing Flutter metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- observability-sre, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100