> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> This page documents important updates and feature releases for Flashduty products

<Update label="2026-08-20" description="☁️ Tencent Cloud CLS data source and mobile War Room support">
  ### Tencent Cloud CLS data source

  Monitoring now supports **Tencent Cloud CLS (Cloud Log Service)** as a data source type:

  * When creating a Tencent CLS data source you can choose the public or internal access mode (choose internal when your Edge instances run inside Tencent Cloud to avoid public traffic charges); authentication uses SecretId/SecretKey, with support for literal values or `${env:VAR_NAME}` environment variable references — the SecretKey is displayed masked after saving
  * Alert rule queries support raw log search (CQL / Lucene) and SQL analysis modes, by region and log topic; raw search windows are capped at 6 hours, SQL analysis at 24 hours
  * Tencent CLS rules can bind exactly one data source; name wildcards are not supported

  ### War Room on mobile

  The Flashduty mobile app now supports the full War Room lifecycle:

  * An entry card on the incident overview deep-links into the IM group chat
  * Create a War Room, add members, and dissolve it from More Actions; adding members and dissolving remain available after the incident is closed for postmortems
  * Requires the On-call Professional plan and at least one IM integration with War Room enabled
</Update>

<Update label="2026-08-19" description="🕒 Incident timeline and alert details experience updates">
  ### Incident timeline redesign

  The incident timeline has been visually and interactively upgraded:

  * Each record now shows the full date and time (`YYYY-MM-DD HH:mm:ss`) by default; hovering switches to a relative time (e.g. "3 minutes ago"). Day-separator rows are no longer inserted
  * New rendering for **reassignment** and **responder-change** events: reassignments (assign or reassign a new responder) and responder changes (updated the responder to) are written into the timeline with member names instead of falling back to the generic display
  * Images in comments and records now open the original image in a new tab when clicked (no more in-page preview)

  ### Alert details tab deep link

  The active tab on the alert details page is controlled by the URL parameter `tab`: appending `?tab=events` to the alert details URL opens the **Associated Events** tab directly, and tab switches are synced to the browser address bar. The **View full event history** entry in the "showing only the latest N alert events" hint on the incident details page uses this mechanism.

  ### Label quick-jump enhancement

  The **View Rule** deep link for `monit.alert` integration labels now recognizes both `rule_id` and `__alert_rule_id` (new data prefers the latter), and renders the link only when the label value is a positive integer; empty or non-numeric values degrade to plain text.
</Update>

<Update label="2026-08-18" description="🔧 Kubernetes App permission details update and quick-silence label exclusion rules">
  ### Kubernetes App permission details update

  The Kubernetes App permission matrix has been updated to clarify what each level can do:

  * No level supports entering a container (exec), Attach, port forwarding, or watch and real-time log following (`-f`) — a limitation of the access method, not of the permission level
  * **Read + limited modifications**: now limited to evicting Pods to restart workloads, scaling Deployments and StatefulSets, and adjusting HPA replica bounds; `kubectl rollout restart` and `kubectl rollout undo` are denied (both are patches to the workload in Kubernetes) — restart by evicting Pods one at a time
  * **Read-only**: read access within the authorized namespaces binds directly to Kubernetes' built-in `view` role, covering non-sensitive resources such as Pods, logs, and ConfigMaps, but never Secrets
  * Rollback: under Read-only and Read + limited modifications, AI SRE derives the target revision and gives you the complete command to run

  ### Quick-silence label exclusion rules

  Labels that hit an exclusion rule no longer participate in quick-silence matching conditions, so similar alerts are not left unsilenced:

  * New account-level configuration: **Organization Profile → Fault Handling → Quick-silence excluded labels**; when creating a quick silence you can see each excluded label and its reason (JSON / Numeric / Datetime / Too long / Globally excluded / Owning integration)
  * Maintain per-integration excluded label lists and toggle system format rules (json / datetime / numeric, all enabled by default); the global blacklist is system-curated and cannot be configured
  * Only the subject account or Account.Admin can modify the rules; other members view them read-only. Changes take effect only for silences created afterwards
</Update>

<Update label="2026-08-17" description="🔎 Structured monitoring datasource queries (monit-query data)">
  ### Structured monitoring datasource queries

  A new stable **structured data query** capability unifies monitoring datasource queries across the CLI, SDK, and Open API:

  * **New API**: `POST /monit/query/data` (`monit-read-query-data`) runs a synchronous query and returns a stable `query_result.v1` structured result (`frames` / `records` / `samples` natural shapes), no longer forcing results into the legacy flattened rows shape; requires monit-edge v0.65.0 or later
  * **CLI**: new `flashduty monit-query data` subcommand supporting 9 datasource types (Prometheus, VictoriaLogs, Loki, MySQL, SLS, Elasticsearch, PostgreSQL, Oracle, ClickHouse), with `--delay-seconds` for point-in-time look-back; the legacy `rows` command is deprecated — migrate to `data`
  * **Go SDK**: `client.Diagnostics.QueryData` provides the typed method; `QueryRows` is deprecated in favor of `QueryData`
</Update>

<Update label="2026-08-14" description="📋 Incident action items, comment types, and Entity Tree views">
  ### Incident action items and follow-ups

  Incident details now support **action items and follow-ups**: pull the things you agreed to do out of the chat and comments and turn them into assignable, trackable, completable entries, with every change recorded on the incident timeline.

  * Two types: **action items** (Action) attach to the incident and capture to-dos during response; **follow-ups** (Follow-up) attach to the post-mortem and track remediation after the review
  * Each work item has a title, description, status, priority, and **assignees**, and the list can be filtered by type and assignee
  * **Assignees-only completion**: assignees can mark a work item complete
  * After the post-mortem, an action item can be **converted into a follow-up**, binding automatically to the incident's post-mortem
  * Creation, updates, completion, conversion, and deletion are all recorded on the timeline
  * Available to **On-call Pro and above** accounts

  ### Comment types

  Timeline comments on incidents now support **comment types**: tag a comment with a colored label such as "Progress update" or "Root cause analysis" so you can find key information at a glance in a long timeline.

  * Account-level configuration: create, rename, recolor, reorder, and delete, up to **10** types per account
  * Type names up to **40** characters, with custom colors (#RRGGBB)
  * Pick a type when publishing a comment; the timeline shows the chosen type

  ### Entity Tree troubleshooting views

  The Entity Tree workspace adds four views that make rule dispatch and execution status visible at a glance:

  * **Runtime status**: see the current availability state (Healthy / Initializing / Unavailable / Unsupported version / Unknown) and its reason, the responsible Edge instance (ID / IP / version / last heartbeat), and the center-vs-Edge plan digest comparison
  * **Deployment plan (debug)**: inspect the execution plan compiled from the saved configuration — data source bindings, groups and matcher conditions, and per-rule, per-severity policies with PromQL; template, plan, and rule digests are one-click copyable for support tickets. The full plan is visible only to entity-category managers
  * **Query preview**: run the condition or recovery PromQL against a selected data source right in the rule editor and read diagnostics such as returned rows, valid entities, and missing-identity, duplicate-alert, and scalar-conflict warnings
  * **Execution history**: review the last **24 hours** of actual evaluations for each rule — the executed PromQL, outcomes, and error summaries; requires VictoriaLogs and caps the display at 200 records

  See [Entity Tree](/en/monitors/entity-tree/entity-tree).
</Update>

<Update label="2026-08-14" description="📈 Alert Rule Experience Upgrade">
  ### Alert Rule Experience Upgrade

  Monitors alert-rule management gets a full upgrade — rule runtime observability, bulk operations, and recovery strategies are now far more flexible:

  * **Per-rule runtime details**: the alert-rule list adds a **Runtime Details** entry showing rule runtime status (Normal / Abnormal / Awaiting first execution / Stale), the last execution time and duration, active-alert instance breakdown (Threshold / AnyData / NoData), and the last **24 hours** of execution history (requires VictoriaLogs, capped at 200 records)
  * **Import/export redesign**: import is now a **file upload** that auto-detects four formats — Flashduty Rules YAML, legacy Flashduty JSON, Prometheus Rules YAML, and Nightingale v6–v9 rule JSON (single file, up to 1MB) — with a conflict policy (skip same-name rules / create copies), pre-import preview, and per-rule selection; export produces a **YAML bundle** (default filename `alert-rules.yaml`) for cross-tenant migration
  * **Bulk metadata editing**: extra labels and custom fields support **incremental patch** (per-key set/delete with value suggestions and impact preview; suggestions disabled beyond 500 selected rules) and **full replacement** modes, with failures reported per rule
  * **Active-alert details**: active alerts gain a per-row **detail drawer** (overview, timing, rule and source, current values, alert dimensions, event labels, alert annotations, diagnostics) and an **Alert Rule** filter; clicking a rule's status cell jumps straight to that rule's active-alert view
  * **Recovery and end modes**: Threshold and AnyData detection add a **Manual close** recovery mode (the alert stays active until closed by hand); no-data alerts gain an **End mode** (auto-end when data reappears / auto-end on recovery or timeout with a configurable auto-close time / manual close only)
  * **Custom-field templating**: custom field values support `${label}` variables and Go templates (a value containing `{{` is rendered like the description template), and a field named `title` becomes the event title
</Update>

<Update label="2026-08-11" description="🧩 Status Page Widgets">
  ### Status Page Widgets

  Public status pages now offer **widgets**: a snippet you can paste into any website's HTML to show your live service status on your own site, help center, or internal system.

  * **Two forms**: the **status badge** always shows the current overall status — ideal for footers and help centers; the **event banner** appears at the top or bottom of the page only during an incident or maintenance, can be dismissed by visitors, and shows scheduled maintenance automatically 24 hours before it starts
  * **Configurable appearance**: theme (Auto / Light / Dark), language (中文 / English), badge size, and banner position
  * **Easy to embed**: go to your status page detail view → **Settings → Widget**, preview live, and copy the embed code in one click (`<script>` + the `<flashduty-status-widget>` Web Component)
  * **Public JSON API**: `GET {status page URL}/api/widget/v1/summary.json` — no key required, with CORS and ETag support, so you can render the data yourself or integrate it into your monitoring stack
  * Available on public status pages only; enabled by default with no configuration needed

  See [Widgets](/en/on-call/statuspage/widgets).
</Update>

<Update label="2026-08-06" description="🔗 Public artifact links and ServiceMap (Beta)">
  ### Artifacts can now be shared with a public link

  The artifact gallery adds a **public link**. Sharing an artifact used to require the recipient to sign in to the same Flashduty account; now you can generate a sign-in-free link and send an investigation write-up or inspection report straight to a customer, an external partner, or a colleague who doesn't have an account yet. This feature is available to **On-call Pro and above** accounts, opening together with the AI SRE public beta.

  * The share panel offers two visibility modes, **Account only** and **Public link**; the default is still account-only
  * A public link shows a **content snapshot** taken when the link was generated and does not sync automatically. When the artifact changes, click **Update snapshot** to sync it — the link itself stays the same
  * **Revoke public link** at any time; the link stops working immediately
  * Artifacts larger than 16 MiB cannot generate a public link

  Before generating, you're warned that anyone with the link can view the artifact and that the link may be forwarded further — don't share secrets, personal information, or unauthorized third-party content.

  Publishable artifact types are also no longer limited to HTML and Markdown: images, PDFs, data files such as CSV / JSON / YAML, common source files, and archives can all be published to the gallery.

  See [Artifacts](/en/ai-sre/artifacts).

  ### ServiceMap (Beta)

  **ServiceMap** automatically builds a dependency topology among hosts, processes, containers, and workloads from the real network connections `monit-agent` observes through eBPF. It doesn't rely on manual configuration or a static architecture diagram — it shows who a machine is actually talking to right now.

  * Filter the topology canvas by resolution status (Confirmed / Candidate / Unresolved), adjust the hop range, and double-click a node to enter focus mode
  * Node and dependency detail panels expose identity, runtime, resolution, and observation fields, so you can judge whether a dependency is trustworthy
  * Unresolved endpoints are grouped by reason, with filtering and CSV export
  * The ServiceMap host list filters by Agent version, Edge cluster, capture mode, and status
  * Query info reports capture mode, evidence freshness, and truncation reasons, so you can tell whether the current topology is complete

  ServiceMap is in beta and relies on `monit-agent`'s eBPF observation — topology data appears only after the Agent supports and enables ServiceMap.

  See [ServiceMap](/en/monitors/targets/servicemap).
</Update>

<Update label="2026-07-28" description="🚀 AI SRE now in open public beta">
  ### AI SRE Open to All Accounts

  AI SRE is now in public beta for every account: no application needed — sign in to the console and start using it. It is not billed separately during the beta.

  * Removed the beta application form and gradual-rollout whitelist; the AI SRE entry is visible to all accounts by default
  * Entry and actions follow the role permissions configured in your account
  * Flashduty will share billing information ahead of general availability

  See [AI SRE](/en/ai-sre) and the [quickstart](/en/ai-sre/quickstart).
</Update>

<Update label="2026-07-08" description="🤖 AI SRE automation, IM, and Runner enhancements">
  ### AI SRE autonomous investigation Agent

  Flashduty AI SRE is now available in beta, bringing conversational autonomous incident investigation to Flashduty. You can describe a problem in natural language and let the Agent plan steps, query monitoring data and logs, execute commands, call MCP tools, delegate work to Subagents when needed, and return a conclusion backed by the investigation process.

  * Start investigation sessions from the console chat workspace and inspect streaming output, tool calls, and conclusions
  * Bring incident or war room context into AI SRE sessions so the Agent investigates a specific incident
  * Extend investigation capabilities with Skills, Knowledge Packs, MCP, and A2A Agents
  * Use `/insight` to review the last 30 days of AI SRE sessions, repeated context, and missing runbooks

  See [AI SRE](/en/ai-sre).

  ### IM-native investigation and automatic war room diagnosis

  AI SRE can now work directly in Slack, Feishu/Lark, Dingtalk, and WeCom. You can mention AI SRE in a group chat or DM to start or continue an investigation, so responders can follow the analysis without switching to the console.

  * Reply in IM threads to keep investigation discussions focused
  * Automatically run an initial diagnosis when a war room is created and post the result back to the room
  * Use `/env` to switch the Environment bound to the current IM session
  * Use `/scope` to switch the team scope bound to the current IM session

  See [IM platform](/en/ai-sre/im).

  ### Automation and BYOC Runner

  AI SRE adds Automations, which run hidden sessions on a schedule, through an API trigger, or from On-call incident events to produce health checks, insights, or post-incident reviews.

  * Trigger Automations with cron schedules, HTTP POST, or On-call incidents
  * Use preset templates, run history, manual runs, and read-only permission controls
  * Choose automatic Environment selection, cloud Sandbox, or a self-hosted BYOC Runner
  * Run the Runner with Linux systemd, Docker, or manual mode, and constrain command execution through a local permission config

  See [Automations](/en/ai-sre/automations) and [Environments](/en/ai-sre/environments).
</Update>

<Update label="2026-06-25" description="📱 RUM miniprogram, HarmonyOS, and mobile symbolication">
  ### WeChat Mini Program RUM

  RUM adds the WeChat Mini Program SDK and insights dashboard, helping you collect and analyze real user experience data from mini programs.

  * Automatically collect page lifecycle events, user actions, network requests, application errors, and performance metrics
  * Configure `service`, `env`, `version`, session sample rate, and proxy reporting
  * Use the new WeChat Mini Program insights dashboard for UV, sessions, errors, launch time, first render, and `setData` metrics
  * Analyze performance trends by version, environment, loading type, and operating system

  See [WeChat Mini Program SDK integration](/en/rum/sdk/wechat-miniprogram/sdk-integration) and [WeChat Mini Program insights](/en/rum/analytics/miniprogram).

  ### HarmonyOS SDK

  RUM adds HarmonyOS NEXT SDK documentation covering RUM, Trace, and Crash integration for ArkTS applications.

  * Use the `@flashcatcloud/core`, `@flashcatcloud/rum`, `@flashcatcloud/trace`, and `@flashcatcloud/crash` modules
  * Collect views, user actions, network requests, errors, and crash events
  * Inject Trace context through the `rcp` interceptor or the `FlashcatHttp` wrapper
  * Follow guidance for HarmonyOS SourceMap and native symbol file uploads

  See [HarmonyOS SDK integration](/en/rum/sdk/harmony/sdk-integration).

  ### Mobile symbolication and compliance guide

  RUM source management now covers more mobile scenarios, helping you restore obfuscated or compiled stack traces in error details.

  * Upload WeChat Mini Program `sourcemap.zip` files and restore mini program stacks
  * Upload Android ProGuard/R8 mapping files and NDK native symbol files
  * Upload iOS dSYM symbol files
  * Use the new SDK developer compliance guide for privacy policy disclosure, delayed initialization, collected fields, and data that the SDK does not collect
  * Use the new Web SDK performance impact guide for SDK size, CPU, memory, network overhead, and Session Replay sampling recommendations

  See [SourceMap and symbol file management](/en/rum/error-tracking/source-mapping), [SDK developer compliance guide](/en/rum/others/compliance-guide), and [Web SDK performance impact](/en/rum/sdk/web/performance-impact).
</Update>

<Update label="2026-05-25" description="🔌 Pull-based alert integrations and developer tooling">
  ### HTTP Pull and DB Pull alert integrations

  On-call adds two pull-based alert integrations for systems that cannot push webhooks or need to decouple alert querying from alert delivery.

  * **HTTP Pull**: Periodically call an external HTTP endpoint, with support for GET/POST, headers, request bodies, timeouts, retries, cursor pagination, and severity mapping
  * **DB Pull**: Periodically query MySQL, PostgreSQL, or ClickHouse and convert rows into standard alert events through field mappings
  * DB Pull uses Keyset Pagination with time and ID cursors to pull incrementally and avoid full table scans
  * Both integrations support dedicated and shared integration modes, and can route events into target channels through default routing and routing rules

  See [HTTP Pull](/en/on-call/integration/alert-integration/alert-sources/http-pull) and [DB Pull](/en/on-call/integration/alert-integration/alert-sources/db-pull).

  ### Dynamic assignment append mode

  Dynamic assignment adds append mode. You can keep the original notification targets in a template escalation rule and append extra responders, teams, or group chat bots from alert labels.

  * Use `reset` mode to replace targets in the template escalation rule
  * Use `append` mode to add notification targets, useful when you want to keep a default team and add business owners
  * Combine label mapping with CMDB, configuration platforms, or CSV data to generate dynamic assignment labels automatically

  See [Dynamic assignment with external data](/en/on-call/practices/dynamic-dispatch-with-external-data).

  ### CLI, Go SDK, and Open API

  Developer tooling continues to expand across terminal workflows, typed SDK usage, and API reference coverage.

  * Flashduty CLI manages incidents, changes, members, teams, channels, status pages, and notification templates from the terminal
  * CLI supports `table`, `json`, and `toon` output formats, plus install, update, and mirror download configuration
  * The Go SDK wraps the Open API in a go-github-style typed client, covering 288 API operations across 32 services
  * The Open API reference continues to add AI SRE, RUM, On-call, and Platform endpoints

  See [CLI](/en/developer/cli), [Go SDK](/en/developer/go-sdk), and [Open API](/en/openapi/introduction).
</Update>

<Update label="2026-04-07" description="📡 Status Page RSS/Atom Subscriptions and Incident List Enhancements">
  ### RSS/Atom Feeds for Public Status Pages

  Public status pages now expose event feeds in both RSS 2.0 and Atom 1.0 formats. Visitors can subscribe through any RSS reader or automation tool — no email confirmation required:

  * Every public page serves four URLs: `feed.rss`, `feed.atom`, `history.rss`, and `history.atom`. The `history.*` pair is an alias for Atlassian Statuspage compatibility
  * Feeds include incidents and maintenance events published in the last 90 days, up to 50 items, ordered by start time descending
  * Hidden sections and components are automatically filtered out and do not appear in the feed
  * Responses support `ETag` / `If-None-Match` and return `304 Not Modified` on cache hits

  See [Subscription management](/en/on-call/statuspage/subscriptions) for details.

  ### Team Filter on the Incident List

  The global **Incident Management** incident list adds a **Teams** filter that narrows incidents by the team that owns each channel. The filter is hidden automatically when you drill into a single channel.

  ### New Alert Events Counter on Incident Rows

  Each incident row now surfaces an **alert events** counter alongside the existing **associated alerts** count. When a new event has been merged in the past 5 minutes, the merge icon turns orange, making it easy to spot incidents that are still actively aggregating. Hovering reveals the associated alert count, associated event count, and the time of the most recent merge.
</Update>

<Update label="2026-03-25" description="🤖 AI Post-Mortem, AI Assistant, and External Incident Submission">
  ### AI Post-Mortem Report

  After incident resolution, how do you quickly capture lessons learned and prevent recurrence? Flashduty introduces **AI Post-Mortem Reports**, automatically generating structured post-mortem documents based on incident timelines and alert data:

  * **One-click Generation**: AI automatically distills incident overview, impact scope, root cause analysis, and improvement recommendations
  * **Collaborative Editing**: Multiple team members can edit the post-mortem report online with real-time sync
  * **Access Control**: Set access permissions for post-mortem reports to protect sensitive information
  * **Image Support**: Upload and embed images directly in post-mortem reports

  ### AI Assistant

  A new **AI Assistant** is now embedded in the console, providing intelligent incident investigation and operations support:

  * **Instant Q\&A**: Chat with AI directly in the console to quickly get incident investigation suggestions
  * **Mermaid Diagram Rendering**: AI-generated flowcharts and architecture diagrams are rendered visually with zoom and fullscreen support
  * **Image Paste**: Paste screenshots directly from your clipboard for easy context sharing
  * **Document Search**: Intelligent retrieval and answers based on the Flashduty knowledge base

  ### External Incident Submission

  New **External Incident Submission** feature allows external users (such as customers or partners) to submit incidents without logging in:

  * Submit incidents via API or a standalone page
  * Upload screenshots and attachments with submissions
  * Automatically match escalation rules for incident assignment

  ### SSO Subdomain Login

  Configure a dedicated subdomain for your tenant, allowing members to sign in directly through the subdomain for a simplified SSO authentication flow:

  * Account administrators can configure a dedicated login subdomain
  * Supports automatic account switching based on subdomain
  * SSO-synced users can be set as non-editable to prevent manual changes from overriding SSO data

  ### Other Optimizations

  1. **Manual Incident Metadata Override**: Manually modify incident title, description, and severity
  2. **Voice Notification Templates**: Voice notifications now support customizable templates instead of fixed formats
  3. **Webhook Custom Payload**: Incident webhooks support user-defined request body formats
  4. **Push Comments by alert\_key**: New API to push comments to incidents via alert key
  5. **War Room Message Limit Increase**: Increased war room message capacity for more complete incident communication records
</Update>

<Update label="2026-03-20" description="🔌 Five New Integrations and Active Alerts">
  ### New Alert Integrations

  Five new monitoring system integrations added, further expanding Flashduty's data ingestion capabilities:

  * **JD Cloud**: Support for JD Cloud monitoring alert ingestion
  * **KS Cloud**: Support for KS Cloud monitoring alert ingestion
  * **UCloud**: Support for UCloud monitoring alert ingestion
  * **Harbor**: Support for Harbor container registry alert ingestion
  * **Nagios**: Support for Nagios monitoring alert ingestion

  ### Monitors Active Alerts

  The Monitors module introduces **Active Alerts**, providing a real-time view of currently firing alerts:

  * Browse active alerts by folder
  * Flexible filtering based on labels
  * Prometheus-compatible label values query API (`/api/v1/label/:label/values`)

  ### Other Optimizations

  1. **Custom Action Fields Expanded**: Custom webhook actions support additional fields
  2. **Feishu War Room Chat History**: Retrieve chat message history from Feishu war rooms
  3. **Webhook Secret Verification Skip**: Webhook integrations can optionally skip secret verification
  4. **Custom Webhook Retry**: Custom webhooks support configurable retry conditions and automatic retry
</Update>

<Update label="2026-02-28" description="📱 RUM Mobile Source Map and Monitors Enhancements">
  ### RUM Mobile Source Map

  The RUM module now supports **iOS and Android** source map upload and parsing:

  * After uploading mobile source map files, error stacks are automatically resolved to readable source code locations
  * Supports iOS dSYM and Android Proguard/R8 mapping files

  ### RUM Error Ingestion Exclusion Rules

  New **Error Ingestion Exclusion Rules** allow you to configure rules to filter out errors you don't need to monitor:

  * Set exclusion rules by error type, message content, and other conditions
  * Excluded errors no longer count toward ingestion volume

  ### Issue Preset Severity

  Pre-configure severity levels for different issue types. Newly created issues automatically inherit the preset severity.

  ### Monitors Edge Enhancements

  * **VictoriaLogs Support**: New VictoriaLogs data source with raw query capability
  * **Fluent-bit Integration**: New Fluent-bit data source support
  * **Loki Query Optimization**: Support `loki.start`/`loki.end` time parameters as first priority, raw query mode
  * **Template Function Expansion**: Alert rule templates gain `timeFormat` function and the Sprig template function library

  ### Flashduty MCP Server V2

  The Flashduty MCP Server has been completely rewritten, providing AI tools (such as Claude) with more powerful Flashduty API integration:

  * Streamlined tool set for improved interaction efficiency
  * New `/mcp` endpoint
  * Structured logging with distributed tracing support
</Update>

<Update label="2025-12-30" description="🗓 Status Page: Service Down, Trust Online">
  Service interruptions are inevitable, but trust shouldn't go offline with them. Flashduty Status Page is designed to break the information opacity barrier:

  **Reduce Repetitive Tickets at the Source**

  Instead of responding passively, let information lead the way. The status page provides users with service status they can check anytime, while supporting subscription to service updates. When an incident occurs, the latest progress is automatically pushed to subscribers.

  **Make Service Maintenance Transparent and Controllable**

  The status page not only reports unexpected incidents but also makes planned maintenance crystal clear. By announcing maintenance windows in advance, users can clearly understand the timing and scope of service adjustments.

  **Prove Stability with Data**

  The status page automatically accumulates historical availability data, transforming abstract SLA commitments into intuitive, verifiable uptime records.

  Go to **Flashduty Console → On-call → Status Page** to try it out.
</Update>

<Update label="2025-12-16" description="🚀 Routing Rules Upgrade">
  This update comprehensively enhances **Alert Routing** capabilities:

  ![Routing Rules Upgrade](https://cloud.headwayapp.co/changelogs_images/images/big/000/152/348-e086902430708fd69a24cd50af51505838ab04e0.png)

  **1. Name Mapping Auto-routing Support**

  New Name Mapping capability allows automatic routing of alerts to **channels with the same name as the label value** based on `labels` in the alert.

  Example:

  * `labels.application_name = "order-service"`
  * Alert will be automatically routed to the channel named `order-service`

  **2. Channel Filtering and Sorting**

  When there are many routing rules, you can now **filter and sort by channel dimension** to quickly locate target rules.

  **3. Routing Rules UI Optimization**

  * Support **drag-and-drop sorting** of routing rules for flexible priority adjustment
  * Optimized rule content display with clearer conditions and actions
  * Cleaner overall layout, reducing configuration and troubleshooting costs
</Update>

<Update label="2025-12-04" description="War Room Launch, Change Management Upgrade">
  ### War Room

  Emergency incident handling is often time-critical, and quickly aligning teams for efficient collaboration is key. Now you can **launch a war room with one click**:

  ![War Room Demo](https://cloud.headwayapp.co/changelogs_images/images/big/000/151/828-00d455e82acf0fad62f37fc56b9aad9c12a48127.gif)

  * **Instant Group Creation**: One-click creation of Feishu/Lark, Dingtalk, WeCom, or Slack group chats, automatically inviting responders and stakeholders
  * **Message Sync**: Incident message cards are automatically delivered to the group, always pinned and updated with the latest status in real-time

  ### Webhook Call History

  Troubleshooting webhook call issues no longer requires guesswork. The system now supports **complete call history tracking**:

  ![Webhook Call History Demo](https://cloud.headwayapp.co/changelogs_images/images/big/000/151/829-ef682fe28b82e888bf2959c34db90935bfa9fff0.gif)

  * Call status and error codes
  * Retry count
  * Complete request and response information

  ### Change History

  Significantly enhanced change event management capabilities:

  ![Change History Page](https://cloud.headwayapp.co/changelogs_images/images/big/000/151/825-6c9743f0cc130b014cc7708eeffe44c72dc2ecd3.png)

  * **Dynamic Routing**: Change events can be automatically routed to relevant channels based on business
  * **Label Enhancement**: Support secondary processing of reported events
  * **New View**: Change history page upgraded with custom view support

  ### Other Optimizations

  1. **Incident List**: Support batch assignment of incidents
  2. **Outlier Incidents**: Support disabling outlier incident detection
  3. **Alert Storm Reminder**: Support configuring multiple storm thresholds for tiered progressive reminders
  4. **Escalation Rule**: Group chat channel configuration can specify application severity
  5. **Incident Details**: Support custom label sorting, support displaying incident labels in JSON format
  6. **Integration Center**: Added Zoho ServiceDesk Plus and Cloudflare integrations
</Update>

<Update label="2025-08-22" description="🚀 AI Summary and ServiceNow Integration">
  ### AI Summary

  New AI Summary feature for quick incident detail extraction, especially useful for scenarios with many grouped alerts:

  ![AI Summary](https://cloud.headwayapp.co/changelogs_images/images/big/000/148/044-90d26730e010f5f8847b4e469f405380f626c7d5.gif)

  Summary focuses on:

  1. Event overview (key information)
  2. Impact scope (resources, services, etc.)
  3. Actionable measures (investigation, mitigation, prevention)

  ### ServiceNow Integration

  New ServiceNow integration with bidirectional incident information sync:

  ![ServiceNow Integration](https://cloud.headwayapp.co/changelogs_images/images/big/000/148/045-485a3bd95fee17d699be776e1947885c220f7cbf.png)

  1. Support manual and automatic sync triggers
  2. Support bidirectional sync between Flashduty and ServiceNow

  ### Mobile App Optimization

  The new Flashduty mobile app is now available on app stores:

  ![Mobile App](https://cloud.headwayapp.co/changelogs_images/images/big/000/148/049-e56be0319a68d40ed031c399763ebc4ec1cc282d.png)

  1. Added English version support
  2. Integrated AI Summary feature
  3. Incident details now include custom fields, optimized label display and text editing experience

  ### Insights

  Insights now supports filtering incidents by labels and custom fields:

  ![Insights](https://cloud.headwayapp.co/changelogs_images/images/big/000/148/047-144590886dcf8a75bdac24aa0c78595ba20f52f4.png)

  ### Microsoft Teams

  Teams app now supports sending incident assignment notifications to channels or groups:

  ![Microsoft Teams](https://cloud.headwayapp.co/changelogs_images/images/big/000/148/048-9cb47b5257eef934d6a9a22c3a08aaf5dfcd0c29.png)

  ### WeCom/Zoom/Feishu Bot

  ![Bot Optimization](https://cloud.headwayapp.co/changelogs_images/images/big/000/148/046-67b92d32a22a0cd943d023c382c7d93467d22186.png)

  1. Support uploading email and account ID mappings for Feishu/Lark and other platforms
  2. Escalation rules support binding mappings for precise @ mentions in group chat pushes
</Update>

<Update label="2025-06-17" description="June Series Updates">
  ### Link Integration

  Seamless association with external systems, supporting direct jump to CMDB host information page based on machine hostname:

  ![Link Integration Demo](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/200-5d9fef4cac5fe7bb950f9cb97a21a4128541ca6a.gif)

  ### Dingtalk and Feishu/Lark Alert Integration

  New support for receiving alert notifications via Dingtalk and Feishu/Lark Webhooks:

  ![Dingtalk Feishu Alert](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/206-44af3f0ae28283cf823e9982f0b432f44ec71fdf.png)

  ### Incident Merge Interaction Optimization

  Support fuzzy matching and deletion of merged incidents:

  ![Incident Merge Optimization](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/201-ba1f42f501a339f9c0ff406db3b8fa4923611377.png)

  ### Intelligent Alert Grouping Supports Custom Fields

  Allow calculating alert similarity based on specified fields:

  ![Intelligent Grouping](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/202-8927673faaa9ca669b2a16a204767bf19d61fae5.png)

  ### Incident Auto-close Timeout Optimization

  New countdown close feature based on the time of the last merged event:

  ![Timeout Close](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/203-1d795abb9db79575ca7c31240103bd64afb63195.png)

  ### Shared Integration Permission Management

  Support setting management teams for shared integrations:

  ![Shared Integration](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/204-9467b061f4b9919a291c3429d198ee70f2cc24c6.png)

  ### Incident Convergence Upgraded to Flapping Detection

  After an incident enters flapping state, you can choose to continue notifications or silence notifications:

  ![Flapping Detection](https://cloud.headwayapp.co/changelogs_images/images/big/000/145/205-f9c946b89be5817b3ef4c30973f1121593f536e2.png)
</Update>

<Update label="2025-05-09" description="Fixed License and Routing Version Management">
  ### License Management

  ![License Management](https://cloud.headwayapp.co/changelogs_images/images/big/000/143/555-f08092c9a42b8c876321834eea45a161b43315f4.png)

  1. **New Fixed License Type**: Permanently valid, cannot be preempted
  2. **Flexible License Assignment**: Account administrators can set fixed or temporary licenses for members
  3. **Member Self-management**: Regular members can voluntarily release their own license
  4. **API Batch Operations**: Support batch setting member license types via API

  ### Routing Version Management

  ![Routing Version Management 1](https://cloud.headwayapp.co/changelogs_images/images/big/000/143/557-7a82761dfdb87f60a126a6a46607f4de31128d6f.png)

  ![Routing Version Management 2](https://cloud.headwayapp.co/changelogs_images/images/big/000/143/556-38beeebdd807b739c1f8eda2a5d1fbdb220d4863.png)

  1. **Historical Version Viewing**: Integration center alert routing now supports viewing historical versions
  2. **Version Comparison**: Support comparing current routing rules with historical versions
  3. **One-click Rollback**: Support rollback to any historical version of routing rules
</Update>

<Update label="2025-03-06" description="Jira Integration and New Template Management Launch">
  ### Jira Integration

  ![Jira Integration Interface](https://cloud.headwayapp.co/changelogs_images/images/big/000/140/906-aa17e83817bdbf69d7d47155f63f78b64c5dca77.png)

  * Manually or automatically sync incident information to Jira Issues
  * Support both Jira Cloud and Server versions
  * Sync incidents within a limited scope
  * Incident field mapping management

  ### Template Management

  ![Template Management Interface](https://cloud.headwayapp.co/changelogs_images/images/big/000/140/905-ae51b086b40d31a1039b34e21a14d9649ab1b0f1.png)

  * **New Interaction Design**: Template management interface redesigned
  * **Historical Incident Preview Debugging**: Support selecting historical incidents for template preview and debugging
  * **Smart Input Hints**: System automatically provides suggestions after typing `{{`

  ### Other Optimizations

  * **IM Integration**: Added support for Feishu/Lark and Dingtalk private deployment versions
  * **Incident Webhook**: Support subscribing to incident comment events
  * **Incident Convergence**: New incident convergence feature, can be enabled or disabled
</Update>

<Update label="2025-02-25" description="🚀 Flashduty APP Launch">
  Flashduty mobile App is officially launched!

  ![Flashduty APP](https://cloud.headwayapp.co/changelogs_images/images/big/000/140/469-8d5defe3d1720ba623d075f5cfb1d735d2af4096.png)

  ### Incident Management at Your Fingertips

  * **Full Mobile Workflow**: Support incident search, detail viewing, acknowledgment, closing, escalation, and manual triggers, improving key operation response speed by 40%
  * **Multi-dimensional Information Aggregation**: Incident timeline, processing records, and associated logs displayed together

  ### Important Notifications, Never Missed

  * **iOS Critical Alerts**: Based on Apple's official Critical Alerts protocol, breaking through Do Not Disturb mode restrictions
  * **Android System-level Channels**: Support system-level channels for all major Android manufacturers

  ### Voice Notifications, More Reliable

  * **Smart Whitelist Sync**: Automatically add Flashduty voice numbers to phone contacts
</Update>

<Update label="2025-01-23" description="Mapping Data Management">
  The label enhancement feature has been well-received since launch, especially for label mapping combined with mapping data.

  ![Mapping Data Management](https://cloud.headwayapp.co/changelogs_images/images/big/000/139/052-4b2cc783915b5ca395d863bca3eefd7d91a46863.png)

  Now, we've added **Mapping Data Management** in the console, allowing you to conveniently operate data directly in the interface without relying on API.
</Update>

<Update label="2025-01-14" description="Insights Dashboard Upgrade">
  ### Added Metric Viewing Dimensions

  Metric aggregation dimensions expanded from global and time dimensions to viewing by team, channel, individual, and more:

  ![Metric Viewing Dimensions](https://cloud.headwayapp.co/changelogs_images/images/big/000/138/649-f14073799a2ea52460634945e0b72c2fe7da18cf.png)

  ### Time Period Segmentation

  Time is now divided into three stages:

  ![Time Period Segmentation](https://cloud.headwayapp.co/changelogs_images/images/big/000/138/650-84cbbc10e13a1db9dc55d24bd86d9da1ba2c0cf8.png)

  * Work hours: Weekdays 8am-7pm
  * Rest hours: Weekdays 7pm-11pm, Non-weekdays 8am-11pm
  * Sleep hours: Every day 11pm-8am

  ### New Workload Metrics

  ![Workload Metrics](https://cloud.headwayapp.co/changelogs_images/images/big/000/138/651-b333a287e28dde3786cfcf0a0cb55b4375440eda.png)

  * Interruptions: High-priority messages like SMS, phone calls, and app pushes are marked as interruptions
  * Response Effort: Sum of time between member acknowledging incident and incident resolution

  ### Report Download and Data Export

  ![Report Download](https://cloud.headwayapp.co/changelogs_images/images/big/000/138/652-30e67a692391bdb35f68186b499694168b5bfe16.png)

  You can now print reports directly in the console, and export to CSV for secondary analysis below each report.
</Update>

<Update label="2024-12-09" description="Alert Processing Pipeline Official Launch">
  Officially released **Alert Processing Pipeline feature** with comprehensive optimization of integration interaction experience.

  ![Alert Processing Pipeline](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/482-777b434c140376043fd957131cfaa9527b514777.png)

  Now you can easily implement severity reset, title modification, filtering, CMDB integration, and various other operations.

  Update highlights:

  1. **New Alert Processing Feature**: Support multiple execution actions
  2. **Optimized Label Enhancement and Routing Rules Configuration**: Added right-side alert history panel to assist rule debugging
</Update>

<Update label="2024-12-09" description="Incident Data Isolation Upgrade">
  ### Channel Access Level

  Channels now support **access levels**. When set to **Private**, incident data is only available to team members and account administrators:

  ![Access Level](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/474-710a0d713540f34063d00b59d918930fcee48ad8.png)

  ### My Channels Filter

  Incident list now supports **My Channels** filtering:

  ![My Channels Filter](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/475-02984507bcc1481dcd2c0ec4f1bf17858d80465f.png)

  ### Data Isolation Best Practices

  * **Personnel Isolation**: Register multiple owners directly, with complete isolation of personnel and resources
  * **Resource Isolation**: Set channel access level to private
  * **Visual Experience**: Keep incident list always filtered to my channels
</Update>

<Update label="2024-12-06" description="Schedule Management Comprehensive Upgrade">
  ### On-call Rotation Notifications Support Scheduled Notifications

  Commonly used for weekly on-call with daily reminders:

  ![Scheduled Notifications](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/457-2ffc5195d9ade8031116d80bb6e0f54fd8180271.png)

  ### On-call Rotation Notification Content and Style Optimization

  Prominently displays current on-call information with next shift:

  ![Rotation Notifications](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/469-e37f27f2881da7f0b0b2ea9e57a5bce05620e4e1.png)

  ### New Date Mask Mode

  Only selected dates participate in on-call, commonly used for separate scheduling on weekdays and weekends:

  ![Date Mask](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/458-d5ccb3f55fb411f0145bf385b8312b81a0bde5b6.png)

  ### Other Optimizations

  ![Schedule Preview](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/459-9129bf4655974b1fc9f18463c93c02ed2e88b59c.png)

  1. Schedule preview adds 2-week mode
  2. Schedule preview calendar mode, color changed from following rules to following rotation
  3. Added **Highlight My On-call** button
</Update>

<Update label="2024-12-05" description="English Version Launch">
  Launched complete English support, covering console, help documentation, and developer documentation:

  ![English Version Settings](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/485-36ce4a3fbd34d81f411d151f01501bc9fb35140f.png)

  1. **Browser Language Setting**: All members can now freely switch browser display language in the console
  2. **Notification Language Setting**: Account owners can select the default notification language in "Account Settings"
</Update>

<Update label="2024-12-05" description="Added CTYun and Guance Alert Integrations">
  ### CTYun Alert Integration Support

  ![CTYun](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/404-276b48310ad0116488110755c50b86c7424c3ba9.png)

  ### Guance Alert Integration Support

  ![Guance](https://cloud.headwayapp.co/changelogs_images/images/big/000/137/403-df2199adc282280e67877c17ec111dc4bce056dd.png)
</Update>

<Update label="2024-11-13" description="📣 Mobile New UI, Better Looking, More Powerful">
  ![Mobile New UI](https://cloud.headwayapp.co/changelogs_images/images/big/000/136/359-09edd45873a93d97f9fdf4b320ef15e354e5105a.png)

  1. Brand new UI interaction design
  2. New incident list page with rich filtering support
  3. New incident details page supporting common actions and custom actions
  4. New incident creation support with escalation rule and direct assignment
  5. New dark theme switching support
</Update>

<Update label="2024-11-04" description="📣 AIops! Intelligent Grouping, Outlier Incidents, Past Incidents">
  ### Intelligent Grouping

  Alert grouping adds intelligent grouping mode where the system can automatically identify and group similar alerts together:

  ![Intelligent Grouping](https://cloud.headwayapp.co/changelogs_images/images/big/000/135/951-689290c7cafff66115deeef4970b6a6cf257175a.png)

  ### Outlier Incidents

  If a newly triggered incident is not similar to any incidents in the channel within the past 30 days, the system will mark it as an "outlier incident":

  ![Outlier Incidents](https://cloud.headwayapp.co/changelogs_images/images/big/000/135/955-154ab989dabe27c1498dce8cbd243c2729492111.png)

  ### Past Incidents

  Past incidents feature shows historical incidents similar to the current incident, helping you trace issues, find root causes, and reference resolutions:

  ![Past Incidents](https://cloud.headwayapp.co/changelogs_images/images/big/000/135/952-8dd907024b614a98399f3c62bea6d0f64e429382.png)

  <Note>The above features are only available in Pro plan</Note>
</Update>

<Update label="2024-10-12" description="📣 Inhibit and Silence Rule Adjustment">
  **Before Change**

  * Matched silence or inhibit rules before incident assignment notification, blocking incident **notification** if matched

  **After Change**

  * Match silence or inhibit rules during alert event delivery, blocking incident **generation** if matched
  * Blocked alerts will no longer trigger or merge into incidents
  * You can choose to retain or discard blocked alerts
</Update>

<Update label="2024-10-11" description="September Interaction Optimizations">
  1. Console requires secondary confirmation before clicking custom actions
  2. Newly created channels displayed at the top
  3. Create incident page adds escalation rule specification, supports markdown description
  4. Assignment records display dynamic assignment reset indicator
  5. Video demo entries added near core feature points
  6. Escalation rule single chat unified configuration supports not setting channel for certain severity levels
  7. Incident reassignment removes current responder
</Update>

<Update label="2024-09-24" description="Meraki and OpManager Integrations">
  ![Integrations](https://cloud.headwayapp.co/changelogs_images/images/big/000/134/097-3b5cee5cdfa63d64a215388ed3fde27c6ac8559b.png)

  1. Support Zabbix v7 version alert integration
  2. Support InfluxData v2 version alert integration
  3. Support Meraki alert integration
  4. Support Zoho OpManager alert integration
</Update>