Organizations using custom ticketing or paging systems need a way to route Sentry alerts without relying on a supported third-party integration. Slack may be available but is not always treated as a paging endpoint, while creating a dedicated Sentry user for an email alias may be incompatible with SAML-enforced provisioning.
The requested capability is a flexible email or webhook-style alert destination that can target an external operational system. Without one, organizations must build and maintain a custom Sentry integration before adopting alerts broadly.
Related requests:
via anthony.yiannakou.
--
View Junior Session [Sentry]
Organizations using custom ticketing or paging systems need a way to route Sentry alerts without relying on a supported third-party integration. Slack may be available but is not always treated as a paging endpoint, while creating a dedicated Sentry user for an email alias may be incompatible with SAML-enforced provisioning.
The requested capability is a flexible email or webhook-style alert destination that can target an external operational system. Without one, organizations must build and maintain a custom Sentry integration before adopting alerts broadly.
Related requests:
via anthony.yiannakou.
--
View Junior Session [Sentry]