From 12025435ce09624d988d1b5a594ac74cb7af29dc Mon Sep 17 00:00:00 2001 From: ysyneu Date: Thu, 16 Jul 2026 07:41:07 -0700 Subject: [PATCH 1/2] docs: publish AI SRE quick start --- docs.json | 2 + en/ai-sre.mdx | 20 ++++-- en/ai-sre/agents.mdx | 4 +- en/ai-sre/apps.mdx | 2 +- en/ai-sre/automations.mdx | 2 +- en/ai-sre/environments.mdx | 2 +- en/ai-sre/im.mdx | 2 +- en/ai-sre/init.mdx | 2 +- en/ai-sre/insight.mdx | 4 +- en/ai-sre/knowledge.mdx | 2 +- en/ai-sre/mcp.mdx | 2 +- en/ai-sre/overview.mdx | 27 ++++---- en/ai-sre/quickstart.mdx | 127 +++++++++++++++++++++++++++++++++++++ en/ai-sre/sandbox.mdx | 2 +- en/ai-sre/sessions.mdx | 2 +- en/ai-sre/skills.mdx | 2 +- en/home.mdx | 8 +-- zh/ai-sre.mdx | 20 ++++-- zh/ai-sre/agents.mdx | 4 +- zh/ai-sre/apps.mdx | 2 +- zh/ai-sre/automations.mdx | 2 +- zh/ai-sre/environments.mdx | 2 +- zh/ai-sre/im.mdx | 2 +- zh/ai-sre/init.mdx | 2 +- zh/ai-sre/insight.mdx | 4 +- zh/ai-sre/knowledge.mdx | 2 +- zh/ai-sre/mcp.mdx | 2 +- zh/ai-sre/overview.mdx | 27 ++++---- zh/ai-sre/quickstart.mdx | 127 +++++++++++++++++++++++++++++++++++++ zh/ai-sre/sandbox.mdx | 2 +- zh/ai-sre/sessions.mdx | 2 +- zh/ai-sre/skills.mdx | 2 +- zh/home.mdx | 8 +-- 33 files changed, 344 insertions(+), 78 deletions(-) create mode 100644 en/ai-sre/quickstart.mdx create mode 100644 zh/ai-sre/quickstart.mdx diff --git a/docs.json b/docs.json index 125feb7..e907f8e 100644 --- a/docs.json +++ b/docs.json @@ -576,6 +576,7 @@ "group": "快速开始", "icon": "rocket", "pages": [ + "zh/ai-sre/quickstart", "zh/ai-sre/overview", "zh/ai-sre/init", "zh/ai-sre/insight" @@ -1783,6 +1784,7 @@ "group": "Quick Start", "icon": "rocket", "pages": [ + "en/ai-sre/quickstart", "en/ai-sre/overview", "en/ai-sre/init", "en/ai-sre/insight" diff --git a/en/ai-sre.mdx b/en/ai-sre.mdx index 0d352d4..94be475 100644 --- a/en/ai-sre.mdx +++ b/en/ai-sre.mdx @@ -6,7 +6,7 @@ sidebarTitle: AI SRE --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## What is AI SRE? @@ -49,22 +49,28 @@ It is not a question-and-answer chatbot but a **hands-on troubleshooter**, integ -## Beta & Billing +## Public Beta and Usage Requirements - - AI SRE requires a **Pro or higher** subscription. During the beta, submit the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. + + AI SRE is available to accounts on **On-call Pro or higher**. If the account does not meet the requirement, upgrade its On-call plan first. - - AI SRE is **free** during the private beta and is not billed separately. It will become a paid capability after commercialization starts. Before billing begins, Flashduty will share the product billing information, and you can choose whether to formally activate AI SRE or pause usage. No AI SRE charges are incurred before you confirm activation. + + AI SRE is available at no additional charge during the public beta. Features and the UI may continue to change. + + + AI SRE can investigate, query, and recommend actions, but you retain final approval for production changes, restarts, rollbacks, and external notifications. ## Get Started + + Start with a real incident and complete your first investigation with context, evidence, and room for follow-up questions + - Learn the full capability map, beta activation, and console navigation + Learn the full capability map, public beta requirements, and console navigation Sessions, streaming output, cancellation, context compaction, and starting from an incident diff --git a/en/ai-sre/agents.mdx b/en/ai-sre/agents.mdx index 159be03..cadcf64 100644 --- a/en/ai-sre/agents.mdx +++ b/en/ai-sre/agents.mdx @@ -6,7 +6,7 @@ sidebarTitle: Agent --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview @@ -176,7 +176,7 @@ The Agent Card also declares Flashduty's "run options" A2A extension: callers ca When a session **enters via an incident route** (e.g., AI SRE is triggered from an incident or war room), the platform binds the corresponding incident to the session and brings it in as context, anchoring troubleshooting to the correct incident from the start. Based on this, AI SRE can use built-in skills during the conversation to further act on the incident — reading incident details, querying the timeline, creating / viewing war rooms, linking changes, and more. For automatic war-room diagnosis on the IM side, see [IM Integration](/en/ai-sre/im). -**Automatic incident integration** for A2A is currently supported conceptually and is under active development: automatic incident binding is not yet fully available, and bidirectional event streams across agents will be progressively completed with each release. Do not treat this as a fully available capability — during private beta, only features that have been explicitly enabled should be relied upon. +**Automatic incident integration** for A2A is currently supported conceptually and is under active development: automatic incident binding is not yet fully available, and bidirectional event streams across agents will be progressively completed with each release. Do not treat this as a fully available capability — during the public beta, rely only on what is currently available in the UI. ## Creating and Managing diff --git a/en/ai-sre/apps.mdx b/en/ai-sre/apps.mdx index 3c2d6d3..3bd1000 100644 --- a/en/ai-sre/apps.mdx +++ b/en/ai-sre/apps.mdx @@ -6,7 +6,7 @@ sidebarTitle: Apps --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/automations.mdx b/en/ai-sre/automations.mdx index 21ef84e..f9e0aa5 100644 --- a/en/ai-sre/automations.mdx +++ b/en/ai-sre/automations.mdx @@ -6,7 +6,7 @@ sidebarTitle: Automations --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/environments.mdx b/en/ai-sre/environments.mdx index 6d410e5..b045863 100644 --- a/en/ai-sre/environments.mdx +++ b/en/ai-sre/environments.mdx @@ -6,7 +6,7 @@ sidebarTitle: Environments --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/im.mdx b/en/ai-sre/im.mdx index 4fb0c02..6b16606 100644 --- a/en/ai-sre/im.mdx +++ b/en/ai-sre/im.mdx @@ -6,7 +6,7 @@ sidebarTitle: IM Platform --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/init.mdx b/en/ai-sre/init.mdx index 3b98c71..5326990 100644 --- a/en/ai-sre/init.mdx +++ b/en/ai-sre/init.mdx @@ -6,7 +6,7 @@ sidebarTitle: Setup --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/insight.mdx b/en/ai-sre/insight.mdx index 19ba8e6..722d6c7 100644 --- a/en/ai-sre/insight.mdx +++ b/en/ai-sre/insight.mdx @@ -6,7 +6,7 @@ sidebarTitle: Usage Insights --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview @@ -143,7 +143,7 @@ Every friction and win must be grounded in at least one real session and carry a --- -The report is **read-only**: it surfaces problems and provides copyable fix text, but **never** automatically applies any changes. During the beta, all suggestions are copy-paste style — you confirm them, then manually apply them in the corresponding resource. +The report is **read-only**: it surfaces problems and provides copyable fix text, but **never** automatically applies any changes. During the public beta, all suggestions are copy-paste style — you confirm them, then manually apply them in the corresponding resource. diff --git a/en/ai-sre/knowledge.mdx b/en/ai-sre/knowledge.mdx index 297b60c..b22c9d7 100644 --- a/en/ai-sre/knowledge.mdx +++ b/en/ai-sre/knowledge.mdx @@ -6,7 +6,7 @@ sidebarTitle: Manage Knowledge --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/mcp.mdx b/en/ai-sre/mcp.mdx index 4dc0121..d4844c7 100644 --- a/en/ai-sre/mcp.mdx +++ b/en/ai-sre/mcp.mdx @@ -6,7 +6,7 @@ sidebarTitle: MCP --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/overview.mdx b/en/ai-sre/overview.mdx index a38747b..48ba198 100644 --- a/en/ai-sre/overview.mdx +++ b/en/ai-sre/overview.mdx @@ -6,7 +6,7 @@ sidebarTitle: Overview --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## What Is AI SRE @@ -49,28 +49,24 @@ AI SRE is more than a chat box in the console — it covers multiple collaborati -## Beta Access & Activation +## Public Beta and Usage Requirements --- -AI SRE is currently in private beta. Activation requires both of the following conditions to be met: +AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Review these requirements before you start: - - AI SRE requires a **Pro or higher** subscription. Consistent with other professional capabilities such as Status Page and alert ingestion, it is unavailable on lower tiers, and the UI will prompt you to upgrade. + + AI SRE is available to accounts on **On-call Pro or higher**. If the account does not meet the requirement, upgrade its On-call plan first. - - During the private beta, AI SRE is available only to accounts approved through the beta application process and must be whitelisted by Flashduty for your account. Even with a Pro subscription, accounts not on the whitelist will not see the AI SRE entry point. + + AI SRE is available at no additional charge during the public beta. Features and the UI may continue to change. - - AI SRE is **free** during the private beta and is not billed separately. It will become a paid capability after commercialization starts. Before billing begins, Flashduty will share the product billing information, and you can choose whether to formally activate AI SRE or pause usage. No AI SRE charges are incurred before you confirm activation. + + AI SRE can investigate, query, and recommend actions, but you retain final approval for production changes, restarts, rollbacks, and external notifications. - -To join the private beta, submit the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH). After approval, Flashduty will add your account to the whitelist. - - ## Core Capabilities --- @@ -133,7 +129,7 @@ Visibility of each area is determined by your access permissions in the account: - Confirm your account has a Pro or higher subscription, then submit the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH). After approval, your account is added to the AI SRE private beta whitelist. + Confirm that the account is on On-call Pro or higher. AI SRE is available at no additional charge during the public beta. In the Flashduty console sidebar, open **AI SRE**. You will land in the **Chat** workspace by default. @@ -158,6 +154,9 @@ Reusable knowledge distilled during an investigation can be saved as a Knowledge --- + + Start with a real incident and complete your first investigation with context, evidence, and room for follow-up questions. + Learn about sessions, streaming output, cancellation and context compaction, and how to launch an investigation from an incident. diff --git a/en/ai-sre/quickstart.mdx b/en/ai-sre/quickstart.mdx new file mode 100644 index 0000000..7fb8b93 --- /dev/null +++ b/en/ai-sre/quickstart.mdx @@ -0,0 +1,127 @@ +--- +title: Complete Your First AI SRE Investigation in 15 Minutes +description: Start with a real incident and complete your first AI SRE investigation with context, evidence, and room for follow-up questions; then add team knowledge and connect real data sources as needed. +sidebarTitle: Quick Start +--- + + + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. + + +This page offers three independent paths. Complete the one that fits your current situation and stop when you reach its completion criteria; you do not need to follow all three in order. + + +Keep your first use read-only: ask AI SRE to query, analyze, and provide evidence. Do not execute production changes, restarts, or rollbacks in this quick start. + + +## 5 minutes: Investigate an existing incident + +**Prerequisites**: Your account is on On-call Pro or higher and already has an incident. + + + + Go to **AI SRE → Chat → New Chat**. + + + Type `@` in the input box, search for the incident, and insert its reference. Before sending, confirm that the incident reference capsule appears in the input box. + + + Send: + + > Analyze this incident. First list the investigation plan, then provide evidence for every conclusion. Do not make any production changes. + + + Wait for AI SRE to show the investigation plan, tool calls, intermediate findings, and conclusion. Expand the tool calls to see what it queried and what each call returned. + + + +### Completion criteria + +You have an investigation with a plan, tool calls, and intermediate findings, and every conclusion maps to evidence. You can continue asking questions in the same context without pasting the incident details again. + +### If it does not work + +- AI SRE is missing: confirm that the account is on On-call Pro or higher and that the current member has access to AI SRE. +- `@` does not find the incident: confirm that the current account has an incident, that you are in the correct account, and that you can view the target incident. +- The message has no incident context: before sending, confirm that the reference capsule remains in the input box. If it was removed, type `@` and insert it again. +- You get a conclusion without evidence: confirm that you sent the complete request above, then ask, “Map each conclusion to the corresponding tool output or incident field.” + +### Next step + +Read [Console sessions](/en/ai-sre/sessions) for details about references, tool calls, follow-up questions, and session management. + +## 15 minutes: Build your first team knowledge + +This path does not depend on the previous one. Create a new session and use the team selector to bind the target team before sending the first message. + + + + In the session bound to the target team, type `/init` and send it. + + + Verify that the team AI SRE shows is the target team, then confirm the write scope. One `/init` session uses one scope throughout. + + + Let AI SRE scan channels, incidents from the last 30 days, teams, and members. Check its summary of services and frequent incidents, then add or correct anything missing. + + + Continue until you have at least one `services.md` or runbook. Review the file list and summaries item by item, then explicitly approve the write; do not use a vague “OK” to skip item-by-item confirmation. + + + +### Completion criteria + +The target team's knowledge base contains at least one `services.md` or runbook that you approved item by item, and it is linked from `DUTY.md`. You can stop here; the next `/init` run continues from the existing knowledge. + +### If it does not work + +- The scope is not the target team: do not continue writing. Create a new session, bind the correct team before the first message, and run `/init` again. +- The scan is empty: confirm that the account has incidents and channels. For a new account, continue with the cold-start interview and enter service information manually. +- The write fails: confirm that you belong to the target team and can edit its knowledge base. +- AI SRE is about to write immediately: ask it to list every file it will create or update with a summary, then approve each item before it writes. + +### Next step + +Read the full [`/init` setup flow](/en/ai-sre/init) for all interview phases, outputs, and safety boundaries. + +## 30 minutes: Connect a real data source + +You can complete this path on its own. First determine whether the data source is publicly reachable, then choose the smallest connection path. + + + + For a publicly reachable HTTP Streaming or SSE MCP server, go to **Plugins → MCP → Browse Marketplace**, choose a template, and click Install. Follow the new conversation to enter the endpoint, authorize credentials, and verify connectivity. + + + If the target is in a VPC or private database, or the MCP server needs to run a local command, open **Environments**, create a self-hosted Environment, and follow its setup guide to deploy the BYOC Runner on a machine that can reach the target. Do not deploy a Runner just for a public MCP server. + + + Create a chat in the appropriate Environment and ask AI SRE to make one read-only query through the new data source, such as reading a metric, listing resources, or retrieving a recent record. Confirm that the tool output comes from the target system. + + + +### Completion criteria + +The MCP server appears in the list and AI SRE can call it to complete one read-only query. If you use a BYOC Runner, the Environment also shows Online. + +### If it does not work + +- A public MCP server cannot connect: check the endpoint, HTTP Streaming or SSE transport, credentials, TLS settings, and whether the service allows access from the cloud Sandbox. +- A VPC, private database, or local command is unreachable: confirm that the session uses the BYOC Runner, then check the Runner's network path, credentials, and local permissions. +- The Runner remains Pending or Offline: check the Runner process, Token, connection URL, outbound firewall, and last heartbeat. +- The query is denied: first confirm that the credential has read access, then check the Runner's read-only command allow rules. Do not broaden it to write access just to pass verification. + +### Next step + +Read [MCP (external tool connections)](/en/ai-sre/mcp) and [Environments (BYOC Runner)](/en/ai-sre/environments). + +## Start using AI SRE + + + + Sign in and start your first read-only investigation from a real incident. + + + Confirm that the account is on On-call Pro or higher. + + diff --git a/en/ai-sre/sandbox.mdx b/en/ai-sre/sandbox.mdx index 9eb95ca..5ca7261 100644 --- a/en/ai-sre/sandbox.mdx +++ b/en/ai-sre/sandbox.mdx @@ -6,7 +6,7 @@ sidebarTitle: Sandbox --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/sessions.mdx b/en/ai-sre/sessions.mdx index dc5628c..a5972f8 100644 --- a/en/ai-sre/sessions.mdx +++ b/en/ai-sre/sessions.mdx @@ -6,7 +6,7 @@ sidebarTitle: Console --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/ai-sre/skills.mdx b/en/ai-sre/skills.mdx index b58103a..84772c3 100644 --- a/en/ai-sre/skills.mdx +++ b/en/ai-sre/skills.mdx @@ -6,7 +6,7 @@ sidebarTitle: Skills --- - **Private beta**: AI SRE is currently in private beta. Pro or higher accounts can apply for free beta access through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH); after approval, Flashduty will add your account to the whitelist. Features and the UI may change during the beta. + **Public beta**: AI SRE is available to accounts on On-call Pro or higher at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. ## Overview diff --git a/en/home.mdx b/en/home.mdx index 2efab4f..a4e393d 100644 --- a/en/home.mdx +++ b/en/home.mdx @@ -19,7 +19,7 @@ Flashduty is a unified observability platform designed for DevOps, SRE, and oper Unified monitoring platform - Autonomous troubleshooting Agent (Beta) + Autonomous troubleshooting Agent (Public beta) @@ -139,15 +139,15 @@ A conversational, autonomous SRE Agent: issue instructions in natural language, -AI SRE is currently in **private beta**. Pro or higher accounts can apply for **free beta access**; it will become paid after commercialization starts, and Flashduty will share billing information so you can choose whether to formally activate AI SRE or pause usage. Apply through the [AI SRE private beta application form](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH), and see the [AI SRE introduction](./ai-sre). +AI SRE is available to accounts on **On-call Pro or higher** at no additional charge during the public beta. Features and the UI may continue to change. You retain final approval for production changes, restarts, rollbacks, and external notifications. See the [AI SRE introduction](./ai-sre). Learn the full capability map and console navigation - - Create a session and start conversational troubleshooting + + Start your first read-only investigation from a real incident diff --git a/zh/ai-sre.mdx b/zh/ai-sre.mdx index f6a90aa..40a785c 100644 --- a/zh/ai-sre.mdx +++ b/zh/ai-sre.mdx @@ -6,7 +6,7 @@ sidebarTitle: AI SRE --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 什么是 AI SRE？ @@ -49,22 +49,28 @@ Flashduty AI SRE 是一个对话式的自治 SRE Agent 平台。你用自然语 -## 内测与计费 +## 公测与使用条件 - - AI SRE 需要**专业版及以上**订阅。内测期间请填写 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请；审核通过后，Flashduty 会为你的账户开通白名单。 + + AI SRE 面向 **On-call 专业版及以上**账户开放。未达到套餐要求时，请先升级 On-call 套餐。 - - 内测期间 AI SRE **免费**提供，不单独计费。正式商用后将开始收费；商用开始前，Flashduty 会提供产品计费信息，你可以选择正式开通或暂停使用。在你确认开通前，不会产生 AI SRE 费用。 + + 公测期间 AI SRE 不单独收费；功能与界面可能继续调整。 + + + AI SRE 可以调查、查询并提出操作建议，但生产变更、重启、回滚和外部通知仍由你最终确认。 ## 快速开始 + + 从一个真实故障开始，完成第一次有上下文、有证据、可继续追问的调查 + - 了解 AI SRE 的能力全景、内测开通与控制台导航 + 了解 AI SRE 的能力全景、公测使用条件与控制台导航 了解会话、流式输出、取消与上下文压缩，以及从故障拉起排查 diff --git a/zh/ai-sre/agents.mdx b/zh/ai-sre/agents.mdx index 915f290..a8805e0 100644 --- a/zh/ai-sre/agents.mdx +++ b/zh/ai-sre/agents.mdx @@ -6,7 +6,7 @@ sidebarTitle: Agent --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 @@ -176,7 +176,7 @@ Agent Card 同时声明了 Flashduty 的「运行选项」A2A 扩展：调用方 当一个会话**经由故障路由进入**（例如从故障或作战室触发 AI SRE）时，平台会把对应的故障绑定到本次会话，并作为上下文带入，让排障从一开始就锚定在正确的故障上。基于此，AI SRE 可在对话中借助内置 Skill 进一步操作故障——读取故障详情、查询时间线、创建 / 查看作战室、关联变更等。IM 侧的作战室自动诊断详见 [IM 集成](/zh/ai-sre/im)。 -A2A 与故障的**自动联动**目前在概念上受支持、并在持续演进中：故障自动绑定尚未完整可用，跨 Agent 的双向事件流会随版本逐步完善。请勿将其视为已完整可用的能力——内测期间以实际开通的功能为准。 +A2A 与故障的**自动联动**目前在概念上受支持、并在持续演进中：故障自动绑定尚未完整可用，跨 Agent 的双向事件流会随版本逐步完善。请勿将其视为已完整可用的能力——公测期间以当前界面和实际可用能力为准。 ## 创建与管理 diff --git a/zh/ai-sre/apps.mdx b/zh/ai-sre/apps.mdx index d6f105b..4602b96 100644 --- a/zh/ai-sre/apps.mdx +++ b/zh/ai-sre/apps.mdx @@ -6,7 +6,7 @@ sidebarTitle: Apps --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/automations.mdx b/zh/ai-sre/automations.mdx index 278b4f0..bd86cd1 100644 --- a/zh/ai-sre/automations.mdx +++ b/zh/ai-sre/automations.mdx @@ -6,7 +6,7 @@ sidebarTitle: 自动化 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/environments.mdx b/zh/ai-sre/environments.mdx index d5469de..446a3cf 100644 --- a/zh/ai-sre/environments.mdx +++ b/zh/ai-sre/environments.mdx @@ -6,7 +6,7 @@ sidebarTitle: 运行环境 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/im.mdx b/zh/ai-sre/im.mdx index 5d9d3a7..244fb4c 100644 --- a/zh/ai-sre/im.mdx +++ b/zh/ai-sre/im.mdx @@ -6,7 +6,7 @@ sidebarTitle: IM 平台 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/init.mdx b/zh/ai-sre/init.mdx index 22d768d..f9b8ea1 100644 --- a/zh/ai-sre/init.mdx +++ b/zh/ai-sre/init.mdx @@ -6,7 +6,7 @@ sidebarTitle: 初始化 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/insight.mdx b/zh/ai-sre/insight.mdx index 0cea150..8bb7e27 100644 --- a/zh/ai-sre/insight.mdx +++ b/zh/ai-sre/insight.mdx @@ -6,7 +6,7 @@ sidebarTitle: 使用洞察 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 @@ -143,7 +143,7 @@ sidebarTitle: 使用洞察 --- -报告是**只读**的：它呈现问题、给出可复制的修复文本，但**绝不**自动应用任何改动。内测期间所有建议都是复制粘贴式的，需要您确认后，再到对应的资源里手动修改。 +报告是**只读**的：它呈现问题、给出可复制的修复文本，但**绝不**自动应用任何改动。公测期间所有建议都是复制粘贴式的，需要您确认后，再到对应的资源里手动修改。 diff --git a/zh/ai-sre/knowledge.mdx b/zh/ai-sre/knowledge.mdx index d61dbde..fb0186a 100644 --- a/zh/ai-sre/knowledge.mdx +++ b/zh/ai-sre/knowledge.mdx @@ -6,7 +6,7 @@ sidebarTitle: 管理知识 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/mcp.mdx b/zh/ai-sre/mcp.mdx index 748a5f7..883a11b 100644 --- a/zh/ai-sre/mcp.mdx +++ b/zh/ai-sre/mcp.mdx @@ -6,7 +6,7 @@ sidebarTitle: MCP --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/overview.mdx b/zh/ai-sre/overview.mdx index dba238f..384af57 100644 --- a/zh/ai-sre/overview.mdx +++ b/zh/ai-sre/overview.mdx @@ -6,7 +6,7 @@ sidebarTitle: 概述 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 什么是 AI SRE @@ -49,28 +49,24 @@ AI SRE 不止是控制台里的一个对话框——它围绕「故障从触发 -## 内测与开通 +## 公测与使用条件 --- -AI SRE 当前处于内测阶段，开通需要同时满足两个条件： +AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费。开始使用前请了解以下条件： - - AI SRE 需要 **专业版及以上**的订阅。与 Status Page、告警接入等专业能力一致，未达版本时无法使用 AI SRE，界面会提示升级。 + + AI SRE 面向 **On-call 专业版及以上**账户开放。未达到套餐要求时，请先升级 On-call 套餐。 - - 内测期间 AI SRE 仅对通过申请审核的账户开放，需要由 Flashduty 为您的账户加入白名单。即使已具备专业版订阅，未进入白名单的账户也不会看到 AI SRE 入口。 + + 公测期间 AI SRE 不单独收费；功能与界面可能继续调整。 - - 内测期间 AI SRE **免费**提供，不单独计费。正式商用后将开始收费；商用开始前，Flashduty 会提供产品计费信息，您可以选择正式开通或暂停使用。在您确认开通前，不会产生 AI SRE 费用。 + + AI SRE 可以调查、查询并提出操作建议，但生产变更、重启、回滚和外部通知仍由您最终确认。 - -如需参与内测，请填写 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH)，审核通过后将开通白名单。 - - ## 核心能力 --- @@ -133,7 +129,7 @@ AI SRE 围绕"对话排障 + 知识沉淀 + 自主执行"构建了一套完整 - 确认账户已具备专业版及以上订阅，并通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后进入 AI SRE 内测白名单。 + 确认账户已使用 On-call 专业版及以上套餐。公测期间 AI SRE 不单独收费。 在 Flashduty 控制台侧边菜单中打开 **AI SRE**，默认进入"对话"工作区。 @@ -158,6 +154,9 @@ AI SRE 围绕"对话排障 + 知识沉淀 + 自主执行"构建了一套完整 --- + + 从一个真实故障开始，完成第一次有上下文、有证据、可继续追问的调查。 + 了解会话、流式输出、取消与上下文压缩，以及如何从故障拉起排查。 diff --git a/zh/ai-sre/quickstart.mdx b/zh/ai-sre/quickstart.mdx new file mode 100644 index 0000000..e413141 --- /dev/null +++ b/zh/ai-sre/quickstart.mdx @@ -0,0 +1,127 @@ +--- +title: 15 分钟完成第一次 AI SRE 排障 +description: 从一个真实故障开始，完成第一次有上下文、有证据、可继续追问的 AI SRE 调查；随后按需建立团队知识并连接真实数据源。 +sidebarTitle: 快速开始 +--- + + + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 + + +本页有三条相互独立的路径。您可以只完成最符合当前条件的一条，看到“完成标志”后就停下；不需要按顺序做完三条。 + + +第一次使用请保持只读：让 AI SRE 查询、分析并给出证据，不要在快速开始里执行生产变更、重启或回滚。 + + +## 5 分钟：调查已有故障 + +**前置条件**：您的账户使用 On-call 专业版及以上套餐，并且账户中已经有一条故障。 + + + + 进入 **AI SRE → 对话 → 新对话**。 + + + 在输入框中输入 `@`，搜索并插入要调查的故障引用。发送前确认输入框中已经出现故障引用胶囊。 + + + 发送： + + > 分析这个故障。先列调查计划，再给出每条结论的证据，不要执行生产变更。 + + + 等待 AI SRE 依次给出调查计划、工具调用、中间发现和结论。展开工具调用可以查看它查询了什么以及返回了什么。 + + + +### 完成标志 + +您看到一份有计划、有工具调用、有中间发现的调查结果，并且每条结论都能对应到证据。此时可以基于同一上下文继续追问，不需要重新粘贴故障信息。 + +### 失败时检查什么 + +- 看不到 AI SRE 入口：确认账户套餐是 On-call 专业版及以上，并确认当前成员有 AI SRE 访问权限。 +- 输入 `@` 搜不到故障：确认当前账户已有故障、您进入了正确账户，并且您有权查看目标故障。 +- 消息里没有故障上下文：发送前确认故障引用胶囊仍在输入框中；如果已移除，请重新输入 `@` 插入。 +- 只有结论、没有证据：确认发送的是上面的完整指令，然后直接追问“请把每条结论与对应的工具输出或故障字段逐项关联”。 + +### 下一步 + +继续阅读 [控制台会话](/zh/ai-sre/sessions)，了解引用、工具调用、继续追问和会话管理。 + +## 15 分钟：建立第一份团队知识 + +这条路径不依赖上一条。开始前新建会话，并在发送第一条消息前用团队选择器绑定目标团队。 + + + + 在已经绑定目标团队的会话中输入 `/init` 并发送。 + + + 核对 AI SRE 回显的团队就是目标团队，再确认本次写入作用域。一次 `/init` 会话只使用一个作用域。 + + + 让 AI SRE 扫描渠道、近 30 天故障、团队与成员；检查它归纳的服务和高频故障是否正确，并补充或纠正缺失信息。 + + + 至少推进到一份 `services.md` 或 runbook。先逐项检查 AI SRE 给出的文件清单和摘要，再明确确认写入；不要用一句模糊的“好”跳过逐项确认。 + + + +### 完成标志 + +目标团队的知识库中已经写入至少一份经您逐项确认的 `services.md` 或 runbook，并已链接进 `DUTY.md`。您可以在这里结束，之后重新运行 `/init` 会从已有知识继续。 + +### 失败时检查什么 + +- 作用域不是目标团队：不要继续写入；新建会话，在第一条消息前绑定正确团队，再运行 `/init`。 +- 扫描结果为空：确认账户中已有故障和渠道；全新账户也可以继续冷启动访谈，手工补充服务信息。 +- 无法写入：确认您属于目标团队，并有该团队知识库的编辑权限。 +- AI SRE 准备直接写文件：要求它先列出将创建或更新的文件及摘要，逐项确认后再写入。 + +### 下一步 + +继续阅读 [`/init` 设置流程](/zh/ai-sre/init)，了解完整访谈阶段、产出和安全边界。 + +## 30 分钟：接入真实数据源 + +这条路径也可以单独完成。先判断数据源是否能从公网访问，再选择最少的连接方式。 + + + + 对公网可达的 HTTP 流式或 SSE MCP，进入 **插件 → MCP → 浏览 Marketplace**，选择模板并点击安装。按新会话中的引导填写端点、完成凭证授权并验证连通性。 + + + 如果目标在 VPC、内网数据库中，或 MCP 需要在本机运行命令，请进入 **环境** 创建自托管 Environment，并按接入指引把 BYOC Runner 部署到能访问目标资源的机器。公网 MCP 不需要为了这一步额外部署 Runner。 + + + 新建会话并选择合适的运行环境，让 AI SRE 通过刚接入的数据源执行一次只读查询，例如读取一项指标、列出一组资源或查询一条近期记录。检查工具输出确实来自目标系统。 + + + +### 完成标志 + +MCP 已出现在列表中，AI SRE 能在会话里调用它完成一次只读查询；如果使用 BYOC Runner，Environment 同时显示在线。 + +### 失败时检查什么 + +- 公网 MCP 无法连接：检查端点、HTTP 流式或 SSE 传输方式、凭证、TLS 设置，以及服务是否允许从云端 Sandbox 访问。 +- VPC、内网数据库或本地命令不可达：确认会话选择了 BYOC Runner，并检查 Runner 到目标资源的网络、凭证和本机权限。 +- Runner 一直等待或离线：检查 Runner 进程、Token、连接 URL、出网防火墙和最后心跳。 +- 查询被拒绝：先确认凭证拥有读取权限，再检查 Runner 的只读命令允许规则；不要为了通过验证扩大到写权限。 + +### 下一步 + +继续阅读 [MCP（外部工具连接）](/zh/ai-sre/mcp) 和 [运行环境（BYOC Runner）](/zh/ai-sre/environments)。 + +## 开始使用 + + + + 登录控制台，从一条真实故障开始第一次只读调查。 + + + 确认账户已使用 On-call 专业版及以上套餐。 + + diff --git a/zh/ai-sre/sandbox.mdx b/zh/ai-sre/sandbox.mdx index 4d6102c..8abda48 100644 --- a/zh/ai-sre/sandbox.mdx +++ b/zh/ai-sre/sandbox.mdx @@ -6,7 +6,7 @@ sidebarTitle: Sandbox --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/sessions.mdx b/zh/ai-sre/sessions.mdx index 6e310fe..6693d4e 100644 --- a/zh/ai-sre/sessions.mdx +++ b/zh/ai-sre/sessions.mdx @@ -6,7 +6,7 @@ sidebarTitle: 控制台 --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/ai-sre/skills.mdx b/zh/ai-sre/skills.mdx index b7c6d16..bb08288 100644 --- a/zh/ai-sre/skills.mdx +++ b/zh/ai-sre/skills.mdx @@ -6,7 +6,7 @@ sidebarTitle: Skill --- - **内测功能**：AI SRE 目前处于内测阶段，专业版及以上用户可申请免费试用。请通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 提交申请，审核通过后将开通白名单；内测期间功能与界面可能调整。 + **公测功能**：AI SRE 面向 On-call 专业版及以上账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由您最终确认。 ## 概述 diff --git a/zh/home.mdx b/zh/home.mdx index 6224ccc..b37e017 100644 --- a/zh/home.mdx +++ b/zh/home.mdx @@ -20,7 +20,7 @@ Flashduty 是面向 DevOps、SRE 和运维团队的一站式可观测性平台 统一监控管理平台 - 自治排障 Agent（内测） + 自治排障 Agent（公测） @@ -140,15 +140,15 @@ Real User Monitoring（真实用户监控）帮助您了解真实用户如何体 -AI SRE 目前处于**内测**阶段，专业版及以上用户可申请**免费试用**；正式商用后收费，Flashduty 会提供计费信息，你可以选择正式开通或暂停使用。通过 [AI SRE 内测申请表](https://c9xudyniiq.feishu.cn/share/base/form/shrcn0ngCfdoygiaHnAT80BfZiH) 申请，详见 [AI SRE 产品介绍](./ai-sre)。 +AI SRE 面向 **On-call 专业版及以上**账户开放，公测期间不单独收费；功能与界面可能继续调整。生产变更、重启、回滚和外部通知仍由你最终确认。详见 [AI SRE 产品介绍](./ai-sre)。 了解能力全景与控制台导航 - - 新建会话，开始对话式排障 + + 从一个真实故障开始第一次只读调查 From 59b4df7cdd1a5e27a76ee83c058fb525bd648513 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Thu, 16 Jul 2026 07:53:23 -0700 Subject: [PATCH 2/2] docs: clarify AI SRE connection paths --- en/ai-sre/quickstart.mdx | 36 +++++++++++++++++++++++++++--------- zh/ai-sre/quickstart.mdx | 36 +++++++++++++++++++++++++++--------- 2 files changed, 54 insertions(+), 18 deletions(-) diff --git a/en/ai-sre/quickstart.mdx b/en/ai-sre/quickstart.mdx index 7fb8b93..181f45c 100644 --- a/en/ai-sre/quickstart.mdx +++ b/en/ai-sre/quickstart.mdx @@ -11,7 +11,7 @@ sidebarTitle: Quick Start This page offers three independent paths. Complete the one that fits your current situation and stop when you reach its completion criteria; you do not need to follow all three in order. -Keep your first use read-only: ask AI SRE to query, analyze, and provide evidence. Do not execute production changes, restarts, or rollbacks in this quick start. +Keep production systems read-only during your first use: ask AI SRE to query, analyze, and provide evidence. Product-configuration writes required to create Knowledge, install MCP, or create an Environment may still proceed after you confirm each one. Without your approval, do not make production changes, restart services, roll back, or send external notifications. ## 5 minutes: Investigate an existing incident @@ -86,30 +86,48 @@ Read the full [`/init` setup flow](/en/ai-sre/init) for all interview phases, ou ## 30 minutes: Connect a real data source -You can complete this path on its own. First determine whether the data source is publicly reachable, then choose the smallest connection path. +You can complete this path on its own. Based on where the target system is reachable, **choose one** of the following connection options. A public MCP server does not also require a Runner, and a BYOC-only Runner does not require an MCP server first. + +### Option A: Public MCP server For a publicly reachable HTTP Streaming or SSE MCP server, go to **Plugins → MCP → Browse Marketplace**, choose a template, and click Install. Follow the new conversation to enter the endpoint, authorize credentials, and verify connectivity. - - If the target is in a VPC or private database, or the MCP server needs to run a local command, open **Environments**, create a self-hosted Environment, and follow its setup guide to deploy the BYOC Runner on a machine that can reach the target. Do not deploy a Runner just for a public MCP server. + + Confirm that the MCP server appears in the list and that AI SRE can discover and call it in a conversation. + + + +**Completion criteria for this option**: The MCP server is installed and callable by AI SRE. + +### Option B: BYOC-only Runner + + + + If the target is in a VPC or private database, or you need to run a local command, open **Environments**, create a self-hosted Environment, and follow its setup guide to deploy the BYOC Runner on a machine that can reach the target. - - Create a chat in the appropriate Environment and ask AI SRE to make one read-only query through the new data source, such as reading a metric, listing resources, or retrieving a recent record. Confirm that the tool output comes from the target system. + + Wait for the Environment to show Online. AI SRE can use a read-only CLI directly on the Runner to query the target system. Configure a local MCP server only when the target tool itself requires MCP; it is not a prerequisite for the BYOC path. +**Completion criteria for this option**: The Environment shows Online; no MCP server is required. + +### Shared final step: Run one read-only query + +Create a chat in the corresponding Environment and ask AI SRE to use the installed public MCP server, or a read-only CLI directly on the BYOC Runner, to read a metric, list resources, or retrieve a recent record. Confirm that the output comes from the target system. + ### Completion criteria -The MCP server appears in the list and AI SRE can call it to complete one read-only query. If you use a BYOC Runner, the Environment also shows Online. +Your chosen connection option meets its completion criteria, and AI SRE successfully completes one read-only query against the target system. ### If it does not work - A public MCP server cannot connect: check the endpoint, HTTP Streaming or SSE transport, credentials, TLS settings, and whether the service allows access from the cloud Sandbox. -- A VPC, private database, or local command is unreachable: confirm that the session uses the BYOC Runner, then check the Runner's network path, credentials, and local permissions. - The Runner remains Pending or Offline: check the Runner process, Token, connection URL, outbound firewall, and last heartbeat. -- The query is denied: first confirm that the credential has read access, then check the Runner's read-only command allow rules. Do not broaden it to write access just to pass verification. +- A read-only CLI on the Runner cannot reach the target: confirm that the session uses that Runner, then check the Runner's network path, read credential, and local permissions. +- The query is denied: first confirm that the credential has read access. For a public MCP server, check server authorization; for a BYOC Runner, check the read-only command allow rules. Do not broaden it to write access just to pass verification. ### Next step diff --git a/zh/ai-sre/quickstart.mdx b/zh/ai-sre/quickstart.mdx index e413141..c63bb8a 100644 --- a/zh/ai-sre/quickstart.mdx +++ b/zh/ai-sre/quickstart.mdx @@ -11,7 +11,7 @@ sidebarTitle: 快速开始 本页有三条相互独立的路径。您可以只完成最符合当前条件的一条，看到“完成标志”后就停下；不需要按顺序做完三条。 -第一次使用请保持只读：让 AI SRE 查询、分析并给出证据，不要在快速开始里执行生产变更、重启或回滚。 +第一次使用请对生产系统保持只读：让 AI SRE 查询、分析并给出证据。创建 Knowledge、安装 MCP 或创建 Environment 所需的产品配置写入，仍可在您逐项确认后执行。未经您确认，不要执行生产变更、重启、回滚或外部通知。 ## 5 分钟：调查已有故障 @@ -86,30 +86,48 @@ sidebarTitle: 快速开始 ## 30 分钟：接入真实数据源 -这条路径也可以单独完成。先判断数据源是否能从公网访问，再选择最少的连接方式。 +这条路径也可以单独完成。请根据目标系统的网络位置，在下面两种连接方式中**二选一**；公网 MCP 不需要再部署 Runner，BYOC-only Runner 也不要求先安装 MCP。 + +### 选项 A：公网 MCP 对公网可达的 HTTP 流式或 SSE MCP，进入 **插件 → MCP → 浏览 Marketplace**，选择模板并点击安装。按新会话中的引导填写端点、完成凭证授权并验证连通性。 - - 如果目标在 VPC、内网数据库中，或 MCP 需要在本机运行命令，请进入 **环境** 创建自托管 Environment，并按接入指引把 BYOC Runner 部署到能访问目标资源的机器。公网 MCP 不需要为了这一步额外部署 Runner。 + + 确认 MCP 已出现在列表中，并且 AI SRE 能在会话中发现和调用它。 + + + +**本选项完成标志**：MCP 已安装并可被 AI SRE 调用。 + +### 选项 B：BYOC-only Runner + + + + 如果目标在 VPC、内网数据库中，或需要执行本地命令，请进入 **环境** 创建自托管 Environment，并按接入指引把 BYOC Runner 部署到能访问目标资源的机器。 - - 新建会话并选择合适的运行环境，让 AI SRE 通过刚接入的数据源执行一次只读查询，例如读取一项指标、列出一组资源或查询一条近期记录。检查工具输出确实来自目标系统。 + + 等待 Environment 显示在线。AI SRE 可以直接在 Runner 上使用只读 CLI 查询目标系统；只有目标工具本身要求 MCP 时才配置本地 MCP，并非 BYOC 路径的前置条件。 +**本选项完成标志**：Environment 显示在线；不要求安装 MCP。 + +### 共同收口：执行一次只读查询 + +新建会话并选择对应的运行环境，让 AI SRE 通过已安装的公网 MCP，或直接在 BYOC Runner 上使用只读 CLI，读取一项指标、列出一组资源或查询一条近期记录。检查输出确实来自目标系统。 + ### 完成标志 -MCP 已出现在列表中，AI SRE 能在会话里调用它完成一次只读查询；如果使用 BYOC Runner，Environment 同时显示在线。 +您选择的连接方式已经达到对应完成标志，并且 AI SRE 成功执行了一次来自目标系统的只读查询。 ### 失败时检查什么 - 公网 MCP 无法连接：检查端点、HTTP 流式或 SSE 传输方式、凭证、TLS 设置，以及服务是否允许从云端 Sandbox 访问。 -- VPC、内网数据库或本地命令不可达：确认会话选择了 BYOC Runner，并检查 Runner 到目标资源的网络、凭证和本机权限。 - Runner 一直等待或离线：检查 Runner 进程、Token、连接 URL、出网防火墙和最后心跳。 -- 查询被拒绝：先确认凭证拥有读取权限，再检查 Runner 的只读命令允许规则；不要为了通过验证扩大到写权限。 +- Runner 上的只读 CLI 无法访问目标：确认会话选择了该 Runner，并检查 Runner 到目标资源的网络、读取凭证和本机权限。 +- 查询被拒绝：先确认凭证拥有读取权限；公网 MCP 检查服务器授权，BYOC Runner 检查只读命令允许规则。不要为了通过验证扩大到写权限。 ### 下一步