Orchestrator Details
Click an orchestrator name from the Orchestrators list to view its detail page. This page provides a comprehensive view of the orchestrator's configuration and the tenants it manages.
Overview Card
The overview card displays orchestrator metadata in a 2x4 grid layout:
| Field | Description |
|---|---|
| Name | Display name of the orchestrator |
| Status | Current operational status |
| Contact Email | Administrative contact |
| URL | Base URL of the orchestrator instance (displayed in monospace) |
| Client ID | Authentication identifier (displayed in monospace) |
| Created | Date the orchestrator was provisioned |
| Last Used | Timestamp of the most recent API interaction |
The Last Used field shows when the orchestrator last called the Global VSA API. This updates on every feature sync (every 5 minutes) or metrics report (every 10 minutes). If this timestamp is stale, the orchestrator may have lost connectivity to Global VSA.
Associated Tenants
Below the overview card, a table lists all tenants registered through this orchestrator. The table header shows the total count as Tenants (N), where N is the number of associated tenants.
Table columns:
| Column | Description |
|---|---|
| Tenant Name | Display name of the tenant |
| Tenant ID | Unique identifier assigned by the orchestrator |
| Status | Current lifecycle status (pending_approval, active, suspended, rejected) |
| Registered Date | When the tenant was first registered with Global VSA |
Click any row to navigate to the tenant detail page, where you can review tenant information, manage feature toggles, and take status actions.
Use Cases
Use the orchestrator detail page to:
- Audit tenant distribution -- Understand which orchestrator manages which tenants.
- Monitor connectivity -- Check the "Last Used" timestamp to confirm the orchestrator is actively communicating with Global VSA.
- Investigate issues -- If a tenant reports problems, identify their orchestrator and check its status.
- Plan capacity -- Review how many tenants are assigned to each orchestrator for load balancing decisions.