All Downloads are FREE. Search and download functionalities are using the official Maven repository.

com.amazonaws.services.xray.model.PutTraceSegmentsRequest Maven / Gradle / Ivy

Go to download

The AWS Java SDK for AWS X-Ray module holds the client classes that are used for communicating with AWS X-Ray Service

There is a newer version: 1.12.780
Show newest version
/*
 * Copyright 2012-2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.
 * 
 * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
 * the License. A copy of the License is located at
 * 
 * http://aws.amazon.com/apache2.0
 * 
 * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
 * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
 * and limitations under the License.
 */
package com.amazonaws.services.xray.model;

import java.io.Serializable;
import javax.annotation.Generated;

import com.amazonaws.AmazonWebServiceRequest;

/**
 * 
 * @see AWS API
 *      Documentation
 */
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class PutTraceSegmentsRequest extends com.amazonaws.AmazonWebServiceRequest implements Serializable, Cloneable {

    /**
     * 

* 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. *

    *
  • *
*/ private java.util.List 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. *

    *
  • *
* * @return 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 java.util.List getTraceSegmentDocuments() { return 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. *

      *
    • *
    * * @param 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 void setTraceSegmentDocuments(java.util.Collection traceSegmentDocuments) { if (traceSegmentDocuments == null) { this.traceSegmentDocuments = null; return; } this.traceSegmentDocuments = new java.util.ArrayList(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 * {@link #setTraceSegmentDocuments(java.util.Collection)} or * {@link #withTraceSegmentDocuments(java.util.Collection)} if you want to override the existing values. *

      * * @param 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. *

        *
      • * @return Returns a reference to this object so that method calls can be chained together. */ public PutTraceSegmentsRequest withTraceSegmentDocuments(String... traceSegmentDocuments) { if (this.traceSegmentDocuments == null) { setTraceSegmentDocuments(new java.util.ArrayList(traceSegmentDocuments.length)); } for (String ele : traceSegmentDocuments) { this.traceSegmentDocuments.add(ele); } return this; } /** *

        * 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. *

          *
        • *
        * * @param 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. *

          *
        • * @return Returns a reference to this object so that method calls can be chained together. */ public PutTraceSegmentsRequest withTraceSegmentDocuments(java.util.Collection traceSegmentDocuments) { setTraceSegmentDocuments(traceSegmentDocuments); return this; } /** * Returns a string representation of this object; useful for testing and debugging. * * @return A string representation of this object. * * @see java.lang.Object#toString() */ @Override public String toString() { StringBuilder sb = new StringBuilder(); sb.append("{"); if (getTraceSegmentDocuments() != null) sb.append("TraceSegmentDocuments: ").append(getTraceSegmentDocuments()); sb.append("}"); return sb.toString(); } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (obj instanceof PutTraceSegmentsRequest == false) return false; PutTraceSegmentsRequest other = (PutTraceSegmentsRequest) obj; if (other.getTraceSegmentDocuments() == null ^ this.getTraceSegmentDocuments() == null) return false; if (other.getTraceSegmentDocuments() != null && other.getTraceSegmentDocuments().equals(this.getTraceSegmentDocuments()) == false) return false; return true; } @Override public int hashCode() { final int prime = 31; int hashCode = 1; hashCode = prime * hashCode + ((getTraceSegmentDocuments() == null) ? 0 : getTraceSegmentDocuments().hashCode()); return hashCode; } @Override public PutTraceSegmentsRequest clone() { return (PutTraceSegmentsRequest) super.clone(); } }




© 2015 - 2025 Weber Informatics LLC | Privacy Policy