From 7ba8e41ea0e71b10c5f460a0cb8828be914e23ce Mon Sep 17 00:00:00 2001 From: ysyneu Date: Fri, 31 Jul 2026 02:35:25 -0700 Subject: [PATCH 1/2] docs(comparison): restructure product section by current product modules MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Reorganize the product dimension into the current module split: On-call (noise reduction, schedules, dispatch & escalation, notification channels), Response, Status Pages, AI SRE, and Platform (ingestion & integrations, alert pipelines & label enrichment, insights & reporting, account & security, developer ecosystem) — replacing the legacy integration/incident-handling/platform grouping - Keep the guide at three purchase dimensions: product, service, pricing - Flatten all Accordions and product-section Tabs into plain headings and tables so the whole comparison is scannable without clicks - Dissolve the standalone customization table into its owning modules and deduplicate rows that appeared in multiple sections --- en/on-call/quickstart/comparison.mdx | 285 ++++++++++++--------------- zh/on-call/quickstart/comparison.mdx | 285 ++++++++++++--------------- 2 files changed, 252 insertions(+), 318 deletions(-) diff --git a/en/on-call/quickstart/comparison.mdx b/en/on-call/quickstart/comparison.mdx index 4183164a..328879b1 100644 --- a/en/on-call/quickstart/comparison.mdx +++ b/en/on-call/quickstart/comparison.mdx @@ -39,7 +39,7 @@ When your organization encounters the following situations, it's time to conside --- -This guide provides **comprehensive On-call tool procurement recommendations**. We'll analyze the points IT managers should focus on when seeking efficient collaborative incident management solutions for development and operations teams, across four core dimensions: **Product Features**, **AI Capabilities**, **Service Quality**, and **Pricing Strategy**. +This guide provides **comprehensive On-call tool procurement recommendations**. We'll analyze the points IT managers should focus on when seeking efficient collaborative incident management solutions for development and operations teams, across three core dimensions: **Product Features**, **Service Quality**, and **Pricing Strategy**. We'll also provide detailed comparison analysis between **Flashduty** and **PagerDuty**, two leading On-call vendors, to help you make an informed choice. @@ -53,146 +53,102 @@ The feature and pricing information on this page is current **as of July 2026**; --- -### Integration Capabilities +Product features are compared module by module, following Flashduty's current product structure: **On-call** (noise reduction, scheduling, escalation, notifications), **Response** (war room collaboration and incident resolution), **Status Pages** (external status communication), **AI SRE** (autonomous troubleshooting agent), and the **platform foundation** that underpins them (integrations, alert pipelines, insights, security, and the open developer ecosystem). This breakdown roughly maps to PagerDuty's own product lines, making it easy to compare block by block. -As the **process handling center** for incident management, the system needs strong data ingestion and outbound capabilities to achieve seamless integration with all kinds of systems. +### On-call -| Core Capability | Flashduty | PagerDuty | Notes | -| --- | --- | --- | --- | -| **Alert Integration** | 60+ integration sources with full coverage of China-region cloud and monitoring ecosystems (Alibaba Cloud, Tencent Cloud, Huawei Cloud, JD Cloud, Kingsoft Cloud, UCloud, etc.), **compatible with the PagerDuty protocol** | 750+ integrations with broad overseas ecosystem coverage | PagerDuty offers more integrations overall; Flashduty covers the China-region tech stack more completely, and existing PagerDuty integration configs can switch over directly | -| **Pull-based Ingestion** | [HTTP Pull](/en/on-call/integration/alert-integration/alert-sources/http-pull) periodically polls an endpoint; [DB Pull](/en/on-call/integration/alert-integration/alert-sources/db-pull) queries MySQL/PostgreSQL/ClickHouse directly to generate alerts from incremental changes | Push-based integration is the primary model | Legacy systems with no Webhook push capability can still integrate with Flashduty | -| **Two-way Ticket Sync** | [Jira](/en/on-call/integration/webhooks/jira-sync), [ServiceNow](/en/on-call/integration/webhooks/servicenow-sync), [ServiceDesk Plus](/en/on-call/integration/webhooks/servicedesk-plus-sync) | Jira, ServiceNow, etc. | Both support | -| **Change Event Integration** | ✅ Supports change event ingestion, dynamic routing, and label enrichment | ✅ Change Events | Both support | -| **External Incident Submission** | ✅ Customers or partners can submit incidents **without logging in**, via a standalone page or API, with automatic escalation policy matching | Only supports email-to-incident, no structured form | Teams serving external customers can plug customer-reported issues directly into the handling process | -| **Link Integration** | ✅ One-click jump to CMDB or internal systems by hostname and other labels | — | | -| **Webhooks** | ✅ Supports outbound push of incident operations, subscribable by event type or source | ✅ | Both support | -| **Open APIs** | ✅ 290 endpoints covering On-call, Monitors, RUM, AI SRE, and platform management | ✅ | Both provide rich APIs with detailed documentation | +On-call solves "getting the alert to the right person": reduce noise first, then notify according to scheduling and escalation policies. + +#### Alert Noise Reduction + +| Capability | Description | Comparison | +| --- | --- | --- | +| **Intelligent Grouping** | Group similar alerts to reduce alert fatigue, with similarity computed from custom fields | ✅ Both support | +| **Incident Silencing** | Stop alert notifications during market closures or system maintenance | ✅ Both support | +| **[Incident Inhibition](/en/on-call/channel/noise-reduction)** | Automatically inhibit related pod incidents when the host fails | ✅ **Flashduty exclusive** | +| **[Storm Warning](/en/on-call/channel/noise-reduction)** | Re-notify with escalated urgency when the number of grouped alerts in an incident gets too high, with multi-tier thresholds | ✅ **Flashduty exclusive** | +| **Flapping Convergence** | Moderately reduce notifications when the same incident triggers and recovers repeatedly | ✅ **Flashduty exclusive** | +| **Delayed Notification** | Delay the notification window to filter out incidents that auto-recover immediately | ✅ Both support | -**Integration-on-demand commitment**: If a commercial or open-source tool you rely on isn't in our integration list yet, contact us — as long as you need it, we commit to fast turnaround support. +Flashduty offers more **exclusive features** for noise reduction, effectively cutting down alert fatigue. -### Incident Handling Capabilities +#### Schedule Management -Incident handling is the system's **core functionality**, evaluated primarily on feature **richness** and **flexibility**. - - - - | Feature | Evaluation Points | Comparison | - | --- | --- | --- | - | **Routing Capability** | Does it support dedicated integrations? Shared integrations with flexible routing rules? | **Both support**. Flashduty lets you set routing rules directly on the integration page, with routing version management and rollback; PagerDuty requires complex Event Orchestration or Workflows to achieve this | - +| Feature | Requirements | Comparison | +| --- | --- | --- | +| **Rotation Cycle** | Rotate by day, week, or custom period | ✅ Both support | +| **Time Restriction** | Restrict on-call hours within the rotation cycle | ✅ Both support | +| **Date Skipping** | Skip specific dates (different rules for workdays/non-workdays), with date-mask mode support | ✅ **Flashduty exclusive** | +| **Period Rules** | Different rotation rules for different time periods | ✅ Both support, Flashduty can set a cycle end time | +| **Temporary Override** | Set temporary schedule overrides | ✅ Both support | +| **On-call Roles** | Set primary/backup and other roles | ✅ **Flashduty exclusive** | +| **Multi-person On-call** | Multiple people on-call at once, rotating together | ✅ **Flashduty exclusive** | +| **Fair Rotation** | Avoid the same person always being on-call at a specific time | ✅ **Flashduty exclusive** (solves the problem where, in a 7-person daily rotation, one person always ends up on-call every Sunday) | +| **Rotation Notifications** | Configure rotation notifications, including advance notice and scheduled notices | ✅ Both support, Flashduty supports more notification methods | +| **Calendar Export** | Export the on-call calendar | ✅ PagerDuty supports | + +#### Dispatch & Escalation + +| Capability | Details | Comparison | +| --- | --- | --- | +| **[Policy Assignment](/en/on-call/channel/escalation-rule)** | Assign to a schedule, team, or individual, with configurable notification methods | Flashduty additionally supports assigning to a team and setting notification methods; PagerDuty can only configure this globally | +| **Condition Matching** | Multiple assignment policies matched by weight | ✅ **Flashduty exclusive** (PagerDuty supports only one escalation policy per Service) | +| **Auto Escalation** | Automatically escalate unresolved incidents on timeout, plus manual escalation | ✅ Both support | +| **[Dynamic Assignment](/en/on-call/advanced/dynamic-notifications)** | Dynamically replace or **append** assignees, teams, and group chats based on labels (reset/append dual modes, combinable with CMDB/CSV mapping data to auto-generate assignment targets) | ✅ **Flashduty exclusive**, greatly reducing the cost of system integration and configuration maintenance | - - | Feature | Description | Comparison | - | --- | --- | --- | - | **Alert Processing Pipeline** | Orchestrate actions like severity reset, title rewriting, alert filtering, and CMDB lookups | Both support; Flashduty provides a right-side alert history panel to help debug rules | - | **Custom Fields** | Add fields, define types and enum values | ✅ Both support | - | **Regex Extraction** | Extract new labels from existing info via regex | ✅ Both support | - | **Info Combination** | Combine existing info to create new labels | ✅ Both support | - | **Data Mapping** | Import data tables to dynamically generate new labels (e.g. imported CMDB data), with mapping data manageable directly in the console | ✅ **Flashduty exclusive** | - +#### Notification Channels - - | Capability | Description | Comparison | - | --- | --- | --- | - | **Intelligent Grouping** | Group similar alerts to reduce alert fatigue, with similarity computed from custom fields | ✅ Both support | - | **Incident Silencing** | Stop alert notifications during market closures or system maintenance | ✅ Both support | - | **[Incident Inhibition](/en/on-call/channel/noise-reduction)** | Automatically inhibit related pod incidents when the host fails | ✅ **Flashduty exclusive** | - | **[Storm Warning](/en/on-call/channel/noise-reduction)** | Re-notify with escalated urgency when the number of grouped alerts in an incident gets too high, with multi-tier thresholds | ✅ **Flashduty exclusive** | - | **Flapping Convergence** | Moderately reduce notifications when the same incident triggers and recovers repeatedly | ✅ **Flashduty exclusive** | - | **Delayed Notification** | Delay the notification window to filter out incidents that auto-recover immediately | ✅ Both support | - - - Flashduty offers more **exclusive features** for noise reduction, effectively cutting down alert fatigue. - - +| Method | Localization Support | Comparison | +| --- | --- | --- | +| **Voice/SMS (Mainland China)** | Voice and SMS support in mainland China | ✅ Both support, but PagerDuty's delivery rate is low and unstable | +| **Fixed Caller ID** | A fixed display number, with the voice number automatically syncable to phone contact allowlists | ✅ Both support | +| **Email Notification** | Email notification support | ✅ Both support | +| **China IM** | Collaboration with mainstream China-region IM apps | ✅ Flashduty supports Feishu/Lark, Dingtalk, and WeCom app integration, **including on-premises versions of Feishu/Lark and Dingtalk** | +| **International IM** | Collaboration with mainstream international IM apps | ✅ Both support Slack and Microsoft Teams; Flashduty additionally supports Zoom and Telegram bots | +| **Mobile** | Mobile app support | ✅ Both support; Flashduty's iOS app uses the Apple Critical Alerts protocol to **break through Do Not Disturb mode**, and its Android app independently adapts to system-level push from mainstream Chinese device makers for higher delivery rates | +| **[Custom Templates](/en/on-call/configuration/templates)** | Fully customizable notification templates across all channels, **including voice notification templates**, with historical-incident preview debugging and smart input suggestions | Flashduty supports rich template syntax; no equivalent cross-channel template customization found in public materials for PagerDuty | - - | Capability | Details | Comparison | - | --- | --- | --- | - | **[Policy Assignment](/en/on-call/channel/escalation-rule)** | Assign to a schedule, team, or individual, with configurable notification methods | Flashduty additionally supports assigning to a team and setting notification methods; PagerDuty can only configure this globally | - | **Condition Matching** | Multiple assignment policies matched by weight | ✅ **Flashduty exclusive** (PagerDuty supports only one escalation policy per Service) | - | **Auto Escalation** | Automatically escalate unresolved incidents on timeout, plus manual escalation | ✅ Both support | - | **[Dynamic Assignment](/en/on-call/advanced/dynamic-notifications)** | Dynamically replace or **append** assignees, teams, and group chats based on labels (reset/append dual modes, combinable with CMDB/CSV mapping data) | ✅ **Flashduty exclusive**, greatly reducing the cost of system integration and configuration maintenance | - +### Response - - | Feature | Description | Comparison | - | --- | --- | --- | - | **Basic Operations** | Manually create, acknowledge, close, comment on, snooze, merge, and bulk-assign incidents | ✅ Both support | - | **Automation** | Auto-close on timeout (countdown can be based on the last event time), auto-cancel snooze on timeout | ✅ Both support | - | **[War Room](/en/on-call/advanced/war-room)** | One-click creation of a Feishu/Lark, Dingtalk, WeCom, or Slack group chat, automatically inviting responders, with a pinned incident card that updates in real time | ✅ **Flashduty exclusive** (for China-region IM scenarios) | - | **[Postmortems](/en/on-call/post-mortem/what-is-post-mortem)** | Full postmortem reports: timeline capture, collaborative editing, permission controls, with support for **[AI-generated postmortems](/en/on-call/post-mortem/ai-generate-post-mortem)** | Both support; Flashduty can generate a structured postmortem in one click from the incident timeline and alert data | - | **Similar Incidents** | Identify and associate similar incidents | ✅ Both support | - | **[Outlier Incidents](/en/on-call/incident/outlier-incidents)** | Automatic alerts for outlier incidents | ✅ **Flashduty exclusive** | - | **[Reassignment](/en/on-call/incident/escalate-dispatch-incident)** | Supports incident reassignment | ✅ Both support | - | **Custom Actions** | Add custom actions (e.g. trigger a host restart), with a confirmation step before execution | ✅ Both support | - | **Reopen Incident** | Reopen after closure and notify | ✅ **Flashduty exclusive** | - | **Custom Fields** | Mark false positives, add meeting links, etc. | ✅ Both support; PagerDuty requires configuring Incident Types first and enabling fields one by one | - | **Search Capability** | Search by labels, custom fields, title, personnel | Flashduty supports exact, wildcard, and regex matching; PagerDuty supports basic field-filter search | - +Response solves "closing the loop quickly once the right person is found": a single timeline, a single war room—handling, collaboration, and postmortems that never lose context. - - | Dimension | Description | Comparison | - | --- | --- | --- | - | **Basic Statistics** | Count incidents and events by dimensions like time, team, and service | ✅ Both support | - | **Handling Metrics** | Track key metrics like MTTA, MTTR | ✅ Both support | - | **Personnel Metrics** | Track individual incident-handling metrics and counts, including interruption counts, response effort, and other workload metrics | ✅ Both support | - | **Frequency Analysis** | Identify the hosts and policies with the most frequent incidents | ✅ **Flashduty exclusive** | - | **Time Cost** | Track time spent handling incidents | ✅ Both support | - | **Time Period Analysis** | Break down metrics by work, rest, and sleep periods | ✅ **Flashduty exclusive** | - | **Data Export** | Download detailed data, with support for report printing and CSV export | ✅ Both support | - - +| Feature | Description | Comparison | +| --- | --- | --- | +| **Basic Operations** | Manually create, acknowledge, close, comment on, snooze, merge, and bulk-assign incidents | ✅ Both support | +| **Closure Automation** | Auto-close on timeout (countdown can be based on the last event time), auto-cancel snooze on timeout | ✅ Both support | +| **[War Room](/en/on-call/advanced/war-room)** | One-click creation of a Feishu/Lark, Dingtalk, WeCom, or Slack group chat, automatically inviting responders, with a pinned incident card that updates in real time, and acknowledge/escalate/close actions in the chat syncing back to Flashduty | ✅ **Flashduty exclusive** (for China-region IM scenarios) | +| **[Postmortems](/en/on-call/post-mortem/what-is-post-mortem)** | Full postmortem reports: timeline capture, collaborative editing, permission controls, with support for **[AI-generated postmortems](/en/on-call/post-mortem/ai-generate-post-mortem)** | Both support; Flashduty can generate a structured postmortem in one click from the incident timeline and alert data | +| **Similar Incidents** | Identify and associate similar incidents | ✅ Both support | +| **[Outlier Incidents](/en/on-call/incident/outlier-incidents)** | Automatic alerts for outlier incidents | ✅ **Flashduty exclusive** | +| **[Reassignment](/en/on-call/incident/escalate-dispatch-incident)** | Supports incident reassignment | ✅ Both support | +| **Custom Actions** | Add custom actions (e.g. trigger a host restart), with a confirmation step before execution | ✅ Both support | +| **Reopen Incident** | Reopen after closure and notify | ✅ **Flashduty exclusive** | +| **[Custom Fields](/en/on-call/configuration/custom-fields)** | Freely define incident business attributes (mark false positives, add meeting links, etc.), **with field-based search** | Both support; PagerDuty requires configuring Incident Types first and enabling fields one by one | +| **[Custom Forms](/en/on-call/configuration/custom-forms)** | Conditionally show supplementary-info forms when creating, acknowledging, or closing an incident | Flashduty supports this across the full lifecycle; PagerDuty only supports required fields at closure (Enterprise tier only) | +| **Search Capability** | Search by labels, custom fields, title, personnel | Flashduty supports exact, wildcard, and regex matching; PagerDuty supports basic field-filter search | + +### Status Pages -### Platform Capabilities - -Platform fundamentals cover core capabilities like **member management**, **on-call response**, and **notification capabilities**. - - - - | Feature | Requirements | Comparison | - | --- | --- | --- | - | **Rotation Cycle** | Rotate by day, week, or custom period | ✅ Both support | - | **Time Restriction** | Restrict on-call hours within the rotation cycle | ✅ Both support | - | **Date Skipping** | Skip specific dates (different rules for workdays/non-workdays), with date-mask mode support | ✅ **Flashduty exclusive** | - | **Period Rules** | Different rotation rules for different time periods | ✅ Both support, Flashduty can set a cycle end time | - | **Temporary Override** | Set temporary schedule overrides | ✅ Both support | - | **On-call Roles** | Set primary/backup and other roles | ✅ **Flashduty exclusive** | - | **Multi-person On-call** | Multiple people on-call at once, rotating together | ✅ **Flashduty exclusive** | - | **Fair Rotation** | Avoid the same person always being on-call at a specific time | ✅ **Flashduty exclusive** (solves the problem where, in a 7-person daily rotation, one person always ends up on-call every Sunday) | - | **Rotation Notifications** | Configure rotation notifications, including advance notice and scheduled notices | ✅ Both support, Flashduty supports more notification methods | - | **Calendar Export** | Export the on-call calendar | ✅ PagerDuty supports | - - - - | Method | Localization Support | Comparison | - | --- | --- | --- | - | **Voice/SMS (Mainland China)** | Voice and SMS support in mainland China | ✅ Both support, but PagerDuty's delivery rate is low and unstable | - | **Fixed Caller ID** | A fixed display number, with the voice number automatically syncable to phone contact allowlists | ✅ Both support | - | **Email Notification** | Email notification support | ✅ Both support | - | **China IM** | Collaboration with mainstream China-region IM apps | ✅ Flashduty supports Feishu/Lark, Dingtalk, and WeCom app integration, **including on-premises versions of Feishu/Lark and Dingtalk** | - | **International IM** | Collaboration with mainstream international IM apps | ✅ Both support Slack and Microsoft Teams; Flashduty additionally supports Zoom and Telegram bots | - | **Mobile** | Mobile app support | ✅ Both support; Flashduty's iOS app uses the Apple Critical Alerts protocol to **break through Do Not Disturb mode**, and its Android app independently adapts to system-level push from mainstream Chinese device makers for higher delivery rates | - | **[Custom Templates](/en/on-call/configuration/templates)** | Custom notification templates | ✅ **Flashduty exclusive**, with rich template syntax | - - - - | Feature | Description | Comparison | - | --- | --- | --- | - | **Single Sign-On** | SSO protocol support | Flashduty: SAML, OIDC, CAS, LDAP, with support for **dedicated subdomain login**, plus setup guides for Authing, Keycloak, and OpenLDAP; PagerDuty: SAML, OAuth2 | - | **Data Isolation** | Incident data isolated by team | ✅ Flashduty supports a **private access level** for collaboration spaces — incident data in a private space is visible only to team members and admins | - | **Operation Audit** | Complete operation audit logs | ✅ Both support | - | **Private Deployment** | On-premises deployment | ✅ **Flashduty supports** (pricing differs from the SaaS service) | - - +Communicating service status to the outside world is the last mile of incident management. Flashduty's Status Page ships with On-call and is more full-featured; PagerDuty Status Pages are tiered by plan and subscriber volume. ---- +| Dimension | Flashduty | PagerDuty | +| --- | --- | --- | +| **Availability** | [Status Page](/en/on-call/statuspage/statuspage) is included with the On-call product, **public + internal status pages in one** | The base plan includes only 1 public status page; internal status pages require Business or above, and private status pages are a Premium add-on | +| **Subscription Cost** | ✅ **Free for subscribers, no account required** | Public-page subscriptions are free but capped by plan (Professional 250 / Business 500 / Enterprise 1,000; exceeding the cap requires a sales add-on); **viewers of internal status pages and internal incident activity must hold an account, at minimum a paid Stakeholder license** | +| **Subscription Granularity & Methods** | **Three-tier subscriptions** (all / component / event level), email + **confirmation-free RSS 2.0 / Atom 1.0 subscriptions**, with bulk import/export and self-service subscriber management | Email / Slack / Webhook; no RSS/Atom subscription found | +| **Multilingual Notifications** | ✅ Natively preserves each subscriber's language preference | Not found in public materials | +| **Internal Status Page Notifications** | Native push to Feishu/Lark, Dingtalk, WeCom, and Slack | Viewers need a PagerDuty account (starting at a Stakeholder license) | +| **Proof of Availability** | Automatically accumulates historical uptime, **with maintenance events excluded from uptime loss** | Supports 7/30/90-day uptime display | +| **Display Customization** | Custom domain, calendar + list dual views, configurable availability display, component visibility controls | Custom domain, logo/color scheme/header and footer | +| **Atlassian Migration** | **Compatible subscription URLs** (`history.rss` / `history.atom`) + one-click CLI migration of components, incidents, and subscribers | — | -## AI Capability Comparison + +If you're currently using Atlassian Statuspage, see our in-depth [Flashduty vs Atlassian Statuspage comparison](/en/on-call/statuspage/comparison). + ---- +### AI SRE The two vendors take different approaches to AI: **PagerDuty splits AI across multiple products**—AIOps handles incident noise reduction and correlation (a separate add-on), Advance provides generative Q&A and summaries, and SRE Agent can autonomously analyze logs and metrics for diagnosis, though its remediation actions depend on pre-configured automation scripts. **Flashduty, beyond its built-in AI summaries and AI postmortems, also provides [AI SRE](/en/ai-sre): an autonomous SRE Agent connected to your real environment that dynamically calls tools and executes commands within a session—able to investigate problems it has never seen before**. @@ -213,52 +169,63 @@ The two vendors take different approaches to AI: **PagerDuty splits AI across mu PagerDuty's AIOps has been refined over many years for large-scale event correlation and is a mature capability. The core differences between the two: first, **how it's sold**—Flashduty bundles it in, while PagerDuty sells it as separate product add-ons; second, **the remediation path**—Flashduty investigates and resolves dynamically within a session, while PagerDuty's automated remediation depends on pre-configured, fixed scripts. ---- - -## Customization Capability Comparison +### Platform ---- - -Incident handling workflows differ from team to team—**every step in the process should be able to adapt to your workflow**. +Platform is the shared foundation underneath the four products above: how data gets in, how alerts get processed before reaching the team, how metrics accumulate, and security plus the open ecosystem. -| Customization | Flashduty | PagerDuty | -| --- | --- | --- | -| **[Custom Fields](/en/on-call/configuration/custom-fields)** | Freely define business attributes for incidents/alerts, **with field-based search** (exact, wildcard, regex) | Supports Custom Fields and field-based filtering, but requires configuring Incident Types first | -| **[Custom Forms](/en/on-call/configuration/custom-forms)** | Conditionally show supplementary-info forms when creating, acknowledging, or closing an incident | Only supports required fields at closure (Enterprise tier only), with no coverage for creation/acknowledgment | -| **Custom Webhooks** | Custom payload format, configurable retry conditions and automatic retries, signature-free verification, **full call-history tracing** (status codes, retry counts, request/response detail) | Fixed payload format, fixed retry policy (3 retries, not configurable), no self-service call-history lookup | -| **[Notification Templates](/en/on-call/configuration/templates)** | Fully customizable templates across all channels, **including voice notification templates**, with historical-incident preview debugging and smart input suggestions | No equivalent cross-channel template customization found in public materials | -| **[Dynamic Assignment](/en/on-call/advanced/dynamic-notifications)** | Dual reset (replace) + append modes, combined with external data mapping to auto-generate assignment targets | — | -| **[Custom Menu](/en/platform/custom-menu)** | Embed external links or iframe pages in the sidebar, visible based on role authorization | — | -| **[Roles & Data Permissions](/en/platform/permission-design)** | Preset RBAC + custom roles, team-level data permissions, private collaboration-space level | RBAC role management | +#### Ingestion & Integrations ---- +| Core Capability | Flashduty | PagerDuty | Notes | +| --- | --- | --- | --- | +| **Alert Integration** | 60+ integration sources with full coverage of China-region cloud and monitoring ecosystems (Alibaba Cloud, Tencent Cloud, Huawei Cloud, JD Cloud, Kingsoft Cloud, UCloud, etc.), **compatible with the PagerDuty protocol** | 750+ integrations with broad overseas ecosystem coverage | PagerDuty offers more integrations overall; Flashduty covers the China-region tech stack more completely, and existing PagerDuty integration configs can switch over directly | +| **Pull-based Ingestion** | [HTTP Pull](/en/on-call/integration/alert-integration/alert-sources/http-pull) periodically polls an endpoint; [DB Pull](/en/on-call/integration/alert-integration/alert-sources/db-pull) queries MySQL/PostgreSQL/ClickHouse directly to generate alerts from incremental changes | Push-based integration is the primary model | Legacy systems with no Webhook push capability can still integrate with Flashduty | +| **Two-way Ticket Sync** | [Jira](/en/on-call/integration/webhooks/jira-sync), [ServiceNow](/en/on-call/integration/webhooks/servicenow-sync), [ServiceDesk Plus](/en/on-call/integration/webhooks/servicedesk-plus-sync) | Jira, ServiceNow, etc. | Both support | +| **Change Event Integration** | ✅ Supports change event ingestion, dynamic routing, and label enrichment | ✅ Change Events | Both support | +| **External Incident Submission** | ✅ Customers or partners can submit incidents **without logging in**, via a standalone page or API, with automatic escalation policy matching | Only supports email-to-incident, no structured form | Teams serving external customers can plug customer-reported issues directly into the handling process | +| **Link Integration** | ✅ One-click jump to CMDB or internal systems by hostname and other labels | — | | +| **Custom Webhooks (Outbound)** | Custom payload format, configurable retry conditions and automatic retries, signature-free verification, **full call-history tracing** (status codes, retry counts, request/response detail), subscribable by event type or source | Fixed payload format, fixed retry policy (3 retries, not configurable), no self-service call-history lookup | | +| **Open APIs** | ✅ 290 endpoints covering On-call, Monitors, RUM, AI SRE, and platform management | ✅ | Both provide rich APIs with detailed documentation | -## Status Page Comparison + +**Integration-on-demand commitment**: If a commercial or open-source tool you rely on isn't in our integration list yet, contact us — as long as you need it, we commit to fast turnaround support. + ---- +#### Alert Pipelines & Label Enrichment -Communicating service status to the outside world is the last mile of incident management. Flashduty's Status Page ships with On-call and is more full-featured; PagerDuty Status Pages are tiered by plan and subscriber volume. +Before reaching the team, alerts pass through routing, filtering, and transformation. -| Dimension | Flashduty | PagerDuty | +| Feature | Description | Comparison | | --- | --- | --- | -| **Availability** | [Status Page](/en/on-call/statuspage/statuspage) is included with the On-call product, **public + internal status pages in one** | The base plan includes only 1 public status page; internal status pages require Business or above, and private status pages are a Premium add-on | -| **Subscription Cost** | ✅ **Free for subscribers, no account required** | Public-page subscriptions are free but capped by plan (Professional 250 / Business 500 / Enterprise 1,000; exceeding the cap requires a sales add-on); **viewers of internal status pages and internal incident activity must hold an account, at minimum a paid Stakeholder license** | -| **Subscription Granularity & Methods** | **Three-tier subscriptions** (all / component / event level), email + **confirmation-free RSS 2.0 / Atom 1.0 subscriptions**, with bulk import/export and self-service subscriber management | Email / Slack / Webhook; no RSS/Atom subscription found | -| **Multilingual Notifications** | ✅ Natively preserves each subscriber's language preference | Not found in public materials | -| **Internal Status Page Notifications** | Native push to Feishu/Lark, Dingtalk, WeCom, and Slack | Viewers need a PagerDuty account (starting at a Stakeholder license) | -| **Proof of Availability** | Automatically accumulates historical uptime, **with maintenance events excluded from uptime loss** | Supports 7/30/90-day uptime display | -| **Display Customization** | Custom domain, calendar + list dual views, configurable availability display, component visibility controls | Custom domain, logo/color scheme/header and footer | -| **Atlassian Migration** | **Compatible subscription URLs** (`history.rss` / `history.atom`) + one-click CLI migration of components, incidents, and subscribers | — | +| **Alert Routing** | Dedicated integrations + flexible routing across shared integrations | **Both support**. Flashduty lets you set routing rules directly on the integration page, with routing version management and rollback; PagerDuty requires complex Event Orchestration or Workflows to achieve this | +| **Alert Processing Pipeline** | Orchestrate actions like severity reset, title rewriting, alert filtering, and CMDB lookups | Both support; Flashduty provides a right-side alert history panel to help debug rules | +| **Regex Extraction** | Extract new labels from existing info via regex | ✅ Both support | +| **Info Combination** | Combine existing info to create new labels | ✅ Both support | +| **Data Mapping** | Import data tables to dynamically generate new labels (e.g. imported CMDB data), with mapping data manageable directly in the console | ✅ **Flashduty exclusive** | - -If you're currently using Atlassian Statuspage, see our in-depth [Flashduty vs Atlassian Statuspage comparison](/en/on-call/statuspage/comparison). - +#### Insights & Reporting ---- +| Dimension | Description | Comparison | +| --- | --- | --- | +| **Basic Statistics** | Count incidents and events by dimensions like time, team, and service | ✅ Both support | +| **Handling Metrics** | Track key metrics like MTTA, MTTR | ✅ Both support | +| **Personnel Metrics** | Track individual incident-handling metrics and counts, including interruption counts, response effort, and other workload metrics | ✅ Both support | +| **Frequency Analysis** | Identify the hosts and policies with the most frequent incidents | ✅ **Flashduty exclusive** | +| **Time Cost** | Track time spent handling incidents | ✅ Both support | +| **Time Period Analysis** | Break down metrics by work, rest, and sleep periods | ✅ **Flashduty exclusive** | +| **Data Export** | Download detailed data, with support for report printing and CSV export | ✅ Both support | -## Developer Ecosystem +#### Account & Security ---- +| Feature | Description | Comparison | +| --- | --- | --- | +| **Single Sign-On** | SSO protocol support | Flashduty: SAML, OIDC, CAS, LDAP, with support for **dedicated subdomain login**, plus setup guides for Authing, Keycloak, and OpenLDAP; PagerDuty: SAML, OAuth2 | +| **[Roles & Data Permissions](/en/platform/permission-design)** | Preset RBAC + custom roles, team-level data permissions | Flashduty supports custom roles and team-level data permissions; PagerDuty provides RBAC role management | +| **Data Isolation** | Incident data isolated by team | ✅ Flashduty supports a **private access level** for collaboration spaces — incident data in a private space is visible only to team members and admins | +| **[Custom Menu](/en/platform/custom-menu)** | Embed external links or iframe pages in the sidebar, visible based on role authorization | ✅ **Flashduty exclusive** | +| **Operation Audit** | Complete operation audit logs | ✅ Both support | +| **Private Deployment** | On-premises deployment | ✅ **Flashduty supports** (pricing differs from the SaaS service) | + +#### Developer Ecosystem | Tool | Flashduty | Notes | | --- | --- | --- | diff --git a/zh/on-call/quickstart/comparison.mdx b/zh/on-call/quickstart/comparison.mdx index 96de7272..20219fe9 100644 --- a/zh/on-call/quickstart/comparison.mdx +++ b/zh/on-call/quickstart/comparison.mdx @@ -39,7 +39,7 @@ keywords: ["产品对比", "PagerDuty", "功能对比", "价格对比", "竞品 --- -本指南将为您提供**全面的 On-call 工具采购建议**，我们将从 **产品功能**、**AI 能力**、**服务质量** 与 **价格策略** 四个核心维度出发，深入分析 IT 管理人员在为开发和运维团队寻找高效协作的故障管理解决方案时应该关注的要点。 +本指南将为您提供**全面的 On-call 工具采购建议**，我们将从 **产品功能**、**服务质量** 与 **价格策略** 三个核心维度出发，深入分析 IT 管理人员在为开发和运维团队寻找高效协作的故障管理解决方案时应该关注的要点。 同时，我们将提供 **Flashduty** 与 **PagerDuty** 两大主流 On-call 供应商的详细对比分析，助您做出明智的选择。 @@ -53,146 +53,102 @@ keywords: ["产品对比", "PagerDuty", "功能对比", "价格对比", "竞品 --- -### 集成能力 +产品功能按 Flashduty 当前的产品模块逐块对比：**On-call**（降噪、排班、升级、通知）、**Response**（作战室协同与故障闭环）、**Status Pages**（对外状态沟通）、**AI SRE**（自治排障 Agent），以及支撑它们的**平台底座**（集成接入、告警流水线、洞察、安全与开放生态）。这一划分与 PagerDuty 的产品线基本对应，方便逐块对照。 -故障管理系统作为**流程处置中心**，需要具备强大的数据接入和外呼能力，实现与各类系统的无缝集成。 +### On-call -| 核心能力 | Flashduty | PagerDuty | 说明 | -| --- | --- | --- | --- | -| **告警集成** | 60+ 集成源，国内云与监控生态全覆盖（阿里云、腾讯云、华为云、京东云、金山云、UCloud 等），**兼容 PagerDuty 协议** | 750+ 集成，海外生态覆盖广 | PagerDuty 集成数量更多；Flashduty 对国内技术栈覆盖更完整，且存量 PagerDuty 集成配置可直接切换 | -| **拉取式接入** | [HTTP Pull](/zh/on-call/integration/alert-integration/alert-sources/http-pull) 周期拉取接口、[DB Pull](/zh/on-call/integration/alert-integration/alert-sources/db-pull) 直查 MySQL/PostgreSQL/ClickHouse 增量生成告警 | 以推送式集成为主 | 老系统没有 Webhook 推送能力也能接入 Flashduty | -| **工单双向同步** | [Jira](/zh/on-call/integration/webhooks/jira-sync)、[ServiceNow](/zh/on-call/integration/webhooks/servicenow-sync)、[ServiceDesk Plus](/zh/on-call/integration/webhooks/servicedesk-plus-sync) | Jira、ServiceNow 等 | 两者均支持 | -| **变更事件集成** | ✅ 支持变更事件接入、动态路由与标签二次加工 | ✅ Change Events | 两者均支持 | -| **外部故障提交** | ✅ 客户或合作伙伴**免登录**通过独立页面或 API 提交故障，自动匹配分派策略 | 仅支持邮件转 incident，无结构化表单 | 对外提供服务的团队可直接把客户报障接入处置流程 | -| **Link 集成** | ✅ 按 hostname 等标签一键跳转 CMDB 或内部系统 | — | | -| **Webhooks** | ✅ 支持故障操作对外推送，可按事件类型或来源订阅 | ✅ | 两者均支持 | -| **Open APIs** | ✅ 290 个接口，覆盖 On-call、Monitors、RUM、AI SRE 与平台管理 | ✅ | 两者均提供丰富的 API 和详细文档 | +On-call 解决「告警找到对的人」：先降噪，再按排班和升级策略通知到人。 + +#### 告警降噪 + +| 降噪能力 | 功能说明 | 对比 | +| --- | --- | --- | +| **智能聚合** | 将相似告警聚合处理，减少告警疲劳，支持基于自定义字段计算相似度 | ✅ 两者均支持 | +| **故障屏蔽** | 休市或系统维护期间，停止告警通知 | ✅ 两者均支持 | +| **[故障抑制](/zh/on-call/channel/noise-reduction)** | 宿主机故障时，自动抑制相关 pod 故障 | ✅ **Flashduty 独有** | +| **[风暴预警](/zh/on-call/channel/noise-reduction)** | 故障聚合告警数量过多时，再次通知提升响应力度，支持多级阶梯阈值 | ✅ **Flashduty 独有** | +| **抖动收敛** | 相同故障频繁发生与恢复时，适当减少通知 | ✅ **Flashduty 独有** | +| **延迟通知** | 延后窗口通知，过滤立即自动恢复的故障 | ✅ 两者均支持 | -**集成按需支持承诺**：如果您常用的商业软件或开源服务尚未在集成列表中，请联系我们——只要您需要，我们承诺快速支持。 +Flashduty 在告警降噪方面提供了更多**独有功能**，有效减少告警疲劳。 -### 故障处置能力 +#### 值班管理 -故障处置为系统的**核心功能**，主要考察产品功能的**丰富度**和**灵活性**。 - - - - | 功能项 | 评估要点 | 对比结果 | - | --- | --- | --- | - | **路由能力** | 是否支持专属集成？是否支持共享集成及灵活的路由规则？ | **两者均支持**。Flashduty 可在集成页面直接设置路由规则，并提供路由版本管理和回滚能力；PagerDuty 需通过复杂的 Event Orchestration 或 Workflow 实现 | - +| 值班功能 | 功能要求 | 对比 | +| --- | --- | --- | +| **轮换周期** | 按天、周或自定义周期轮换 | ✅ 两者均支持 | +| **时间限定** | 限定轮换周期内的值班时间 | ✅ 两者均支持 | +| **日期跳过** | 跳过特定日期（工作日/非工作日不同规则），支持日期掩码模式 | ✅ **Flashduty 独有** | +| **时段规则** | 不同时间段不同轮换规则 | ✅ 两者均支持，Flashduty 可设置周期结束时间 | +| **临时调班** | 设置临时调班 | ✅ 两者均支持 | +| **值班角色** | 设置主备值班等角色 | ✅ **Flashduty 独有** | +| **多人值班** | 同时多人值班并一起轮换 | ✅ **Flashduty 独有** | +| **公平轮换** | 避免固定人员在特定时间值班 | ✅ **Flashduty 独有**（解决 7 人按天轮换时某人永远周日值班的问题） | +| **轮换通知** | 设定轮换通知包括提前通知、定时通知 | ✅ 两者均支持，Flashduty 支持更多通知方式 | +| **日历导出** | 值班日历导出功能 | ✅ PagerDuty 支持 | + +#### 分派与升级 + +| 分派能力 | 功能详情 | 对比 | +| --- | --- | --- | +| **[策略分派](/zh/on-call/channel/escalation-rule)** | 支持分派给值班、团队或个人，同时设定通知方式 | Flashduty 额外支持分派到团队、设定通知方式；PagerDuty 仅能全局配置 | +| **条件匹配** | 多个分派策略按权重匹配 | ✅ **Flashduty 独有**（PagerDuty 一个 Service 下仅支持一个升级策略） | +| **自动升级** | 故障超时未解决自动升级 + 手动升级 | ✅ 两者均支持 | +| **[动态分派](/zh/on-call/advanced/dynamic-notifications)** | 根据标签动态替换或**追加**分派人员、团队与群聊（reset/append 双模式，可结合 CMDB/CSV 映射数据自动生成分派对象） | ✅ **Flashduty 独有**，大幅降低系统打通和配置维护成本 | - - | 功能项 | 功能说明 | 对比 | - | --- | --- | --- | - | **告警处理 Pipeline** | 等级重设、标题修改、告警过滤、CMDB 联动等处理动作编排 | 两者均支持；Flashduty 提供右侧告警历史面板辅助规则调试 | - | **自定义字段** | 增加字段，定义类型和枚举值 | ✅ 两者均支持 | - | **正则提取** | 通过已有信息正则提取出新的标签 | ✅ 两者均支持 | - | **信息组合** | 通过已有信息组合出新的标签 | ✅ 两者均支持 | - | **数据映射** | 导入数据表，动态生成新标签（如导入 CMDB 数据），支持控制台直接管理映射数据 | ✅ **Flashduty 独有** | - +#### 通知渠道 - - | 降噪能力 | 功能说明 | 对比 | - | --- | --- | --- | - | **智能聚合** | 将相似告警聚合处理，减少告警疲劳，支持基于自定义字段计算相似度 | ✅ 两者均支持 | - | **故障屏蔽** | 休市或系统维护期间，停止告警通知 | ✅ 两者均支持 | - | **[故障抑制](/zh/on-call/channel/noise-reduction)** | 宿主机故障时，自动抑制相关 pod 故障 | ✅ **Flashduty 独有** | - | **[风暴预警](/zh/on-call/channel/noise-reduction)** | 故障聚合告警数量过多时，再次通知提升响应力度，支持多级阶梯阈值 | ✅ **Flashduty 独有** | - | **抖动收敛** | 相同故障频繁发生与恢复时，适当减少通知 | ✅ **Flashduty 独有** | - | **延迟通知** | 延后窗口通知，过滤立即自动恢复的故障 | ✅ 两者均支持 | - - - Flashduty 在告警降噪方面提供了更多**独有功能**，有效减少告警疲劳。 - - +| 通知方式 | 本地化支持 | 对比 | +| --- | --- | --- | +| **语音短信（中国大陆）** | 中国大陆语音和短信支持 | ✅ 两者均支持，但 PagerDuty 触达率低、不稳定 | +| **固定显号** | 固定显示号码，语音号码可自动同步至手机通讯录白名单 | ✅ 两者均支持 | +| **邮件通知** | 邮件通知支持 | ✅ 两者均支持 | +| **中国大陆 IM** | 国内主流 IM 应用协同 | ✅ Flashduty 支持飞书、钉钉、企业微信应用集成，**含飞书/钉钉私有化版本** | +| **国际化 IM** | 国际主流 IM 应用协同 | ✅ 两者均支持 Slack、Microsoft Teams；Flashduty 额外支持 Zoom、Telegram 机器人 | +| **移动端** | 移动端 App 支持 | ✅ 两者均支持；Flashduty iOS 基于 Apple Critical Alerts 协议**突破勿扰模式**，Android 独立适配国内主流厂商系统级推送，触达率更高 | +| **[自定义模板](/zh/on-call/configuration/templates)** | 全渠道自定义通知模板，**含语音通知模板**，支持历史故障预览调试与智能输入提示 | Flashduty 支持丰富的模板语法；PagerDuty 公开资料未见对应的全渠道模板定制 | - - | 分派能力 | 功能详情 | 对比 | - | --- | --- | --- | - | **[策略分派](/zh/on-call/channel/escalation-rule)** | 支持分派给值班、团队或个人，同时设定通知方式 | Flashduty 额外支持分派到团队、设定通知方式；PagerDuty 仅能全局配置 | - | **条件匹配** | 多个分派策略按权重匹配 | ✅ **Flashduty 独有**（PagerDuty 一个 Service 下仅支持一个升级策略） | - | **自动升级** | 故障超时未解决自动升级 + 手动升级 | ✅ 两者均支持 | - | **[动态分派](/zh/on-call/advanced/dynamic-notifications)** | 根据标签动态替换或**追加**分派人员、团队与群聊（reset/append 双模式，可结合 CMDB/CSV 映射数据） | ✅ **Flashduty 独有**，大幅降低系统打通和配置维护成本 | - +### Response - - | 处理功能 | 功能说明 | 对比 | - | --- | --- | --- | - | **基础操作** | 手动创建、认领、关闭、评论、暂缓、合并、批量分派故障 | ✅ 两者均支持 | - | **自动化** | 超时自动关闭（支持按最后事件时间倒计时）、暂缓超时自动取消 | ✅ 两者均支持 | - | **[作战室](/zh/on-call/advanced/war-room)** | 一键创建飞书、钉钉、企微或 Slack 群聊，自动邀请处理人，故障卡片置顶实时更新 | ✅ **Flashduty 独有**（国内 IM 场景） | - | **[故障复盘](/zh/on-call/post-mortem/what-is-post-mortem)** | 完整的复盘报告：时间线沉淀、协同编辑、权限管控，支持 **[AI 自动生成复盘](/zh/on-call/post-mortem/ai-generate-post-mortem)** | 两者均支持；Flashduty 可基于故障时间线和告警数据一键生成结构化复盘 | - | **相似故障** | 识别和关联相似故障 | ✅ 两者均支持 | - | **[新奇故障](/zh/on-call/incident/outlier-incidents)** | 新奇故障自动提醒 | ✅ **Flashduty 独有** | - | **[重新分派](/zh/on-call/incident/escalate-dispatch-incident)** | 支持故障重新分派 | ✅ 两者均支持 | - | **自定义操作** | 添加自定义操作（如触发主机重启），执行前二次确认 | ✅ 两者均支持 | - | **故障重开** | 关闭后重新打开并通知 | ✅ **Flashduty 独有** | - | **自定义字段** | 标记误报、添加会议链接等 | ✅ 两者均支持；PagerDuty 需先配置 Incident Types 并逐字段启用 | - | **检索能力** | 按标签、自定义字段、标题、人员检索 | Flashduty 支持精确、通配、正则匹配；PagerDuty 支持基础的字段过滤检索 | - +Response 解决「找到人之后怎么快速闭环」：一条时间线、一间作战室，处理、协同、复盘不丢上下文。 - - | 分析维度 | 功能描述 | 对比 | - | --- | --- | --- | - | **基础统计** | 按时间、团队、服务等维度统计故障和事件数量 | ✅ 两者均支持 | - | **处理指标** | 统计 MTTA、MTTR 等关键指标 | ✅ 两者均支持 | - | **人员指标** | 统计人员处理故障指标和数量，含中断次数、响应投入等工作量指标 | ✅ 两者均支持 | - | **频发分析** | 统计最频繁发生故障的主机和策略 | ✅ **Flashduty 独有** | - | **时间成本** | 统计人员处理故障耗费时间 | ✅ 两者均支持 | - | **时段分析** | 按工作、休息、睡眠时段统计指标 | ✅ **Flashduty 独有** | - | **数据导出** | 下载数据明细，支持报表打印与 CSV 导出 | ✅ 两者均支持 | - - +| 处理功能 | 功能说明 | 对比 | +| --- | --- | --- | +| **基础操作** | 手动创建、认领、关闭、评论、暂缓、合并、批量分派故障 | ✅ 两者均支持 | +| **收尾自动化** | 超时自动关闭（支持按最后事件时间倒计时）、暂缓超时自动取消 | ✅ 两者均支持 | +| **[作战室](/zh/on-call/advanced/war-room)** | 一键创建飞书、钉钉、企微或 Slack 群聊，自动邀请处理人，故障卡片置顶实时更新，群内确认/升级/关闭状态同步回 Flashduty | ✅ **Flashduty 独有**（国内 IM 场景） | +| **[故障复盘](/zh/on-call/post-mortem/what-is-post-mortem)** | 完整的复盘报告：时间线沉淀、协同编辑、权限管控，支持 **[AI 自动生成复盘](/zh/on-call/post-mortem/ai-generate-post-mortem)** | 两者均支持；Flashduty 可基于故障时间线和告警数据一键生成结构化复盘 | +| **相似故障** | 识别和关联相似故障 | ✅ 两者均支持 | +| **[新奇故障](/zh/on-call/incident/outlier-incidents)** | 新奇故障自动提醒 | ✅ **Flashduty 独有** | +| **[重新分派](/zh/on-call/incident/escalate-dispatch-incident)** | 支持故障重新分派 | ✅ 两者均支持 | +| **自定义操作** | 添加自定义操作（如触发主机重启），执行前二次确认 | ✅ 两者均支持 | +| **故障重开** | 关闭后重新打开并通知 | ✅ **Flashduty 独有** | +| **[自定义字段](/zh/on-call/configuration/custom-fields)** | 故障业务属性自由定义（标记误报、会议链接等），**支持按字段检索** | 两者均支持；PagerDuty 需先配置 Incident Types 并逐字段启用 | +| **[自定义表单](/zh/on-call/configuration/custom-forms)** | 创建/认领/关闭故障时，按条件展示补充信息表单 | Flashduty 全流程支持；PagerDuty 仅关闭环节支持必填字段（限 Enterprise 档） | +| **检索能力** | 按标签、自定义字段、标题、人员检索 | Flashduty 支持精确、通配、正则匹配；PagerDuty 支持基础的字段过滤检索 | + +### Status Pages -### 平台能力 - -平台基础能力涵盖**成员管理**、**值班响应**和**通知能力**等核心功能。 - - - - | 值班功能 | 功能要求 | 对比 | - | --- | --- | --- | - | **轮换周期** | 按天、周或自定义周期轮换 | ✅ 两者均支持 | - | **时间限定** | 限定轮换周期内的值班时间 | ✅ 两者均支持 | - | **日期跳过** | 跳过特定日期（工作日/非工作日不同规则），支持日期掩码模式 | ✅ **Flashduty 独有** | - | **时段规则** | 不同时间段不同轮换规则 | ✅ 两者均支持，Flashduty 可设置周期结束时间 | - | **临时调班** | 设置临时调班 | ✅ 两者均支持 | - | **值班角色** | 设置主备值班等角色 | ✅ **Flashduty 独有** | - | **多人值班** | 同时多人值班并一起轮换 | ✅ **Flashduty 独有** | - | **公平轮换** | 避免固定人员在特定时间值班 | ✅ **Flashduty 独有**（解决 7 人按天轮换时某人永远周日值班的问题） | - | **轮换通知** | 设定轮换通知包括提前通知、定时通知 | ✅ 两者均支持，Flashduty 支持更多通知方式 | - | **日历导出** | 值班日历导出功能 | ✅ PagerDuty 支持 | - - - - | 通知方式 | 本地化支持 | 对比 | - | --- | --- | --- | - | **语音短信（中国大陆）** | 中国大陆语音和短信支持 | ✅ 两者均支持，但 PagerDuty 触达率低、不稳定 | - | **固定显号** | 固定显示号码，语音号码可自动同步至手机通讯录白名单 | ✅ 两者均支持 | - | **邮件通知** | 邮件通知支持 | ✅ 两者均支持 | - | **中国大陆 IM** | 国内主流 IM 应用协同 | ✅ Flashduty 支持飞书、钉钉、企业微信应用集成，**含飞书/钉钉私有化版本** | - | **国际化 IM** | 国际主流 IM 应用协同 | ✅ 两者均支持 Slack、Microsoft Teams；Flashduty 额外支持 Zoom、Telegram 机器人 | - | **移动端** | 移动端 App 支持 | ✅ 两者均支持；Flashduty iOS 基于 Apple Critical Alerts 协议**突破勿扰模式**，Android 独立适配国内主流厂商系统级推送，触达率更高 | - | **[自定义模板](/zh/on-call/configuration/templates)** | 自定义通知模板 | ✅ **Flashduty 独有**，支持丰富的模板语法 | - - - - | 安全功能 | 功能说明 | 对比 | - | --- | --- | --- | - | **单点登录** | SSO 协议支持 | Flashduty：SAML、OIDC、CAS、LDAP，支持**专属子域名登录**，另有 Authing、Keycloak、OpenLDAP 接入指南；PagerDuty：SAML、OAuth2 | - | **数据隔离** | 故障数据按团队隔离 | ✅ Flashduty 支持协作空间**私有访问级别**，私有空间故障数据仅团队成员与管理员可见 | - | **操作审计** | 完整的操作审计日志 | ✅ 两者均支持 | - | **私有化部署** | 本地化部署方案 | ✅ **Flashduty 支持**（定价与 SaaS 服务不同） | - - +对外传递服务状态是故障管理的最后一公里。Flashduty 状态页随 On-call 提供且功能更全；PagerDuty Status Pages 按套餐与订阅量分层收费。 ---- +| 维度 | Flashduty | PagerDuty | +| --- | --- | --- | +| **提供方式** | [状态页](/zh/on-call/statuspage/statuspage)随 On-call 产品提供，**公开 + 内部状态页一体** | 基础套餐仅含 1 个公开状态页；内部状态页需 Business 及以上，私有状态页在 Premium 加购包 | +| **订阅费用** | ✅ **订阅者免费、无需账号** | 公开页订阅免费但按套餐限名额（Professional 250 / Business 500 / Enterprise 1,000，超出需向销售加购）；**内部状态页与内部事件动态的围观者需持账号，最低为付费 Stakeholder 席位** | +| **订阅粒度与方式** | 全量/组件/事件**三级订阅**，邮件 + **RSS 2.0 / Atom 1.0 免确认订阅**，订阅者批量导入导出与自助管理 | Email / Slack / Webhook，未见 RSS/Atom 订阅 | +| **多语言通知** | ✅ 原生保留订阅者语言偏好 | 公开资料未见 | +| **内部状态页通知** | 飞书/钉钉/企业微信/Slack 原生推送 | 查看者需 PagerDuty 账号（Stakeholder 席位起） | +| **可用性证明** | 自动沉淀历史 Uptime，**维护事件不计入 uptime 损耗** | 支持 7/30/90 天 uptime 展示 | +| **展示定制** | 自定义域名、日历 + 列表双视图、可用性展示方式可配置、组件展示控制 | 自定义域名、Logo/配色/页头页脚 | +| **Atlassian 迁移** | **兼容订阅地址**（`history.rss` / `history.atom`）+ CLI 一键迁移组件、事件与订阅者 | — | -## AI 能力对比 + +如果您正在使用 Atlassian Statuspage，可参考 [Flashduty vs Atlassian Statuspage 深度对比](/zh/on-call/statuspage/comparison)。 + ---- +### AI SRE 两家的 AI 布局不同：**PagerDuty 将 AI 拆成多个产品**——AIOps 负责事件降噪与关联（单独加购），Advance 提供生成式问答与摘要，SRE Agent 可自主分析日志指标做诊断、修复动作依赖预先配置的自动化脚本；**Flashduty 除了内置的 AI 摘要与 AI 复盘，还提供 [AI SRE](/zh/ai-sre)：一个接入您真实环境的自治 SRE Agent，在会话中动态调用工具、执行命令，可以排查未预设过的问题**。 @@ -213,52 +169,63 @@ keywords: ["产品对比", "PagerDuty", "功能对比", "价格对比", "竞品 PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟。两者的核心差异：一是**售卖方式**——Flashduty 一体化提供，PagerDuty 分产品加购；二是**处置路径**——Flashduty 在会话中动态排查处置，PagerDuty 的自动修复依赖预先配置的固定脚本。 ---- - -## 自定义能力对比 +### 平台 ---- - -故障处置流程因团队而异，**流程里的每个环节都应该能按您的业务改形状**。 +平台是上面四个产品共用的底座：数据怎么接进来、告警在抵达团队前怎么加工、指标怎么沉淀，以及安全与开放生态。 -| 自定义项 | Flashduty | PagerDuty | -| --- | --- | --- | -| **[自定义字段](/zh/on-call/configuration/custom-fields)** | 故障/告警业务属性自由定义，**支持按字段检索**（精确、通配、正则） | 支持 Custom Fields 与按字段过滤，需先配置 Incident Types | -| **[自定义表单](/zh/on-call/configuration/custom-forms)** | 创建/认领/关闭故障时，按条件展示补充信息表单 | 仅关闭环节支持必填字段（限 Enterprise 档），未覆盖创建/认领环节 | -| **自定义 Webhook** | 自定义 Payload 格式、重试条件与自动重试、免密验证，**完整调用历史追溯**（状态码、重试次数、请求响应详情） | Payload 格式固定，重试策略固定（3 次不可配置），无自助调用历史查询 | -| **[通知模板](/zh/on-call/configuration/templates)** | 全渠道自定义模板，**含语音通知模板**，支持历史故障预览调试与智能输入提示 | 公开资料未见对应的全渠道模板定制 | -| **[动态分派](/zh/on-call/advanced/dynamic-notifications)** | reset 替换 + append 追加双模式，结合外部数据映射自动生成分派对象 | — | -| **[自定义菜单](/zh/platform/custom-menu)** | 侧边栏嵌入外部链接或 iframe 页面，按角色授权可见 | — | -| **[角色与数据权限](/zh/platform/permission-design)** | RBAC 预置 + 自定义角色，团队维度数据权限，协作空间私有级别 | RBAC 角色管理 | +#### 接入与集成 ---- +| 核心能力 | Flashduty | PagerDuty | 说明 | +| --- | --- | --- | --- | +| **告警集成** | 60+ 集成源，国内云与监控生态全覆盖（阿里云、腾讯云、华为云、京东云、金山云、UCloud 等），**兼容 PagerDuty 协议** | 750+ 集成，海外生态覆盖广 | PagerDuty 集成数量更多；Flashduty 对国内技术栈覆盖更完整，且存量 PagerDuty 集成配置可直接切换 | +| **拉取式接入** | [HTTP Pull](/zh/on-call/integration/alert-integration/alert-sources/http-pull) 周期拉取接口、[DB Pull](/zh/on-call/integration/alert-integration/alert-sources/db-pull) 直查 MySQL/PostgreSQL/ClickHouse 增量生成告警 | 以推送式集成为主 | 老系统没有 Webhook 推送能力也能接入 Flashduty | +| **工单双向同步** | [Jira](/zh/on-call/integration/webhooks/jira-sync)、[ServiceNow](/zh/on-call/integration/webhooks/servicenow-sync)、[ServiceDesk Plus](/zh/on-call/integration/webhooks/servicedesk-plus-sync) | Jira、ServiceNow 等 | 两者均支持 | +| **变更事件集成** | ✅ 支持变更事件接入、动态路由与标签二次加工 | ✅ Change Events | 两者均支持 | +| **外部故障提交** | ✅ 客户或合作伙伴**免登录**通过独立页面或 API 提交故障，自动匹配分派策略 | 仅支持邮件转 incident，无结构化表单 | 对外提供服务的团队可直接把客户报障接入处置流程 | +| **Link 集成** | ✅ 按 hostname 等标签一键跳转 CMDB 或内部系统 | — | | +| **自定义 Webhook（出站）** | 自定义 Payload 格式、重试条件与自动重试、免密验证，**完整调用历史追溯**（状态码、重试次数、请求响应详情），可按事件类型或来源订阅 | Payload 格式固定，重试策略固定（3 次不可配置），无自助调用历史查询 | | +| **Open APIs** | ✅ 290 个接口，覆盖 On-call、Monitors、RUM、AI SRE 与平台管理 | ✅ | 两者均提供丰富的 API 和详细文档 | -## 状态页对比 + +**集成按需支持承诺**：如果您常用的商业软件或开源服务尚未在集成列表中，请联系我们——只要您需要，我们承诺快速支持。 + ---- +#### 告警流水线与标签增强 -对外传递服务状态是故障管理的最后一公里。Flashduty 状态页随 On-call 提供且功能更全；PagerDuty Status Pages 按套餐与订阅量分层收费。 +告警在抵达团队之前，先经过路由、过滤与转换。 -| 维度 | Flashduty | PagerDuty | +| 功能项 | 功能说明 | 对比 | | --- | --- | --- | -| **提供方式** | [状态页](/zh/on-call/statuspage/statuspage)随 On-call 产品提供，**公开 + 内部状态页一体** | 基础套餐仅含 1 个公开状态页；内部状态页需 Business 及以上，私有状态页在 Premium 加购包 | -| **订阅费用** | ✅ **订阅者免费、无需账号** | 公开页订阅免费但按套餐限名额（Professional 250 / Business 500 / Enterprise 1,000，超出需向销售加购）；**内部状态页与内部事件动态的围观者需持账号，最低为付费 Stakeholder 席位** | -| **订阅粒度与方式** | 全量/组件/事件**三级订阅**，邮件 + **RSS 2.0 / Atom 1.0 免确认订阅**，订阅者批量导入导出与自助管理 | Email / Slack / Webhook，未见 RSS/Atom 订阅 | -| **多语言通知** | ✅ 原生保留订阅者语言偏好 | 公开资料未见 | -| **内部状态页通知** | 飞书/钉钉/企业微信/Slack 原生推送 | 查看者需 PagerDuty 账号（Stakeholder 席位起） | -| **可用性证明** | 自动沉淀历史 Uptime，**维护事件不计入 uptime 损耗** | 支持 7/30/90 天 uptime 展示 | -| **展示定制** | 自定义域名、日历 + 列表双视图、可用性展示方式可配置、组件展示控制 | 自定义域名、Logo/配色/页头页脚 | -| **Atlassian 迁移** | **兼容订阅地址**（`history.rss` / `history.atom`）+ CLI 一键迁移组件、事件与订阅者 | — | +| **告警路由** | 专属集成 + 共享集成灵活路由 | **两者均支持**。Flashduty 可在集成页面直接设置路由规则，并提供路由版本管理和回滚能力；PagerDuty 需通过复杂的 Event Orchestration 或 Workflow 实现 | +| **告警处理 Pipeline** | 等级重设、标题修改、告警过滤、CMDB 联动等处理动作编排 | 两者均支持；Flashduty 提供右侧告警历史面板辅助规则调试 | +| **正则提取** | 通过已有信息正则提取出新的标签 | ✅ 两者均支持 | +| **信息组合** | 通过已有信息组合出新的标签 | ✅ 两者均支持 | +| **数据映射** | 导入数据表，动态生成新标签（如导入 CMDB 数据），支持控制台直接管理映射数据 | ✅ **Flashduty 独有** | - -如果您正在使用 Atlassian Statuspage，可参考 [Flashduty vs Atlassian Statuspage 深度对比](/zh/on-call/statuspage/comparison)。 - +#### 洞察与报表 ---- +| 分析维度 | 功能描述 | 对比 | +| --- | --- | --- | +| **基础统计** | 按时间、团队、服务等维度统计故障和事件数量 | ✅ 两者均支持 | +| **处理指标** | 统计 MTTA、MTTR 等关键指标 | ✅ 两者均支持 | +| **人员指标** | 统计人员处理故障指标和数量，含中断次数、响应投入等工作量指标 | ✅ 两者均支持 | +| **频发分析** | 统计最频繁发生故障的主机和策略 | ✅ **Flashduty 独有** | +| **时间成本** | 统计人员处理故障耗费时间 | ✅ 两者均支持 | +| **时段分析** | 按工作、休息、睡眠时段统计指标 | ✅ **Flashduty 独有** | +| **数据导出** | 下载数据明细，支持报表打印与 CSV 导出 | ✅ 两者均支持 | -## 开发者生态 +#### 账户与安全 ---- +| 安全功能 | 功能说明 | 对比 | +| --- | --- | --- | +| **单点登录** | SSO 协议支持 | Flashduty：SAML、OIDC、CAS、LDAP，支持**专属子域名登录**，另有 Authing、Keycloak、OpenLDAP 接入指南；PagerDuty：SAML、OAuth2 | +| **[角色与数据权限](/zh/platform/permission-design)** | RBAC 预置 + 自定义角色，团队维度数据权限 | Flashduty 支持自定义角色与团队级数据权限；PagerDuty 提供 RBAC 角色管理 | +| **数据隔离** | 故障数据按团队隔离 | ✅ Flashduty 支持协作空间**私有访问级别**，私有空间故障数据仅团队成员与管理员可见 | +| **[自定义菜单](/zh/platform/custom-menu)** | 侧边栏嵌入外部链接或 iframe 页面，按角色授权可见 | ✅ **Flashduty 独有** | +| **操作审计** | 完整的操作审计日志 | ✅ 两者均支持 | +| **私有化部署** | 本地化部署方案 | ✅ **Flashduty 支持**（定价与 SaaS 服务不同） | + +#### 开发者生态 | 工具 | Flashduty | 说明 | | --- | --- | --- | From e60645e228e715be71bd6fef1152b22179d88d20 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Fri, 31 Jul 2026 03:17:11 -0700 Subject: [PATCH 2/2] docs(comparison): tighten competitive facts, add cost chart, fix dollar rendering - War room: supported on Slack too, drop the China-IM-only qualifier (Teams not yet supported) - Status Pages: full feature parity from the free tier vs plan-tiered features - AI SRE: reflect PagerDuty's four preset AI Agents (SRE/Scribe/Shift/Insights) and their extensibility model (preset connector list + prompt-style Skills, outward-facing MCP); contrast with the open-ended Agent loop (Skills/MCP/Subagents/A2A); concretize AI Actions allowances per plan - Developer ecosystem: add a PagerDuty column (CLI status, official client libraries) - SSO: compare protocols only - Escape bare dollar signs that triggered LaTeX math rendering in tables - Add an SVG cost-curve chart (zh/en) to the cost comparison example --- en/on-call/quickstart/comparison.mdx | 34 +++++++++--------- images/oncall/comparison-cost-en.svg | 52 ++++++++++++++++++++++++++++ images/oncall/comparison-cost-zh.svg | 52 ++++++++++++++++++++++++++++ zh/on-call/quickstart/comparison.mdx | 34 +++++++++--------- 4 files changed, 140 insertions(+), 32 deletions(-) create mode 100644 images/oncall/comparison-cost-en.svg create mode 100644 images/oncall/comparison-cost-zh.svg diff --git a/en/on-call/quickstart/comparison.mdx b/en/on-call/quickstart/comparison.mdx index 328879b1..ffde14ed 100644 --- a/en/on-call/quickstart/comparison.mdx +++ b/en/on-call/quickstart/comparison.mdx @@ -118,7 +118,7 @@ Response solves "closing the loop quickly once the right person is found": a sin | --- | --- | --- | | **Basic Operations** | Manually create, acknowledge, close, comment on, snooze, merge, and bulk-assign incidents | ✅ Both support | | **Closure Automation** | Auto-close on timeout (countdown can be based on the last event time), auto-cancel snooze on timeout | ✅ Both support | -| **[War Room](/en/on-call/advanced/war-room)** | One-click creation of a Feishu/Lark, Dingtalk, WeCom, or Slack group chat, automatically inviting responders, with a pinned incident card that updates in real time, and acknowledge/escalate/close actions in the chat syncing back to Flashduty | ✅ **Flashduty exclusive** (for China-region IM scenarios) | +| **[War Room](/en/on-call/advanced/war-room)** | One-click creation of a Feishu/Lark, Dingtalk, WeCom, or Slack group chat (Teams not yet supported), automatically inviting responders, with a pinned incident card that updates in real time, and acknowledge/escalate/close actions in the chat syncing back to Flashduty | ✅ **Flashduty exclusive** | | **[Postmortems](/en/on-call/post-mortem/what-is-post-mortem)** | Full postmortem reports: timeline capture, collaborative editing, permission controls, with support for **[AI-generated postmortems](/en/on-call/post-mortem/ai-generate-post-mortem)** | Both support; Flashduty can generate a structured postmortem in one click from the incident timeline and alert data | | **Similar Incidents** | Identify and associate similar incidents | ✅ Both support | | **[Outlier Incidents](/en/on-call/incident/outlier-incidents)** | Automatic alerts for outlier incidents | ✅ **Flashduty exclusive** | @@ -135,7 +135,7 @@ Communicating service status to the outside world is the last mile of incident m | Dimension | Flashduty | PagerDuty | | --- | --- | --- | -| **Availability** | [Status Page](/en/on-call/statuspage/statuspage) is included with the On-call product, **public + internal status pages in one** | The base plan includes only 1 public status page; internal status pages require Business or above, and private status pages are a Premium add-on | +| **Availability** | [Status Page](/en/on-call/statuspage/statuspage) ships with the On-call product—public status pages are included starting from the free tier with **full feature parity across every tier**, and public + internal status pages are unified in one (internal status pages included from Professional up) | Each plan includes 1 public status page, **with features tiered by plan**; internal status pages require Business or above, and private status pages are a Premium add-on | | **Subscription Cost** | ✅ **Free for subscribers, no account required** | Public-page subscriptions are free but capped by plan (Professional 250 / Business 500 / Enterprise 1,000; exceeding the cap requires a sales add-on); **viewers of internal status pages and internal incident activity must hold an account, at minimum a paid Stakeholder license** | | **Subscription Granularity & Methods** | **Three-tier subscriptions** (all / component / event level), email + **confirmation-free RSS 2.0 / Atom 1.0 subscriptions**, with bulk import/export and self-service subscriber management | Email / Slack / Webhook; no RSS/Atom subscription found | | **Multilingual Notifications** | ✅ Natively preserves each subscriber's language preference | Not found in public materials | @@ -150,23 +150,23 @@ If you're currently using Atlassian Statuspage, see our in-depth [Flashduty vs A ### AI SRE -The two vendors take different approaches to AI: **PagerDuty splits AI across multiple products**—AIOps handles incident noise reduction and correlation (a separate add-on), Advance provides generative Q&A and summaries, and SRE Agent can autonomously analyze logs and metrics for diagnosis, though its remediation actions depend on pre-configured automation scripts. **Flashduty, beyond its built-in AI summaries and AI postmortems, also provides [AI SRE](/en/ai-sre): an autonomous SRE Agent connected to your real environment that dynamically calls tools and executes commands within a session—able to investigate problems it has never seen before**. +The two vendors take different approaches to AI: **PagerDuty splits AI across multiple products and preset agents**—AIOps handles incident noise reduction and correlation (a separate add-on), Advance provides generative Q&A and summaries, and there are four purpose-built preset AI Agents (SRE for incident diagnosis, Scribe for meeting notes, Shift for schedule swaps, and Insights for data Q&A). **Flashduty, beyond its built-in AI summaries and AI postmortems, also provides [AI SRE](/en/ai-sre): a fully capable autonomous Agent loop connected to your real environment that dynamically calls tools and executes commands, extensible without limit through Skills, MCP, Subagents, and A2A—able to investigate problems it has never seen before**. | Dimension | Flashduty AI SRE | PagerDuty (AIOps / Advance / AI Agents) | | --- | --- | --- | -| **Product Form** | Autonomous SRE Agent: conversational troubleshooting + autonomous planning and execution + knowledge accumulation | AIOps for incident noise reduction/correlation; Advance as a generative AI assistant (summaries, Q&A, postmortem drafts); SRE Agent for autonomous diagnosis | +| **Product Form** | Autonomous SRE Agent: conversational troubleshooting + autonomous planning and execution + knowledge accumulation | AIOps for incident noise reduction/correlation; Advance as a generative AI assistant (summaries, Q&A, postmortem drafts); four preset AI Agents each own a slice: SRE (diagnosis + pre-configured remediation), Scribe (meeting notes), Shift (scheduling), Insights (data Q&A) | | **Troubleshooting & Remediation** | Cloud sandbox + self-hosted [Runner (BYOC)](/en/ai-sre/environments), dynamically executing diagnostic commands and querying monitoring data and logs within your environment—**able to investigate problems it has never seen before** | SRE Agent can automatically analyze logs/metrics and match them against historical incidents; remediation actions depend on **pre-configured** Automation Actions scripts | | **Native IM Collaboration** | [Group-chat @-mentions and private-chat troubleshooting](/en/ai-sre/im) across Feishu/Lark, Dingtalk, WeCom, and Slack, with **automatic initial diagnosis triggered once a war room is created** | Primarily Slack and Teams, no China-region IM support | | **Code Repositories & K8s** | [GitHub/GitLab App](/en/ai-sre/apps) accesses code repositories from within the sandbox and can submit PRs/MRs/Issues; a Kubernetes App connects to clusters at the namespace level | Not found in public materials | | **AI Automation Tasks** | [Automations](/en/ai-sre/automations) trigger on a cron schedule, via HTTP API, or on incident events, with built-in templates for alert noise analysis, incident postmortems, on-call insights, and more | Relies on the separate Event Orchestration and Runbook Automation product lines | -| **Extensibility** | [Skills marketplace](/en/ai-sre/skills), [MCP external tools](/en/ai-sre/mcp), [Subagent and A2A delegation](/en/ai-sre/agents) | No equivalent extension system found in public materials | +| **Extensibility** | [Skills marketplace](/en/ai-sre/skills), [MCP external tools](/en/ai-sre/mcp), [Subagent and A2A delegation](/en/ai-sre/agents), **with no ceiling on the extension surface** | SRE Agent is limited to toggling official preset connectors (about 23, e.g. Datadog, Splunk, CloudWatch) and appending prompt-style Skills; it doesn't support mounting arbitrary MCP tools to its own agents, has no subagent spawning, and cross-vendor agent collaboration is still in early access | | **Knowledge & Memory** | [Knowledge base](/en/ai-sre/knowledge) (DUTY.md + file references), [automatic memory extraction](/en/ai-sre/memory); `/init` can import existing knowledge from tools like Claude Code and Cursor | Not found in public materials | | **AI Postmortems** | One-click postmortem generation + scheduled automated postmortems | Postmortems (formerly Jeli, being merged into the core product) are available from Professional up, capped at 300 per year on the Professional/Business tiers | | **Usage Insight** | [/insight](/en/ai-sre/insight) reviews the last 30 days of AI usage, quantifying friction points and providing improvement recommendations | Not found in public materials | -| **Billing** | **Free during the public beta**; usage-based credits billing after general availability—see the [pricing page](https://www.flashduty.com/pricing) for details | AIOps sold as a separate add-on (starting at $699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with additional AI credits required beyond that | +| **Billing** | **Free during the public beta**; usage-based credits billing after general availability—see the [pricing page](https://www.flashduty.com/pricing) for details | AIOps sold as a separate add-on (starting at \$699+/month, billed by event volume); each plan includes a one-time AI Actions allowance (Professional 1,000 / Business 5,000 / Enterprise 20,000), with SRE Agent queries and Scribe meetings metered per use—additional usage requires an add-on | -PagerDuty's AIOps has been refined over many years for large-scale event correlation and is a mature capability. The core differences between the two: first, **how it's sold**—Flashduty bundles it in, while PagerDuty sells it as separate product add-ons; second, **the remediation path**—Flashduty investigates and resolves dynamically within a session, while PagerDuty's automated remediation depends on pre-configured, fixed scripts. +PagerDuty's AIOps has been refined over many years for large-scale event correlation and is a mature capability; its MCP Server is built for third-party AI tools to query PagerDuty data, not to extend its own Agents' capabilities. The core differences between the two: first, **how it's sold**—Flashduty bundles it in, while PagerDuty sells it as separate product add-ons; second, **the remediation path**—Flashduty is a fully open-ended Agent loop that investigates and resolves dynamically within a session, while PagerDuty runs four preset Agents each covering a fixed scenario, with automated remediation depending on pre-configured scripts. ### Platform @@ -218,7 +218,7 @@ Before reaching the team, alerts pass through routing, filtering, and transforma | Feature | Description | Comparison | | --- | --- | --- | -| **Single Sign-On** | SSO protocol support | Flashduty: SAML, OIDC, CAS, LDAP, with support for **dedicated subdomain login**, plus setup guides for Authing, Keycloak, and OpenLDAP; PagerDuty: SAML, OAuth2 | +| **Single Sign-On** | SSO protocol support | Flashduty: SAML, OIDC, CAS, LDAP; PagerDuty: SAML, OAuth2 | | **[Roles & Data Permissions](/en/platform/permission-design)** | Preset RBAC + custom roles, team-level data permissions | Flashduty supports custom roles and team-level data permissions; PagerDuty provides RBAC role management | | **Data Isolation** | Incident data isolated by team | ✅ Flashduty supports a **private access level** for collaboration spaces — incident data in a private space is visible only to team members and admins | | **[Custom Menu](/en/platform/custom-menu)** | Embed external links or iframe pages in the sidebar, visible based on role authorization | ✅ **Flashduty exclusive** | @@ -227,13 +227,13 @@ Before reaching the team, alerts pass through routing, filtering, and transforma #### Developer Ecosystem -| Tool | Flashduty | Notes | +| Tool | Flashduty | PagerDuty | | --- | --- | --- | -| **[Open API](/en/openapi/api-catalog)** | 290 endpoints: On-call 176, Monitors 36, RUM 18, AI SRE 33, Platform 27 | Both provide rich APIs; Flashduty opens its full endpoint set with bilingual documentation | -| **[CLI](/en/developer/cli)** | 288 API operation commands + 10 built-in Agent Skills, ready to hand directly to AI coding tools like Claude Code, Cursor, and Codex | Lets AI coding tools operate the incident management platform directly | -| **[Go SDK](/en/developer/go-sdk)** | go-github-style wrapper covering 288 API operations across 32 services | | -| **[Terraform Provider](/en/developer/terraform)** | 12 resource types + 13 data source types, managing collaboration spaces, escalation policies, schedules, and more as IaC | Both support Terraform | -| **[MCP Server](/en/developer/mcp-server)** | 8 tool sets with 23 tools, deployable remotely, via Docker, or from source | Both provide an official MCP Server | +| **[Open API](/en/openapi/api-catalog)** | 290 endpoints covering On-call, Monitors, RUM, AI SRE, and platform management, with bilingual docs | ✅ Full-featured REST API, mature documentation | +| **[CLI](/en/developer/cli)** | 288 API operation commands + built-in Agent Skills, ready to hand directly to AI coding tools like Claude Code, Cursor, and Codex | No official CLI actively promoted: the community's most-used `pagerduty-cli` is an employee's personal project (officially not endorsed, and the author has announced it's archived); the official go-pagerduty library ships a limited `pd` command-line tool | +| **SDK** | [Go SDK](/en/developer/go-sdk): a go-github-style wrapper covering 288 API operations across 32 services | PagerDuty officially maintains go-pagerduty, python-pagerduty, and other client libraries | +| **[Terraform Provider](/en/developer/terraform)** | 12 resource types + 13 data source types, managing collaboration spaces, escalation policies, schedules, and more as IaC | ✅ Official Terraform Provider, mature ecosystem | +| **[MCP Server](/en/developer/mcp-server)** | 8 tool sets with 23 tools, deployable remotely, via Docker, or from source | ✅ Official MCP Server | --- @@ -247,7 +247,7 @@ Pricing is a critical factor in enterprise decisions—you need to choose the mo | --- | --- | --- | | **Pricing Page** | [flashduty.com/pricing](https://www.flashduty.com/pricing) | [pagerduty.com/pricing](https://www.pagerduty.com/pricing/incident-response/) | | **Billing Model** | License fee + excess communication fees | Seat fee + Add-Ons | -| **Edition Pricing** | **Professional ¥199/user/month**, including intelligent grouping, AI summaries, and AI postmortems; AI SRE is free during the public beta and billed on usage-based credits after general availability | Business $41/user/month (annual billing); AIOps requires a separate add-on (starting at $699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with extra usage billed separately | +| **Edition Pricing** | **Professional ¥199/user/month**, including intelligent grouping, AI summaries, and AI postmortems; AI SRE is free during the public beta and billed on usage-based credits after general availability | Business \$41/user/month (annual billing); AIOps requires a separate add-on (starting at \$699+/month, billed by event volume); Advance tiers each include a one-time AI Action allowance, with extra usage billed separately | | **Billing Target** | ✅ **Only active users are charged**—only members who view and handle incidents need a License | ❌ **All users must pay**—including members who only receive notifications | | **Notification Capability** | ✅ Members without a License can still receive all notifications (email, SMS, voice call, IM) | ❌ A paid seat is required to receive notifications; even just viewing internal incident activity requires at least a paid Stakeholder license | | **Status Page Subscriptions** | ✅ Free, no account required, doesn't consume a License | Public-page subscriptions are capped by plan (250/500/1,000), with an add-on required beyond that; viewing internal status pages requires a Stakeholder license | @@ -276,12 +276,14 @@ This is the most fundamental pricing difference between Flashduty and PagerDuty. ### Cost Comparison Example +Estimated monthly cost: every seat vs active users only + Take a 100-person engineering team where 15 people are routinely involved in incident handling as an example: | Cost Item | Flashduty Professional | PagerDuty Business | | --- | --- | --- | | Seats/Licenses required | **15** Licenses | **100** seats | -| Monthly cost | 15 × ¥199 = **¥2,985/month** | 100 × $41 ≈ **¥29,500/month** | +| Monthly cost | 15 × ¥199 = **¥2,985/month** | 100 × \$41 ≈ **¥29,500/month** | | Notification coverage | **100 people** (everyone can receive notifications) | **100 people** (but everyone must pay) | | Annual total cost | **~¥35,820** | **~¥354,000** | | **Savings** | — | **~90% savings** | diff --git a/images/oncall/comparison-cost-en.svg b/images/oncall/comparison-cost-en.svg new file mode 100644 index 00000000..b56cdb75 --- /dev/null +++ b/images/oncall/comparison-cost-en.svg @@ -0,0 +1,52 @@ + + Estimated monthly cost: every seat vs active users only + Assuming 15% of members handle incidents · Flashduty Professional ¥199/user/mo · PagerDuty Business $41/user/mo (annual) + + + + + + + + + + + ¥1,000 + + 0 + 30 + 60 + 90 + 120 + 150 + + + 0 + 100 + 200 + 300 + 400 + 500 + + Team size (people) + + + + + + + + + ¥29,500 + ¥2,985 + + + + PagerDuty Business + ≈¥147.5K/mo · seats for all 500 + Flashduty Professional + ≈¥14.9K/mo · only 75 licenses + + Same 100% notification coverage, + ≈10× difference in monthly cost + diff --git a/images/oncall/comparison-cost-zh.svg b/images/oncall/comparison-cost-zh.svg new file mode 100644 index 00000000..bbbd7299 --- /dev/null +++ b/images/oncall/comparison-cost-zh.svg @@ -0,0 +1,52 @@ + + 月费用估算：全员席位 vs 仅活跃用户付费 + 假设 15% 成员参与故障处理 · Flashduty 专业版 ¥199/人/月 · PagerDuty Business $41/人/月（年付） + + + + + + + + + + + 万元 + + 0 + 3 + 6 + 9 + 12 + 15 + + + 0 + 100 + 200 + 300 + 400 + 500 + + 团队规模（人） + + + + + + + + + ¥2.95 万 + ¥0.30 万 + + + + PagerDuty Business + ¥14.75 万/月 · 全员 500 席位 + Flashduty 专业版 + ¥1.49 万/月 · 仅 75 人需 License + + 同样实现全员通知覆盖 + 月费用相差约 10 倍 + diff --git a/zh/on-call/quickstart/comparison.mdx b/zh/on-call/quickstart/comparison.mdx index 20219fe9..c4ce3311 100644 --- a/zh/on-call/quickstart/comparison.mdx +++ b/zh/on-call/quickstart/comparison.mdx @@ -118,7 +118,7 @@ Response 解决「找到人之后怎么快速闭环」：一条时间线、一 | --- | --- | --- | | **基础操作** | 手动创建、认领、关闭、评论、暂缓、合并、批量分派故障 | ✅ 两者均支持 | | **收尾自动化** | 超时自动关闭（支持按最后事件时间倒计时）、暂缓超时自动取消 | ✅ 两者均支持 | -| **[作战室](/zh/on-call/advanced/war-room)** | 一键创建飞书、钉钉、企微或 Slack 群聊，自动邀请处理人，故障卡片置顶实时更新，群内确认/升级/关闭状态同步回 Flashduty | ✅ **Flashduty 独有**（国内 IM 场景） | +| **[作战室](/zh/on-call/advanced/war-room)** | 一键创建飞书、钉钉、企业微信或 Slack 群聊（Teams 暂不支持），自动邀请处理人，故障卡片置顶实时更新，群内确认/升级/关闭状态同步回 Flashduty | ✅ **Flashduty 独有** | | **[故障复盘](/zh/on-call/post-mortem/what-is-post-mortem)** | 完整的复盘报告：时间线沉淀、协同编辑、权限管控，支持 **[AI 自动生成复盘](/zh/on-call/post-mortem/ai-generate-post-mortem)** | 两者均支持；Flashduty 可基于故障时间线和告警数据一键生成结构化复盘 | | **相似故障** | 识别和关联相似故障 | ✅ 两者均支持 | | **[新奇故障](/zh/on-call/incident/outlier-incidents)** | 新奇故障自动提醒 | ✅ **Flashduty 独有** | @@ -135,7 +135,7 @@ Response 解决「找到人之后怎么快速闭环」：一条时间线、一 | 维度 | Flashduty | PagerDuty | | --- | --- | --- | -| **提供方式** | [状态页](/zh/on-call/statuspage/statuspage)随 On-call 产品提供，**公开 + 内部状态页一体** | 基础套餐仅含 1 个公开状态页；内部状态页需 Business 及以上，私有状态页在 Premium 加购包 | +| **提供方式** | [状态页](/zh/on-call/statuspage/statuspage)随 On-call 产品提供，免费版起即含公开状态页且**功能全量不分档**，公开 + 内部状态页一体（内部状态页随专业版提供） | 各套餐含 1 个公开状态页，**功能按套餐分层**；内部状态页需 Business 及以上，私有状态页在 Premium 加购包 | | **订阅费用** | ✅ **订阅者免费、无需账号** | 公开页订阅免费但按套餐限名额（Professional 250 / Business 500 / Enterprise 1,000，超出需向销售加购）；**内部状态页与内部事件动态的围观者需持账号，最低为付费 Stakeholder 席位** | | **订阅粒度与方式** | 全量/组件/事件**三级订阅**，邮件 + **RSS 2.0 / Atom 1.0 免确认订阅**，订阅者批量导入导出与自助管理 | Email / Slack / Webhook，未见 RSS/Atom 订阅 | | **多语言通知** | ✅ 原生保留订阅者语言偏好 | 公开资料未见 | @@ -150,23 +150,23 @@ Response 解决「找到人之后怎么快速闭环」：一条时间线、一 ### AI SRE -两家的 AI 布局不同：**PagerDuty 将 AI 拆成多个产品**——AIOps 负责事件降噪与关联（单独加购），Advance 提供生成式问答与摘要，SRE Agent 可自主分析日志指标做诊断、修复动作依赖预先配置的自动化脚本；**Flashduty 除了内置的 AI 摘要与 AI 复盘，还提供 [AI SRE](/zh/ai-sre)：一个接入您真实环境的自治 SRE Agent，在会话中动态调用工具、执行命令，可以排查未预设过的问题**。 +两家的 AI 路线不同：**PagerDuty 将 AI 拆成多个产品与预置 Agent**——AIOps 负责事件降噪与关联（单独加购），Advance 提供生成式问答与摘要，另有四个各司其职的预置 AI Agent（SRE 事故诊断、Scribe 会议记录、Shift 排班替换、Insights 数据问答）；**Flashduty 除了内置的 AI 摘要与 AI 复盘，还提供 [AI SRE](/zh/ai-sre)：一个能力完整的自治 Agent loop，接入您的真实环境动态调用工具、执行命令，可通过 Skills、MCP、Subagent 与 A2A 无上限扩展，能排查未预设过的问题**。 | 维度 | Flashduty AI SRE | PagerDuty（AIOps / Advance / AI Agents） | | --- | --- | --- | -| **产品形态** | 自治 SRE Agent：对话式排障 + 自主规划执行 + 知识沉淀 | AIOps 事件降噪/关联；Advance 生成式 AI 助手（摘要、问答、复盘草稿）；SRE Agent 自主诊断 | +| **产品形态** | 自治 SRE Agent：对话式排障 + 自主规划执行 + 知识沉淀 | AIOps 事件降噪/关联；Advance 生成式 AI 助手（摘要、问答、复盘草稿）；四个预置 AI Agent 各管一段：SRE（诊断+预配置修复）、Scribe（会议记录）、Shift（排班）、Insights（数据问答） | | **排障与修复方式** | 云端沙箱 + 自托管 [Runner（BYOC）](/zh/ai-sre/environments)，在您的环境中动态执行诊断命令、查询监控与日志，**可排查未预设过的问题** | SRE Agent 可自动分析日志/指标并匹配历史事件；修复动作依赖**预先配置**的 Automation Actions 脚本 | | **IM 原生协同** | 飞书/钉钉/企业微信/Slack [群聊 @ 召唤、私聊排障](/zh/ai-sre/im)，**作战室创建后自动发起初步诊断** | Slack、Teams 为主，无国内 IM | | **代码仓库与 K8s** | [GitHub/GitLab App](/zh/ai-sre/apps) 沙箱内访问代码仓库、提交 PR/MR/Issue；Kubernetes App 按 namespace 接入集群 | 公开资料未见 | | **AI 自动化任务** | [自动化](/zh/ai-sre/automations)按 cron、HTTP API 或故障事件触发，内置告警噪音分析、事故复盘、值班洞察等模板 | 依赖 Event Orchestration 与 Runbook Automation 独立产品线 | -| **可扩展性** | [Skills 市场](/zh/ai-sre/skills)、[MCP 外部工具](/zh/ai-sre/mcp)、[Subagent 与 A2A 委派](/zh/ai-sre/agents) | 公开资料未见对应扩展体系 | +| **可扩展性** | [Skills 市场](/zh/ai-sre/skills)、[MCP 外部工具](/zh/ai-sre/mcp)、[Subagent 与 A2A 委派](/zh/ai-sre/agents)，**扩展面不设上限** | SRE Agent 限于启停官方预置连接器（Datadog、Splunk、CloudWatch 等约 23 个）与追加提示词式 Skill；不支持为自家 Agent 挂载任意 MCP 工具，无子 Agent 派生，跨厂商 Agent 协作尚在 early access | | **知识与记忆** | [知识库](/zh/ai-sre/knowledge)（DUTY.md + 文件引用）、[自动记忆提炼](/zh/ai-sre/memory)，`/init` 可导入 Claude Code、Cursor 等工具的已有知识 | 公开资料未见 | | **AI 复盘** | 故障复盘一键生成 + 自动化定时复盘 | 复盘（原 Jeli，正并入主产品）随 Professional 及以上提供，Professional/Business 档限每年 300 次 | | **使用洞察** | [/insight](/zh/ai-sre/insight) 复盘近 30 天 AI 使用情况，量化摩擦并给出改进建议 | 公开资料未见 | -| **计费方式** | **公测期间免费**，正式商用后按 credits 用量计费，详见[官网价格页](https://www.flashduty.com/zh/pricing) | AIOps 单独加购（$699+/月起，按事件量计费）；Advance 各档位含一次性 AI Action 额度，超额需购买 AI credits | +| **计费方式** | **公测期间免费**，正式商用后按 credits 用量计费，详见[官网价格页](https://www.flashduty.com/zh/pricing) | AIOps 单独加购（\$699+/月起，按事件量计费）；各套餐含一次性 AI Actions 额度（Professional 1,000 / Business 5,000 / Enterprise 20,000 次），SRE Agent 查询、Scribe 会议按次扣点，超额需加购 | -PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟。两者的核心差异：一是**售卖方式**——Flashduty 一体化提供，PagerDuty 分产品加购；二是**处置路径**——Flashduty 在会话中动态排查处置，PagerDuty 的自动修复依赖预先配置的固定脚本。 +PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟；其 MCP Server 的方向是让第三方 AI 工具调用 PagerDuty 数据，而非为自家 Agent 扩展能力。两者的核心差异：一是**售卖方式**——Flashduty 一体化提供，PagerDuty 分产品加购；二是**处置路径**——Flashduty 是一个能力开放的完整 Agent loop，在会话中动态排查处置；PagerDuty 是四个预置 Agent 各管固定场景，自动修复依赖预先配置的脚本。 ### 平台 @@ -218,7 +218,7 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟 | 安全功能 | 功能说明 | 对比 | | --- | --- | --- | -| **单点登录** | SSO 协议支持 | Flashduty：SAML、OIDC、CAS、LDAP，支持**专属子域名登录**，另有 Authing、Keycloak、OpenLDAP 接入指南；PagerDuty：SAML、OAuth2 | +| **单点登录** | SSO 协议支持 | Flashduty：SAML、OIDC、CAS、LDAP；PagerDuty：SAML、OAuth2 | | **[角色与数据权限](/zh/platform/permission-design)** | RBAC 预置 + 自定义角色，团队维度数据权限 | Flashduty 支持自定义角色与团队级数据权限；PagerDuty 提供 RBAC 角色管理 | | **数据隔离** | 故障数据按团队隔离 | ✅ Flashduty 支持协作空间**私有访问级别**，私有空间故障数据仅团队成员与管理员可见 | | **[自定义菜单](/zh/platform/custom-menu)** | 侧边栏嵌入外部链接或 iframe 页面，按角色授权可见 | ✅ **Flashduty 独有** | @@ -227,13 +227,13 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟 #### 开发者生态 -| 工具 | Flashduty | 说明 | +| 工具 | Flashduty | PagerDuty | | --- | --- | --- | -| **[Open API](/zh/openapi/api-catalog)** | 290 个接口：On-call 176、Monitors 36、RUM 18、AI SRE 33、平台 27 | 两者均提供丰富 API；Flashduty 全量接口开放且有双语文档 | -| **[CLI](/zh/developer/cli)** | 288 个 API 操作命令 + 内置 10 个 Agent Skills，可直接配给 Claude Code、Cursor、Codex 等 AI 编程工具 | 让 AI 编程工具直接操作故障管理平台 | -| **[Go SDK](/zh/developer/go-sdk)** | go-github 风格封装，覆盖 288 个 API 操作、32 个服务 | | -| **[Terraform Provider](/zh/developer/terraform)** | 12 类资源 + 13 类数据源，IaC 管理协作空间、分派策略、值班表等 | 两者均支持 Terraform | -| **[MCP Server](/zh/developer/mcp-server)** | 8 个工具集 23 个工具，支持远程、Docker、源码三种部署 | 两者均提供官方 MCP Server | +| **[Open API](/zh/openapi/api-catalog)** | 290 个接口，覆盖 On-call、Monitors、RUM、AI SRE 与平台管理，双语文档 | ✅ REST API 完善，文档成熟 | +| **[CLI](/zh/developer/cli)** | 288 个 API 操作命令 + 内置 Agent Skills，可直接配给 Claude Code、Cursor、Codex 等 AI 编程工具 | 无官方力推的完整 CLI：社区最常用的 `pagerduty-cli` 为员工个人项目（官方声明不背书、作者已宣布归档），官方 go-pagerduty 库附带功能有限的 `pd` 命令行小工具 | +| **SDK** | [Go SDK](/zh/developer/go-sdk)：go-github 风格封装，覆盖 288 个 API 操作、32 个服务 | 官方维护 go-pagerduty、python-pagerduty 等客户端库 | +| **[Terraform Provider](/zh/developer/terraform)** | 12 类资源 + 13 类数据源，IaC 管理协作空间、分派策略、值班表等 | ✅ 官方 Terraform Provider，生态成熟 | +| **[MCP Server](/zh/developer/mcp-server)** | 8 个工具集 23 个工具，支持远程、Docker、源码三种部署 | ✅ 官方 MCP Server | --- @@ -247,7 +247,7 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟 | --- | --- | --- | | **价格页面** | [flashduty.com/zh/pricing](https://www.flashduty.com/zh/pricing) | [pagerduty.com/pricing](https://www.pagerduty.com/pricing/incident-response/) | | **收费模式** | License 费 + 超额通信费用 | 席位费 + Add-Ons | -| **版本定价** | **专业版 ¥199/人/月**，含智能聚合、AI 摘要、AI 复盘；AI SRE 公测期免费，正式商用后按 credits 用量计费 | Business 版 $41/人/月（年付）；AIOps 需单独加购（$699+/月起，按事件量计费），Advance 各档含一次性 AI Action 额度、超额另付 | +| **版本定价** | **专业版 ¥199/人/月**，含智能聚合、AI 摘要、AI 复盘；AI SRE 公测期免费，正式商用后按 credits 用量计费 | Business 版 \$41/人/月（年付）；AIOps 需单独加购（\$699+/月起，按事件量计费），Advance 各档含一次性 AI Action 额度、超额另付 | | **计费对象** | ✅ **仅对活跃用户收费**——只有查看和处理故障的成员需要 License | ❌ **所有用户都需付费**——包括仅接收通知的成员 | | **通知能力** | ✅ 无 License 成员也可接收所有通知（邮件、短信、电话、IM） | ❌ 接收通知需购买席位；仅围观内部事件动态也需最低 Stakeholder 付费席位 | | **状态页订阅** | ✅ 免费、无需账号、不占 License | 公开页订阅按套餐限名额（250/500/1,000）、超出加购；内部状态页围观需 Stakeholder 席位 | @@ -276,12 +276,14 @@ PagerDuty AIOps 在超大规模事件关联场景上打磨多年，能力成熟 ### 成本对比示例 +月费用估算：全员席位 vs 仅活跃用户付费 + 以 100 人技术团队、其中 15 人日常参与故障处理为例： | 费用项 | Flashduty 专业版 | PagerDuty Business | | --- | --- | --- | | 需购买席位/License 数 | **15 个** License | **100 个**席位 | -| 月费用 | 15 × ¥199 = **¥2,985/月** | 100 × $41 ≈ **¥29,500/月** | +| 月费用 | 15 × ¥199 = **¥2,985/月** | 100 × \$41 ≈ **¥29,500/月** | | 通知覆盖人数 | **100 人**（全员可接收通知） | **100 人**（但全员需付费） | | 年度总成本 | **约 ¥35,820** | **约 ¥354,000** | | **节省比例** | — | **节省约 90%** |