Module 11 cheat sheet
One-page revision summary for Monitoring, Logging & Troubleshooting: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.
Assumes: AWS CLI v2 · AWS SDK for .NET v4 · OpenTelemetry .NET · .NET 10 LTS · Region us-east-1 · facts as stated in the Module 11 lessons; items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.
A printable summary of Module 11. Each row links back to the lesson with the detail.
Key services
| Service | What it is for |
|---|---|
| CloudWatch Logs | Log groups with per-group retention and class (Standard or Essentials); metric filters and subscription filters |
| Logs Insights | Ad hoc queries over log groups; billed by data scanned, so narrow the time range |
| CloudWatch metrics + EMF | Technical and custom business metrics; EMF turns a JSON log line into metrics with no API call |
| Alarms / composite alarms | Metric alarms with datapoints-to-alarm; composites combine alarms so one incident is one page |
| Dashboards + Synthetics | One on-call screen; canaries probe from outside (Node.js, Python or Java runtimes, no .NET) |
| X-Ray + OpenTelemetry (ADOT) | Distributed traces; instrument with OpenTelemetry, X-Ray is a backend |
| Application Signals | Service map, standard metrics, SLOs and burn-rate alarms built from OpenTelemetry data |
| CloudTrail | Who did what, when, from where; event history is 90 days of management events, free |
| SNS / EventBridge | Alarm actions and event-driven alerts (for example a risky API call) |
| Budgets / Cost Anomaly Detection | Catch CloudWatch cost mistakes within a day |
.NET / Azure → AWS
| Microsoft / Azure | AWS |
|---|---|
| Application Insights | Application Signals + X-Ray over OpenTelemetry |
| Log Analytics + KQL | CloudWatch Logs + Logs Insights query language |
TelemetryClient.GetMetric | EMF line or PutMetricData |
| Azure Monitor alerts + action groups | Alarms + SNS (composite alarms to cut noise) |
| Availability tests | Synthetics canaries |
| Workbooks / dashboards | CloudWatch dashboards (keep in Git) |
| Activity Log | CloudTrail event history and trails |
| Basic Logs table plan | Essentials log class |
ActivitySource / Activity | OpenTelemetry spans, W3C traceparent |
Most useful CLI commands
| Task | Command |
|---|---|
| Tail a log group | aws logs tail /hl-m11/transfers-api --follow --since 10m |
| Set retention | aws logs put-retention-policy --log-group-name NAME --retention-in-days 7 |
| Run a Logs Insights query | aws logs start-query --log-group-name NAME --start-time T --end-time T --query-string '...' then aws logs get-query-results --query-id ID |
| Publish a metric | aws cloudwatch put-metric-data --namespace Harbourline/Payments --metric-name TransferCount ... |
| Create / combine alarms | aws cloudwatch put-metric-alarm ... · aws cloudwatch put-composite-alarm ... |
| Rehearse a page | aws cloudwatch set-alarm-state --alarm-name NAME --state-value ALARM --state-reason TEXT |
| Read alarm history | aws cloudwatch describe-alarm-history --alarm-name NAME --history-item-type StateUpdate |
| Who changed it? | aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=NAME |
| List SLOs | aws application-signals list-service-level-objectives |
| Anything left over? | aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab |
| Live .NET counters | dotnet-counters monitor --process-id PID |
Key limits and defaults
| Item | Value | Lesson |
|---|---|---|
| Log group retention default | Never expires; set it deliberately | CloudWatch Logs for .NET |
Log event size / PutLogEvents batch | 1,024 KB / 1 MB | CloudWatch Logs for .NET |
| Metric filters / subscription filters per log group | 100 / 5 | CloudWatch Logs for .NET |
StartQuery rate | 10 per second | CloudWatch Logs for .NET |
| Essentials log class | No metric filters, subscription filters or EMF; class fixed at creation | Log aggregation and error monitoring |
| EMF event | Single valid JSON object; up to 30 dimensions per metric (cost, not count, is the limit) | CloudWatch metrics and custom metrics |
| Each dimension combination | A separately billed metric | CloudWatch metrics and custom metrics |
| Custom metric price (US East) | USD 0.30 per metric per month for the first 10,000 | CloudWatch metrics and custom metrics |
| Anomaly detection | About two weeks of history to learn | Alarms and composite alarms |
| CloudTrail event history | 90 days, management events only, one Region at a time | CloudTrail for operations |
| X-Ray trace ID | 1-<8 hex time>-<24 hex>; a W3C trace ID is reformatted to it | Distributed tracing |
Decision rules
| If… | Then… |
|---|---|
| Deciding what to alert on | Customer-visible symptom, sustained over several periods, with a named action |
| Failures only publish a metric when they happen | notBreaching for missing data |
| Traffic vanishing means trouble | breaching (traffic floor), and alarm the canary the same way |
| Several alarms describe one incident | Composite alarm; put actions on the composite |
| A rate with small traffic is noisy | Add a minimum-traffic guard |
| Metric has a daily or weekly shape | Anomaly detection; otherwise a static threshold |
| A business count is needed | EMF from the app, not a log scan |
| Need a request across services | OpenTelemetry traces with W3C propagation; scrub attributes |
| Need an SLO | SLI, goal, window; page on fast burn, ticket on slow burn |
| Log group feeds alarms or EMF | Standard class, never Essentials |
| Logs needed across accounts | Read in place with cross-account observability; copy only for retention or SIEM |
| Something changed with no deploy | CloudTrail first: who, which credentials, from where |
| Debugging an incident | Symptom, hypothesis, evidence, fix; mitigate before root cause |
| Needing an incident tool | Incident Manager is closed to new customers (2025-11-07); alarms to SNS or third-party on-call |
Common exam traps
- Event history is not a trail. 90 days, management events only, per Region. Longer retention or data events need a trail.
- CloudTrail is not an application log and not a business audit trail.
- Log groups never expire by default, and the log class cannot be changed later.
- Essentials (formerly Infrequent Access) loses metric filters, subscriptions and EMF.
- EMF needs a pure JSON line; logging it through a normal logger that adds text breaks it.
- Each dimension combination is its own metric; a user ID as a dimension is a cost and cardinality bug.
- Missing data is a decision:
missingleaves state unchanged,notBreachingandbreachingforce it. - Use
Sumfor counters, percentiles for latency, not Average. - Synthetics has no .NET runtime; a Node.js or Python script calls your endpoint.
- ADOT .NET SDK does not support AWS SDK for .NET v4; check before relying on automatic spans.
- Logs Insights is for investigation; use metrics and alarms for continuous checks.
Cost traps
| Trap | Avoid it by |
|---|---|
| Ingestion of chatty logs (Standard class, USD 0.50 per GB in US East) | Log levels, sampling, retention, Essentials for rarely read logs |
| High-cardinality dimensions | Price the series count before deploying |
| Debug logging left on in production | Alarm on IncomingBytes; also a data-protection problem |
| Logs Insights over 30 days "to be safe" | Start at 15 to 60 minutes and filter early |
| Canaries left running | They bill per run; delete after the lab |
| Collector-less X-Ray export at default 100% sampling | Sample low; put a collector in front |
| Extra CloudTrail trails and data events | One organisation trail; select data events narrowly |
| Cost surprises noticed at month end | CloudWatch-scoped budget and anomaly detection |
Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.
Cost monitoring for observability: CloudWatch bills, budgets and anomaly alerts
Understand what makes CloudWatch and related observability services expensive, find your largest log groups and metric sources, cut waste without losing signal, and set up a budget and anomaly detection so a logging mistake is caught in a day rather than at month end.
Module 12: High Availability & Disaster Recovery
Design banking systems that keep running when a server, an Availability Zone or a whole Region fails, and prove it with tested recovery. You learn auto scaling, resilience patterns, the four disaster-recovery strategies with RTO and RPO targets, backup and restore testing, and chaos engineering.