There are four types of time zones that can be selected within OpsGenie:
Account Time Zone: The account-wide time zone setting of your OpsGenie domain. This time zone is mandatory to be selected. While the account for your domain is being created, the owner is asked to specify the account time zone. The account time zone for your OpsGenie account can be seen on Settings page. The owner and admin users can update this setting any time.
User Time Zone: The time zone setting of each OpsGenie user. Each user can update their user time zones via Profile page any time. Please note that the account time zone is being used as default for user time zone when this time zone is needed but none is specified.
Schedule Time Zone: The time zone setting of each schedule configuration. This time zone is mandatory to be selected while creating an on-call schedule. This setting can be updated within the details page of each schedule any time by owners and admin users.
Scheduled Maintenance Time Zone: The time zone setting of a maintenance configuration whose time is restricted according to a schedule.
- Alert Policies: Account Time Zone
- Team Routing Rules: Account Time Zone
- Notification Rules: User Time Zone
- Quiet Hours: User Time Zone
- Forwarding Rules: User Time Zone
- On-Call Schedules, Rotations & Overrides: Schedule Time Zone
- Scheduled Maintenance: Scheduled Maintenance Time Zone
The flow of alerts and notifications are being shaped by setting up different configurations. Alert policies, notification rules and quiet hours are some of those configurations that can be restricted to specific times with different time constraints. This ability provides an easiness to configure and a great flexibility while you are defining the flows and processes of the alerts and notifications for your OpsGenie team.
There are two types of time constraints that can be used while restricting these configurations to specific times and one of those should be selected while defining a time restriction:
Time of Day: Start and end times are specified using hours/minutes. Only one constraint of this type can be defined for a single configuration entity. The following examples explain further about the behavior of Time of Day based time constraints.
- Start Time: 11.00 End Time: 19.00 -> The constraint is being satisfied for 8 hours each day. For example, if this is an alert policy configuration, the policy can be executed only between 11 A.M. and 7 P.M. each day.
- Start Time: 19.00 End Time: 11.00 -> The constraint is being satisfied for 16 hours each day. For example, if this is a quiet hours configurations, user can receive notifications only between 11 A.M. and 7 P.M. each day.
- Start Time: 11.00 End Time: 11.00 -> The constraint is being satisfied for all the time.
Weekday & Time of Day: Start and end times are specified using day of weeks along with hours/minutes. You can define up to 15 constraints of this type for a single configuration entity. If the time restriction is selected with this type, at least one the time constraints that were defined should be matched to be able to use this configuration.
- Start Time: Friday 18.00 End Time: Monday 9.00 -> The constraint is being satisfied from each Friday 6 P.M. to each Monday 9 A.M.
- Start Time: Friday 11.30 End Time: Friday 13.30 -> The constraint is being satisfied for the period of two hours on Fridays from 11.30 AM to 1.30 PM.
- Start Time: Friday 13.30 End Time: Friday 11.30 -> The constraint is being satisfied through all the week excepting the period of two hours from 11.30 AM to 1.30 PM on Fridays.