Sentry has client SDKs for many programming languages and frameworks.
Sentry has deprecated their old "Raven" series of client SDKs in favor
of a new series of client SDKs following their unified API format.
As it stood, our Sentry integration was already outdated being written
for the version 5 payloads (the Raven SDKs stopped at version 6 which
is already vastly different from version 5) when the current and
prominently used version is version 7.
This commit completely rewrites the existing Sentry integration.
Tested and supported events:
- Issue created, resolved, assigned, and ignored events.
- "Sentry events" for "capture exception" and "capture message" with
the Golang, Node.js, and Python SDKs (other SDKs should also work but
only these were used for testing).
For reference:
- Old (Raven) SDK for python:
https://github.com/getsentry/raven-python
- New (Unified API format) SDK for python:
https://github.com/getsentry/sentry-python
Signed-off-by: Hemanth V. Alluri <hdrive1999@gmail.com>
1.3 KiB
Get Zulip notifications for the issues in your Sentry projects!
-
{!create-stream.md!}
-
{!create-bot-construct-url-indented.md!}
-
Go to your organization's settings in Sentry. Then go to Developer Settings and click on the button to create a New Internal Integration. There, set the Webhook URL to the URL you constructed in the above step then enable Alert Rule Action. You can fill out the remaining details as you like. If you want notifications for issues and not just events, you can scroll down to Webhooks on the same page and check the box that says issues. Make sure that you set up the permissions so that the integration will visible to the right people.
-
Once you've saved the internal integration, go to you're project's settings (settings > Projects > Select the project). Once there go to Alerts and click on the New Alert Rule button to create a new alert rule. Set the conditions to be whatever you want (the events you want to be notified for) and under PERFORM THESE ACTIONS select Add an action... > Send notification to one legacy integration and set it to the internal integration you created in the previous step.
{!congrats.md!}

