Tracing an HTTP request

Posted on by admin
Tracing an HTTP request
06
Aug

What to do when customers complain about high latencies or server-side errors? How to find out which part of your infrastructure is causing trouble? Is something wrong with CloudFront, the ELB, or your web application?

[wpcc-element _tag=”source” type=”image/webp” srcset=”/images/2020/11/tracing@730w.webp 730w, /images/2020/11/tracing@730w2x.webp 1460w, /images/2020/11/tracing@610w.webp 610w, /images/2020/11/tracing@610w2x.webp 1220w, /images/2020/11/tracing@450w.webp 450w, /images/2020/11/tracing@450w2x.webp 900w, /images/2020/11/tracing@330w.webp 330w, /images/2020/11/tracing@330w2x.webp 660w, /images/2020/11/tracing@545w.webp 545w, /images/2020/11/tracing@545w2x.webp 1090w” sizes=”(min-width: 1200px) 730px, (min-width: 992px) 610px, (min-width: 768px) 450px, (min-width: 576px) 330px, 545px” _close=”0″]

Our video demonstrates how to use request IDs, also called tracing IDs, to debug your systems. You will learn how to use Athena to combine access logs from the ALB stored on S3 and an NGINX server stored on CloudWatch Logs.

[wpcc-iframe class=”embed-responsive-item lozad” data-src=”https://www.youtube-nocookie.com/embed/6QEsQJ9AP1I” allow=”accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture” allowfullscreen=””]

Read more:

Articles on the same topic:

admin