Monitor Amazon GameLift with Amazon CloudWatch
You can monitor Amazon GameLift using Amazon CloudWatch, an Amazon service that collects raw data and processes it into readable, near real-time metrics. These statistics are kept for 15 months to provide a historical perspective on how your game server hosting with Amazon GameLift is performing. You can set alarms that watch for certain thresholds and send notifications or take actions when those thresholds are met. For more information, see the Amazon CloudWatch User Guide.
The following tables list the metrics and dimensions for Amazon GameLift. All metrics that are available in CloudWatch are also available in the Amazon GameLift console, which provides the data as a set of customizable graphs. To access CloudWatch metrics for your games, use the Amazon Web Services Management Console, the Amazon CLI, or the CloudWatch API.
If a metric does not have a location, it uses the home location.
Dimensions for Amazon GameLift metrics
Amazon GameLift supports filtering metrics by the following dimensions.
Dimension | Description |
---|---|
|
Filter metrics for a fleet deployment location. If a metric does not have a location, it uses the home location. |
|
Filter metrics for a single fleet. This dimension can be used with all fleet metrics for instances, server processes, game sessions, and player sessions. |
|
Filter metrics for a collection of fleets. Add a fleet to a metric group by adding the metric group name to the fleet's attributes (see UpdateFleetAttributes()). This dimension can be used with all fleet metrics for instances, server processes, game sessions, and player sessions. |
|
Filter metrics for a single queue. This dimension is used with metrics for game session queues only. |
|
Filter metrics for a single matchmaking configuration. This dimension is used with metrics for matchmaking configurations. |
|
Filter metrics for an intersect of a matchmaking configuration and matchmaking rule. This dimension is used with metrics for matchmaking rules only. |
|
Filter metrics for an EC2 instance type designation, such as "c4.large". This dimension is used with metrics for spot instances. |
|
Filter metrics for an instance's operating system This dimension is used with metrics for spot instances. |
|
Filter FleetIQ metrics for a game server group. |
Amazon GameLift metrics for fleets
The AWS/GameLift
namespace includes the following metrics related to
activity across a fleet or a group of fleets. Fleets are used with a managed Amazon GameLift
solution. The Amazon GameLift service sends metrics to CloudWatch every minute.
Instances
Metric | Description |
---|---|
|
Instances with ACTIVE status, which means they are running active server processes. The count includes idle instances and those that are hosting one or more game sessions. This metric measures current total instance capacity. This metric can be used with automatic scaling. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Target number of active instances that Amazon GameLift is working to maintain in the fleet. With automatic scaling, this value is determined based on the scaling policies currently in force. Without automatic scaling, this value is set manually. This metric is not available when viewing data for fleet metric groups. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Active instances that are currently hosting zero (0) game sessions. This metric measures capacity that is available but unused. This metric can be used with automatic scaling. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Maximum number of instances that are allowed for the fleet. A fleet's instance maximum determines the capacity ceiling during manual or automatic scaling up. This metric is not available when viewing data for fleet metric groups. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Minimum number of instances allowed for the fleet. A fleet's instance minimum determines the capacity floor during manual or automatic scaling down. This metric is not available when viewing data for fleet metric groups. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Percentage of all active instances that are idle (calculated
as Units: Percent Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Number of spot instances that have been recycled and replaced. Amazon GameLift recycles spot instances that are not currently hosting game sessions and have a high probability of interruption. Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum Dimensions: Location |
|
Number of spot instances that have been interrupted. Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum Dimensions: Location |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. The percentage of physical CPU time that Amazon EC2 uses to run the instance, which includes time spent to run both the user code and Amazon EC2 code. Tools in your operating system can show a different percentage than CloudWatch due to factors such as legacy device simulation, configuration of non-legacy devices, interrupt-heavy workloads, live migration, and live update. Units: Percent |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. The number of bytes received on all network interfaces by the instance. This metric identifies the volume of incoming network traffic to an application on a single instance. Units: Bytes |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. The number of bytes sent out on all network interfaces by the instance. This metric identifies the volume of outgoing network traffic to an application on a single instance. Units: Bytes |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. Bytes read from all instance store volumes available to the instance. This metric is used to determine the volume of the data the application reads from the hard disk of the instance. You can use it to determine the speed of the application. Units: Bytes |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. Bytes written to all instance store volumes available to the instance. This metric is used to determine the volume of the data the application writes onto the hard disk of the instance. You can use it to determine the speed of the application. Units: Bytes |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. Completed read operations from all instance store volumes available to the instance in a specified period of time. To calculate the average I/O operations per second (IOPS) for the period, divide the total operations in the period by the number of seconds in that period. Units: Count |
|
EC2 metric. For Amazon GameLift this metric represents hardware performance across all active instances in a fleet location. Completed write operations to all instance store volumes available to the instance in a specified period of time. To calculate the average I/O operations per second (IOPS) for the period, divide the total operations in the period by the number of seconds in that period. Units: Count |
Server processes
Metric | Description |
---|---|
|
Server processes with ACTIVE status, which means they are running and able to host game sessions. The count includes idle server processes and those that are hosting game sessions. This metric measures current total server process capacity. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Active server processes that are reporting healthy. This metric is useful for tracking the overall health of the fleet's game servers. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Percentage of all active server processes that are reporting
healthy (calculated as Units: Percent Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Server processes that were shut down due to abnormal circumstances since the last report. This metric includes terminations that were initiated by the Amazon GameLift service. This occurs when a server process stops responding, consistently reports failed health checks, or does not terminate cleanly (by calling ProcessEnding()). Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum Dimensions: Location |
|
Server processes that successfully transitioned from ACTIVATING to ACTIVE status since the last report. Server processes cannot host game sessions until they are active. Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum Dimensions: Location |
|
Server processes that were shut down since the last report. This includes all server processes that transitioned to TERMINATED status for any reason, including normal and abnormal process terminations. Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum Dimensions: Location |
Game sessions
Metric | Description |
---|---|
|
Game sessions with ACTIVATING status, which means they are in the process of starting up. Game sessions cannot host players until they are active. High numbers for a sustained period of time may indicate that game sessions are not transitioning from ACTIVATING to ACTIVE status. This metric can be used with automatic scaling. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Game sessions with ACTIVE status, which means they are able to host players, and are hosting zero or more players. This metric measures the total number of game sessions currently being hosted. This metric can be used with automatic scaling. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Active, healthy server processes that are not currently being used to host a game session and can start a new game session without a delay to spin up new server processes or instances. This metric can be used with automatic scaling. NoteFor fleets that limit concurrent game session activations,
use the metric
Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Active, healthy server processes that are not currently being used to host a game session and can immediately start a new game session. This metric differs from Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: Location |
|
Percentage of game session slots on all active server
processes (healthy or unhealthy) that are not currently being
used (calculated as Units: Percent Relevant CloudWatch statistics: Average Dimensions: Location |
|
Number of game sessions on spot instances that have been interrupted. Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum Dimensions: Location |
Player sessions
Metric | Description |
---|---|
|
Player sessions with either ACTIVE status (player is connected to an active game session) or RESERVED status (player has been given a slot in a game session but hasn't yet connected). This metric can be used with automatic scaling. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum |
|
Player sessions that transitioned from RESERVED status to ACTIVE since the last report. This occurs when a player successfully connects to an active game session. Units: Count Relevant CloudWatch statistics: Sum, Average, Minimum, Maximum |
Amazon GameLift metrics for queues
The Amazon GameLift
namespace includes the following metrics related to activity
across a game session placement queue. Queues are used with a managed Amazon GameLift solution.
The Amazon GameLift service sends metrics to CloudWatch every minute.
Metric | Description |
---|---|
|
Average amount of time that game session placement requests in the queue with status PENDING have been waiting to be fulfilled. Units: Seconds Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum Dimensions: Location |
|
Game sessions that were successfully placed but NOT in the first-choice fleet, because that fleet was considered not viable (such as a spot fleet with a high interruption rate). This metric is based on cost, not latency. The first-choice fleet is either the first fleet listed in the queue or—when a placement request includes player latency data—it is the first fleet chosen by FleetIQ prioritization. If there are no viable spot fleets, any fleet in that region may be selected. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game sessions that were successfully placed but NOT in the first-choice fleet, because that fleet had no available resources. The first-choice fleet is either the first fleet listed in the queue or—when a placement request includes player latency data —it is the first fleet chosen by your defined FleetIQ prioritization. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game sessions that were successfully placed in a region that offers the queue's lowest possible latency for the players. This metric is emitted only when player latency data is included in the placement request. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game sessions that were successfully placed in a fleet with the queue's lowest possible price for the chosen region. This fleet can be either a spot fleet or an on-demand instance if the queue has no spot instances. This metric is emitted only when player latency data is included in the placement request. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game sessions that are successfully placed in fleets located in
the specified region. This metric breaks down the
Units: Count Relevant CloudWatch statistics: Sum |
|
Game session placement requests that were canceled before timing out since the last report. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game session placement requests that failed for any reason since the last report. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
New game session placement requests that were added to the queue since the last report. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game session placement requests that resulted in a new game session since the last report. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Game session placement requests that reached the queue's timeout limit without being fulfilled since the last report. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
Number of game session placement requests in the queue with status PENDING. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum Dimensions: Location |
Amazon GameLift metrics for matchmaking
The Amazon GameLift
namespace includes metrics on FlexMatch activity for matchmaking
configurations and matchmaking rules. FlexMatch matchmaking is used with a managed Amazon GameLift
solution. The Amazon GameLift service sends metrics to CloudWatch every minute.
For more information on the sequence of matchmaking activity, see How Amazon GameLift FlexMatch works.
Matchmaking configurations
Metric |
Description |
---|---|
|
Matchmaking requests currently being processed or waiting to be processed. Units: Count Relevant CloudWatch statistics: Average, Minimum, Maximum, Sum |
|
For matchmaking configurations that require acceptance, the potential matches that timed out during acceptance since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
For matchmaking configurations that require acceptance, the potential matches that were accepted since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
Potential matches that were created since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
Matches that were successfully placed into a game session since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
For matchmaking configurations that require acceptance, the potential matches that were rejected by at least one player since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
Players in matchmaking tickets that were added since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
Matchmaking requests that resulted in failure since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
New matchmaking requests that were created since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
Matchmaking requests that reached the timeout limit since the last report. Units: Count Relevant CloudWatch statistics: Sum |
|
For matchmaking requests that were put into a potential match before the last report, the amount of time between ticket creation and potential match creation. Units: Seconds Relevant CloudWatch statistics: Data Samples, Average, Minimum, Maximum |
|
For matchmaking requests that were canceled before the last report, the amount of time between ticket creation and cancellation. Units: Seconds Relevant CloudWatch statistics: Data Samples, Average, Minimum, Maximum |
|
For matchmaking requests that succeeded before the last report, the amount of time between ticket creation and successful match placement. Units: Seconds Relevant CloudWatch statistics: Data Samples, Average, Minimum, Maximum |
Matchmaking rules
Metric | Description |
---|---|
|
Rule evaluations during the matchmaking process that passed since
the last report. This metric is limited to the top 50
rules. Units: Count Relevant CloudWatch statistics: Sum |
|
Rule evaluations during matchmaking that failed since the last report. This metric is limited to the top 50 rules. Units: Count Relevant CloudWatch statistics: Sum |
Amazon GameLift metrics for FleetIQ
The Amazon GameLift
namespace includes metrics for FleetIQ game server group and game
server activity as part of a FleetIQ standalone solution for game hosting. The Amazon GameLift
service sends metrics to CloudWatch every minute. Also see Monitoring your Auto Scaling groups and
instances using amazon CloudWatch in the
Amazon EC2 Auto Scaling User Guide.
Metric | Description |
---|---|
|
Game servers that are available to run a game execution and are not currently occupied with gameplay. This number includes game servers that have been claimed but are still in AVAILABLE status. Units: Count Relevant CloudWatch statistics: Sum Dimensions: GameServerGroup |
|
Game servers that are currently occupied with gameplay. This number includes game servers that are in UTILIZED status. Units: Count Relevant CloudWatch statistics: Sum Dimensions: GameServerGroup |
|
Game servers on instances scheduled for termination that are currently not supporting gameplay. These game servers are the lowest priority to be claimed in response to a new claim request. Units: Count Relevant CloudWatch statistics: Sum Dimensions: GameServerGroup |
|
Game servers on instances scheduled for termination that are currently supporting gameplay. Units: Count Relevant CloudWatch statistics: Sum Dimensions: GameServerGroup |
|
Portion of game servers that are currently supporting game executions. This metric indicates the amount of game server capacity that is currently in use. It is useful for driving an Auto Scaling policy that can dynamically add and remove instances to match with player demand. Units: Percent Relevant CloudWatch statistics: Average, Minimum, Maximum Dimensions: GameServerGroup |
|
Game servers on Spot Instances that were interrupted due to limited Spot availability. Units: Count Relevant CloudWatch statistics: Sum Dimensions: GameServerGroup, InstanceType |
|
Spot Instances that were interrupted due to limited availability. Units: Count Relevant CloudWatch statistics: Sum Dimensions: GameServerGroup, InstanceType |