File Coverage

blib/lib/Paws/GameLift/Event.pm
Criterion Covered Total %
statement 3 3 100.0
branch n/a
condition n/a
subroutine 1 1 100.0
pod n/a
total 4 4 100.0


line stmt bran cond sub pod time code
1             package Paws::GameLift::Event;
2 1     1   719 use Moose;
  1         4  
  1         11  
3             has EventCode => (is => 'ro', isa => 'Str');
4             has EventId => (is => 'ro', isa => 'Str');
5             has EventTime => (is => 'ro', isa => 'Str');
6             has Message => (is => 'ro', isa => 'Str');
7             has PreSignedLogUrl => (is => 'ro', isa => 'Str');
8             has ResourceId => (is => 'ro', isa => 'Str');
9             1;
10              
11             ### main pod documentation begin ###
12              
13             =head1 NAME
14              
15             Paws::GameLift::Event
16              
17             =head1 USAGE
18              
19             This class represents one of two things:
20              
21             =head3 Arguments in a call to a service
22              
23             Use the attributes of this class as arguments to methods. You shouldn't make instances of this class.
24             Each attribute should be used as a named argument in the calls that expect this type of object.
25              
26             As an example, if Att1 is expected to be a Paws::GameLift::Event object:
27              
28             $service_obj->Method(Att1 => { EventCode => $value, ..., ResourceId => $value });
29              
30             =head3 Results returned from an API call
31              
32             Use accessors for each attribute. If Att1 is expected to be an Paws::GameLift::Event object:
33              
34             $result = $service_obj->Method(...);
35             $result->Att1->EventCode
36              
37             =head1 DESCRIPTION
38              
39             Log entry describing an event that involves Amazon GameLift resources
40             (such as a fleet). In addition to tracking activity, event codes and
41             messages can provide additional information for troubleshooting and
42             debugging problems.
43              
44             =head1 ATTRIBUTES
45              
46              
47             =head2 EventCode => Str
48              
49             Type of event being logged. The following events are currently in use:
50              
51             =over
52              
53             =item *
54              
55             General events:
56              
57             =over
58              
59             =item *
60              
61             B<GENERIC_EVENT> E<ndash> An unspecified event has occurred.
62              
63             =back
64              
65             =item *
66              
67             Fleet creation events:
68              
69             =over
70              
71             =item *
72              
73             B<FLEET_CREATED> E<ndash> A fleet record was successfully created with
74             a status of NEW. Event messaging includes the fleet ID.
75              
76             =item *
77              
78             B<FLEET_STATE_DOWNLOADING> E<ndash> Fleet status changed from NEW to
79             DOWNLOADING. The compressed build has started downloading to a fleet
80             instance for installation.
81              
82             =item *
83              
84             B<FLEET_BINARY_DOWNLOAD_FAILED> E<ndash> The build failed to download
85             to the fleet instance.
86              
87             =item *
88              
89             B<FLEET_CREATION_EXTRACTING_BUILD> E<ndash> The game server build was
90             successfully downloaded to an instance, and the build files are now
91             being extracted from the uploaded build and saved to an instance.
92             Failure at this stage prevents a fleet from moving to ACTIVE status.
93             Logs for this stage display a list of the files that are extracted and
94             saved on the instance. Access the logs by using the URL in
95             I<PreSignedLogUrl>).
96              
97             =item *
98              
99             B<FLEET_CREATION_RUNNING_INSTALLER> E<ndash> The game server build
100             files were successfully extracted, and the Amazon GameLift is now
101             running the build's install script (if one is included). Failure in
102             this stage prevents a fleet from moving to ACTIVE status. Logs for this
103             stage list the installation steps and whether or not the install
104             completed sucessfully. Access the logs by using the URL in
105             I<PreSignedLogUrl>).
106              
107             =item *
108              
109             B<FLEET_CREATION_VALIDATING_RUNTIME_CONFIG> E<ndash> The build process
110             was successful, and the Amazon GameLift is now verifying that the game
111             server launch path(s), which are specified in the fleet's run-time
112             configuration, exist. If any listed launch path exists, Amazon GameLift
113             tries to launch a game server process and waits for the process to
114             report ready. Failures in this stage prevent a fleet from moving to
115             ACTIVE status. Logs for this stage list the launch paths in the
116             run-time configuration and indicate whether each is found. Access the
117             logs by using the URL in I<PreSignedLogUrl>). Once the game server is
118             launched, failures and crashes are logged; these logs can be downloaded
119             from the Amazon GameLift console.
120              
121             =item *
122              
123             B<FLEET_STATE_VALIDATING> E<ndash> Fleet status changed from
124             DOWNLOADING to VALIDATING.
125              
126             =item *
127              
128             B<FLEET_VALIDATION_LAUNCH_PATH_NOT_FOUND> E<ndash> Validation of the
129             run-time validation failed because the executable specified in a launch
130             path does not exist on the instance.
131              
132             =item *
133              
134             B<FLEET_STATE_BUILDING> E<ndash> Fleet status changed from VALIDATING
135             to BUILDING.
136              
137             =item *
138              
139             B<FLEET_VALIDATION_EXECUTABLE_RUNTIME_FAILURE> E<ndash> Validation of
140             the runtime validation failed because the executable specified in a
141             launch path failed to run on the fleet instance.
142              
143             =item *
144              
145             B<FLEET_STATE_ACTIVATING> E<ndash> Fleet status changed from BUILDING
146             to ACTIVATING.
147              
148             =item *
149              
150             B<FLEET_ACTIVATION_FAILED> - The fleet failed to successfully complete
151             one of the steps in the fleet activation process. This event code
152             indicates that the game build was successfully downloaded to a fleet
153             instance, built, and validated, but was not able to start a server
154             process. A possible reason for failure is that the game server is not
155             reporting "process ready" to the Amazon GameLift service.
156              
157             =item *
158              
159             B<FLEET_STATE_ACTIVE> E<ndash> The fleet's status changed from
160             ACTIVATING to ACTIVE. The fleet is now ready to host game sessions.
161              
162             =back
163              
164             =item *
165              
166             Other fleet events:
167              
168             =over
169              
170             =item *
171              
172             B<FLEET_SCALING_EVENT> E<ndash> A change was made to the fleet's
173             capacity settings (desired instances, minimum/maximum scaling limits).
174             Event messaging includes the new capacity settings.
175              
176             =item *
177              
178             B<FLEET_NEW_GAME_SESSION_PROTECTION_POLICY_UPDATED> E<ndash> A change
179             was made to the fleet's game session protection policy setting. Event
180             messaging includes both the old and new policy setting.
181              
182             =item *
183              
184             B<FLEET_DELETED> E<ndash> A request to delete a fleet was initiated.
185              
186             =back
187              
188             =back
189              
190              
191              
192             =head2 EventId => Str
193              
194             Unique identifier for a fleet event.
195              
196              
197             =head2 EventTime => Str
198              
199             Time stamp indicating when this event occurred. Format is a number
200             expressed in Unix time as milliseconds (for example "1469498468.057").
201              
202              
203             =head2 Message => Str
204              
205             Additional information related to the event.
206              
207              
208             =head2 PreSignedLogUrl => Str
209              
210             Location of stored logs with additional detail related to the event,
211             useful for debugging issues. The URL is valid for 15 minutes. Fleet
212             creation logs can also be accessed through the Amazon GameLift console.
213              
214              
215             =head2 ResourceId => Str
216              
217             Unique identifier for an event resource, such as a fleet ID.
218              
219              
220              
221             =head1 SEE ALSO
222              
223             This class forms part of L<Paws>, describing an object used in L<Paws::GameLift>
224              
225             =head1 BUGS and CONTRIBUTIONS
226              
227             The source code is located here: https://github.com/pplu/aws-sdk-perl
228              
229             Please report bugs to: https://github.com/pplu/aws-sdk-perl/issues
230              
231             =cut
232