2023-05-25 20:26:13 +02:00
|
|
|
from enum import Enum
|
|
|
|
|
|
2023-10-05 09:46:48 +01:00
|
|
|
from django.db.models import IntegerChoices
|
2023-05-25 20:26:13 +02:00
|
|
|
|
2023-10-05 09:46:48 +01:00
|
|
|
|
|
|
|
|
class ActionSource(IntegerChoices):
|
|
|
|
|
SLACK = 0, "Slack"
|
|
|
|
|
WEB = 1, "Web"
|
|
|
|
|
PHONE = 2, "Phone"
|
|
|
|
|
TELEGRAM = 3, "Telegram"
|
|
|
|
|
API = 4, "API"
|
2024-03-27 13:37:01 +01:00
|
|
|
BACKSYNC = 5, "Backsync"
|
2025-04-21 14:23:37 -03:00
|
|
|
MATTERMOST = 6, "Mattermost"
|
2022-06-03 08:09:47 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
TASK_DELAY_SECONDS = 1
|
|
|
|
|
|
|
|
|
|
NEXT_ESCALATION_DELAY = 5
|
2023-05-25 20:26:13 +02:00
|
|
|
|
User notifications bundle (#4457)
# What this PR does
This PR adds two new models: UserNotificationBundle and
BundledNotification (proposals for naming are welcome).
`UserNotificationBundle` manages the information about last notification
time and scheduled notification task for bundled notifications. It is
unique per user + notification_channel + notification importance.
`BundledNotification` contains notification policy and alert group, that
triggered the notification. The BundledNotification instance is created
in `notify_user_task` for every notification, that should be bundled,
and is attached to UserNotificationBundle by ForeignKey connection.
How it works:
If the user was notified recently (within the last two minutes) by the
current notification channel, and this channel is bundlable,
BundledNotification instance will be created and attached to the
UserNotificationBundle instance, and `send_bundled_notification` task
will be scheduled to execute in 2 min.
In `send_bundled_notification` task we get all BundledNotification
attached to the current UserNotificationBundle instance, check if alert
groups are still active and if there is only one notification - perform
regular notification by calling `perform_notification` task, otherwise
call "notify_by_<channel>_bundle" method for the current notification
channel.
PR with method to send notification bundle by SMS -
https://github.com/grafana/oncall/pull/4624
**This feature is disabled by default by feature flag. Public docs will
be added in a separate PR with enabling this feature.**
## Which issue(s) this PR closes
related to https://github.com/grafana/oncall-private/issues/2712
## 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-07-16 13:24:08 +02:00
|
|
|
BUNDLED_NOTIFICATION_DELAY_SECONDS = 60 * 2 # 2 min
|
|
|
|
|
|
2023-05-25 20:26:13 +02:00
|
|
|
|
|
|
|
|
# AlertGroup states verbal
|
|
|
|
|
class AlertGroupState(str, Enum):
|
|
|
|
|
FIRING = "firing"
|
|
|
|
|
ACKNOWLEDGED = "acknowledged"
|
|
|
|
|
RESOLVED = "resolved"
|
|
|
|
|
SILENCED = "silenced"
|
2025-01-14 11:02:23 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SERVICE_LABEL = "service_name"
|
2025-01-14 12:21:52 +01:00
|
|
|
SERVICE_LABEL_TEMPLATE_FOR_ALERTING_INTEGRATION = "{{ payload.commonLabels.service_name }}"
|