Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Configure Flashduty
  • Getting Started
    • Introduction
    • Quick start
    • FAQ
    • Product Comparison
  • Incidents
    • What is an Incident
    • View Incidents
    • Handle Incidents
    • Escalations and Assignments
    • Custom Fields
    • Custom Actions
    • Alert Noise Reduction
    • Past Incidents
    • Outlier Incidents
  • Configure Flashduty
    • Channels
    • Integrate Alerts
    • Alert Noise Reduction
    • Escalation Rules
    • Label Enrichment
    • Schedules
    • Templates
    • Service Calendars
    • Preferences
    • Alert Routing
    • Silence and Inhibition
    • Filters
    • Notification Bots
    • Alert Pipeline
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
    • Insights
  • Advanced Features
    • Referencing Variables
    • Dynamic Assignment
  • Integrations
    • Alerts integration
      • Standard Alert Integration
      • Email Integration
      • Nightingale/FlashCat Integration
      • Prometheus Integration
      • Grafana Integration
      • Zabbix Integration
      • Uptime Kuma Integration
      • Alibaba Cloud ARMS Integration
      • Alibaba Cloud Monitor CM Event Integration
      • Alibaba Cloud Monitor CM Metrics Integration
      • Alibaba Cloud SLS Integration
      • AWS CloudWatch Integration
      • Azure Monitor Integration
      • Baidu Cloud BCM Integration
      • Huawei Cloud CES Integration
      • Influxdata Integration
      • Open Falcon Integration
      • PagerDuty Integration
      • Tencent BlueKing Integration
      • Tencent Cloud CLS Integration
      • Tencent Cloud Monitor CM Integration
      • Tencent Cloud EventBridge
      • OceanBase Integration
      • Graylog Integration
      • Skywalking Integration
      • Sentry Integration
      • Jiankongbao Integration
      • AWS EventBridge Integration
      • Dynatrace Integration
      • Huawei Cloud LTS Integration
      • GCP Integration
      • Splunk Alert Events Integration
      • AppDynamics Alert Integration
      • SolarWinds Alert Events Integration
      • Volcengine CM Alert Events Integration
      • Volcengine CM Event Center Integration
      • Volcengine TLS Integration
      • OpManager Integration
      • Meraki Integration
      • Keep Integration
      • ElastAlert2 Alert Integration
      • StateCloud Alert Events
      • Guance Alert Events
      • Zilliz Alert Events
      • Huawei Cloud APM Alerts
      • zstack integration
    • Change integration
      • Standard Change Event
      • Jira Issue Events
    • IM integration
      • Feishu (Lark) Integration Guide
      • Dingtalk Integration
      • WeCom Integration
      • Slack Integration
      • Microsoft Teams Integration
    • Single Sign-On
      • Authing Integration
      • Keycloak Guide
      • OpenLDAP Guide
    • Webhooks
      • Alert webhook
      • Incident webhook
      • Costom action
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Configure Flashduty

Schedules

Schedule rules are one of the core management practices in enterprises, helping organizations effectively arrange employee work hours and ensure business continuity and efficiency. FlashDuty's schedule provides comprehensive on-call rules that enterprises can adjust and customize according to their specific business needs.

Schedule#


1.
You can view a summary of all your schedules on the schedule management page.
2.
Core members can view all schedules or only the schedules they manage.
3.
Before setting up schedule rules, you need to create a schedule, which can be assigned to a team for maintenance and planning by team members.
4.
When creating a schedule, you can flexibly configure notification methods for shift rotations:
Advance notification:Notify the next on-call person N minutes before shift handover.
Scheduled notification:Notify the next on-call person at a fixed time every day.
Notification channels: Direct message (one-on-one notifications via SMS, voice call, email, etc.), Group chat (push to IM group chat with @ mentions for responders).

Schedule Rule Components#

The final schedule rules are formed by combining regular schedule rules and temporary schedule changes.
Schedule rules can be viewed from both timeline and calendar perspectives to see the final on-call arrangement.
description

Edit Rules#

1. Creation#

A single schedule can have multiple schedule rules to meet different business requirements.
When scheduling, carefully consider on-call times and rotation cycles to avoid coverage gaps.

2. Modification#

Hover over a rule and click to open the rule configuration dialog.
Changes to existing schedule rules, including adding/removing on-call personnel or modifying schedule times, won't affect historical data.
Rule changes take effect immediately after saving.

3. Delete#

Rule deletion cannot be undone, please proceed with caution.
Deletion takes effect immediately, please confirm if any business operations are still using the rule before deletion.

4. Temporary Schedule Changes#

Temporary schedule changes are mainly used for pre-planned schedules, such as when an on-call person needs a replacement due to unexpected circumstances or leave.
Before making schedule changes, thoroughly communicate the required on-call times with the replacement person. While shift rotations include notifications, immediate adjustments take effect instantly without system notifications.

Schedule Examples#

Daily Schedule#

Requirements Overview:
Teams A and B alternate on-call duties daily.
Rules/Effects:
描述

Combined Schedule#

Requirements Overview:
Team A is on-call from 9 AM to 6 PM, Monday through Friday.
Team B is on-call from 7 PM to 9 AM the next day, Monday through Friday.
Team C handles weekend on-call duties.
Teams rotate weekly.
Rule Display:
描述
Effect Display:
描述
修改于 2025-01-02 07:53:05
上一页
Label Enrichment
下一页
Templates
Built with