-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Labels
A-Feedback-ReportingReporting process for bugs, debug logs (rageshakes), suggestionsReporting process for bugs, debug logs (rageshakes), suggestionsT-EnhancementT-FeatureRequest to add a new feature which does not exist right nowRequest to add a new feature which does not exist right now
Description
Your use case
What would you like to do?
A number of deployments turn off rageshaking as they:
- Don't want to report to the official rageshake server.
- Don't want to deploy and manage a rageshake instance
Why would you like to do it?
But they would also like to debug issues that arise, and so targeted logging is useful.
How would you like to achieve it?
Probably the most satisfactory way is an explicit on/off button for log capture (similar to the profiling tools you find in browsers) that captures enough lots to be useful, and then subsequently allows you to export them to a file.
Have you considered any alternatives?
Asking these deployments to run their own rageshake instances could be an alternative, although it's quite an undertaking for it to be useful.
Additional context
No response
Metadata
Metadata
Assignees
Labels
A-Feedback-ReportingReporting process for bugs, debug logs (rageshakes), suggestionsReporting process for bugs, debug logs (rageshakes), suggestionsT-EnhancementT-FeatureRequest to add a new feature which does not exist right nowRequest to add a new feature which does not exist right now