<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Observability &amp; Troubleshooting on 🏠</title><link>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/</link><description>Recent content in Observability &amp; Troubleshooting on 🏠</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/index.xml" rel="self" type="application/rss+xml"/><item><title>25. CloudWatch</title><link>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/cloudwatch/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/cloudwatch/</guid><description>&lt;h1 id="cloudwatch"&gt;CloudWatch&lt;a class="anchor" href="#cloudwatch"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;CloudWatch is AWS&amp;rsquo;s primary observability service — a unified platform for collecting metrics, logs, and events from virtually every AWS service and your own applications. Before CloudWatch, understanding what was actually happening inside your infrastructure meant stitching together custom scripts, third-party agents, and ad-hoc logging setups. CloudWatch solves this by providing a single place to monitor resource health, detect anomalies, trigger automated responses, and query logs — all without managing any underlying infrastructure.&lt;/p&gt;</description></item><item><title>26. X-Ray</title><link>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/x-ray/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/x-ray/</guid><description>&lt;h2 id="x-ray"&gt;X-Ray&lt;a class="anchor" href="#x-ray"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Modern applications rarely live in a single process. A user request might pass through an API Gateway, trigger a Lambda function, query DynamoDB, call an external HTTP service, and publish to an SQS queue — all before a response is returned. When something goes wrong (or is simply slow), finding &lt;em&gt;where&lt;/em&gt; in that chain the problem originated is genuinely hard with logs alone. AWS X-Ray solves this by tracing requests end-to-end across your distributed system, giving you a visual map of every service involved and exactly how long each hop took. For the DVA-C02 exam, X-Ray is the go-to answer whenever a question involves diagnosing latency, pinpointing errors in a microservice architecture, or understanding request flow.&lt;/p&gt;</description></item><item><title>27. CloudTrail</title><link>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/cloudtrail/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/8-observability-troubleshooting-cloudwatch-xray-cloudtrail/cloudtrail/</guid><description>&lt;h2 id="cloudtrail"&gt;CloudTrail&lt;a class="anchor" href="#cloudtrail"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Every action taken in your AWS account — whether from the console, CLI, SDK, or another AWS service — is an API call. CloudTrail records all of these calls, giving you a complete, auditable history of &lt;em&gt;who did what, when, and from where&lt;/em&gt;. This makes it the foundational tool for security auditing, compliance, and forensic investigation. Without CloudTrail, answering questions like &amp;ldquo;who deleted that S3 bucket?&amp;rdquo; or &amp;ldquo;which IAM role created this resource at 2am?&amp;rdquo; would be nearly impossible.&lt;/p&gt;</description></item></channel></rss>