oncall-engine/engine/apps/slack/tests/tasks
Joey Orlando 26946f0d43
fix: improve Slack rate limiting logic when updating alert groups (#5287)
# What this PR does

https://www.loom.com/share/1ac33822301444748133ffe72638ddc4

The two asks in the [original GH
issue](https://github.com/grafana/oncall-private/issues/2947) were:

> 1. Make the error message clearer. We can identify if it's delivering
or updating and being rate-limited. This is possible because Slack sets
limits per API method. Also, this limit is a per-slack channel while we
are posting messages & applying ratelimit per on-call integration, which
confuses customers.
> 2. Debounce update alert group message in Slack

Both of these have been addressed in this PR

## Which issue(s) this PR closes

Closes https://github.com/grafana/oncall-private/issues/2947

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] Added the relevant release notes label (see labels prefixed w/
`release:`). These labels dictate how your PR will
    show up in the autogenerated release notes.
2024-12-02 14:40:30 -05:00
..
__init__.py fix slack API rate limit errors in send_message_to_thread_if_bot_not_in_channel task (#3803) 2024-01-31 13:42:52 -05:00
test_send_message_to_thread_if_bot_not_in_channel.py fix slack API rate limit errors in send_message_to_thread_if_bot_not_in_channel task (#3803) 2024-01-31 13:42:52 -05:00
test_update_alert_group_slack_message.py fix: improve Slack rate limiting logic when updating alert groups (#5287) 2024-12-02 14:40:30 -05:00