Overview

What Topology Studio is

TrackMe knows a great deal about your environment: every monitored entity, its health, its priority, its metrics. Topology Studio lets you arrange that knowledge the way you think about your environment — as a dependency map. A payment flow, a datacenter, an ingestion pipeline, a business service: you decide what belongs on the map and how it connects, and TrackMe keeps the map alive.

A topology view is:

• Built from real entities. Every node on the canvas is a monitored TrackMe entity (from any tenant, any component) or a live aggregate of many entities — never a static drawing. When an entity turns red, so does its node.

• Authored, not generated. You place the nodes, you draw the edges, you choose the icons and the layout. The map reflects your understanding of dependencies — which is exactly what makes it valuable during an incident.

• Shared. Views are stored centrally and shared under role-based access control, with separate read and write permissions — author once, consume everywhere, including full-screen on a wall of screens.

• Alerting-capable. Any view can carry Topology Alerts — a state-aware engine that correlates the health of the map and notifies on transitions, with the rendered topology image embedded in the notification email.

• AI-integrated. The AI Assistant understands your views and alerts in context — and can create or modify topologies for you through consented, audited actions.

Core concepts

Views

A view is one topology map: an identifier (view_id, lowercase, up to 40 characters), a display alias, an optional description and category (views sharing a category are grouped together in the list), the canvas content itself, and the role-based access lists. Views are global objects — they are not owned by a tenant, they reference entities across tenants.

Node types

Three kinds of nodes live on the canvas:

• Entity nodes — a single monitored entity, referenced by tenant, component and identity. The node carries the entity’s live state color, and optionally one KPI displayed as an on-canvas card (delay, latency, volume, skip rate… — or, for Flex Objects, FQM and WorkLoad, any of the entity’s own metrics).

• Aggregate nodes — a live roll-up of many entities: one or more tenant/component scopes plus an optional filter (the same filter grammar as Virtual Groups). The node folds to the worst state of everything it matches and shows per-state counts — or, by opt-in, classifies by a healthy-percentage policy with your own thresholds. Aggregates can also auto-populate: their current members appear as linked satellite nodes around them, following membership dynamically.

• Label nodes — free-text annotations with color control, for naming zones, tiers or flows on the map.

Live status

Open a view and it polls live status on a fixed cadence (with an honest countdown, a manual refresh, and a pause/resume toggle). Entity nodes colorize by object_state; aggregates fold their scopes server-side. Nodes whose underlying entity was deleted are flagged as missing (with a one-click cleanup); nodes referencing tenants outside your permissions render neutrally as restricted — see tenant isolation.

How it compares

Feature	Purpose
Topology Studio	Your topology: user-authored maps across tenants and components, persistent, shared under RBAC, live, and alerting-capable.
Built-in topology views	TrackMe’s topology: auto-derived, per-component relationship graphs (tenant → groups → entities) opened from Tenant Home. Read-only, not persistent, no authoring.
Virtual Groups	Read-only aggregation cards in the Virtual Tenants grid — counts across tenants, no canvas, no edges, no alerting.

Hint

The three are complementary: use the built-in topology to discover structure, a Virtual Group for a quick cross-tenant counter, and Topology Studio when you want a curated, persistent, alerting map of what matters.

Where to find it

Click Topology Studio in the TrackMe navigation bar.

The landing page lists every view your roles can see, grouped by category, with search; from there you create, open, duplicate, export or import views. On a fresh install there is nothing to list yet, so the page invites you to create your first view — or to Import one exported from another instance. See Authoring topologies to build the first one.