Skip to main content
Version: 1.4 (Current)

Topologies

Route: /service-topology ( Services tab )

A topology record binds a display Name, Description, target Service, and optional Service KPI to the graph of nodes and edges you edit separately in the graph editor. Each service can have at most one topology, and the service of a topology cannot be changed once created.

See also: Overview · Graph editor · Weight policies

Table columns​

ColumnDescription
NameTopology title; click to edit
DescriptionShort summary
ServiceLinked service ID; click to open the graph editor
Service KPIsLinked KPI name, or Not set
Create TimeWhen the record was created
ActionsView, Edit, Delete (when permitted)

The list supports name search (Enter the name) and the TQL ON / TQL OFF tag — see TQL search and filters.

Create a topology​

  1. Open Management → Service Topology ( Services tab ).
  2. Click Create topology.
  3. Choose Service to fetch (required). Services come from the service catalog; use Go to Services if none are listed yet.
  4. Enter Name and Description (required). Selecting a service can auto-fill the name and description.
  5. Optionally select Service KPIs — only KPIs for the chosen service appear.
  6. Click Create.

Create topology drawer

Form fields​

FieldRequiredDescription
Service to fetchYesService ID for this topology; must be unique across topologies
NameYesDisplay name in lists and the graph header
DescriptionYesDescription shown in the table
Service KPIsNoKPI used for service-level uptime views
Service catalog

If no services are available, the drawer shows a warning with Go to Services to create or import services first.

Edit, view, delete​

ActionHow
ViewRow View (eye) or click Service — opens /service-topology/<id>
EditClick Name or Description, double-click the row, bulk Edit topology, or row edit icon. Footer: Update
DeleteRow trash or bulk Delete topology — confirmation required

Closing the drawer with unsaved edits shows the standard unsaved-changes prompt.

Deleting a topology also removes the relations it wrote to the resource graph (source topology). Alerts are not changed.

Bulk actions​

When you select rows, use the bulk bar or context menu — see List tables and bulk actions.

Bulk actionNotes
Edit topologyExactly one row
View topologyExactly one row
Delete topologyOne or more rows — a single confirmation deletes all selected topologies and their resource graph relations

Older topologies​

Topologies created in earlier releases are converted automatically to the nodes-and-edges model when the backend starts on this release. A topology that the migration could not convert (for example the same resource under two environments) still opens and works; fix it in the graph editor and Save changes to store it in the new model. See Upgrading from tree-based topologies.

The Services tab accepts query parameters to open a topology automatically:

QueryBehavior
?id=<topology-id>Opens the graph for that topology if it exists
?service_name=<service-id>Resolves by service name and opens the graph

Invalid IDs show a not-found message and clear the query.

Best practices​

  • Pick the service before naming so auto-description ({name} service topology) stays consistent.
  • Assign a KPI when operators need the KPI dashboard and topology graph for the same service.
  • Use TQL filters on large lists instead of scrolling.
  • Delete unused topologies to stay under license limits and reduce clutter.