Servers
Servers are viewed and managed through the servers dashboard.
To get there:
- Expand the Infrastructure tab from the main, left-hand navigation.
- Select Servers from the sub menu below.
Events
A graph and list of infrastructure events for the selected server.
Server Telemetry
A series of relevant server telemetry. The time-frame can be changed using the gear.
| Graph | Description |
|---|---|
| Load Averages | System load averages over time-frame selected. This indicates how busy the server's CPU is. |
| CPU Usage | CPU usage over the time-frame selected. |
| RAM Usage | Current RAM usage over the time-frame selected. |
| Pool Storage Usage | How much of the total pool storage is being used. |
| Base Storage Usage | How much of the base volume is currently in use. |
Learn more about server storage fields
Server Details
An aggregate of fields describing server information.
| Field | Description |
|---|---|
| Cluster | The cluster the server is deployed in. |
| Provider | The cloud or infrastructure provider hosting the server. |
| Node ID | The unique identifier for the server node in the infrastructure. |
| Load | The 1, 5, and 15 minute load average. |
| RAM | Current RAM usage vs total available. |
| Base Volume | Current base volume usage vs total available. |
| Last Checkin | The time since the server last reported its status. |
| Uptime | The total time the server has been continuously running without restarting. |
| Drivers | Additional Drivers information. |
| CPU | The specifications of the CPU, including the model, core count, and thread count. |
| Constraints | Data on current server configuration in regards to allow pool and allow services. |
| Kernel | The version of the kernel the server is currently using. |
| Versions | Information about versions of Cycle software the server is running. |
| External IPs | The public-facing IP addresses of the server, including both IPv4 and IPv6 addresses. |
| Base Volume | Used vs total available on the node. |
| Agent Volume | Used vs total available on the node. Indicates the storage for agent-specific data. Having a separate volume allows the agent to not be constrained in space during times of extreme usage on any given node. |
| Log Volume | Each server now mounts a 10GB hard capped log volume. This guards against disk pressure caused by containers with uncontrolled log output from filling the servers disk entirely. Once disk usage for this volume hits 90% log retention is reduced from 72 to 48 hours. |
| RAM Usage | Used vs total available on the node. Reflects the current memory utilization. |
| RAM Allocation | Used vs total available on the node. Displays reserved memory allocation. |
| CPU Allocation | Used vs total available on the node. Highlights allocated CPU resources. This uses "Shares" a value specific to Cycle. See CPU Shares. |
Neighbor Latency
A table that describes the latency between nodes in the cluster.
| Field | Description |
|---|---|
| Destination | The neighboring server or node that is being measured for latency. |
| Latency | The round-trip time (in milliseconds) it takes for data to travel to the destination and back. |
| Last Checked | The time elapsed since the latency was last measured. |