# Flashduty

Flashduty is an incident management platform for alert noise reduction, on-call scheduling, incident response, status pages, and AI SRE workflows.

## English Pages
- Homepage: https://www.flashduty.com/en
- Pricing: https://www.flashduty.com/en/pricing
- On-call: https://www.flashduty.com/en/products/on-call
- Incident response: https://www.flashduty.com/en/products/response
- AI SRE: https://www.flashduty.com/en/products/ai-sre
- Status pages: https://www.flashduty.com/en/products/status-page
- Real user monitoring (RUM): https://www.flashduty.com/en/products/rum
- Monitors alert engine: https://www.flashduty.com/en/products/monitors
- Blog: https://www.flashduty.com/en/now/blog
- Changelog: https://www.flashduty.com/en/now/changelog
- Customer stories: https://www.flashduty.com/en/now/customer-cases
- About: https://www.flashduty.com/en/about
- PagerDuty alternative: https://www.flashduty.com/en/alternatives/pagerduty
- Opsgenie alternative: https://www.flashduty.com/en/alternatives/opsgenie
- Grafana OnCall alternative: https://www.flashduty.com/en/alternatives/grafana-oncall

## Chinese Pages
- Homepage: https://www.flashduty.com/zh
- Pricing: https://www.flashduty.com/zh/pricing
- On-call: https://www.flashduty.com/zh/products/on-call
- Incident response: https://www.flashduty.com/zh/products/response
- AI SRE: https://www.flashduty.com/zh/products/ai-sre
- Status pages: https://www.flashduty.com/zh/products/status-page
- Real user monitoring (RUM): https://www.flashduty.com/zh/products/rum
- Monitors alert engine: https://www.flashduty.com/zh/products/monitors
- Blog: https://www.flashduty.com/zh/now/blog
- Changelog: https://www.flashduty.com/zh/now/changelog
- Customer stories: https://www.flashduty.com/zh/now/customer-cases
- About: https://www.flashduty.com/zh/about
- PagerDuty 替代方案: https://www.flashduty.com/zh/alternatives/pagerduty
- Opsgenie 替代方案: https://www.flashduty.com/zh/alternatives/opsgenie
- Grafana OnCall 替代方案: https://www.flashduty.com/zh/alternatives/grafana-oncall

## Languages
- English: https://www.flashduty.com/en
- Chinese: https://www.flashduty.com/zh

## Notes For AI Readers
- Prefer canonical localized URLs with /en or /zh prefixes.
- Product pages describe current positioning and capabilities.
- Blog and customer story pages provide deeper technical and adoption context.
- Alternatives pages compare Flashduty to named competitors for buying decisions.

## External Documentation
- Product documentation: https://docs.flashduty.com/en/home
- Developer documentation: https://docs.flashduty.com/en/openapi/introduction
- 中文产品文档: https://docs.flashduty.com/zh/home
- 中文开发者文档: https://docs.flashduty.com/zh/openapi/introduction

## EN Blog Posts
- AI SRE and your agents can now delegate tasks to each other (2026-08-17): https://www.flashduty.com/en/now/blog/a2a-in-production — Register an external agent in the console and AI SRE can delegate whole tasks to it, with progress streaming back into the conversation. It works the other way too: AI SRE exposes a standard A2A endpoint and accepts tasks from other agents.
- Safe cluster access for AI SRE: No kubeconfig, no open ports (2026-08-17): https://www.flashduty.com/en/now/blog/ai-agent-kubernetes-access — To bring a cluster into AI SRE we wanted four things at once: full kubectl, no inbound ports, no credentials leaving the cluster, and tight permissions without a hand-written tool list. What we shipped runs real kubectl, has your cluster dial out to us, and leaves every permission decision to Kubernetes.
- AI SRE Artifacts: A permanent, shareable link per report (2026-08-17): https://www.flashduty.com/en/now/blog/ai-sre-artifacts — Reports, design documents, and pages from your AI SRE sessions can now be published as artifacts. An artifact does two things: it stays, with its own address in the team gallery, and it goes out, over a public link that needs no sign-in.
- Working at 3 a.m.: Five ways to use AI SRE Automations (2026-08-17): https://www.flashduty.com/en/now/blog/ai-sre-automations — Five ways to use Flashduty AI SRE Automations: weekly insights, alert governance, incident analysis, deploy checks, and change risk checks. Each comes with the exact task prompt and shows how results reach people.
- GitHub and GitLab Apps for AI SRE: Commits, CI logs, and PRs (2026-08-17): https://www.flashduty.com/en/now/blog/ai-sre-github-gitlab-access — AI SRE can now connect to your GitHub organization or GitLab instance: it reads recent commits during an investigation, reads the failing CI logs on its own, and opens PRs for small fixes. You never paste a token.
- Alerts in a group chat don't mean anyone owns the incident (2026-06-24): https://www.flashduty.com/en/now/blog/alert-in-group-not-ownership — A group chat bot makes alerts visible, but it doesn't assign an owner. Incident response needs an owner, acknowledgment, escalation, closure, a timeline, and a review. Here's a quick self-check: audit your last 10 critical alerts.
- How to turn an alert storm into a few incidents in 14 days (2026-05-20): https://www.flashduty.com/en/now/blog/alert-storm-noise-reduction-practice — Noise reduction means converging many alerts into a few incidents you can act on, not deleting alerts. This playbook gives a 14-day plan, a reusable configuration template, and the metrics that show whether it worked.
- From MCP to a CLI: Give agents a CLI on platforms you own (2026-07-27): https://www.flashduty.com/en/now/blog/cli-not-mcp — In January, our AI SRE operated Flashduty through a built-in MCP server. By late May, we replaced it with a generated CLI. This post explains why we didn't expand the MCP server, why we chose not to use search-based loading, and what the switch cost.
- Why DeepSeek moved from Atlassian Statuspage to Flashduty (2026-06-10): https://www.flashduty.com/en/now/blog/deepseek-statuspage-migration — DeepSeek moved its public status page from Atlassian Statuspage to Flashduty Statuspage. The decision came down to Chinese support, cost, page experience, the credibility of self-hosting, and subscriber migration. The migration took two CLI commands.
- Keep monitoring data local and manage alerting in one place (2026-09-03): https://www.flashduty.com/en/now/blog/distributed-data-source-control-plane — Distributed data sources are a reasonable reality, but alerting rules, runtime status, and investigation should not fragment with them. Flashduty Monitors keeps data inside private networks while centralizing alerting and analysis in one control plane.
- flashduty-cli lets you and coding agents handle incidents (2026-06-08): https://www.flashduty.com/en/now/blog/flashduty-cli — Why an incident response platform builds a command-line interface (CLI), and why the CLI is how AI coding agents operate Flashduty. An engineering note on the design tradeoffs.
- Flashduty Monitors: Alert on Loki and VictoriaLogs queries (2026-01-09): https://www.flashduty.com/en/now/blog/flashduty-monitors-loki-and-victorialogs — Flashduty Monitors supports Grafana Loki and VictoriaLogs with native query syntax, three alerting modes, separate recovery logic, and raw log samples in alert messages.
- Futures on-call: Handling tens of thousands of alerts a week (2024-08-20): https://www.flashduty.com/en/now/blog/futures-oncall-practice — The ops team at a Shanghai futures company handles tens of thousands of alerts a week. Their approach has four parts: one unified platform, an on-call process, CMDB metadata, and ongoing measurement with MTTA and MTTR. Based on a talk at the CCF Nightingale forum.
- go-flashduty: A Go SDK generated 1:1 from the Flashduty API (2026-06-08): https://www.flashduty.com/en/now/blog/go-flashduty-sdk — go-flashduty is the official Go client for the Flashduty Open API. It's thin, strongly typed, and generated from an OpenAPI spec. This post explains how we design and maintain an SDK that covers 27 services and 253 endpoints, and why we generate code, keep a strict 1:1 boundary with the API, and let that boundary prevent drift.
- How Google SRE and Datadog keep on-call sustainable (2023-12-26): https://www.flashduty.com/en/now/blog/google-sre-oncall-tools — Google never open-sourced its on-call tool, Outalator, but tooling isn't the hard part of on-call. Google SRE and Datadog put their effort into a cap on toil, sustainable schedules, and metrics. Here's how each approach works, plus three first steps that need no extra budget.
- Don't let on-call burn out your most responsible engineer (2024-03-18): https://www.flashduty.com/en/now/blog/how-to-oncall — Many teams say everyone is on call, but the most responsible person takes most shifts, gets an average review, and quits. Here are six practices that make on-call fair and sustainable, plus six common anti-patterns.
- The eight stages of on-call and how far to take each one (2024-08-27): https://www.flashduty.com/en/now/blog/oncall-concept — On-call is much more than scheduling. From alert ingestion to analytics, this post covers why each of eight stages exists, how far to take it, and where it goes wrong. The cheapest noise reduction happens before an alert fires.
- Opsgenie alternatives in 2026: Move before April 2027 (2026-09-04): https://www.flashduty.com/en/now/blog/opsgenie-alternatives-2026 — Opsgenie ends support on April 5, 2027, and Atlassian deletes data that hasn't moved. Compare Jira Service Management with independent on-call platforms, with sourced pricing as of October 2026 and a four-week migration plan.
- PagerDuty alternatives in 2026: Compare who you pay for (2026-09-04): https://www.flashduty.com/en/now/blog/pagerduty-alternatives-2026 — A sourced comparison of six PagerDuty alternatives as of October 2026: Flashduty, incident.io, Grafana Cloud IRM, Better Stack, FireHydrant, and Jira Service Management. Covers pricing for notification-only users, AI, status pages, and migration.
- PagerDuty vs Flashduty cost for 100 people: Who needs a seat (2026-05-20): https://www.flashduty.com/en/now/blog/pagerduty-on-call-cost — A sourced on-call cost model as of October 2026. Separate responders from notification-only users, then compare PagerDuty full seats, PagerDuty Stakeholder licenses, and Flashduty responder licenses.
- Is Prometheus Alertmanager enough for on-call? (2026-05-20): https://www.flashduty.com/en/now/blog/prometheus-alertmanager-on-call-platform — Alertmanager routes alerts. An on-call platform manages incident response. This post gives a comparison table and two checklists that show when Alertmanager is enough, when to add an on-call platform after it, and how to connect it to Flashduty.
- Ordered, crash-safe AI agent sessions with one Redis lock (2026-10-07): https://www.flashduty.com/en/now/blog/redis-actor-session-runtime — Inside Flashduty AI SRE, part 1: Redis locks, lists, and Pub/Sub keep session messages in order, recover unfinished work after crashes, and keep idle sessions from tying up connections.
- From a user error to a fix PR in 8 minutes: RUM × AI SRE (2026-07-22): https://www.flashduty.com/en/now/blog/rum-ai-sre-8-minutes — A user hit three frontend errors while creating a monitoring rule. RUM preserved the session, version, and SourceMap stack; AI SRE located the right repository, made a one-line fix, and opened a PR.
- We stopped writing docs by hand (2026-06-08): https://www.flashduty.com/en/now/blog/stop-writing-docs-by-hand — A small team with no dedicated product manager built an AI agent that finds documentation gaps, writes the missing docs, and opens pull requests. The fix was to make drift visible instead of reminding engineers to write docs.

## EN Customer Stories
- Geely: Building a Unified Incident Response Hub with Flashduty (2026-04-13): https://www.flashduty.com/en/customer-cases/flashduty-geely — As Geely accelerates its electric, intelligent, and global transformation, its IT teams face multi-cloud complexity, fragmented alert sources, alert noise, and cross-region on-call coordination. With Flashduty, Geely built a unified alerting and incident response hub and moved from scattered alert handling to a standardized incident governance model.
- Starbucks China: Turning 3,000+ Daily Raw Alerts into 500 Actionable Incidents (2026-04-13): https://www.flashduty.com/en/customer-cases/flashduty-starbucks — Across stores, mobile apps, membership systems, and supply chain operations, Starbucks China faced alert storms, difficult alert configuration, and the risk of missed or unhandled alerts. With Flashduty, the team unified alert ingestion, intelligent noise reduction, precise routing, escalation, and closed-loop management, reducing more than 3,000 raw alerts per day to about 500 actionable incidents.
- Tuyoo Games: Running On-call Across Multi-cloud and IDC Environments with Flashduty (2023-11-26): https://www.flashduty.com/en/customer-cases/flashduty-tuyoo — Tuyoo Games uses Flashduty to connect monitoring systems across cloud and on-prem environments, reduce alert noise, implement on-call scheduling, and route incidents to the right responders without interrupting the entire operations team.
- Yifeng Pharmacy: Unifying Alert Management Across Monitoring Systems with Flashduty (2023-11-23): https://www.flashduty.com/en/customer-cases/flashduty-yfdyf — Yifeng Pharmacy uses Flashduty to centralize alerts from Zabbix, Prometheus, Nightingale, and multiple cloud monitoring systems, adding alert aggregation, noise reduction, acknowledgment, escalation, and flexible routing to its incident response workflow.

## EN Alternatives
- Flashduty vs PagerDuty: https://www.flashduty.com/en/alternatives/pagerduty — Flashduty vs PagerDuty: more than on-call — alert intake, noise reduction, paging, IM collaboration, status pages, and AI investigation in one platform. Notify everyone; pay only for responders.
- Flashduty vs Opsgenie: https://www.flashduty.com/en/alternatives/opsgenie — An honest comparison of Flashduty and Opsgenie for on-call and incident response — sunset timeline, migration choices, pricing, China IM channels, and when Jira Service Management is still the better path.
- Flashduty vs Grafana OnCall/IRM: https://www.flashduty.com/en/alternatives/grafana-oncall — An honest comparison of Flashduty and Grafana OnCall/IRM — the OnCall Cloud sunset and OSS archival timeline, Grafana Cloud IRM pricing and platform fee, China IM channels, private deployment, and when staying inside Grafana makes sense.

## EN Changelog
- Set Up Feishu/Lark, DingTalk, and WeCom by Scanning a QR Code, and Members Link Automatically (2026-10-19): https://www.flashduty.com/en/now/changelog/2026-10-19-im-scan-to-set-up — Feishu and DingTalk integrations can create their app by QR code, WeCom third-party apps bind by scanning, and Flashduty can host the access domain and HTTPS certificate of a WeCom self-built app. Members are linked to their IM accounts by verified phone number or email, and the Microsoft Teams page shows where notifications go.
- AI SRE Publishes Slides and Design Canvases, Links Answers to Console Pages, and Tunes Channel Noise Reduction (2026-10-19): https://www.flashduty.com/en/now/changelog/2026-10-19-ai-sre-artifacts-console-links-noise — AI SRE artifacts can now be multi-file pages, slide decks, or design canvases, and the gallery plays video and audio and shows CSV files as tables. Answers link incidents, alerts, and rules to their console pages, a channel's noise reduction pages can hand the setup to AI SRE, and automations run in the war room or IM chat they belong to.
- RUM Custom Dashboards: Build Your Own Dashboards From Explorer Analytics (2026-10-18): https://www.flashduty.com/en/now/changelog/2026-10-18-rum-custom-dashboards — RUM Insights now hosts dashboards you build yourself, next to the built-in ones. Panels use the same aggregation queries as Explorer analytics, charts can be saved straight to a dashboard, and every save keeps a version, with deleted dashboards kept in the trash for 30 days.
- Notification Templates Preview Each Channel and Send a Test Message, and Feishu Cards Can Use Native Tables (2026-10-16): https://www.flashduty.com/en/now/changelog/2026-10-16-notification-template-send-test — The template detail page previews each channel block by block, with its byte usage and a warning when the content would fail, be truncated, or lose its tables. Send test delivers the editor's current content for a real incident, and Feishu app templates can render Markdown tables as native card tables.
- Wildcard Conditions Match Literally, Integration Secrets Are Masked, and Alert Event Queries Need a Time Range (2026-10-15): https://www.flashduty.com/en/now/changelog/2026-10-15-literal-wildcards-masked-secrets — In filter conditions, only * and ? are wildcards now, and regular expressions are written as /…/. Saved integration secrets read back as ******, and changing where a secret is sent requires entering it again. The alert event list API requires a time range of at most 31 days.
- Monitors Alert Rules Get Investigation Entries That Open the Right Dashboard or Query (2026-10-14): https://www.flashduty.com/en/now/changelog/2026-10-14-monitors-investigation-entries — A Monitors alert rule can now carry up to 20 investigation entries that open a dashboard or a query from the alert. Dashboards gain built-in time variables, a display time zone, and search across all folders, and related and recovery queries accept Go templates.
- AI SRE Settings Move Under Customize, and Memory Is Now Viewable and Editable in the Console (2026-10-05): https://www.flashduty.com/en/now/changelog/2026-10-05-ai-sre-customize-memory-subagents — AI SRE knowledge, memory, plugins, and environments now live under one Customize area; memory is stored as Markdown files you can view and edit; subagents can run in another execution environment; and Monitors data sources can be handed to AI SRE directly.
- 235 New Alert and Change Integrations, and an Integration Catalog You Can Browse by Category (2026-10-05): https://www.flashduty.com/en/now/changelog/2026-10-05-235-new-integrations — Since mid-September, Flashduty added 197 alert integrations and 38 change integrations, plus an Opsgenie-compatible endpoint. The add-integration panel is now grouped by category, a full-screen catalog lists every integration, and you can request a system that isn't there yet.
- Status Page Widgets: Put Your Live Status Where Your Users Already Are (2026-08-11): https://www.flashduty.com/en/now/changelog/2026-08-11-status-page-widgets — Public status pages now offer embeddable widgets — a status badge and an incident banner — so a single snippet shows your live service status on your own site or help center.
- Artifacts Get Public Links: Send a Report to Someone Without an Account (2026-08-06): https://www.flashduty.com/en/now/changelog/2026-08-06-artifact-public-links — The AI SRE artifact gallery adds public links: generate a sign-in-free link and send an investigation write-up or inspection report straight to a customer or partner. The content is a snapshot you can update or revoke at any time.
- ServiceMap (Beta): Who Is This Machine Actually Talking To (2026-08-06): https://www.flashduty.com/en/now/changelog/2026-08-06-servicemap-beta — Monitors adds ServiceMap (Beta): built from monit-agent's eBPF observation, it automatically maps the real dependencies among hosts, processes, containers, and workloads, so you can judge the blast radius of a change or an incident.
- AI SRE Open Public Beta: No Application, Sign In and Go (2026-07-28): https://www.flashduty.com/en/now/changelog/2026-07-28-ai-sre-open-to-all — AI SRE is now in public beta for every account: the application form and allowlist are gone — sign in to the console and start using it, free during the beta.
- Artifacts Gallery: What the Agent Builds Doesn't Disappear With the Chat (2026-07-27): https://www.flashduty.com/en/now/changelog/2026-07-27-agent-artifacts-gallery — AI SRE adds an Artifacts gallery. Reports and pages the Agent produces in a session can be published, searched, shared, and managed, instead of dug back out of chat history.
- Kubernetes App: Bring a Cluster Into AI SRE, on the Boundary You Draw (2026-07-27): https://www.flashduty.com/en/now/changelog/2026-07-27-kubernetes-app-ai-sre — AI SRE adds a Kubernetes App that brings a cluster into the investigation flow, scoped to specific namespaces and read-only or limited-write permissions, installed and removed by commands you run yourself.
- Where AI SRE Runs: Cloud Sandbox and a Runner Inside Your Network (2026-07-23): https://www.flashduty.com/en/now/changelog/2026-07-23-ai-sre-sandbox-runner — An Agent that actually runs commands needs somewhere to stand. The cloud Sandbox works out of the box, and a BYOC Runner brings the investigation into your own network without opening an inbound port.
- AI SRE Connects to Your Code: Trace an Investigation Down to the Commit (2026-07-22): https://www.flashduty.com/en/now/changelog/2026-07-22-ai-sre-code-investigation — Once you authorize the GitHub App or GitLab App, AI SRE can read source code, trace commits and PRs during an investigation, and open a fix PR when you ask for one. The GitLab App is now available to all accounts.
- AI SRE Public Beta: Let the Agent Run the First Round of Investigation (2026-07-20): https://www.flashduty.com/en/now/changelog/2026-07-20-ai-sre-public-beta — AI SRE is now in public beta for On-call Professional accounts and above. It investigates with the alert, incident, and on-call context already loaded, then hands the findings and evidence back to whoever is responding.
- RUM Explorer Adds Natural-Language Query (2026-07-18): https://www.flashduty.com/en/now/changelog/2026-07-18-rum-natural-language-query — Filtering sessions and events no longer requires learning DQL first. Describe what you want in plain language and review the AI-generated query before it applies.
- Custom Incident Forms: Capture What You Need at Create, Acknowledge, and Resolve (2026-07-14): https://www.flashduty.com/en/now/changelog/2026-07-14-custom-incident-forms — Incident create, acknowledge, and resolve now each support a configurable form, with required fields and conditional display, delivered through one consistent interface across five IM platforms.
- Login Governance Update: Tightening Password Sign-in, API Key Scope, and Account Cleanup (2026-07-06): https://www.flashduty.com/en/now/changelog/2026-07-06-login-governance-update — Enforced SSO login, scoped App Key permissions, brute-force protection and configurable session length for self-hosted deployments, and stronger member deletion now ship together, covering several login and access-control questions common in enterprise security reviews.
- RUM Fills In Crash Analysis for Mini Programs, HarmonyOS, and Android NDK (2026-06-24): https://www.flashduty.com/en/now/changelog/2026-06-24-rum-crash-analysis-platforms — Crash symbolication now covers WeChat Mini Programs, HarmonyOS, and Android NDK native code. RUM alerts no longer require On-call, and the SDK supports custom ingest endpoints for private deployments.
- Status Page Upgrade: Dual-Region Custom Domains and One-Click Atlassian Statuspage Migration (2026-06-05): https://www.flashduty.com/en/now/changelog/2026-06-05-status-page-regions-atlassian-migration — Custom domains now resolve through separate mainland China and international routes, and Atlassian Statuspage users can migrate components, history, and subscribers with the CLI.
- Post-Mortem is Here: Turn Every Incident into a Starting Point for Team Growth (2026-03-19): https://www.flashduty.com/en/now/changelog/2026-03-19-incident-postmortem — Restoring service doesn't mean the incident is truly over. The real closure begins with a post-mortem.
- Flashduty Status Pages: Sevice Down, Trust Online (2025-12-30): https://www.flashduty.com/en/now/changelog/2025-12-30-status-pages-resilience — Service interruptions are inevitable. Trust should not go offline with them.
- Routing Rules Update (2025-12-16): https://www.flashduty.com/en/now/changelog/2025-12-16-routing-rules-update — This release introduces significant enhancements to Alert Routing, focusing on better automation, improved readability, and a smoother configuration experience for complex routing scenarios.
- Introducing War Room, Enhanced Change Management & Streamlined Incident Collaboration (2025-12-04): https://www.flashduty.com/en/now/changelog/2025-12-04-war-room-change-management — When critical incidents strike, every second counts. Now you can spin up a War Room with a single click to rally your team and accelerate incident response.
- AI Summary and ServiceNow (2025-08-22): https://www.flashduty.com/en/now/changelog/2025-08-22-ai-summary-servicenow — Added AI Summary feature to quickly distill incident details, ideal for scenarios with numerous aggregated alerts. The summary focuses on:
- Changes in June (2025-06-17): https://www.flashduty.com/en/now/changelog/2025-06-17-june-feature-roundup — Link Integration Enables seamless connection with external systems, allowing direct navigation to CMDB host information pages based on machine hostname, boosting operational efficiency.
- Fixed License and Alert Routing Version Management (2025-05-09): https://www.flashduty.com/en/now/changelog/2025-05-09-fixed-license-routing-versions
- New Jira Integration and Template Management! (2025-03-06): https://www.flashduty.com/en/now/changelog/2025-03-06-jira-template-management
- Flashduty app now available, boosting response efficiency by 40%! (2025-02-25): https://www.flashduty.com/en/now/changelog/2025-02-25-mobile-app-launch — Dear Flashduty users,
- Enhanced Label Mapping: Now Manage Data Directly in the Console! (2025-01-23): https://www.flashduty.com/en/now/changelog/2025-01-23-label-mapping-console-management — Since its launch, the Label Enrichment feature has been well received, especially for mapping labels using mapping data. However, managing mapping schemas and handling data uploads/downloads was previously only possible via the API, whic…
- Brand new Insights dashbord! (2025-01-14): https://www.flashduty.com/en/now/changelog/2025-01-14-insights-dashboard-upgrade — The new insights dashboard is now live! Thank you for your patience.
- Upgrade for Incident Isolation (2024-12-09): https://www.flashduty.com/en/now/changelog/2024-12-09-incident-isolation-upgrade — Many users have reported that Flashduty's incident permission control was relatively weak. We have now made improvements to address this.
- Introducing the All-New Alert Pipeline! (2024-12-09): https://www.flashduty.com/en/now/changelog/2024-12-09-alert-pipeline-launch — Many users have reported common issues with their internal alert configuration policies, such as missing alert information, numerous duplicate reports, and unclear severity levels. These problems have caused significant concerns for aler…
- Schdule Management Upgrade! (2024-12-06): https://www.flashduty.com/en/now/changelog/2024-12-06-schedule-management-upgrade — We have comprehensively upgraded our on-call management system, with improvements in notifications, scheduling, and UI design.
- StateCloud and Guance integrations. (2024-12-05): https://www.flashduty.com/en/now/changelog/2024-12-05-statecloud-guance-integrations — New alert integrations for StateCloud (天翼云) and Guance Cloud (观测云).
- English UI launch (2024-12-05): https://www.flashduty.com/en/now/changelog/2024-12-05-english-ui-launch — We now offer full English support across the console, help docs, and developer documentation so more users can use the product without language barriers.
- New mobile UI: sleeker and more powerful! (2024-11-13): https://www.flashduty.com/en/now/changelog/2024-11-13-mobile-ui-refresh
- AIOps! Intelligent grouping, Rare and Past incidents. (2024-11-04): https://www.flashduty.com/en/now/changelog/2024-11-04-aiops-intelligent-incident-grouping — We've launched a series of AIOps capabilities. Try them out now!
- Breaking changes: Updates to inhibit and silence rules. (2024-10-12): https://www.flashduty.com/en/now/changelog/2024-10-12-inhibit-silence-rule-changes — When an incident aggregates multiple alerts, its labels may differ from the original alerts. Matching silence/inhibit rules at the incident level caused these issues:
- September UI/UX improvements (2024-10-11): https://www.flashduty.com/en/now/changelog/2024-10-11-ui-ux-improvements
- Meraki, OpManager and other integrations (2024-09-24): https://www.flashduty.com/en/now/changelog/2024-09-24-meraki-opmanager-integrations
- Solarwinds and Volcengine integrations (2024-08-19): https://www.flashduty.com/en/now/changelog/2024-08-19-solarwinds-volcengine-integrations
- Appdynamics and Splunk alert integrations (2024-08-06): https://www.flashduty.com/en/now/changelog/2024-08-06-appdynamics-splunk-integrations
- CAS SSO and Google Cloud Monitoring integrations (2024-07-30): https://www.flashduty.com/en/now/changelog/2024-07-30-cas-sso-google-cloud-monitoring
- Dynatrace and Huawei Cloud Log Service integrations (2024-07-24): https://www.flashduty.com/en/now/changelog/2024-07-24-dynatrace-huawei-cloud-log-integrations
- License transfer and permission enhancements (2024-07-18): https://www.flashduty.com/en/now/changelog/2024-07-18-license-transfer-rbac
- AWS EventBridge & JianKongBao integrations (2024-07-16): https://www.flashduty.com/en/now/changelog/2024-07-16-eventbridge-jiankongbao-integrations — Ingest AWS EventBridge events and alerts from JianKongBao (监控宝), plus smoother snooze behavior on incidents.
- Welcome to Flashduty — onboarding refresh (2024-07-12): https://www.flashduty.com/en/now/changelog/2024-07-12-onboarding-refresh — A new onboarding flow walks you and your teammates through core Flashduty capabilities so you can get productive faster.
- SkyWalking & Sentry integrations (2024-07-03): https://www.flashduty.com/en/now/changelog/2024-07-03-skywalking-sentry-integrations — Bring SkyWalking trace metrics and Sentry metric alerts or issue events into Flashduty.
- Faster silence workflows, SSO & quality-of-life fixes (2024-06-19): https://www.flashduty.com/en/now/changelog/2024-06-19-silence-sso-workflow-updates — Quick silence from incident details, LDAP SSO on private deployments, safer deletions, and richer filtering and analytics.
- Graylog & OceanBase integrations (2024-06-14): https://www.flashduty.com/en/now/changelog/2024-06-14-graylog-oceanbase-integrations — Stream Graylog alerts via webhook and OceanBase database alerts via shell scripts into Flashduty.
- IM cards & notification UX improvements (2024-05-10): https://www.flashduty.com/en/now/changelog/2024-05-10-im-cards-notification-ux — Richer IM cards, Slack DMs, @mentions in dispatch, configurable synced actions, and push-friendly loop notifications.
- Label enrichment, Microsoft Teams & more improvements (2024-04-22): https://www.flashduty.com/en/now/changelog/2024-04-22-label-enrichment-teams — Label enrichment from CMDB, refreshed IM cards with Microsoft Teams, better incident lists, channels, dispatch, and Alibaba Cloud Monitor event integration.

## ZH Blog Posts
- AI SRE 与外部 Agent 通过 A2A 互相委派任务 (2026-08-17): https://www.flashduty.com/zh/now/blog/a2a-in-production — 在控制台登记外部 Agent 后，AI SRE 可以将完整任务委派给该 Agent，进度以流式方式返回对话；AI SRE 也提供标准 A2A 接口，接受其他 Agent 委派的任务。
- AI SRE 安全访问 Kubernetes 集群：无须开放公网，无须提供 kubeconfig (2026-08-17): https://www.flashduty.com/zh/now/blog/ai-agent-kubernetes-access — 将集群接入 AI SRE 需要同时满足四个条件：kubectl 的全部能力、不开放入站端口、凭据不离开集群、权限严格受控且不依赖能力清单。我们的方案是让 Agent 运行原生 kubectl，由集群主动建立出站连接，权限完全由 Kubernetes RBAC 判定。
- AI SRE 产物：每份报告都有可长期保存、可分享的链接 (2026-08-17): https://www.flashduty.com/zh/now/blog/ai-sre-artifacts — AI SRE 会话中生成的报告、设计文档和页面现在可以发布为产物。产物有两项作用：长期保存，每个产物在产物库中拥有独立地址，团队成员随时可以打开；对外分享，需要时可生成免登录的公开链接，并可随时撤销。
- 凌晨三点自动开始调查：AI SRE 自动化的五种用法 (2026-08-17): https://www.flashduty.com/zh/now/blog/ai-sre-automations — 每周洞察、告警治理、故障自动分析、发布后巡检和变更风险预检五种用法，各附完整的任务提示词，并说明运行结果送达相关人员的方式。
- GitHub / GitLab App：AI SRE 读取提交、分析 CI 日志并创建 PR (2026-08-17): https://www.flashduty.com/zh/now/blog/ai-sre-github-gitlab-access — AI SRE 现已支持连接 GitHub 组织或 GitLab 实例：排查故障时读取最近的提交，CI 失败时分析失败日志，小型修复直接创建 PR 并等待人工评审。整个过程无须粘贴令牌。
- 告警发到群里，不等于故障有人负责 (2026-06-24): https://www.flashduty.com/zh/now/blog/alert-in-group-not-ownership — 群机器人让告警可见，但不会指定负责人。故障响应需要留下负责人、认领、升级、关闭、时间线和复盘记录。本文给出一个自查方法：抽查最近 10 条关键告警。
- 告警风暴降噪实践：用 14 天把告警收敛为可处理的故障 (2026-05-20): https://www.flashduty.com/zh/now/blog/alert-storm-noise-reduction-practice — 降噪的目标是把海量告警收敛为少量可处理的故障，而非删除告警。本文给出 14 天的分步做法、一份可复用的配置模板，以及判断降噪是否有效的指标。
- 从 MCP 到 CLI：自有平台应为 Agent 提供命令行 (2026-07-27): https://www.flashduty.com/zh/now/blog/cli-not-mcp — 今年一月，我们的 AI SRE 通过内置 MCP 操作 Flashduty；五月底，我们改用生成式 CLI。本文说明为什么没有扩充 MCP、为什么放弃搜索式加载，以及切换之后付出的代价。
- DeepSeek 为什么把状态页从 Atlassian 迁到 Flashduty (2026-06-10): https://www.flashduty.com/zh/now/blog/deepseek-statuspage-migration — DeepSeek 把公开状态页从 Atlassian Statuspage 迁到了 Flashduty Statuspage。影响选型的因素包括中文支持、成本、页面体验、自建的可信度和订阅者迁移。迁移通过两条 CLI 命令完成。
- 数据保留在各个环境，告警集中管理 (2026-09-03): https://www.flashduty.com/zh/now/blog/distributed-data-source-control-plane — 数据源分散有其合理原因，但告警规则、运行状态和排障入口不应随之分散。Flashduty Monitors 让数据保留在私网中，将告警和分析能力集中到一个控制面。
- flashduty-cli：在终端中处理故障，并让 AI Agent 安全地参与处理 (2026-06-08): https://www.flashduty.com/zh/now/blog/flashduty-cli — 本文说明我们为什么为故障响应平台开发命令行工具，以及为什么将它设计为 AI 编程 Agent 操作 Flashduty 的入口。这是一篇关于 CLI 设计取舍的工程笔记。
- 用现有的 Loki 和 VictoriaLogs 查询做告警：Flashduty Monitors 已支持 (2026-01-09): https://www.flashduty.com/zh/now/blog/flashduty-monitors-loki-and-victorialogs — Flashduty Monitors 支持 Grafana Loki 和 VictoriaLogs 数据源，保留原生查询语法，并提供三种告警模式、独立恢复逻辑和告警中的日志原文样例。
- 期货行业的 On-call 实践：每周数万条告警如何管理 (2024-08-20): https://www.flashduty.com/zh/now/blog/futures-oncall-practice — 一家上海期货公司的运维团队每周处理数万条告警。他们的做法包括四项：选用统一平台、建立值班制度、打通 CMDB 元数据、用 MTTA 和 MTTR 持续运营。本文整理自该公司技术专家在 CCF 夜莺论坛上的分享。
- SDK 不应比 API 更聪明：go-flashduty 的三个设计决定 (2026-06-08): https://www.flashduty.com/zh/now/blog/go-flashduty-sdk — go-flashduty 是 Flashduty Open API 的官方 Go 客户端：薄、强类型、由 OpenAPI 规范代码生成。一个覆盖 27 个服务、253 个接口的 SDK 该如何设计与长期维护：为什么选 codegen 而非手写，为什么坚持与 API 严格 1:1，以及这条边界如何让 SDK 多年不腐化。
- Google 和 Datadog 的 On-call：工具最容易复制，排班和度量才是门槛 (2023-12-26): https://www.flashduty.com/zh/now/blog/google-sre-oncall-tools — Google 的 On-call 工具 Outalator 没有开源，但工具并非 On-call 的难点。Google SRE 和 Datadog 都把投入放在琐事上限、可持续排班和度量上。本文拆解两家的做法，并给出三项无须额外预算的起步动作。
- 别让 On-call 累垮最负责的人 (2024-03-18): https://www.flashduty.com/zh/now/blog/how-to-oncall — 很多团队名义上全员 On-call，实际上最负责的人承担最多值班，绩效却普通，最终离职。本文给出让 On-call 公平且可持续的六项做法，以及六个常见反模式。
- On-call 体系的八个环节：每个环节做到什么程度 (2024-08-27): https://www.flashduty.com/zh/now/blog/oncall-concept — On-call 远不止排班。从告警接入到统计分析，本文逐个说明八个环节为什么需要、做到什么程度、哪里容易出错。最划算的降噪，发生在告警产生之前。
- Opsgenie 替代方案 2026：在 2027 年 4 月停服前确定迁移路径 (2026-09-04): https://www.flashduty.com/zh/now/blog/opsgenie-alternatives-2026 — Opsgenie 将于 2027 年 4 月 5 日停止支持，未迁出的数据会被删除。本文对比 Jira Service Management 与独立 On-call 平台，提供截至 2026 年 10 月的定价出处，以及四周迁移计划。
- PagerDuty 替代方案 2026：按计费对象比较，而非按席位单价比较 (2026-09-04): https://www.flashduty.com/zh/now/blog/pagerduty-alternatives-2026 — 截至 2026 年 10 月，对比六个 PagerDuty 替代方案：Flashduty、incident.io、Grafana Cloud IRM、Better Stack、FireHydrant 和 Jira Service Management。重点比较只接收通知的成员如何计费，以及 AI、状态页和迁移成本。
- 100 人团队的 PagerDuty 与 Flashduty 成本对比：取决于为谁付费 (2026-05-20): https://www.flashduty.com/zh/now/blog/pagerduty-on-call-cost — 截至 2026 年 10 月、附出处的 On-call 成本模型：先区分处理人和只接收通知的成员，再对比 PagerDuty 完整席位、PagerDuty Stakeholder 席位和 Flashduty 处理人 License。
- Alertmanager 够用吗？一张表判断是否需要 On-call 平台 (2026-05-20): https://www.flashduty.com/zh/now/blog/prometheus-alertmanager-on-call-platform — Alertmanager 负责告警路由，On-call 平台负责故障响应。本文给出一张对比表和两份判断清单，说明 Alertmanager 何时够用、何时需要在其后接入 On-call 平台，以及接入 Flashduty 的配置方法。
- 每个会话一个锁：用 Redis 为 AI Agent 实现会话运行时 (2026-10-07): https://www.flashduty.com/zh/now/blog/redis-actor-session-runtime — Flashduty AI SRE 技术揭秘第 1 篇：使用 Redis 锁、列表和 Pub/Sub 保证会话串行处理和崩溃后恢复，并使空闲会话不占用 Redis 连接。
- 从真实用户报错到修复 PR：RUM × AI SRE 的 8⁠分⁠钟 (2026-07-22): https://www.flashduty.com/zh/now/blog/rum-ai-sre-8-minutes — 一名用户在监控规则创建页遇到 3 次前端异常。RUM 留下会话与版本，并通过 SourceMap 还原到具体源码；AI SRE 随后定位仓库、完成一行修复并创建 PR。
- 我们不再手写文档 (2026-06-08): https://www.flashduty.com/zh/now/blog/stop-writing-docs-by-hand — 一个没有专职产品经理的小团队，借助一个 AI Agent 找出数百个文档缺口、补齐内容并提交 PR。解决方法是让文档漂移及时暴露，而不是反复提醒工程师编写文档。

## ZH Customer Stories
- 吉利集团：用 Flashduty 建设统一事件响应中枢 (2026-04-13): https://www.flashduty.com/zh/customer-cases/flashduty-geely — 吉利集团在电动化、智能化与全球化加速推进过程中，面临多云架构、告警来源分散、跨区域值班协同复杂等挑战。通过引入 Flashduty，吉利集团构建了统一的告警与事件响应中枢，实现从分散告警处理到标准化事件治理体系的升级。
- 星巴克中国：每天 3000+ 原始告警，如何收敛到 500 条有效故障 (2026-04-13): https://www.flashduty.com/zh/customer-cases/flashduty-starbucks — 星巴克中国在门店、移动应用、会员体系和供应链等复杂业务体系下，面临告警风暴、配置维护困难和漏报漏处理等问题。通过引入 Flashduty，团队实现了多源告警接入、智能降噪、精准路由和闭环管理，将每天 3000 多条原始告警收敛到约 500 条有效故障。
- 途游游戏：Flashduty 案例分享 (2023-11-26): https://www.flashduty.com/zh/customer-cases/flashduty-tuyoo — Flashduty 作为功能完备的事件OnCall中心，可以接入云上、云下不同监控系统，统一做告警降噪分派、认领升级、排班协同，已经得到众多先进企业的认可。我们采访了一些典型客户代表，了解他们的痛点、选型考虑和未来展望，集成本系列文章，以飨读者
- 益丰大药房：Flashduty 案例分享 (2023-11-23): https://www.flashduty.com/zh/customer-cases/flashduty-yfdyf — Flashduty 作为功能完备的事件OnCall中心，可以接入云上、云下不同监控系统，统一做告警降噪分派、认领升级、排班协同，已经得到众多先进企业的认可。我们采访了一些典型客户代表，了解他们的痛点、选型考虑和未来展望，集成本系列文章，以飨读者

## ZH Alternatives
- Flashduty vs PagerDuty: https://www.flashduty.com/zh/alternatives/pagerduty — 告警送到人只是故障的开始——Flashduty 不仅仅是 On-call 工具：降噪、值班呼叫、IM 协作、状态页、AI 排查全档自带；通知覆盖不限人数，只为处理者付费。
- Flashduty vs Opsgenie: https://www.flashduty.com/zh/alternatives/opsgenie — 对比 Flashduty 与 Opsgenie 在 On-call / 故障响应上的差异：停售与停服时间线、迁移去向、计费模型、中国 IM 渠道，以及什么时候更该走 Atlassian 的 Jira Service Management 路径。
- Flashduty vs Grafana OnCall/IRM: https://www.flashduty.com/zh/alternatives/grafana-oncall — Flashduty 与 Grafana OnCall/IRM 在 On-call / 故障响应上的对比：OnCall Cloud 停服与 OSS 归档时间线、Grafana Cloud IRM 定价与平台费、中国 IM 渠道、私有化部署，以及什么时候留在 Grafana 体系内更合理。

## ZH Changelog
- 飞书、钉钉、企业微信扫码即可接入，成员自动关联 IM 账号 (2026-10-19): https://www.flashduty.com/zh/now/changelog/2026-10-19-im-scan-to-set-up — 飞书和钉钉集成可以扫码创建应用，企业微信第三方应用扫码绑定，企业微信自建应用的访问域名和 HTTPS 证书可以交给 Flashduty 托管；成员按已验证的手机号或邮箱自动关联 IM 账号；Microsoft Teams 页面列出通知发往的位置。
- AI SRE 可以发布幻灯片和设计画布，回答直接链接到控制台页面，还能帮协作空间配置降噪 (2026-10-19): https://www.flashduty.com/zh/now/changelog/2026-10-19-ai-sre-artifacts-console-links-noise — AI SRE 的产物可以是多文件网页、幻灯片或设计画布，产物库能播放音视频、以表格展示 CSV；回答里的故障、告警、规则直接链接到控制台页面；协作空间降噪页可以把配置交给 AI SRE；自动化可以在作战室或 IM 群聊里执行。
- RUM 自定义看板：用查看器的聚合分析搭自己的看板 (2026-10-18): https://www.flashduty.com/zh/now/changelog/2026-10-18-rum-custom-dashboards — RUM 分析看板除了内置看板，现在可以放自己搭的看板。面板使用与查看器聚合分析相同的查询，图表可以直接保存到看板；每次保存保留一个版本，删除的看板在回收站保留 30 天。
- 通知模板按渠道预览并支持发送测试，飞书卡片可以使用原生表格 (2026-10-16): https://www.flashduty.com/zh/now/changelog/2026-10-16-notification-template-send-test — 模板详情页按渠道逐块预览，显示字节用量，并在内容会发送失败、被截断或表格无法渲染时提前提示；发送测试按所选故障真实发送编辑器当前内容；飞书应用模板可以把 Markdown 表格渲染成卡片原生表格。
- 通配条件按字面匹配，集成密钥不再回显，告警事件列表接口必须带时间范围 (2026-10-15): https://www.flashduty.com/zh/now/changelog/2026-10-15-literal-wildcards-masked-secrets — 过滤条件里只有 * 和 ? 是通配符，正则需写成 /…/；已保存的集成密钥读取时显示为 ******，修改发送目标时需要重新填写密钥；告警事件列表接口要求时间范围不超过 31 天。
- Monitors 告警规则新增调查入口，从告警直接打开对应的仪表盘或查询 (2026-10-14): https://www.flashduty.com/zh/now/changelog/2026-10-14-monitors-investigation-entries — Monitors 告警规则可以配置最多 20 个调查入口，从告警直接打开仪表盘或查询；仪表盘新增内置时间变量、显示时区和跨目录搜索；关联查询与恢复查询支持 Go 模板。
- AI SRE 配置统一到「自定义」，记忆可以在控制台查看和编辑 (2026-10-05): https://www.flashduty.com/zh/now/changelog/2026-10-05-ai-sre-customize-memory-subagents — AI SRE 的知识、记忆、插件和运行环境合并到「自定义」一个入口；记忆改为 Markdown 文件，可在控制台查看和编辑；子智能体可以派到其它执行环境；Monitors 数据源可以直接交给 AI SRE 分析。
- 新增 235 个告警与变更集成，集成中心支持按类别浏览和提交集成需求 (2026-10-05): https://www.flashduty.com/zh/now/changelog/2026-10-05-235-new-integrations — 9 月中旬以来新增 197 个告警集成和 38 个变更集成，并提供 Opsgenie 兼容接口；集成中心的添加面板按类别分组，新增全屏集成目录，找不到的系统可以直接提交集成需求。
- 状态页嵌入组件（Widget）：把服务状态，放到你的用户眼前 (2026-08-11): https://www.flashduty.com/zh/now/changelog/2026-08-11-status-page-widgets — 公开状态页新增可嵌入 Widget——状态徽标与事件横幅两种形态，一段代码即可在你的官网、帮助中心展示实时服务状态。
- 产物支持公开链接：把报告发给没有账户的人 (2026-08-06): https://www.flashduty.com/zh/now/changelog/2026-08-06-artifact-public-links — AI SRE 产物库新增公开链接：生成一条免登录的链接，把排障结论或巡检报告直接发给客户和外部协作方；内容以快照呈现，可随时更新或撤销。
- ServiceMap 服务地图（Beta）：这台机器此刻在和谁通信 (2026-08-06): https://www.flashduty.com/zh/now/changelog/2026-08-06-servicemap-beta — Monitors 新增 ServiceMap（Beta）：基于 monit-agent 的 eBPF 观测，自动构建主机、进程、容器与工作负载之间的真实依赖拓扑，用来判断变更和故障的影响范围。
- AI SRE 全量开放公测：无需申请，登录即用 (2026-07-28): https://www.flashduty.com/zh/now/changelog/2026-07-28-ai-sre-open-to-all — AI SRE 向所有账户全量开放公测：不再需要申请表和白名单，登录控制台即可使用，公测期间免费。
- 产物库上线：Agent 做的报告不会随对话消失 (2026-07-27): https://www.flashduty.com/zh/now/changelog/2026-07-27-agent-artifacts-gallery — AI SRE 新增产物库：Agent 在会话中生成的报告和页面可以发布、检索、分享和管理，不用再翻聊天记录去找。
- Kubernetes App：把集群接进 AI SRE，权限收在你划的那条线里 (2026-07-27): https://www.flashduty.com/zh/now/changelog/2026-07-27-kubernetes-app-ai-sre — AI SRE 新增 Kubernetes App，可以把集群接入调查流程，按 namespace 和只读/有限修改两档权限限制 Agent 的操作范围，安装和卸载都由你在集群里执行命令完成。
- AI SRE 的运行环境：云端 Sandbox 与你内网的 Runner (2026-07-23): https://www.flashduty.com/zh/now/changelog/2026-07-23-ai-sre-sandbox-runner — Agent 排障要真的动手执行命令，就需要一个落脚的地方。云端 Sandbox 开箱即用，BYOC Runner 让调查进到你自己的网络，全程不需要开放入站端口。
- AI SRE 接入代码仓库：调查可以一直追到那次改动 (2026-07-22): https://www.flashduty.com/zh/now/changelog/2026-07-22-ai-sre-code-investigation — 授权 GitHub App 或 GitLab App 之后，AI SRE 能在调查过程中读源码、追溯改动和 PR，并在你要求时提交修复 PR。GitLab App 已面向全部账户开放。
- AI SRE 开放公测：告警之后，先让 Agent 跑完第一轮调查 (2026-07-20): https://www.flashduty.com/zh/now/changelog/2026-07-20-ai-sre-public-beta — AI SRE 面向 On-call 专业版及以上账户灰度开放公测。它带着告警、故障和值班上下文自主调查，把结论和证据交回给正在响应的人。
- RUM 查看器支持自然语言查询 (2026-07-18): https://www.flashduty.com/zh/now/changelog/2026-07-18-rum-natural-language-query — 筛选 Session 和事件不必先学 DQL 语法，用一句话描述想找什么，AI 生成的查询条件应用前可见、可撤销。
- 自定义故障表单：创建、认领、关闭都能收集你要的信息 (2026-07-14): https://www.flashduty.com/zh/now/changelog/2026-07-14-custom-incident-forms — 故障创建、认领、关闭三个环节现在都能配置自定义表单，字段可设必填和显示条件，五大 IM 平台统一走同一套表单界面。
- 登录治理更新：密码登录、密钥权限、账号清理一起收紧 (2026-07-06): https://www.flashduty.com/zh/now/changelog/2026-07-06-login-governance-update — 强制 SSO 登录、App Key 权限分域、私有化部署登录防爆破与会话时长控制、成员删除治理一起上线，覆盖企业安全审计里常被问到的几个登录与权限控制点。
- RUM 补齐微信小程序、鸿蒙与 Android NDK 的崩溃分析 (2026-06-24): https://www.flashduty.com/zh/now/changelog/2026-06-24-rum-crash-analysis-platforms — 崩溃符号化能力扩展到微信小程序、HarmonyOS 和 Android NDK 原生代码，RUM 告警不再强绑 On-call，SDK 支持私有化自定义上报地址。
- 状态页升级：自定义域名双线路与 Atlassian Statuspage 一键迁移 (2026-06-05): https://www.flashduty.com/zh/now/changelog/2026-06-05-status-page-regions-atlassian-migration — 自定义域名改为中国大陆和国际双线路托管，Atlassian Statuspage 用户可以用 CLI 一键迁移组件、历史事件和订阅者。
- 故障复盘上线：让每一次故障，都成为团队进步的起点 (2026-03-19): https://www.flashduty.com/zh/now/changelog/2026-03-19-incident-postmortem — 故障恢复并不意味着流程的结束。真正的闭环，始于复盘。
- Flashduty 状态页：服务宕机，信任在线 (2025-12-30): https://www.flashduty.com/zh/now/changelog/2025-12-30-status-pages-resilience — 服务中断不可避免，但信任不应随之掉线。
- 路由规则升级 (2025-12-16): https://www.flashduty.com/zh/now/changelog/2025-12-16-routing-rules-update — 本次更新对 Alert Routing（告警路由） 能力进行了全面增强，重点提升自动化程度、规则可读性以及配置体验，帮助团队更高效地管理复杂告警路由场景。
- 作战室上线，变更管理升级，故障协同更高效 (2025-12-04): https://www.flashduty.com/zh/now/changelog/2025-12-04-war-room-change-management — 紧急故障处理往往争分夺秒，如何快速拉齐团队、高效协同是关键。现在，您可以一键拉起作战室，让信息同步更迅速、故障响应更敏捷。
- AI 总结 和 ServiceNow 集成 (2025-08-22): https://www.flashduty.com/zh/now/changelog/2025-08-22-ai-summary-servicenow — 新增 AI 总结功能，快速提炼故障详情，特别适用于聚合大量告警的场景。总结聚焦于：
- 6月系列更新 (2025-06-17): https://www.flashduty.com/zh/now/changelog/2025-06-17-june-feature-roundup — Link集成 实现与外部系统的无缝关联，支持根据机器hostname直接跳转至CMDB主机信息页面，提升运维效率。
- 固定License与路由版本管理 (2025-05-09): https://www.flashduty.com/zh/now/changelog/2025-05-09-fixed-license-routing-versions
- Jira 集成与全新模板管理上线 (2025-03-06): https://www.flashduty.com/zh/now/changelog/2025-03-06-jira-template-management
- 响应效率提升40%！Flashduty APP上线 (2025-02-25): https://www.flashduty.com/zh/now/changelog/2025-02-25-mobile-app-launch — 亲爱的Flashduty用户，
- 映射数据管理 (2025-01-23): https://www.flashduty.com/zh/now/changelog/2025-01-23-label-mapping-console-management — 标签增强功能自推出以来广受好评，特别是在结合 mapping 数据进行标签映射方面。然而，过去只能通过 API 管理映射 schema 及数据上传下载，对于部分用户而言存在一定使用门槛。
- 分析看板全新升级！ (2025-01-14): https://www.flashduty.com/zh/now/changelog/2025-01-14-insights-dashboard-upgrade — 全新的分析看板正式上线，各位久等了！
- 故障数据隔离升级 (2024-12-09): https://www.flashduty.com/zh/now/changelog/2024-12-09-incident-isolation-upgrade — 很多用户反馈Flashduty对故障权限管控较弱，今天我们发布如下优化。
- 告警处理 Pipeline 正式上线！ (2024-12-09): https://www.flashduty.com/zh/now/changelog/2024-12-09-alert-pipeline-launch — 许多用户反馈，公司内部告警策略配置不规范，存在如：告警信息缺失、大量重复上报、严重度不明确等问题，这些问题给告警治理带来困扰。
- 值班管理全面升级 (2024-12-06): https://www.flashduty.com/zh/now/changelog/2024-12-06-schedule-management-upgrade — 我们对值班管理进行了全面升级，从通知到排班到UI样式，都做了优化。
- 新增天翼云与观测云告警集成 (2024-12-05): https://www.flashduty.com/zh/now/changelog/2024-12-05-statecloud-guance-integrations — 支持天翼云告警接入
- 英文版上线 (2024-12-05): https://www.flashduty.com/zh/now/changelog/2024-12-05-english-ui-launch — 我们推出了完整的英文支持，覆盖控制台、帮助文档以及开发者文档，让更多用户能够无障碍地使用我们的服务。
- 移动端新UI，更好看，更强大！ (2024-11-13): https://www.flashduty.com/zh/now/changelog/2024-11-13-mobile-ui-refresh
- AIops！智能聚合，新奇故障，历史故障 (2024-11-04): https://www.flashduty.com/zh/now/changelog/2024-11-04-aiops-intelligent-incident-grouping — 本次升级上线了一系列AIops相关的功能，快来试试吧！
- 不兼容升级，抑制静默策略调整 (2024-10-12): https://www.flashduty.com/zh/now/changelog/2024-10-12-inhibit-silence-rule-changes — 一个故障可能聚合多条告警，故障的标签可能不同于告警。静默/抑制策略在故障层面匹配将导致以下三个问题：
- 9月交互优化 (2024-10-11): https://www.flashduty.com/zh/now/changelog/2024-10-11-ui-ux-improvements
- Meraki和OpManager等集成 (2024-09-24): https://www.flashduty.com/zh/now/changelog/2024-09-24-meraki-opmanager-integrations
- Solarwinds和火山引擎多个集成 (2024-08-19): https://www.flashduty.com/zh/now/changelog/2024-08-19-solarwinds-volcengine-integrations
- Appdynamics和Splunk告警集成 (2024-08-06): https://www.flashduty.com/zh/now/changelog/2024-08-06-appdynamics-splunk-integrations
- CAS单点登录和Google云监控集成 (2024-07-30): https://www.flashduty.com/zh/now/changelog/2024-07-30-cas-sso-google-cloud-monitoring
- Dynatrace和华为云日志服务集成 (2024-07-24): https://www.flashduty.com/zh/now/changelog/2024-07-24-dynatrace-huawei-cloud-log-integrations
- License转移和权限扩充 (2024-07-18): https://www.flashduty.com/zh/now/changelog/2024-07-18-license-transfer-rbac
- AWS Event Bridge 和监控宝集成 (2024-07-16): https://www.flashduty.com/zh/now/changelog/2024-07-16-eventbridge-jiankongbao-integrations
- Onboarding! (2024-07-12): https://www.flashduty.com/zh/now/changelog/2024-07-12-onboarding-refresh — 我们精心准备了onboarding页面，为您和同事们提供平台核心功能指引。通过这些指引，您将了解如何更好的使用Flashduty！
- 新增Skywalking和Sentry集成 (2024-07-03): https://www.flashduty.com/zh/now/changelog/2024-07-03-skywalking-sentry-integrations
- 快速静默与单点登录等优化 (2024-06-19): https://www.flashduty.com/zh/now/changelog/2024-06-19-silence-sso-workflow-updates
- 新增Graylog和OceanBase集成 (2024-06-14): https://www.flashduty.com/zh/now/changelog/2024-06-14-graylog-oceanbase-integrations
- IM 卡片等系列优化 (2024-05-10): https://www.flashduty.com/zh/now/changelog/2024-05-10-im-cards-notification-ux — 我们近期针对IM进行了一系列的优化，以下是我们更新的内容：
- 标签增强，Microsoft Teams 以及系列优化 (2024-04-22): https://www.flashduty.com/zh/now/changelog/2024-04-22-label-enrichment-teams — 我们近期进行了一系列的优化，以下是我们的更新内容：