performance impact: leave no trace (minimize performance impact, particularly for default enabled metrics)
Extensible: it should be easy to add new metrics as needed
Only add metrics as a way to answer a specific question in mind, with an explicit documented rationale
user experience: improving user experience of reporting issues to the project
Quests (provisional)
Supporting rust feature development
Improved ICE Reporting
build tooling for automated cleanup of metrics in cargo
collate information in crater
build support for reporting specific issues back to relevant contributors
e.g. cargo plugins, vscode, or rust-analyzer could be used to locally analyze metrics for issues rust teams care about and present users with an appropriate summary to file as a ticket
Direct improvements of User Experience e.g. identifying which compiler errors to focus on improving