feat: implement telemetry and crash reporting system #14
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Discussion
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Platform
All
Platform
Android
Platform
IOS
Platform
Linux
Platform
MacOS
Platform
Mobile
Platform
UNIX
Platform
Web
Platform
Windows
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Testing
Not needed
Testing
Required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: nonsensical-dev/zenyx-engine#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Zenyx Bug Report & System Information Collection
This should be implemented in a new subcrate named "telemetry".
CPU Information:
Memory Information:
Operating System information:
Graphics Information:
Storage Information:
Network Information:
Zenyx Version:
External Software Information:
NOTE:
Information about applications that are injected into our application is potentially sensitive. Even if sending crash-reports and telemetry is entirely opt-in the user should be REQUIRED to be notified if that information has been collected and given the option to omit the information, simply replacing the information with the amount of injected applications.
Input Device Information:
System Locale and Language Settings:
System Uptime:
Collecting this information systematically will greatly enhance the effectiveness of bug reports and the development team's ability to address issues.
Example JSON for telemetry: