You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempt to create new alert that will post to slack channel
Get an error saying The slack resource "my-public-or-private-channel" does not exist or has not been granted access in the MyCompany Slack workspace.
Also in logs for sentry-web I can see the following record: 10:43:30 [INFO] sentry.rules: rule.slack.channel_list_failed (error=u'method_deprecated')
What you expected to happen
I should be able to create alerts that will post to slack using new global slack integration
What to do
I saw a bunch of different issues related to this problem, and as I saw here #19446 it was fixed for v10, but as far as I can see the fix was never backported for 9.1.x branch. Is it possible to backport it somehow, or is there any protocols to help me to contribute on that matter.
The text was updated successfully, but these errors were encountered:
Important Details
How are you running Sentry?
On-Premise w/ Docker, version x9.1.2
Description
[What happened]
Can't send alerts that'll post messages to slack. Link substitution isn't working. Tested this with both public and private channels.
Steps to Reproduce
The slack resource "my-public-or-private-channel" does not exist or has not been granted access in the MyCompany Slack workspace.
Also in logs for sentry-web I can see the following record:
10:43:30 [INFO] sentry.rules: rule.slack.channel_list_failed (error=u'method_deprecated')
What you expected to happen
I should be able to create alerts that will post to slack using new global slack integration
What to do
I saw a bunch of different issues related to this problem, and as I saw here #19446 it was fixed for v10, but as far as I can see the fix was never backported for 9.1.x branch. Is it possible to backport it somehow, or is there any protocols to help me to contribute on that matter.
The text was updated successfully, but these errors were encountered: