Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Notify Feature for Escalation chain: Notify if Workday is #4752

Open
Hackmeat opened this issue Jul 29, 2024 · 3 comments
Open

New Notify Feature for Escalation chain: Notify if Workday is #4752

Hackmeat opened this issue Jul 29, 2024 · 3 comments

Comments

@Hackmeat
Copy link

Hackmeat commented Jul 29, 2024

What would you like to see!

Hi All,

we just stumbled across the limitation that we can only set time windows for notifications, but no workday windows. We would love to see some kind of resource addition to the escalation chain which might add a structure like this

resource "grafana_oncall_escalation" "example_notify_step" {
  escalation_chain_id     = grafana_oncall_escalation_chain.default.id
  type                    = "notify_if_day_of_week"
  notify_if_day_of_week   = ["monday", "tuesday", "wednesday", "thursday", "friday"]
  position                = 0
}

Product Area

Alert Flow & Configuration

Anything else to add?

No response

Copy link
Contributor

The current version of Grafana OnCall, at the time this issue was opened, is v1.8.8. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!

@Hackmeat Hackmeat changed the title NEw Notify Feature for Escalation chain: Notify if Workday is New Notify Feature for Escalation chain: Notify if Workday is Jul 29, 2024
@Axel-sys-777
Copy link

I support this request.

@ondrejlevy
Copy link

I support this request too. We are currently facing the same issue where we want to limit notification only for workdays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants