Trek10 Team
Caylent Catalysts™
IoT
Connect, understand, and act on data from industrial devices at scale to improve uptime, efficiency, and reliability across manufacturing, energy, and utilities.
Amazon CloudWatch ServiceLens: A Visual Overview
Managed Services
Infrastructure & DevOps Modernization
Learn how Amazon CloudWatch ServiceLens unifies X-Ray traces with Amazon CloudWatch metrics to streamline serverless monitoring. Explore service maps, request filtering by dimensions, and practical debugging techniques through a hands-on test case.
This blog was originally written and published by Trek10, which is now part of Caylent.
"Amazon CloudWatch ServiceLens bridges the gap between X-Ray and CloudWatch by providing a “single pane of glass” unifying X-Ray traces with CloudWatch features such as metrics and alarms. The resulting experience definitely feels X-Ray-esque, built around the concept of a “service map” you can drill down into to get more information about a poorly-performing request. The new console experience makes it easy to slice and dice requests by dimensions, such as client IP or URL to quickly discover and understand your systems." - Forrest Brazeal
Prepping Our Test Case
In order to effectively understand ServiceLens, we want a diversified test case. Below is a repository provided that leverages a bunch of different services and points of interaction between those services. This will serve as our test bed for playing with everything that ServiceLens has to offer.
The services and interactions involved are as follows. Everything is deployed in via AWS Serverless Application Model (SAM).
You can check out the repository, and even deploy it easily to your own account with sam build && sam deploy if you would like!
The Basics
You will notice we have turned out pretty extensive logging capabilities, as well as instrumented a bit of the code.
Globals:
Function:
Runtime: nodejs10.x
MemorySize: 256
Timeout: 3
Tracing: Active
Environment:
Variables:
SAMPLE_TABLE: !Ref SampleTable
Api:
EndpointConfiguration: REGIONAL
TracingEnabled: True
MethodSettings:
- LoggingLevel: INFO
MetricsEnabled: False
DataTraceEnabled: True
ResourcePath: "/*"
HttpMethod: "*"const AWSXRay = require('aws-xray-sdk');
// Create a DocumentClient that represents the query to add an item
const AWS = require('aws-sdk');
const docClient = new AWS.DynamoDB.DocumentClient({
service: new AWS.DynamoDB()
});
AWSXRay.captureAWSClient(docClient.service);With just these few bits of things, this opens up quite a bit of functionality and capabilities in ServiceLens.
First things first, we get a "ServiceMap" that we can filter in different ways. For our "listing" endpoint this is what it looks like.
Check out looking at our request map. Can you understand where errors may be in the system?
Your browser does not support the video tag.
Let's Dive Into Those Errors
So we quickly surface that there is a problem, let's see if we can figure out WHAT went wrong.
Your browser does not support the video tag.
Yep. We found that error saw it was a POST request from API Gateway.
The body was {"id": 1, "key2":"value2"} and our error was One or more parameter values were invalid: Type mismatch for key id expected: S actual: N. Oops! Our id was supposed be a string.
Easy fix!
Understanding Our Users
Let's pretend we just got a massive spike of traffic. How can we quickly understand the genesis of this?
Let's play with our traces screen.
Your browser does not support the video tag.
Well there we go, someone (me) decided to slam our service with ApacheBench and generated 94% of our traffic. We can see everyone else is behaving correctly.
If desired we can drill down into what specifically a particular IP or user agent is doing, filter by response codes or URLs, etc. Once we've got our interesting batch of traces, we are free to start investigating them in detail to understand call for call what the actors are doing.
What You Put In Is What You Get Out
With X-Ray and by extensions, ServiceLens, you get out the value based on what you invest ahead of time. The more instrumented your calls are, and the more annotations and metadata you add to your X-Ray, the more value you will be able to extract.
I think ServiceLens is one of the largest observability leaps we have seen in the native AWS tooling yet.
Managed Services
Infrastructure & DevOps Modernization
Trek10 Team
Founded in 2013, Trek10 helped organizations migrate to and maximize the value of AWS by designing, building, and supporting cloud-native workloads with deep technical expertise. In 2025, Trek10 joined Caylent, forming one of the most comprehensive AWS-only partners in the ecosystem, delivering end-to-end services across strategy, migration and modernization, product innovation, and managed services.
View Trek10's articlesLearn more about the services mentioned
Caylent Services
Managed Services
Reliably Operate and Optimize Your AWS Environment
Caylent Services
Infrastructure & DevOps Modernization
Quickly establish an AWS presence that meets technical security framework guidance by establishing automated guardrails that ensure your environments remain compliant.
Related Blog Posts
Datadog Event Mapping
Learn how Datadog Event Mapping works — how to correlate logs, events, and alerts into meaningful context, improve observability, and reduce noise so your team can quickly detect and respond to issues.
Managed Services
Infrastructure & DevOps Modernization
CloudFormation Nested Stacks Primer
Get a practical introduction to AWS CloudFormation nested stacks — how they work, when to use them, and best practices for organizing and managing reusable infrastructure templates at scale.
Managed Services
Infrastructure & DevOps Modernization
Dedicated Hosts vs. Dedicated Instances on AWS: What is the Difference?
Understand the differences between AWS Dedicated Hosts and Dedicated Instances — when to use each, how they impact compliance and licensing, and best practices for controlling tenancy and cost in your cloud environment.
Managed Services
Infrastructure & DevOps Modernization