Tracing an HTTP request
06
Aug
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?
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.
JavaScript is disabled. Please visit YouTube.com to watch the video.
Read more:
Articles on the same topic:
-
Unboxing Amazon Managed Service for Prometheus (AMP)
-
Tweaking RDS database performance and ElastiCache
-
Transition to IMDSv2 on EC2 – Introduction, Preparation, Pitfalls
-
Tidying up after failed Terraform tests
-
Three ways to run Docker on AWS
-
Three simple rules to avoid data leaking from S3
-
3½ ways to workaround missing CloudFormation support
-
The somewhat different AWS re:Invent recap
-
The Life of a Serverless Microservice on AWS
-
The Cloud Switch: IoT Button, Lambda, and CloudFormation
-
The AWS Security Journey (2021)
-
Deprecated Terraform provider template causes `Incompatible provider version` error
-
Terraform, can you keep a secret?
-
Step Functions pitfall: The execution reached the maximum number of history events (25000)
-
Static Website Templates for AWS CloudFormation
-
Simplified AMI deletion: new feature streamlines cleanup
