docs: remove ServiceMap documentation and OpenAPI

docs.json

@@ -2034,8 +2034,7 @@
                   "zh/monitors/targets/overview",
                   "zh/monitors/targets/install-agent",
                   "zh/monitors/targets/configure-targets",
-                  "zh/monitors/targets/reload-and-verify",
-                  "zh/monitors/targets/servicemap"
+                  "zh/monitors/targets/reload-and-verify"
                 ]
               },
               {
@@ -2532,17 +2531,6 @@
                       "POST /monit/tools/invoke",
                       "POST /monit/targets"
                     ]
-                  },
-                  {
-                    "group": "服务拓扑",
-                    "icon": "diagram-project",
-                    "pages": [
-                      "POST /monit/servicemap/status",
-                      "POST /monit/servicemap/topology",
-                      "POST /monit/servicemap/summary",
-                      "POST /monit/servicemap/fleet",
-                      "POST /monit/servicemap/fleet/summary"
-                    ]
                   }
                 ]
               },
@@ -3446,8 +3434,7 @@
                   "en/monitors/targets/overview",
                   "en/monitors/targets/install-agent",
                   "en/monitors/targets/configure-targets",
-                  "en/monitors/targets/reload-and-verify",
-                  "en/monitors/targets/servicemap"
+                  "en/monitors/targets/reload-and-verify"
                 ]
               },
               {
@@ -3944,17 +3931,6 @@
                       "POST /monit/tools/invoke",
                       "POST /monit/targets"
                     ]
-                  },
-                  {
-                    "group": "Service map",
-                    "icon": "diagram-project",
-                    "pages": [
-                      "POST /monit/servicemap/status",
-                      "POST /monit/servicemap/topology",
-                      "POST /monit/servicemap/summary",
-                      "POST /monit/servicemap/fleet",
-                      "POST /monit/servicemap/fleet/summary"
-                    ]
                   }
                 ]
               },

en/ai-sre/sessions.mdx

@@ -137,7 +137,7 @@ When the console publishes a new version, a **version update notice** appears ab
     **Inline truncation of large files**: attachments reach the agent as extracted text. When the extracted text exceeds **64 KB**, only the first **32 KB** is inlined (cut at a valid UTF-8 boundary), and the attachment envelope carries a pointer to the full file staged in the sandbox (like `~/.flashduty/attachments/...`) — if the full content matters, ask the agent to read the file from the sandbox with the read / bash tools; nothing is lost. In addition, PDFs larger than **3 MB** are no longer passed natively to the model; they fall back to text extraction under the same truncation rule.
   </Accordion>
   <Accordion title="Context references" icon="link">
-    When you enter AI SRE from an incident, alert, monitor rule, monitor target, or service topology page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, monitor target, service topology, or on-call analytics — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time. Typing an email address does not false-trigger it: when the `@` directly follows an email-address character (a letter, a digit, or one of `._%+-`), the picker does not open; an `@` after a space or adjacent to Chinese text still triggers it.
+    When you enter AI SRE from an incident, alert, monitor rule, or monitor target page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, monitor target, or on-call analytics — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time. Typing an email address does not false-trigger it: when the `@` directly follows an email-address character (a letter, a digit, or one of `._%+-`), the picker does not open; an `@` after a space or adjacent to Chinese text still triggers it.
   </Accordion>
   <Accordion title="Knowledge and skills" icon="book">
     When a session starts, the knowledge packs and skills for the bound team are loaded automatically. See <a href="/en/ai-sre/knowledge">Knowledges</a> and <a href="/en/ai-sre/skills">Skills</a> for details.

en/changelog/changelog.mdx

@@ -310,7 +310,7 @@ See [Widgets](/en/on-call/statuspage/widgets).
 
 </Update>
 
-<Update label="2026-08-06" description="🔗 Public artifact links and ServiceMap (Beta)">
+<Update label="2026-08-06" description="🔗 Public artifact links">
 
 ### Artifacts can now be shared with a public link
 
@@ -327,20 +327,6 @@ Publishable artifact types are also no longer limited to HTML and Markdown: imag
 
 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">

en/developer/cli.mdx

@@ -604,20 +604,6 @@ Core fields for `datasource-create` / `datasource-update`:
 - `kafka`: `sasl_mechanism` (`none` default / `plain` / `scram-sha-256` / `scram-sha-512`, the latter three require username and password), `username` / `password`, `timeout_ms` (default 5000), TLS fields (`tls_min_version` defaults to 1.2, max 1.3).
 - Passwords and `kafka.tls_key` support `${env:NAME}` references (resolved on the edge); literal values are omitted from responses, only `${env:...}` references are echoed. **On update, omit those fields to preserve stored secrets; explicitly send an empty string to clear**.
 
-### monit servicemap — Service topology (Beta)
-
-The `monit servicemap-*` command family accesses the ServiceMap capability; see [Service Map](/en/monitors/targets/servicemap) for the UI workflow.
-
-```bash
-flashduty monit servicemap-fleet [flags]             # Browse fleet hosts (filter by --statuses/--agent-versions/--capture-modes/--edge-clusters)
-flashduty monit servicemap-fleet-summary [flags]     # Fleet host summary
-flashduty monit servicemap-status [flags]            # Check host collection status (--host-id/--host-ids, or --fleet to sample)
-flashduty monit servicemap-summary --data '<json>'   # Get a topology summary for an anchor host
-flashduty monit servicemap-topology --data '<json>' [flags]  # Query topology (--depth 1–3, default 1)
-```
-
-`summary` and `topology` take the anchor host via `--data '{"anchor":{...}}'`. Common `topology` flags: `--depth` (traversal depth, 1–3, default 1), `--max-nodes` (default 100, cap 500), `--max-edges` (default 200, cap 1000).
-
 ### alert — Alert and alert-event queries
 
 ```bash

en/developer/go-sdk.mdx

@@ -1,7 +1,7 @@
 ---
 title: Flashduty Go SDK
 sidebarTitle: Go SDK
-description: "go-flashduty is the official open-source Go SDK for Flashduty — a typed, strictly 1:1 wrapper over the Open API currently covering all 349 API operations across 39 services."
+description: "go-flashduty is the official open-source Go SDK for Flashduty — a typed, strictly 1:1 wrapper over the Open API."
 keywords: ["Go SDK", "go-flashduty", "Open API", "Golang", "client"]
 ---
 
@@ -11,7 +11,7 @@ keywords: ["Go SDK", "go-flashduty", "Open API", "Golang", "client"]
 
 `go-flashduty` is the official open-source Go client for Flashduty, covering every REST endpoint of the Flashduty Open API. It follows the same design as [go-github](https://github.com/google/go-github) — service groups, typed requests and responses, a composable transport layer — and stays strictly 1:1 with the OpenAPI spec: each method maps to exactly one HTTP call, returns `(*T, *Response, error)`, and performs no implicit cross-endpoint aggregation or enrichment.
 
-The SDK currently covers **349 API operations** across **39 services**, all generated from the Flashduty OpenAPI spec, covered by unit tests, and end-to-end verified against the live API.
+The SDK provides typed API operations generated from the Flashduty OpenAPI spec, covered by unit tests, and end-to-end verified against the live API.
 
 <Note>
 The SDK is deliberately "thin." Consumer-side logic such as short-ID resolution and cross-endpoint orchestration belongs in the caller (CLI / MCP), not stuffed into the SDK or shoehorned into an endpoint. This keeps the SDK strictly one-to-one with the API — predictable, generatable, and verifiable.
@@ -161,7 +161,6 @@ Endpoints are grouped by service and hang off the client: the call convention is
 | `client.NotificationTemplates` | Notification templates |
 | `client.Changes` | Changes |
 | `client.Diagnostics` | Diagnostics |
-| `client.ServiceMap` | Service map (ServiceMap) |
 | `client.Analytics` | Analytics |
 | `client.A2aAgents` | A2A Agents |
 | `client.Artifacts` | AI SRE artifacts |

en/monitors/targets/configure-targets.mdx

@@ -1,12 +1,12 @@
 ---
 title: "Configure host diagnostic tools"
 description: "Configure host collection, Shell execution policies, and tool switches in agent.yaml"
-keywords: ["agent.yaml", "host diagnostics", "shell.exec", "tool policy", "ServiceMap"]
+keywords: ["agent.yaml", "host diagnostics", "shell.exec", "tool policy"]
 ---
 
 The installation package includes a default `agent.yaml`. Keep the host configuration for initial onboarding. After the host appears in the console, adjust collection settings and tool policies as needed.
 
-Agent configuration contains `host`, `tool_policy`, and optional `servicemap` settings. Edge data sources handle database and middleware connections and diagnostics. See [Data source configuration](/en/monitors/data-sources/data-sources).
+Agent configuration contains `host` and `tool_policy` settings. Edge data sources handle database and middleware connections and diagnostics. See [Data source configuration](/en/monitors/data-sources/data-sources).
 
 ## Basic configuration example
 
@@ -143,8 +143,3 @@ tool_policy:
 ```
 
 After changing `shell_exec.enabled`, `shell_exec.unknown_command_policy`, or `tool_policy.disabled_tools`, send SIGHUP to reload the configuration without restarting the Agent. Policy changes apply to new calls; commands already running or awaiting approval retain their original behavior. See [Reload configuration and verify onboarding](/en/monitors/targets/reload-and-verify#change-the-unknown-command-policy).
-
-
-## ServiceMap
-
-The `servicemap` configuration controls host topology collection and reporting. See [ServiceMap](/en/monitors/targets/servicemap) for requirements and configuration. Configure host tools and ServiceMap as needed.

en/monitors/targets/overview.mdx

@@ -28,7 +28,7 @@ The Agent controls execution through tool policies, parameter validation, comman
 flowchart TD
   center["SaaS Center / AI-SRE"] <-->|WebSocket| edge["monit-edge"]
   edge <-->|WebSocket| agent["monit-agent"]
-  agent --> host["Host tools / ServiceMap"]
+  agent --> host["Host tools"]
   edge --> datasource["Data source queries / Database and middleware diagnostics"]
 ```
 
@@ -78,7 +78,6 @@ Errors are returned via `error.reason`:
 | `datasource_disabled` | The data source is disabled (`enabled=false`) |
 | `datasource_not_found` | The data source does not exist |
 
-The Agent also provides host topology collection and reporting for [ServiceMap](/en/monitors/targets/servicemap).
 
 <Tip>
 Use stable and recognizable values for object identifiers (`target_locator`), such as fixed private IP addresses or DNS names. Do not use addresses that only make sense locally, such as `localhost` or `127.0.0.1`, as the displayed object address.

en/monitors/targets/reload-and-verify.mdx

@@ -10,7 +10,7 @@ Different `monit-agent` configuration changes take effect in different ways. Thi
 
 | Change | How it takes effect |
 |---|---|
-| `host` collection, `tool_policy` settings, and `servicemap` configuration in `agent.yaml` | Send SIGHUP to reload |
+| `host` collection, `tool_policy` settings in `agent.yaml` | Send SIGHUP to reload |
 | `host.shell_exec.unknown_command_policy` | Send SIGHUP to reload |
 | Edge address, Basic Auth, TLS, `hostLocator`, audit directory | Restart the Agent |
 
@@ -87,7 +87,7 @@ If `agent.yaml` was modified, check for YAML syntax errors, unsupported fields,
 
 1. Onboard only the host object first.
 2. After the host appears in the console, adjust host collection, Shell execution policies, and tool switches.
-3. Verify host diagnostic results. Configure ServiceMap for topology, or a separate data source for database and middleware diagnostics.
+3. Verify host diagnostic results. Configure a separate data source for database and middleware diagnostics.
 
 ## Related docs