APM Service Map Cross-workspace Configuration Guide¶

In the Deployment Plan, the cross-workspace page entry for "APM > Service > Service Map" and the cross-workspace query capability on the Kodo side are controlled by two independent configurations. They can be configured separately based on the scenario or used together to provide both the page entry and cross-workspace topology query capability.

Configuration Items Description¶

Configuration Item	Component	Purpose	Example Value
`enableApmServiceTopology`	Studio Backend	Controls whether the cross-workspace selector is displayed on the Service Map page in the Deployment Plan.	`true`
`cross_workspace_on`	`kodo-inner`	Controls whether Kodo queries cross-workspace service map relationships.	`true`

Feature Description¶

enableApmServiceTopology is a site-level page entry switch. When enabled, workspaces on the Deployment Plan, provided they meet version and permission requirements, will see a workspace scope selector on the Service Map page. Service nodes, call relationships, and topology metrics are queried based on the currently selected workspace scope.

cross_workspace_on is a Kodo-side service map query switch, configured in the kodo-inner ConfigMap. When enabled, the Studio backend, when querying the service map, will convert the user-authorized target workspaces into Kodo query parameters. Kodo then returns service nodes and call edges based on the corresponding workspace scope.

Configuration Location¶

Studio Backend¶

Find the Studio backend configuration in Launcher. Add or modify the following in the corresponding configuration file:

enableApmServiceTopology: true

This configuration is disabled by default. Only when set to true will the frontend display the cross-workspace selection entry on the Deployment Plan's Service Map page.

kodo-inner¶

Find the KodoInner configuration in Launcher. The corresponding Kubernetes ConfigMap is kodo-inner. Add or modify the following in the servicemap configuration section:

servicemap:
  cross_workspace_on: true

Scope of Effect¶

Once enabled, the Service Map page can display ServiceMap data based on the current workspace, all accessible workspaces, or specified authorized workspaces. Searches, filters, service count statistics, node colors, and topology metrics on the page are all calculated based on the currently selected workspace scope.

Without cross-workspace authorization configured, users will still only see data from the current workspace and will not, by default, see service nodes, call edges, or metric data from other workspaces.

Notes¶

enableApmServiceTopology and cross_workspace_on are two independent switches. The former controls the Studio page entry, the latter controls the Kodo-side cross-workspace topology query capability. They can be configured separately based on deployment scenarios or used together.
In the SaaS Commercial Plan, data visibility scope is determined by cross-workspace authorization configuration. The Deployment Plan requires enabling the capability via the site-level configurations mentioned above.
During cross-site queries, all target workspaces in a single query must belong to the same target site.
After modifying configurations, restart or perform rolling updates on the relevant components as required by the deployment environment for the changes to take effect.

Verification Method¶

Navigate to "APM > Service > Service Map".
Confirm that a workspace scope selector appears at the top of the page.
Select other authorized workspace(s) or multiple workspaces.
Confirm that the topology graph, service count, call relationships, and metric data refresh according to the selected workspace scope.
After revoking authorization or disabling the configuration, confirm that entries or data from other workspaces are no longer accessible.