View payload metrics

On the Payloads page of the zeuz control panel (ZCP), you can view payload metrics for active payloads that match your filter criteria. See Filter payloads for more information. The metrics show how your payloads are performing based on a time period that you select.

The Active Payloads section of the **Payloads **page shows different types of metrics for your selected active payloads.

Image: Active Payloads section showing performance data for two active payloads.

Select the following options to view different metrics for active payloads matching your filter criteria.

OptionDescription
DATEPICKERSelect one of the following time periods for which to display performance and usage information for your active payloads:

  • Live (default): Current performance data at one minute intervals, for the last 5 minutes.

  • Today: Today’s performance data starting at 00:00H your time in 5-minute intervals.

  • Yesterday: Yesterday’s performance data in 5-minute intervals.

  • Last 7 days: Average hourly performance for the last seven days.

  • Last 30 days: Hourly performance for the last 30 days.

  • Last 90 days: Hourly performance for the last 90 days.

  • Custom: Selecting Custom displays a field allowing you to enter a date range using a pop-up calendar datepicker. Performance data is displayed for the selected date range on hourly intervals.

If you select a time period other than Live, the performance charts do not auto-refresh.
CPU (AVG)Shows average CPU usage across all machines that are running active payloads. This is measured as a percentage of the hardware configuration you specified for the allocation. For example, if a payload quota is set to 2 vcores, then using half a core constitutes 25% CPU.

You can use the metrics_payloadcpuusage API endpoint to fetch current real time data. For more information see metrics_payloadcpuusage.
MEMORY (TOTAL)Shows the total server memory usage (RAM) for all active payloads in mebibytes (MiB).

You can use the metrics_payloadmemoryusage API endpoint to fetch current real time data. For more information see metrics_payloadmemoryusage.
TRAFFIC IN (TOTAL)Shows inbound data transfer network traffic to the active payloads in bytes per second (B/s).

You can use the metrics_payloadnetworkreceived API endpoint to fetch current real time data. For more information see metrics_payloadnetworkreceived.
TRAFFIC OUT (TOTAL)Shows the total outbound data transfer network traffic from the active payloads in bytes per second (B/s).

You can use the metrics_payloadnetworksent API endpoint to fetch current real time data. For more information see metrics_payloadnetworksent.

The Active Payloads window shows performance data for each active payload in a different color, as in the following example:

Image: Chart showing average CPU performance data for each active payload in the last 30 days, with a different color for each payload. The color key for the payloads is to the right of the chart.

Interpreting the charts

Peaks in usage metrics can indicate times of high demand and high CCU. Regular patterns of peak usage can help you determine when you need to allocate more resources to cope with increased demand. Viewing data for the past 7, 30 or 90 days can help you spot any patterns.

Random peaks in payload metrics might indicate external triggers that caused a surge in demand (for example, media coverage about your game or new features might have spiked player interest).


2021-sep-22 Page added with editorial review.


Last edited on: October 15, 2021 (4db86fbb)