line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
package Paws::GameLift::Event; |
2
|
1
|
|
|
1
|
|
464
|
use Moose; |
|
1
|
|
|
|
|
3
|
|
|
1
|
|
|
|
|
8
|
|
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
|
|
|
|
|
|
|
B<General events:> |
52
|
|
|
|
|
|
|
|
53
|
|
|
|
|
|
|
=over |
54
|
|
|
|
|
|
|
|
55
|
|
|
|
|
|
|
=item * |
56
|
|
|
|
|
|
|
|
57
|
|
|
|
|
|
|
GENERIC_EVENT -- An unspecified event has occurred. |
58
|
|
|
|
|
|
|
|
59
|
|
|
|
|
|
|
=back |
60
|
|
|
|
|
|
|
|
61
|
|
|
|
|
|
|
B<Fleet creation events:> |
62
|
|
|
|
|
|
|
|
63
|
|
|
|
|
|
|
=over |
64
|
|
|
|
|
|
|
|
65
|
|
|
|
|
|
|
=item * |
66
|
|
|
|
|
|
|
|
67
|
|
|
|
|
|
|
FLEET_CREATED -- A fleet record was successfully created with a status |
68
|
|
|
|
|
|
|
of C<NEW>. Event messaging includes the fleet ID. |
69
|
|
|
|
|
|
|
|
70
|
|
|
|
|
|
|
=item * |
71
|
|
|
|
|
|
|
|
72
|
|
|
|
|
|
|
FLEET_STATE_DOWNLOADING -- Fleet status changed from C<NEW> to |
73
|
|
|
|
|
|
|
C<DOWNLOADING>. The compressed build has started downloading to a fleet |
74
|
|
|
|
|
|
|
instance for installation. |
75
|
|
|
|
|
|
|
|
76
|
|
|
|
|
|
|
=item * |
77
|
|
|
|
|
|
|
|
78
|
|
|
|
|
|
|
FLEET_BINARY_DOWNLOAD_FAILED -- The build failed to download to the |
79
|
|
|
|
|
|
|
fleet instance. |
80
|
|
|
|
|
|
|
|
81
|
|
|
|
|
|
|
=item * |
82
|
|
|
|
|
|
|
|
83
|
|
|
|
|
|
|
FLEET_CREATION_EXTRACTING_BUILD E<ndash> The game server build was |
84
|
|
|
|
|
|
|
successfully downloaded to an instance, and the build files are now |
85
|
|
|
|
|
|
|
being extracted from the uploaded build and saved to an instance. |
86
|
|
|
|
|
|
|
Failure at this stage prevents a fleet from moving to C<ACTIVE> status. |
87
|
|
|
|
|
|
|
Logs for this stage display a list of the files that are extracted and |
88
|
|
|
|
|
|
|
saved on the instance. Access the logs by using the URL in |
89
|
|
|
|
|
|
|
I<PreSignedLogUrl>. |
90
|
|
|
|
|
|
|
|
91
|
|
|
|
|
|
|
=item * |
92
|
|
|
|
|
|
|
|
93
|
|
|
|
|
|
|
FLEET_CREATION_RUNNING_INSTALLER E<ndash> The game server build files |
94
|
|
|
|
|
|
|
were successfully extracted, and the Amazon GameLift is now running the |
95
|
|
|
|
|
|
|
build's install script (if one is included). Failure in this stage |
96
|
|
|
|
|
|
|
prevents a fleet from moving to C<ACTIVE> status. Logs for this stage |
97
|
|
|
|
|
|
|
list the installation steps and whether or not the install completed |
98
|
|
|
|
|
|
|
successfully. Access the logs by using the URL in I<PreSignedLogUrl>. |
99
|
|
|
|
|
|
|
|
100
|
|
|
|
|
|
|
=item * |
101
|
|
|
|
|
|
|
|
102
|
|
|
|
|
|
|
FLEET_CREATION_VALIDATING_RUNTIME_CONFIG -- The build process was |
103
|
|
|
|
|
|
|
successful, and the Amazon GameLift is now verifying that the game |
104
|
|
|
|
|
|
|
server launch paths, which are specified in the fleet's run-time |
105
|
|
|
|
|
|
|
configuration, exist. If any listed launch path exists, Amazon GameLift |
106
|
|
|
|
|
|
|
tries to launch a game server process and waits for the process to |
107
|
|
|
|
|
|
|
report ready. Failures in this stage prevent a fleet from moving to |
108
|
|
|
|
|
|
|
C<ACTIVE> status. Logs for this stage list the launch paths in the |
109
|
|
|
|
|
|
|
run-time configuration and indicate whether each is found. Access the |
110
|
|
|
|
|
|
|
logs by using the URL in I<PreSignedLogUrl>. |
111
|
|
|
|
|
|
|
|
112
|
|
|
|
|
|
|
=item * |
113
|
|
|
|
|
|
|
|
114
|
|
|
|
|
|
|
FLEET_STATE_VALIDATING -- Fleet status changed from C<DOWNLOADING> to |
115
|
|
|
|
|
|
|
C<VALIDATING>. |
116
|
|
|
|
|
|
|
|
117
|
|
|
|
|
|
|
=item * |
118
|
|
|
|
|
|
|
|
119
|
|
|
|
|
|
|
FLEET_VALIDATION_LAUNCH_PATH_NOT_FOUND -- Validation of the run-time |
120
|
|
|
|
|
|
|
configuration failed because the executable specified in a launch path |
121
|
|
|
|
|
|
|
does not exist on the instance. |
122
|
|
|
|
|
|
|
|
123
|
|
|
|
|
|
|
=item * |
124
|
|
|
|
|
|
|
|
125
|
|
|
|
|
|
|
FLEET_STATE_BUILDING -- Fleet status changed from C<VALIDATING> to |
126
|
|
|
|
|
|
|
C<BUILDING>. |
127
|
|
|
|
|
|
|
|
128
|
|
|
|
|
|
|
=item * |
129
|
|
|
|
|
|
|
|
130
|
|
|
|
|
|
|
FLEET_VALIDATION_EXECUTABLE_RUNTIME_FAILURE -- Validation of the |
131
|
|
|
|
|
|
|
run-time configuration failed because the executable specified in a |
132
|
|
|
|
|
|
|
launch path failed to run on the fleet instance. |
133
|
|
|
|
|
|
|
|
134
|
|
|
|
|
|
|
=item * |
135
|
|
|
|
|
|
|
|
136
|
|
|
|
|
|
|
FLEET_STATE_ACTIVATING -- Fleet status changed from C<BUILDING> to |
137
|
|
|
|
|
|
|
C<ACTIVATING>. |
138
|
|
|
|
|
|
|
|
139
|
|
|
|
|
|
|
=item * |
140
|
|
|
|
|
|
|
|
141
|
|
|
|
|
|
|
FLEET_ACTIVATION_FAILED - The fleet failed to successfully complete one |
142
|
|
|
|
|
|
|
of the steps in the fleet activation process. This event code indicates |
143
|
|
|
|
|
|
|
that the game build was successfully downloaded to a fleet instance, |
144
|
|
|
|
|
|
|
built, and validated, but was not able to start a server process. A |
145
|
|
|
|
|
|
|
possible reason for failure is that the game server is not reporting |
146
|
|
|
|
|
|
|
"process ready" to the Amazon GameLift service. |
147
|
|
|
|
|
|
|
|
148
|
|
|
|
|
|
|
=item * |
149
|
|
|
|
|
|
|
|
150
|
|
|
|
|
|
|
FLEET_STATE_ACTIVE -- The fleet's status changed from C<ACTIVATING> to |
151
|
|
|
|
|
|
|
C<ACTIVE>. The fleet is now ready to host game sessions. |
152
|
|
|
|
|
|
|
|
153
|
|
|
|
|
|
|
=back |
154
|
|
|
|
|
|
|
|
155
|
|
|
|
|
|
|
B<VPC peering events:> |
156
|
|
|
|
|
|
|
|
157
|
|
|
|
|
|
|
=over |
158
|
|
|
|
|
|
|
|
159
|
|
|
|
|
|
|
=item * |
160
|
|
|
|
|
|
|
|
161
|
|
|
|
|
|
|
FLEET_VPC_PEERING_SUCCEEDED -- A VPC peering connection has been |
162
|
|
|
|
|
|
|
established between the VPC for an Amazon GameLift fleet and a VPC in |
163
|
|
|
|
|
|
|
your AWS account. |
164
|
|
|
|
|
|
|
|
165
|
|
|
|
|
|
|
=item * |
166
|
|
|
|
|
|
|
|
167
|
|
|
|
|
|
|
FLEET_VPC_PEERING_FAILED -- A requested VPC peering connection has |
168
|
|
|
|
|
|
|
failed. Event details and status information (see |
169
|
|
|
|
|
|
|
DescribeVpcPeeringConnections) provide additional detail. A common |
170
|
|
|
|
|
|
|
reason for peering failure is that the two VPCs have overlapping CIDR |
171
|
|
|
|
|
|
|
blocks of IPv4 addresses. To resolve this, change the CIDR block for |
172
|
|
|
|
|
|
|
the VPC in your AWS account. For more information on VPC peering |
173
|
|
|
|
|
|
|
failures, see |
174
|
|
|
|
|
|
|
http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/invalid-peering-configurations.html |
175
|
|
|
|
|
|
|
|
176
|
|
|
|
|
|
|
=item * |
177
|
|
|
|
|
|
|
|
178
|
|
|
|
|
|
|
FLEET_VPC_PEERING_DELETED -- A VPC peering connection has been |
179
|
|
|
|
|
|
|
successfully deleted. |
180
|
|
|
|
|
|
|
|
181
|
|
|
|
|
|
|
=back |
182
|
|
|
|
|
|
|
|
183
|
|
|
|
|
|
|
B<Other fleet events:> |
184
|
|
|
|
|
|
|
|
185
|
|
|
|
|
|
|
=over |
186
|
|
|
|
|
|
|
|
187
|
|
|
|
|
|
|
=item * |
188
|
|
|
|
|
|
|
|
189
|
|
|
|
|
|
|
FLEET_SCALING_EVENT -- A change was made to the fleet's capacity |
190
|
|
|
|
|
|
|
settings (desired instances, minimum/maximum scaling limits). Event |
191
|
|
|
|
|
|
|
messaging includes the new capacity settings. |
192
|
|
|
|
|
|
|
|
193
|
|
|
|
|
|
|
=item * |
194
|
|
|
|
|
|
|
|
195
|
|
|
|
|
|
|
FLEET_NEW_GAME_SESSION_PROTECTION_POLICY_UPDATED -- A change was made |
196
|
|
|
|
|
|
|
to the fleet's game session protection policy setting. Event messaging |
197
|
|
|
|
|
|
|
includes both the old and new policy setting. |
198
|
|
|
|
|
|
|
|
199
|
|
|
|
|
|
|
=item * |
200
|
|
|
|
|
|
|
|
201
|
|
|
|
|
|
|
FLEET_DELETED -- A request to delete a fleet was initiated. |
202
|
|
|
|
|
|
|
|
203
|
|
|
|
|
|
|
=back |
204
|
|
|
|
|
|
|
|
205
|
|
|
|
|
|
|
|
206
|
|
|
|
|
|
|
|
207
|
|
|
|
|
|
|
=head2 EventId => Str |
208
|
|
|
|
|
|
|
|
209
|
|
|
|
|
|
|
Unique identifier for a fleet event. |
210
|
|
|
|
|
|
|
|
211
|
|
|
|
|
|
|
|
212
|
|
|
|
|
|
|
=head2 EventTime => Str |
213
|
|
|
|
|
|
|
|
214
|
|
|
|
|
|
|
Time stamp indicating when this event occurred. Format is a number |
215
|
|
|
|
|
|
|
expressed in Unix time as milliseconds (for example "1469498468.057"). |
216
|
|
|
|
|
|
|
|
217
|
|
|
|
|
|
|
|
218
|
|
|
|
|
|
|
=head2 Message => Str |
219
|
|
|
|
|
|
|
|
220
|
|
|
|
|
|
|
Additional information related to the event. |
221
|
|
|
|
|
|
|
|
222
|
|
|
|
|
|
|
|
223
|
|
|
|
|
|
|
=head2 PreSignedLogUrl => Str |
224
|
|
|
|
|
|
|
|
225
|
|
|
|
|
|
|
Location of stored logs with additional detail that is related to the |
226
|
|
|
|
|
|
|
event. This is useful for debugging issues. The URL is valid for 15 |
227
|
|
|
|
|
|
|
minutes. You can also access fleet creation logs through the Amazon |
228
|
|
|
|
|
|
|
GameLift console. |
229
|
|
|
|
|
|
|
|
230
|
|
|
|
|
|
|
|
231
|
|
|
|
|
|
|
=head2 ResourceId => Str |
232
|
|
|
|
|
|
|
|
233
|
|
|
|
|
|
|
Unique identifier for an event resource, such as a fleet ID. |
234
|
|
|
|
|
|
|
|
235
|
|
|
|
|
|
|
|
236
|
|
|
|
|
|
|
|
237
|
|
|
|
|
|
|
=head1 SEE ALSO |
238
|
|
|
|
|
|
|
|
239
|
|
|
|
|
|
|
This class forms part of L<Paws>, describing an object used in L<Paws::GameLift> |
240
|
|
|
|
|
|
|
|
241
|
|
|
|
|
|
|
=head1 BUGS and CONTRIBUTIONS |
242
|
|
|
|
|
|
|
|
243
|
|
|
|
|
|
|
The source code is located here: https://github.com/pplu/aws-sdk-perl |
244
|
|
|
|
|
|
|
|
245
|
|
|
|
|
|
|
Please report bugs to: https://github.com/pplu/aws-sdk-perl/issues |
246
|
|
|
|
|
|
|
|
247
|
|
|
|
|
|
|
=cut |
248
|
|
|
|
|
|
|
|