You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<Updatelabel="2026-07-08"description="🤖 AI SRE automation, IM, and Runner enhancements">
8
+
9
+
### AI SRE autonomous investigation Agent
10
+
11
+
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.
12
+
13
+
- Start investigation sessions from the console chat workspace and inspect streaming output, tool calls, and conclusions
14
+
- Bring incident or war room context into AI SRE sessions so the Agent investigates a specific incident
15
+
- Extend investigation capabilities with Skills, Knowledge Packs, MCP, and A2A Agents
16
+
- Use `/insight` to review the last 30 days of AI SRE sessions, repeated context, and missing runbooks
17
+
18
+
See [AI SRE](/en/ai-sre).
19
+
20
+
### IM-native investigation and automatic war room diagnosis
21
+
22
+
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.
23
+
24
+
- Reply in IM threads to keep investigation discussions focused
25
+
- Automatically run an initial diagnosis when a war room is created and post the result back to the room
26
+
- Use `/env` to switch the Environment bound to the current IM session
27
+
- Use `/scope` to switch the team scope bound to the current IM session
28
+
29
+
See [IM platform](/en/ai-sre/im).
30
+
31
+
### Automation and BYOC Runner
32
+
33
+
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.
34
+
35
+
- Trigger Automations with cron schedules, HTTP POST, or On-call incidents
36
+
- Use preset templates, run history, manual runs, and read-only permission controls
37
+
- Choose automatic Environment selection, cloud Sandbox, or a self-hosted BYOC Runner
38
+
- Run the Runner with Linux systemd, Docker, or manual mode, and constrain command execution through a local permission config
39
+
40
+
See [Automations](/en/ai-sre/automations) and [Environments](/en/ai-sre/environments).
41
+
42
+
</Update>
43
+
44
+
<Updatelabel="2026-06-25"description="📱 RUM miniprogram, HarmonyOS, and mobile symbolication">
45
+
46
+
### WeChat Mini Program RUM
47
+
48
+
RUM adds the WeChat Mini Program SDK and insights dashboard, helping you collect and analyze real user experience data from mini programs.
49
+
50
+
- Automatically collect page lifecycle events, user actions, network requests, application errors, and performance metrics
- Use the new WeChat Mini Program insights dashboard for UV, sessions, errors, launch time, first render, and `setData` metrics
53
+
- Analyze performance trends by version, environment, loading type, and operating system
54
+
55
+
See [WeChat Mini Program SDK integration](/en/rum/sdk/wechat-miniprogram/sdk-integration) and [WeChat Mini Program insights](/en/rum/analytics/miniprogram).
56
+
57
+
### HarmonyOS SDK
58
+
59
+
RUM adds HarmonyOS NEXT SDK documentation covering RUM, Trace, and Crash integration for ArkTS applications.
60
+
61
+
- Use the `@flashcatcloud/core`, `@flashcatcloud/rum`, `@flashcatcloud/trace`, and `@flashcatcloud/crash` modules
62
+
- Collect views, user actions, network requests, errors, and crash events
63
+
- Inject Trace context through the `rcp` interceptor or the `FlashcatHttp` wrapper
64
+
- Follow guidance for HarmonyOS SourceMap and native symbol file uploads
65
+
66
+
See [HarmonyOS SDK integration](/en/rum/sdk/harmony/sdk-integration).
67
+
68
+
### Mobile symbolication and compliance guide
69
+
70
+
RUM source management now covers more mobile scenarios, helping you restore obfuscated or compiled stack traces in error details.
71
+
72
+
- Upload WeChat Mini Program `sourcemap.zip` files and restore mini program stacks
73
+
- Upload Android ProGuard/R8 mapping files and NDK native symbol files
74
+
- Upload iOS dSYM symbol files
75
+
- Use the new SDK developer compliance guide for privacy policy disclosure, delayed initialization, collected fields, and data that the SDK does not collect
76
+
- Use the new Web SDK performance impact guide for SDK size, CPU, memory, network overhead, and Session Replay sampling recommendations
77
+
78
+
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).
79
+
80
+
</Update>
81
+
82
+
<Updatelabel="2026-05-25"description="🔌 Pull-based alert integrations and developer tooling">
83
+
84
+
### HTTP Pull and DB Pull alert integrations
85
+
86
+
On-call adds two pull-based alert integrations for systems that cannot push webhooks or need to decouple alert querying from alert delivery.
87
+
88
+
-**HTTP Pull**: Periodically call an external HTTP endpoint, with support for GET/POST, headers, request bodies, timeouts, retries, cursor pagination, and severity mapping
89
+
-**DB Pull**: Periodically query MySQL, PostgreSQL, or ClickHouse and convert rows into standard alert events through field mappings
90
+
- DB Pull uses Keyset Pagination with time and ID cursors to pull incrementally and avoid full table scans
91
+
- Both integrations support dedicated and shared integration modes, and can route events into target channels through default routing and routing rules
92
+
93
+
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).
94
+
95
+
### Dynamic assignment append mode
96
+
97
+
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.
98
+
99
+
- Use `reset` mode to replace targets in the template escalation rule
100
+
- Use `append` mode to add notification targets, useful when you want to keep a default team and add business owners
101
+
- Combine label mapping with CMDB, configuration platforms, or CSV data to generate dynamic assignment labels automatically
102
+
103
+
See [Dynamic assignment with external data](/en/on-call/practices/dynamic-dispatch-with-external-data).
104
+
105
+
### CLI, Go SDK, and Open API
106
+
107
+
Developer tooling continues to expand across terminal workflows, typed SDK usage, and API reference coverage.
108
+
109
+
- Flashduty CLI manages incidents, changes, members, teams, channels, status pages, and notification templates from the terminal
110
+
- CLI supports `table`, `json`, and `toon` output formats, plus install, update, and mirror download configuration
111
+
- The Go SDK wraps the Open API in a go-github-style typed client, covering 288 API operations across 32 services
112
+
- The Open API reference continues to add AI SRE, RUM, On-call, and Platform endpoints
113
+
114
+
See [CLI](/en/developer/cli), [Go SDK](/en/developer/go-sdk), and [Open API](/en/openapi/introduction).
115
+
116
+
</Update>
117
+
7
118
<Updatelabel="2026-04-07"description="📡 Status Page RSS/Atom Subscriptions and Incident List Enhancements">
0 commit comments