log
A time-stamped record of an individual event in a system, such as one request being handled; structured logs record it as named fields rather than free text.
In more detail
Structured fields such as status, duration, operation and request identifier can be searched and counted. Use consistent severity names and never log credentials, tokens or unnecessary personal data.
Example
{"ts": "2026-09-11T09:55:22Z", "level": "INFO", "service": "checkout", "event": "order_accepted", "order_id": 1071}Related terms
- observability — How well you can understand what a system is doing, and why, from the data it emits: mainly logs, metrics and traces.
- correlation ID — A unique value attached to one request and passed along everywhere it goes, so its logs and traces can be found together.
- redaction — Removing or hiding sensitive values, such as tokens or personal data, before data is logged, displayed or shared.
- log level — A label on each log message saying how serious it is, from debug and info up to error, critical and emergency.
- structured logging — Writing each log entry as named fields, such as status, duration and request identifier, instead of a free-text sentence.
- log retention — How long a log group keeps its entries before deleting them.
- Amazon CloudWatch — The AWS monitoring service that collects metrics and logs from AWS resources and applications and raises alarms on them.
- event stream — A continuous, time-ordered flow of events with no fixed beginning or end.
- metric — A number measured over time, such as requests per second or error count, that shows how a system behaves in aggregate.
- trace — A record of one request’s whole journey through a system, made of nested spans that show where the time went.
Taught in
- Error Handling And Safe Retries — Modern API Architecture: REST, GraphQL & gRPC
- API Gateways And Proxies — Modern API Architecture: REST, GraphQL & gRPC
- Observability: Logs, Metrics, Traces — Modern API Architecture: REST, GraphQL & gRPC
- Handling PII And Data Privacy — Modern API Architecture: REST, GraphQL & gRPC
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- Users, Groups and Roles — Cloud Infrastructure & Hyperscaler Architecture
- The Danger of Long-Lived Keys — Cloud Infrastructure & Hyperscaler Architecture
- Containers on AWS (ECS and EKS) — Cloud Infrastructure & Hyperscaler Architecture
- Serverless Compute (Lambda) — Cloud Infrastructure & Hyperscaler Architecture
- Auto Scaling Groups — Cloud Infrastructure & Hyperscaler Architecture
- Object, Block, and File Storage — Cloud Infrastructure & Hyperscaler Architecture
- When to Pick Which Database — Cloud Infrastructure & Hyperscaler Architecture
- Observability with CloudWatch — Cloud Infrastructure & Hyperscaler Architecture
- Metrics, Logs, and Alarms — Cloud Infrastructure & Hyperscaler Architecture
- Cost, Budgets, and Tagging — Cloud Infrastructure & Hyperscaler Architecture
- How Bills Actually Get Large — Cloud Infrastructure & Hyperscaler Architecture
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Disposability, Dev Prod Parity And Logs — DevOps & Site Reliability Engineering
- Writing A Postmortem: The SRE Appendix — DevOps & Site Reliability Engineering
- Observability Context — DevOps & Site Reliability Engineering
- Observability Versus Monitoring — Full-Stack Observability: Metrics, Tracing & Logging
- The Three Signals: Logs, Metrics And Traces — Full-Stack Observability: Metrics, Tracing & Logging
- Structured Logging And Why Text Fails — Full-Stack Observability: Metrics, Tracing & Logging
- Log Levels Done Properly — Full-Stack Observability: Metrics, Tracing & Logging
- Cardinality And How It Bankrupts You — Full-Stack Observability: Metrics, Tracing & Logging
- Dashboards That Answer Questions — Full-Stack Observability: Metrics, Tracing & Logging
- OpenTelemetry: The Vendor Neutral Path — Full-Stack Observability: Metrics, Tracing & Logging
- The OpenTelemetry Collector — Full-Stack Observability: Metrics, Tracing & Logging
- Instrumenting A Service With Client Libraries — Full-Stack Observability: Metrics, Tracing & Logging
- Bringing The Three Signals Together — Full-Stack Observability: Metrics, Tracing & Logging
- The Blameless Postmortem — Full-Stack Observability: Metrics, Tracing & Logging
- A Worked Example Postmortem — Full-Stack Observability: Metrics, Tracing & Logging
- Six Minutes Nobody Saw: Prometheus In One Outage — Prometheus Certified Associate (PCA) Exam Prep
- Ninety Minutes, No Question Count: Exam Strategy — Prometheus Certified Associate (PCA) Exam Prep
- Observability Sprint: One Failed Checkout — Prometheus Certified Associate (PCA) Exam Prep
- Where Did Two Hours Go? Prometheus Architecture — Prometheus Certified Associate (PCA) Exam Prep
- A Week Without A Scrape: Configuration And Relabelling — Prometheus Certified Associate (PCA) Exam Prep
- Off By Five: What Prometheus Is Not For — Prometheus Certified Associate (PCA) Exam Prep
- Fundamentals Sprint: Nine Calls On The Server — Prometheus Certified Associate (PCA) Exam Prep
- Milliseconds Versus Seconds: Naming Metrics And Labels — Prometheus Certified Associate (PCA) Exam Prep
- Forty One Buzzes: Routing Alerts With Alertmanager — Prometheus Certified Associate (PCA) Exam Prep
- One Week, Three Objectives: Final Review — Prometheus Certified Associate (PCA) Exam Prep
References
- OpenTelemetry: Logs
- OWASP Cheat Sheet Series: Logging
- What is Amazon CloudWatch Logs?
- The Twelve-Factor App: XI. Logs