element-hq / element-hq/element-web
Ability to capture a specific period of logs when rageshaking is disabled
- Dominant language
- TypeScript
- Stars
- 13.5k
- Forks
- 2.8k
- PR merge metrics
- PR metrics pending
Description
### Your use case
#### What would you like to do?
A number of deployments turn off rageshaking as they:
1) Don't want to report to the official rageshake server.
2) 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_
Contributor guide
Assessment
This issue has not been assessed yet.