We measure literal end-to-end processing time on our status page here: https://status.sentry.io/ https://status.sentry.io/ It should never be slow, so it's po

We measure literal end-to-end processing time on our status page here: https://status.sentry.io/ https://status.sentry.io/ It should never be slow, so it's possible there was a misunderstanding in how something was working, a bug in an SDK, or we were simply having a really bad day. Comparatively, Rollbar publishes some similar numbers, and suggest they are slower: http://status.rollbar.com/ http://status.rollbar.com/ While being as real-time as possible is nice, we internally have an SLA of 10s for end-to-end as we feel thats appropriate enough for a success metric. I will also say we did a lot of work around this recently to improve our 99th percentile. Part of that is our recent improvements around source map processing times: https://blog.sentry.io/2016/10/19/fixing-python-performance-with-rust.html https://blog.sentry.io/2016/10/19/fixing-python-performance-...