If you are running distributed microservices on AWS and find it challenging to troubleshoot issues as they come up, you’ll definitely want to learn more about the AWS X-Ray service. Announced in preview at the AWS re:Invent conference in November 2016, AWS X-Ray is a new distributed tracing service. Updated at the AWS Global Summit San Francisco in April 2017, it graduated to GA (general availability) in all 14 public AWS regions.
In this post, we will give you an overview of AWS X-Ray Distributed Tracing System, Composition and Pricing.
AWS X-Ray Distributed Tracing System OverviewAWS X-Ray helps you analyze and debug distributed applications. AWS X-Ray aids in the understanding of complex system behavior by helping you identify and troubleshoot performance issues and errors.
Modern Engineering Challenges
Stepping back, let’s take a look at what motivates a requirement for a distributed tracing service such as AWS X-Ray.
In recent years, there has been a strong progression away from monolithic architectures toward microservices. Software applications built using microservices have multiplied rapidly, and the trend shows no signs of slowing down.
A microservices architecture is a software design pattern in which a large application is decomposed into many smaller units, each with its own simple and discrete objective. The individual microservices are designed to collaborate and coordinate over a network, typically using a lightweight mechanism such as HTTP/REST with JSON. This communication may either be synchronous or asynchronous.
Coupled with the initial emergence and now wide use of cloud platforms such as AWS, we are seeing applications becoming more and more distributed and dynamic at the infrastructure layer. A single application today could well be composed of many servers deployed across multiple regions, multiple physical facilities, multiple VPCs, and/or multiple Availability Zones. These cloud architectures are additionally highly elastic and dynamic, so they adjust to application demand in real time.
Jeff Barr from AWS succinctly articulates the challenge that X-Ray is built to address:
“The combination of cloud computing, microservices, and asynchronous, notification-based architectures has brought forth systems that have hundreds or thousands of moving parts. The challenge of identifying and addressing performance issues in these complex systems has only grown, as has the difficulty of aggregating individual, service-level observations into meaningful top-level results. There has been no easy way for developers to “follow-the-thread” as execution traverses EC2 instances, ECS containers, microservices, AWS database and messaging services”.
AWS X-Ray Service
AWS X-Ray provides distributed tracing and monitoring support by extracting and deriving operational insights from within and across distributed systems running at scale. AWS X-Ray provides visibility into the pathways and performance of your deployed applications by providing traces of requests as they are routed through the different service touchpoints.
Highlights of the AWS X-Ray service include:
- Visualization of complex and detailed service relationships within highly distributed applications
- Message tracing, timelines, and pathways of call stacks at scale
- Trace aggregation and filtering features that enable you to find performance bottlenecks and hotspots
- Drill down and pinpoint service exceptions and errors
AWS X-Ray creates a map of services used by your application with trace data that you can use to drill down into specific services or issues. This provides a view of connections between services in your application and aggregated data for each service, including average latency and failure rates.
Within the service map, the health of each node is represented by coloring on the ratio of successful calls to errors and faults:
- Green = successful calls
- Red = server faults (500 series errors)
- Yellow = client errors (400 series errors)
- Purple = throttling errors (429 Too Many Requests)
AWS X-Ray Service Composition
The AWS X-Ray service is made up of the following key components:
|X-Ray SDK||The AWS X-Ray SDK is used to instrument your application code.|
|X-Ray Daemon||The AWS X-Ray daemon collects all the local trace data, batches the information up, and periodically sends it over the internet to the AWS X-Ray service. The daemon by default listens on port 2000 for UDP connections.|
|X-Ray API||The AWS X-Ray service has an API endpoint that is used to receive the collected telemetry as delivered from the AWS X-Ray daemon.|
|Other Clients||The AWS X-Ray service can be integrated using either the AWS SDK, the AWS CLI, or other third party provided clients.|
|X-Ray Console||The AWS X-Ray service console is where all of the visualization magic comes together. You can log in to the AWS X-Ray service console and navigate all your collected traces.|
AWS X-Ray Distributed Tracing System Pricing
Pricing for the AWS X-Ray service is very simple. First, there is a perpetual free tier that allows for the following:
- Free for the first 100,000 traces recorded each month.
- Free for the first 1,000,000 traces retrieved or scanned each month.
Next, actual costs are accrued after the free tier thresholds have been reached, at the following rates:
- $5 per 1 million traces recorded ($0.000005 per trace).
- $0.50 per 1 million traces retrieved or scanned ($0.0000005 per trace).
To leverage the AWS X-Ray service you will need to instrument your application utilizing the appropriate X-Ray SDK. The X-Ray SDKs (Java, .Net, and Node.js) have been designed to be very low touch. At times, it takes no more than four lines of extra code to X-Ray enable your application.
For example, the following Node.js code would instruct X-Ray to capture and collect any downstream HTTPS requests, which would then be correlated back to the originating call:
var xray = require('aws-xray-sdk'); var http = xray.captureHTTPs(require('http')); app.use(xray.express.openSegment('SERVICE1'));
The next Node.js example shows how to instruct X-Ray to capture and collect any downstream SQS activity:
var xray = require('aws-xray-sdk'); var aws = require('aws-sdk'); app.use(xray.express.openSegment('SERVICE2')); var sqs = xray.captureAWSClient(new aws.SQS());
AWS X-Ray Console
The AWS X-Ray console has two main features:
- Service Map
The Service Map is a visualization computed by AWS over collected tracing data. It quickly allows you to understand the relationships and interplay between individual services that make up your application.
As you can see, the Service Map allows us to see the connectivity that exists between services and also highlights performance characteristics such as average response latency, etc.
The computed Service Map graph is an aggregated view of the tracing data collected based on the user selected time range. In the screenshot above, the time range has been set to the predefined value “Last 15 Minutes.”
The Traces view displays a list of individual traces. Traces can be filtered by entering a custom filter expression within the filter expression input field (top), and/or by time range. For example, we could enter the following filtered expression:
service("CALCULATOR") AND annotation.calcid = "1234"
This will find all traces that have hit the CALCULATOR service and carry a custom supplied annotation named calcid with a value set to 1234:
From here, we can now drill down into the details of any of the individually listed traces. Clicking on the first trace record brings up the following view:
Here we can see that the ADD trace segment has a red status indicator and that the response code is 503 (service unavailable).
By clicking on the red status indicator icon we can drill down into even more detail:
Here we can see additional details specific to the ADD segment such as start and end times, calculated duration, etc. We can also view message Annotations, Metadata, and/or Exceptions.
AWS X-Ray Distributed Tracing System: Getting Started
For a more comprehensive lesson on AWS X-Ray, check out the latest Cloud Academy course on AWS X-Ray:
Using AWS X-Ray to monitor a Node.js App deployed with Docker containers
The course covers the following agenda:
- Detailed review of the AWS X-Ray service and the functionality that it offers
- Detailed review of the underlying mechanics of the service and how it all works together
- Demonstration of the AWS X-Ray Console, highlighting key areas such as the Service Map and Tracing windows
- End-to-end demonstration implementing a locally hosted Microservices based Node.js application using Docker Containers instrumented with AWS X-Ray
The new AWS X-Ray service has launched to much fanfare, and it’s easy to see why. In essence, the service is well thought out and extremely easy to work with.
The AWS X-Ray Service Map console computes valuable operational insights into how your application is actually working at runtime. This allows you to compare this back to the architectural intent of your application, and deviations and latency hotspots will be quickly apparent.
Application instrumentation required to X-Ray-enable an application is generally very low touch; this coupled with the very efficient price point of the service will make it extremely appealing.
Go ahead and try it out today. It rocks!
AWS Certified Solutions Architect Associate: A Study Guide
The AWS Solutions Architect - Associate Certification (or Sol Arch Associate for short) offers some clear benefits: Increases marketability to employers Provides solid credentials in a growing industry (with projected growth of as much as 70 percent in five years) Market anal...
Moving Data to S3 with Apache NiFi
Moving data to the cloud is one of the cornerstones of any cloud migration. Apache NiFi is an open source tool that enables you to easily move and process data using a graphical user interface (GUI). In this blog post, we will examine a simple way to move data to the cloud using NiFi c...
Amazon DynamoDB: 10 Things You Should Know
Amazon DynamoDB is a managed NoSQL service with strong consistency and predictable performance that shields users from the complexities of manual setup.Whether or not you've actually used a NoSQL data store yourself, it's probably a good idea to make sure you fully understand the key ...
The 11 AWS Certifications: Which is Right for You and Your Team?
As companies increasingly shift workloads to the public cloud, cloud computing has moved from a nice-to-have to a core competency in the enterprise. This shift requires a new set of skills to design, deploy, and manage applications in cloud computing.As the market leader and most ma...
Aviatrix Integration of a NextGen Firewall in AWS Transit Gateway
Learn how Aviatrix’s intelligent orchestration and control eliminates unwanted tradeoffs encountered when deploying Palo Alto Networks VM-Series Firewalls with AWS Transit Gateway.Deploying any next generation firewall in a public cloud environment is challenging, not because of the f...
AWS Config Best Practices for Compliance
Use AWS Config the Right Way for Successful ComplianceIt’s well-known that AWS Config is a powerful service for monitoring all changes across your resources. As AWS Config has constantly evolved and improved over the years, it has transformed into a true powerhouse for monitoring your...
Cloud Academy is Coming to the AWS Summits in Atlanta, London, and Chicago
Cloud Academy is a proud sponsor of the 2019 AWS Summits in Atlanta, London, and Chicago. We hope you plan to attend these free events that bring the cloud computing community together to connect, collaborate, and learn about AWS. These events are all about learning. You can learn how t...
How to Monitor Your AWS Infrastructure
The AWS cloud platform has made it easier than ever to be flexible, efficient, and cost-effective. However, monitoring your AWS infrastructure is the key to getting all of these benefits. Realizing these benefits requires that you follow AWS best practices which constantly change as AWS...
AWS EC2 Instance Types Explained
Amazon Web Services’ resource offerings are constantly changing, and staying on top of their evolution can be a challenge. Elastic Cloud Compute (EC2) instances are one of their core resource offerings, and they form the backbone of most cloud deployments. EC2 instances provide you with...
How DNS Works – the Domain Name System (Part One)
Before migrating domains to Amazon's Route53, we should first make sure we properly understand how DNS worksWhile we'll get to AWS's Route53 Domain Name System (DNS) service in the second part of this series, I thought it would be helpful to first make sure that we properly understand...
Multiple AWS Account Management using AWS Organizations
As businesses expand their footprint on AWS and utilize more services to build and deploy their applications, it becomes apparent that multiple AWS accounts are required to manage the environment and infrastructure. A multi-account strategy is beneficial for a number of reasons as ...
WaitCondition Controls the Pace of AWS CloudFormation Templates
AWS's WaitCondition can be used with CloudFormation templates to ensure required resources are running.As you may already be aware, AWS CloudFormation is used for infrastructure automation by allowing you to write JSON templates to automatically install, configure, and bootstrap your ...