Skip to content

Servers

Servers document your infrastructure inventory—physical servers, virtual machines, containers, and cloud instances. Link servers to applications, locations, and connections to build a complete picture of your IT infrastructure.

Getting started

Navigate to IT Operations → Servers to see your server inventory. Click Add Server to create your first entry.

Required fields: - Name: A unique server name or hostname - Server Type: Web server, database, application server, etc. - Provider: On-premises, AWS, Azure, GCP, etc. - Environment: Which environment this server belongs to

Strongly recommended: - Lifecycle: Current status (Active, Deprecated, Retired) - Location: Where the server is hosted

Tip: Use consistent naming conventions that include environment and role information (e.g., prod-web-01, dev-db-master).

Working with the list

Default columns: - Name: Server name (click to open workspace) - Server Type: The server's role - Provider: Hosting provider or on-prem - Cluster: Cluster membership or "Cluster" badge if this is a cluster - Environment: Prod, Pre-prod, QA, Test, Dev, Sandbox - Region / Zone: Geographic deployment details - Lifecycle: Current status - Assignments: Number of application assignments - Created: When the record was created

Actions: - Add Server: Create a new server (requires applications:manager permission) - Delete Selected: Remove selected servers (requires applications:admin permission)

Clusters

Servers can be organized into clusters:

Regular server: An individual infrastructure instance Cluster: A group of servers acting as a single logical unit

When creating a server: - Check Is Cluster to mark it as a cluster - Or select an existing cluster in the Cluster field to make it a member

Cluster members inherit some properties from the cluster while maintaining their own identity.

The Servers workspace

Click any row to open the workspace.

Overview

Identity fields: - Name: Server hostname - Server Type: Role (Web, Database, Application, etc.) - Provider: Hosting provider - Environment: Which environment - Region / Zone: Cloud region and availability zone - Location: Link to a Location record - Lifecycle: Current status

Cluster settings: - Is Cluster: Whether this server represents a cluster - Cluster: Which cluster this server belongs to (if any)

Technical details: - Operating System: OS type and version - IP Address: Network address - Network Segment: Network zone or VLAN

Notes: Free-form notes about the server

Application assignments

Servers can be assigned to application instances:

  1. Open an Application workspace
  2. Go to the Servers tab
  3. Add server assignments for each environment's instances

This creates a two-way relationship—you can see: - From the Application: Which servers host each instance - From the Server: Which applications run on it (via the Assignments count)

Connection mapping

Servers participate in Connections:

  1. Create a Connection
  2. Set the Source Server and Destination Server
  3. Or for multi-server connections, add all participating servers

The Connection Map visualizes these relationships.

Tips

  • Name consistently: Include environment, role, and sequence in server names for easy identification.
  • Use clusters: Group related servers (e.g., web cluster, database cluster) to simplify management.
  • Track lifecycle: Mark deprecated and retired servers to maintain accurate inventory.
  • Link to locations: Assign servers to locations for geographic reporting and DR planning.
  • Assign to applications: Link servers to application instances to understand what runs where.