Skip to main content
Version: 1.3

Alert-based suggestions

Route: /services

Feature removed from the service map

The dedicated Alert-based suggestions button (lightbulb icon) that used to preview missing services as ghost nodes on the service map, and let you bulk-add them from the Enterprise hub, is no longer present in the current UI. There is no button, tooltip, or ghost-node preview for this on the map toolbar.

Current equivalent​

The closest current equivalent lives in the Add service drawer:

  1. Open Alerts → Services (/services) and click Add service.
  2. Open the Service ID dropdown — it lists service values seen on active alerts that are not yet in the catalog.
  3. Pick one to prefill the ID, or type a new value if none match.

This covers the same underlying data (alert-derived service names missing from the catalog) but as a searchable dropdown, one service at a time — there is no map-wide ghost-node preview or bulk "add all" action anymore.

See also: Overview · Managing services · Service map

Suggestions inside a service topology​

Alert-driven suggestions do exist for the graph of one service: in the graph editor, Alert-driven service topology asks the server for the environment and resource nodes that the service's active alerts mention but the topology does not have yet. The server also resolves the parents of each suggested resource — from the resourceParent declared by the alerts and, failing that, from the resource graph — so suggestions arrive already chained under the right nodes. This covers resources and environments within a service, not missing services in the catalog.

Bulk-adding many services​

Since there is no bulk "add all suggested services" action, add several missing services one at a time via Add service, or use the service management API (write:services) if you need to script bulk creation.

Empty or limited alert data​

If your environment has no active alerts with a service field not already cataloged, the Service ID dropdown will only show existing catalog IDs or let you type a new one manually.

Best practices​

  1. Check the Service ID dropdown after onboarding a new alert source — new service names appear there automatically.
  2. Align Service ID with alert payloads — the dropdown only helps if alerts already carry a service attribute.
  3. Do not duplicate — if a service already exists in the catalog, it will not appear in the dropdown suggestions.