# 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
- 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
- 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
- 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
- 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 can now delegate to your agents — and vice versa (2026-08-17): https://www.flashduty.com/en/now/blog/a2a-in-production — Register an external agent in the console and AI SRE can hand whole tasks over to it, with progress streaming back into the conversation. It works the other way too: AI SRE exposes a standard A2A endpoint and accepts work 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 three things at once: no public exposure, tight permissions, and no hand-written tool list. What we shipped runs real kubectl, has your cluster dial out to us, and leaves every permission decision to Kubernetes.
- Introducing AI SRE Artifacts (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, change risk reads — each with the exact task prompt, plus how results reach people.
- Introducing GitHub and GitLab Apps for AI SRE (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.
- Sending Alerts to a Group Chat Does Not Mean Someone Owns the Incident (2026-06-24): https://www.flashduty.com/en/now/blog/alert-in-group-not-ownership — Group chat alerts improve visibility, but they do not create ownership. Real incident response needs an owner, acknowledgment, escalation, closure, a timeline, and reviewable follow-up.
- How to Turn an Alert Storm Into Actionable Incidents: A Practical Noise-Reduction Playbook (2026-05-20): https://www.flashduty.com/en/now/blog/alert-storm-noise-reduction-practice — A Flashduty noise-reduction playbook covering events, alerts, incidents, label enrichment, Pipeline cleanup, grouping, storm warnings, flapping detection, silences, suppression, and a 14-day validation method.
- From MCP to a CLI: how our AI SRE operates all of Flashduty (2026-07-27): https://www.flashduty.com/en/now/blog/cli-not-mcp — In January we wired a built-in MCP server into every agent session. By late May we had replaced it with a CLI. Why we didn't expand the MCP, why we passed on search-based loading, and what the switch cost us.
- DeepSeek Status Page Migration: From Atlassian 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 engineering math behind it: why they switched, whether to self-host, whether it migrates cleanly, and the key differences between Flashduty and Atlassian.
- When Monitoring Data Lives Across Dozens of Environments, Alerting Shouldn't Fragment with It (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.
- A CLI for humans and agents (2026-06-08): https://www.flashduty.com/en/now/blog/flashduty-cli — Why an incident response platform builds a CLI at all, and why we made it the entry point for AI coding agents to operate Flashduty — an engineering note on CLI design tradeoffs.
- Flashduty Monitors now supports Loki and VictoriaLogs (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.
- On-call practice in the futures industry (2024-08-20): https://www.flashduty.com/en/now/blog/futures-oncall-practice — Futures trading spans multiple sessions and runs under tight latency and risk-control requirements. This case shows how one futures company used a unified monitoring and incident response platform to speed up alert response and reduce operations pressure.
- An SDK shouldn't be smarter than its 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: thin, strongly typed, and generated from an OpenAPI spec. We want to talk about how to design and maintain an SDK spanning 27 services and 253 endpoints — why we chose codegen over hand-writing, why we keep a strict 1:1 boundary with the API, and how that boundary keeps the SDK from rotting over the years.
- How Google and Datadog run on-call (2023-12-26): https://www.flashduty.com/en/now/blog/google-sre-oncall-tools — Google open-sourced Borg into Kubernetes and Borgmon into Prometheus. So what about Outalator, its internal on-call tool? We unpack the mature on-call practices at Google SRE and Datadog, show why the hard part was never the tooling, and look at what teams can actually borrow.
- Don't let on-call burn out your best people (2024-03-18): https://www.flashduty.com/en/now/blog/how-to-oncall — Plenty of teams claim everyone is on-call, and yet the most conscientious person ends up doing the most work, getting the most average review, and quitting. Here is how to make on-call both fair and sustainable, plus a checklist of anti-patterns to avoid.
- Scheduling is the easy part (2024-08-27): https://www.flashduty.com/en/now/blog/oncall-concept — Integration, label enrichment, grouping, suppression, schedules, escalation, acknowledgement, collaboration, notification, analytics — every stage of On-call explained, along with how far to push each one and where the traps are.
- Best Opsgenie Alternatives in 2026: Where Your On-call Moves Before the Sunset (2026-09-04): https://www.flashduty.com/en/now/blog/opsgenie-alternatives-2026 — Opsgenie ends support on April 5, 2027 and unmigrated data will be deleted. An honest guide to the best Opsgenie alternatives in 2026 — Flashduty, Jira Service Management, PagerDuty, incident.io, Better Stack, and Grafana Cloud IRM — plus a practical migration plan.
- PagerDuty Alternatives in 2026: An Engineer's Guide to Modern Incident Management (2026-09-04): https://www.flashduty.com/en/now/blog/pagerduty-alternatives-2026 — An honest comparison of the top PagerDuty alternatives in 2026 — Flashduty, incident.io, Opsgenie, Grafana OnCall/IRM, Better Stack, and FireHydrant — covering pricing models, AI capabilities, notification coverage, and migration cost.
- Is PagerDuty Too Expensive? How to Calculate On-call Cost for a 100-Person Engineering Team (2026-05-20): https://www.flashduty.com/en/now/blog/pagerduty-on-call-cost — A cost model for comparing PagerDuty and Flashduty On-call: responders, notification-only users, licenses, communication quotas, Add-ons, and the questions teams often miss.
- Is Alertmanager enough? (2026-05-20): https://www.flashduty.com/en/now/blog/prometheus-alertmanager-on-call-platform — Where Prometheus Alertmanager ends and a dedicated On-call platform begins: routing, schedules, automatic escalation, incidents, IM collaboration, and analytics — with a side-by-side selection table and a concrete path for connecting Alertmanager to Flashduty.
- From a Real 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 to find hundreds of documentation gaps, write the missing docs, and open PRs. The fix was not asking engineers to remember docs; it was making drift visible.

## 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
- 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 可以互相派活了 (2026-08-17): https://www.flashduty.com/zh/now/blog/a2a-in-production — 在控制台登记一个外部 Agent，AI SRE 就能把任务整个派过去，进度流式地回到对话里；反过来，AI SRE 自己也提供标准 A2A 接口，可以接受别的 Agent 派活。
- 让 AI SRE 安全地访问你的 Kubernetes 集群：不开公网，不交 kubeconfig (2026-08-17): https://www.flashduty.com/zh/now/blog/ai-agent-kubernetes-access — 把集群接进 AI SRE，我们要三件事同时成立：不开公网、权限收得紧、不做能力表。最后的做法是让 Agent 跑真的 kubectl，但由你的集群主动连出来，权限全部交给 Kubernetes 自己判。
- 介绍 AI SRE Artifacts：把结果留下来，发出去 (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 可以读你的代码仓库了 (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 — 很多团队从群机器人开始做告警治理，但群消息只解决可见性，不解决责任。真正的 On-call 响应要留下 owner、认领、升级、关闭、时间线和复盘。
- 如何把告警风暴变成可处理故障：一套告警降噪实践 (2026-05-20): https://www.flashduty.com/zh/now/blog/alert-storm-noise-reduction-practice — 本文介绍 Flashduty 告警降噪实践，从事件、告警、故障模型出发，梳理标签增强、Pipeline 清洗、告警聚合、风暴预警、抖动检测、静默、抑制和 14 天验证方法。
- 从 MCP 到 CLI：AI SRE 怎么操作整个 Flashduty (2026-07-27): https://www.flashduty.com/zh/now/blog/cli-not-mcp — 一月我们把内置 MCP 挂进 Agent 的每个会话，五月底换成了命令行。为什么没有扩充 MCP，为什么放弃了搜索式加载，切换之后又付出了哪些代价。
- DeepSeek 状态页迁移：从 Atlassian 到 Flashduty (2026-06-10): https://www.flashduty.com/zh/now/blog/deepseek-statuspage-migration — DeepSeek 把公开状态页从 Atlassian Statuspage 迁到了 Flashduty Statuspage。选型看的不只是页面样式，还包括中文、成本、可信度、订阅迁移和故障时的可用性。
- 当监控数据散落在几十套环境里，告警不该跟着碎片化 (2026-09-03): https://www.flashduty.com/zh/now/blog/distributed-data-source-control-plane — 数据源分散是合理现状，但告警规则、运行状态和排障入口不该随之碎片化。Flashduty Monitors 让数据留在私网，把告警和分析能力集中到一个控制面。
- 写给人，也写给 AI 的命令行 (2026-06-08): https://www.flashduty.com/zh/now/blog/flashduty-cli — 我们为什么给一个故障响应平台做命令行工具，又为什么把它做成 AI 编程 Agent 操作 Flashduty 的入口。一篇关于 CLI 设计取舍的工程笔记。
- Flashduty Monitors 支持 Loki 和 VictoriaLogs (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 — 期货行业有多时段交易、高实时性和高风险要求。把管理机制、技术要求和运营机制落到统一的监控事件响应平台，可以提升告警响应速度，降低运维压力。
- SDK 不该比 API 更聪明 (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 把 Borg 开源成了 Kubernetes，把 Borgmon 开源成了 Prometheus，那它内部的 On-call 工具 Outalator 呢？我们拆开 Google SRE 与 Datadog 两套成熟实践，看清 On-call 真正的难点不在工具，并谈谈国内团队能借鉴什么。
- 别让 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：停服倒计时下，值班体系迁去哪里 (2026-09-04): https://www.flashduty.com/zh/now/blog/opsgenie-alternatives-2026 — Opsgenie 将于 2027 年 4 月 5 日停止支持，未迁出数据将被删除。客观盘点 2026 年最值得评估的 Opsgenie 替代方案——Flashduty、Jira Service Management、PagerDuty、incident.io、Better Stack、Grafana Cloud IRM，并给出务实的迁移计划。
- PagerDuty 替代方案 2026：写给工程团队的故障管理选型指南 (2026-09-04): https://www.flashduty.com/zh/now/blog/pagerduty-alternatives-2026 — 客观对比 2026 年主流 PagerDuty 替代方案——Flashduty、incident.io、Opsgenie、Grafana OnCall/IRM、Better Stack、FireHydrant，覆盖计费模式、AI 能力、通知覆盖与迁移成本。
- PagerDuty 太贵？100 人技术团队的 On-call 成本怎么算 (2026-05-20): https://www.flashduty.com/zh/now/blog/pagerduty-on-call-cost — 本文从处理人、通知接收人、License 席位、通信额度和 Add-ons 等维度，拆解 100 人技术团队评估 PagerDuty 与 Flashduty On-call 成本时容易算错的关键问题。
- Alertmanager 够用吗 (2026-05-20): https://www.flashduty.com/zh/now/blog/prometheus-alertmanager-on-call-platform — 从告警路由、值班表、自动升级、故障对象、IM 协同和数据化管理几个维度，拆解 Prometheus Alertmanager 与专业 On-call 平台的职责边界，并给出一张选型对比表和接入 Flashduty 的具体路径。
- 从真实用户报错到修复 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
- 状态页嵌入组件（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 — 我们近期进行了一系列的优化，以下是我们的更新内容：