Skip to main content
Version: 1.3

Managing services

Route: /services

Create, edit, and delete entries in the service catalog. Each entry defines how a service appears on the service map and which Service ID links alerts, KPIs, and topologies to that service.

See also: Overview · Service map · Alert-based suggestions

Catalog fields​

FieldCreateEditDescription
Service IDRequiredRead-onlyUnique identifier; must match the service value on alerts. Pick from alert-derived suggestions or type a new ID.
NameRequiredEditableDisplay name on the map node and in lists
DescriptionOptionalEditableInternal notes (not shown on the map node label)
IconOptionalEditableIcon on the map node; default is a server icon
Service ID

The Service ID cannot be changed after creation. Plan IDs to match your alert sources (for example payments-api, core-db). On create, the Service ID dropdown lists service names seen in alerts that are not yet in the catalog; you can also type a new value.

Create a service​

  1. Open Alerts → Services (/services).
  2. Click Add service.
  3. Set Service ID — select an existing alert service name or enter a new ID (for example docs-demo-service).
  4. Set Name (for example Docs Demo Service).
  5. Optionally add Description.
  6. Choose an Icon (see Icon picker below).
  7. Click Save.

The new node appears on the service map connected to the Enterprise hub.

Add service drawer

Create service — filled form

Edit a service​

  1. Right-click the service node and choose Edit service, or select the node and click Edit service in the alerts panel header.
  2. Update Name, Description, or Icon. Service ID is disabled.
  3. Click Save.

The map node label and icon update immediately.

Edit service drawer

You can also deep-link to edit mode with ?service=<service-id>&edit=1 on /services.

Delete a service​

Single delete​

  1. Right-click the node → Delete service, or select the node and click Delete service in the alerts panel.
  2. Confirm in the dialog.

The node and catalog entry are removed. This does not delete historical alerts — only the catalog record.

Bulk delete​

  1. Select multiple service nodes on the map (click with modifier keys or drag a selection box).
  2. Right-click the selection.
  3. Choose Delete N services from the context menu.
  4. Confirm.

The Enterprise hub node and suggested (dashed) nodes cannot be deleted.

Icon picker​

The Icon field uses a searchable icon picker with three types:

TypeDescription
DashboardBuilt-in product icons (SVG assets)
FontAwesomeSolid Font Awesome icons — search by name
Custom SVGPaste raw SVG markup; preview shown below the textarea
  1. In the create or edit drawer, find Icon.
  2. Use the segmented control to switch Dashboard, FontAwesome, or Custom SVG.
  3. For Dashboard or FontAwesome, open the dropdown, type in Search icon…, and pick an icon.
  4. For Custom SVG, paste markup and verify the Preview.
  5. Save the service — the map node uses the new icon (size scales with alert count).

Icon picker — FontAwesome

Service ID from alerts​

When creating a service, the Service ID dropdown is populated from unique service values on active alerts that are not already in the catalog. If every alert service is already cataloged, the dropdown shows You have already added all services — enter a new ID manually instead.

This is the current way to spot missing services from alert traffic — see Alert-based suggestions for details (note: the old map-wide ghost-node preview described there has been removed; only this dropdown remains).

Best practices​

  1. Align Service ID with alert payloads — mismatched IDs mean alerts won't attach to the node.
  2. Use descriptive Names even when the ID is technical (prod-k8s-ingress → Production Ingress).
  3. Standardize icons by layer (database, queue, API) using FontAwesome or Dashboard sets.
  4. Avoid duplicate catalog entries — check the Service ID dropdown before manually typing IDs.
  5. Review before bulk delete — topologies and KPIs may reference catalog services.