Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web error telemetry (passive Sentry) #6660

Open
lampholder opened this issue May 3, 2018 · 1 comment
Open

Web error telemetry (passive Sentry) #6660

lampholder opened this issue May 3, 2018 · 1 comment
Assignees
Labels
A-Telemetry Telemetry / analytics to understand usage T-Enhancement

Comments

@lampholder
Copy link
Member

We don't currently have visibility on errors occurring in riot web 'in the wild' - information that could be used both to capture, diagnose and fix problems that users experience (but might not report), and to track our progress against reducing the incidence of known problems such as Unable To Decrypt failures.

I'd like for such errors to be reported to a sentry instance (or similar) - obvs this could be configurable per riot deploy, and data should be anonymised (and probably opt-in, too).

@aaronraimist aaronraimist mentioned this issue Oct 22, 2018
3 tasks
@aaronraimist aaronraimist added the A-Telemetry Telemetry / analytics to understand usage label Feb 21, 2020
@novocaine
Copy link
Contributor

We have Sentry configured to receive Rageshake data, see matrix-org/matrix-react-sdk#6597

In order to fulfil this ticket and make that reporting happen as part of passive telemetry, we need to strip more data out of the Sentry reporting to ensure it complies to our description of what we track, then have Sentry capture all errors if tracking/telemetry consent has been given by the user

@novocaine novocaine self-assigned this Sep 9, 2021
@novocaine novocaine changed the title Riot.im web error telemetry Web error telemetry (passive Sentry) Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Telemetry Telemetry / analytics to understand usage T-Enhancement
Projects
None yet
Development

No branches or pull requests

4 participants