aws xray

AWS X-Ray provides APIs for managing debug traces and retrieving service maps and other data created by processing those traces


batch-get-tracesRetrieves a list of traces specified by ID. Each trace is a collection of segment documents that originates from a single request. Use GetTraceSummaries to get a list of trace IDs
create-groupCreates a group resource with a name and a filter expression
create-sampling-ruleCreates a rule to control sampling behavior for instrumented applications. Services retrieve rules with GetSamplingRules, and evaluate each rule in ascending order of priority for each request. If a rule matches, the service records a trace, borrowing it from the reservoir size. After 10 seconds, the service reports back to X-Ray with GetSamplingTargets to get updated versions of each in-use rule. The updated rule contains a trace quota that the service can use instead of borrowing from the reservoir
delete-groupDeletes a group resource
delete-sampling-ruleDeletes a sampling rule
get-encryption-configRetrieves the current encryption configuration for X-Ray data
get-groupRetrieves group resource details
get-groupsRetrieves all active group details
get-insightRetrieves the summary information of an insight. This includes impact to clients and root cause services, the top anomalous services, the category, the state of the insight, and the start and end time of the insight
get-insight-eventsX-Ray reevaluates insights periodically until they're resolved, and records each intermediate state as an event. You can review an insight's events in the Impact Timeline on the Inspect page in the X-Ray console
get-insight-impact-graphRetrieves a service graph structure filtered by the specified insight. The service graph is limited to only structural information. For a complete service graph, use this API with the GetServiceGraph API
get-insight-summariesRetrieves the summaries of all insights in the specified group matching the provided filter values
get-sampling-rulesRetrieves all sampling rules
get-sampling-statistic-summariesRetrieves information about recent sampling results for all sampling rules
get-sampling-targetsRequests a sampling quota for rules that the service is using to sample requests
get-service-graphRetrieves a document that describes services that process incoming requests, and downstream services that they call as a result. Root services process incoming requests and make calls to downstream services. Root services are applications that use the AWS X-Ray SDK. Downstream services can be other applications, AWS resources, HTTP web APIs, or SQL databases
get-time-series-service-statisticsGet an aggregation of service statistics defined by a specific time range
get-trace-graphRetrieves a service graph for one or more specific trace IDs
get-trace-summariesRetrieves IDs and annotations for traces available for a specified time frame using an optional filter. To get the full traces, pass the trace IDs to BatchGetTraces. A filter expression can target traced requests that hit specific service nodes or edges, have errors, or come from a known user. For example, the following filter expression targets traces that pass through service("") This filter expression finds traces that have an annotation named account with the value 12345: annotation.account = "12345" For a full list of indexed fields and keywords that you can use in filter expressions, see Using Filter Expressions in the AWS X-Ray Developer Guide
list-tags-for-resourceReturns a list of tags that are applied to the specified AWS X-Ray group or sampling rule
put-encryption-configUpdates the encryption configuration for X-Ray data
put-telemetry-recordsUsed by the AWS X-Ray daemon to upload telemetry
put-trace-segmentsUploads segment documents to AWS X-Ray. The X-Ray SDK generates segment documents and sends them to the X-Ray daemon, which uploads them in batches. A segment document can be a completed segment, an in-progress segment, or an array of subsegments. Segments must include the following fields. For the full segment document schema, see AWS X-Ray Segment Documents in the AWS X-Ray Developer Guide. 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 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, for instance, 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
tag-resourceApplies tags to an existing AWS X-Ray group or sampling rule
untag-resourceRemoves tags from an AWS X-Ray group or sampling rule. You cannot edit or delete system tags (those with an aws: prefix)
update-groupUpdates a group resource
update-sampling-ruleModifies a sampling rule's configuration