AWS - CloudWatchYou want to organize logs from multiple microservices in AWS CloudWatch. Which approach best uses log groups and log streams?ACreate one log stream per instance and no log groupsBCreate one log stream per microservice and one log group for allCCreate one log group for all microservices and one log stream per microserviceDCreate one log group per microservice and multiple log streams per instanceCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand log group and stream hierarchyLog groups are containers for logs from a source; log streams organize logs within groups by instance or thread.Step 2: Apply to microservices architectureBest practice is one log group per microservice for separation, with multiple streams per instance for detailed logs.Final Answer:Create one log group per microservice and multiple log streams per instance -> Option DQuick Check:Log groups per microservice, streams per instance [OK]Quick Trick: Use log groups for services, streams for instances [OK]Common Mistakes:MISTAKESMixing streams and groups rolesUsing one group for all microservicesNot using log groups at all
Master "CloudWatch" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - API Gateway throttling - Quiz 10hard API Gateway - API Gateway throttling - Quiz 4medium Auto Scaling - Minimum, maximum, and desired capacity - Quiz 7medium CloudWatch - CloudWatch alarms - Quiz 3easy Elastic Load Balancing - Target groups concept - Quiz 10hard Elastic Load Balancing - Cross-zone load balancing - Quiz 9hard SNS and SQS - Why messaging services matter - Quiz 2easy SNS and SQS - Standard vs FIFO queues - Quiz 10hard SNS and SQS - SNS and SQS integration pattern (fan-out) - Quiz 11easy SNS and SQS - SNS notification types (email, SMS, Lambda) - Quiz 11easy