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

Tracing Notifications on the Backend #2452

Open
Tracked by #2442
gnunicorn opened this issue Dec 19, 2024 · 1 comment
Open
Tracked by #2442

Tracing Notifications on the Backend #2452

gnunicorn opened this issue Dec 19, 2024 · 1 comment
Labels
f-push-notifications Problem with the push notifications feature

Comments

@gnunicorn
Copy link
Contributor

gnunicorn commented Dec 19, 2024

and ideally all the way to the client to make sure we are not loosing them somewhere there before they even make it to the server.

Synapse and Sygnal both have support for OpenTelemetry/OpenTracing, so does the matrix-rust-sdk, and Sentry. If I am not mistaken we should technically be able to trace the notifications throughout the entire stack and thus figure out where they go lost....

@github-project-automation github-project-automation bot moved this to Backlog in Product Dec 19, 2024
@gnunicorn gnunicorn added the f-push-notifications Problem with the push notifications feature label Dec 19, 2024
@gnunicorn gnunicorn moved this from Backlog to Next in Product Dec 19, 2024
@gnunicorn
Copy link
Contributor Author

so, it appears that though we should see exceptions and warning in the logs, for some reason they do not show up. On better news, there is a promotheus metric to tell us how often submitting to the push-server failed in synapse...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
f-push-notifications Problem with the push notifications feature
Projects
Status: Next
Development

No branches or pull requests

1 participant