@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class PutTraceSegmentsRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP| Constructor and Description |
|---|
PutTraceSegmentsRequest() |
| Modifier and Type | Method and Description |
|---|---|
PutTraceSegmentsRequest |
clone() |
boolean |
equals(Object obj) |
List<String> |
getTraceSegmentDocuments()
A JSON document defining one or more segments or subsegments.
|
int |
hashCode() |
void |
setTraceSegmentDocuments(Collection<String> traceSegmentDocuments)
A JSON document defining one or more segments or subsegments.
|
String |
toString()
Returns a string representation of this object; useful for testing and debugging.
|
PutTraceSegmentsRequest |
withTraceSegmentDocuments(Collection<String> traceSegmentDocuments)
A JSON document defining one or more segments or subsegments.
|
PutTraceSegmentsRequest |
withTraceSegmentDocuments(String... traceSegmentDocuments)
A JSON document defining one or more segments or subsegments.
|
addHandlerContext, copyBaseTo, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic List<String> getTraceSegmentDocuments()
A JSON document defining one or more segments or subsegments. Segments must include the following fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16 hexadecimal
digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a single
client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch time,
accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example, 1480615200.090 or
1.480615200090E9. Specify either an end_time or in_progress.
in_progress - Set to true instead of specifying an end_time to record that
a segment has been started, but is not complete. Send an in progress segment when your application receives a
request that will take a long time to serve, to trace the fact that the request was received. When the response
is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM December 2nd,
2016 PST in epoch time is 1480615200 seconds, or 58406520 in hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16
hexadecimal digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a
single client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch
time, accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9
.
end_time - Time the segment or subsegment was closed. For example,
1480615200.090 or 1.480615200090E9. Specify either an end_time or
in_progress.
in_progress - Set to true instead of specifying an end_time to
record that a segment has been started, but is not complete. Send an in progress segment when your
application receives a request that will take a long time to serve, to trace the fact that the request
was received. When the response is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM
December 2nd, 2016 PST in epoch time is 1480615200 seconds, or 58406520 in
hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
public void setTraceSegmentDocuments(Collection<String> traceSegmentDocuments)
A JSON document defining one or more segments or subsegments. Segments must include the following fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16 hexadecimal
digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a single
client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch time,
accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example, 1480615200.090 or
1.480615200090E9. Specify either an end_time or in_progress.
in_progress - Set to true instead of specifying an end_time to record that
a segment has been started, but is not complete. Send an in progress segment when your application receives a
request that will take a long time to serve, to trace the fact that the request was received. When the response
is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM December 2nd,
2016 PST in epoch time is 1480615200 seconds, or 58406520 in hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
traceSegmentDocuments - A JSON document defining one or more segments or subsegments. Segments must include the following
fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16
hexadecimal digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a
single client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch
time, accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example,
1480615200.090 or 1.480615200090E9. Specify either an end_time or
in_progress.
in_progress - Set to true instead of specifying an end_time to
record that a segment has been started, but is not complete. Send an in progress segment when your
application receives a request that will take a long time to serve, to trace the fact that the request was
received. When the response is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM
December 2nd, 2016 PST in epoch time is 1480615200 seconds, or 58406520 in
hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
public PutTraceSegmentsRequest withTraceSegmentDocuments(String... traceSegmentDocuments)
A JSON document defining one or more segments or subsegments. Segments must include the following fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16 hexadecimal
digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a single
client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch time,
accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example, 1480615200.090 or
1.480615200090E9. Specify either an end_time or in_progress.
in_progress - Set to true instead of specifying an end_time to record that
a segment has been started, but is not complete. Send an in progress segment when your application receives a
request that will take a long time to serve, to trace the fact that the request was received. When the response
is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM December 2nd,
2016 PST in epoch time is 1480615200 seconds, or 58406520 in hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
NOTE: This method appends the values to the existing list (if any). Use
setTraceSegmentDocuments(java.util.Collection) or
withTraceSegmentDocuments(java.util.Collection) if you want to override the existing values.
traceSegmentDocuments - A JSON document defining one or more segments or subsegments. Segments must include the following
fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16
hexadecimal digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a
single client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch
time, accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example,
1480615200.090 or 1.480615200090E9. Specify either an end_time or
in_progress.
in_progress - Set to true instead of specifying an end_time to
record that a segment has been started, but is not complete. Send an in progress segment when your
application receives a request that will take a long time to serve, to trace the fact that the request was
received. When the response is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM
December 2nd, 2016 PST in epoch time is 1480615200 seconds, or 58406520 in
hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
public PutTraceSegmentsRequest withTraceSegmentDocuments(Collection<String> traceSegmentDocuments)
A JSON document defining one or more segments or subsegments. Segments must include the following fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16 hexadecimal
digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a single
client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch time,
accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example, 1480615200.090 or
1.480615200090E9. Specify either an end_time or in_progress.
in_progress - Set to true instead of specifying an end_time to record that
a segment has been started, but is not complete. Send an in progress segment when your application receives a
request that will take a long time to serve, to trace the fact that the request was received. When the response
is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM December 2nd,
2016 PST in epoch time is 1480615200 seconds, or 58406520 in hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
traceSegmentDocuments - A JSON document defining one or more segments or subsegments. Segments must include the following
fields.
Required Segment Document Fields
name - The name of the service that handled the request.
id - A 64-bit identifier for the segment, unique among segments in the same trace, in 16
hexadecimal digits.
trace_id - A unique identifier that connects all segments and subsegments originating from a
single client request.
start_time - Time the segment or subsegment was created, in floating point seconds in epoch
time, accurate to milliseconds. For example, 1480615200.010 or 1.480615200010E9.
end_time - Time the segment or subsegment was closed. For example,
1480615200.090 or 1.480615200090E9. Specify either an end_time or
in_progress.
in_progress - Set to true instead of specifying an end_time to
record that a segment has been started, but is not complete. Send an in progress segment when your
application receives a request that will take a long time to serve, to trace the fact that the request was
received. When the response is sent, send the complete segment to overwrite the in-progress segment.
A trace_id consists of three numbers separated by hyphens. For example,
1-58406520-a006649127e371903a2de979. This includes:
Trace ID Format
The version number, i.e. 1.
The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM
December 2nd, 2016 PST in epoch time is 1480615200 seconds, or 58406520 in
hexadecimal.
A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.
public String toString()
toString in class ObjectObject.toString()public PutTraceSegmentsRequest clone()
clone in class AmazonWebServiceRequestCopyright © 2017. All rights reserved.