Observability & Monitoring

Logs, metrics and traces you can trust, alerts that page on real user pain, dashboards people actually open, and the routines that keep telemetry useful and affordable.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Observability & Monitoring, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Observability & Monitoring

Instrumenting systems with logs, metrics, traces and alerts so engineers can see what is happening in production and fix problems quickly.

  1. Telemetry inventory of production services
  2. Structured logging standard and field names
  3. Correlation IDs across every request path
  4. Golden signals for each user-facing service
  5. Choosing an observability stack
  6. OpenTelemetry instrumentation of the first service
  7. Health check and readiness endpoints
  8. Telemetry retention and data classification policy
  9. Service overview dashboard for the main product
  10. First paging alerts on user-facing symptoms
  11. Weekly alert noise review
  12. Monthly dashboard pruning
  13. Observability definition of done for new services
  14. Metric cardinality guardrails
  15. Monitoring the monitoring with a heartbeat alert
  16. Alert ownership and routing register
  17. Synthetic checks of critical user flows
  18. Observability bill by team and signal
  19. Quarterly telemetry coverage review
  20. Deploy markers and change events on dashboards
  21. Metrics query language fluency
  22. Reading distributed trace waterfalls
  23. Log search drills on past incidents
  24. Percentiles, histograms and why averages lie
  25. Exploratory debugging with wide events
  26. Trace sampling strategies
  27. Team observability skills matrix
  28. Writing alert messages people can act on
  29. Migrating proprietary agents to OpenTelemetry
  30. Log level clean-up across services
  31. Moving counters out of log lines into metrics
  32. Cold storage tier for older logs
  33. Real user monitoring for the web frontend
  34. Error tracking with release tagging
  35. Consolidating duplicate monitoring tools
  36. Redacting secrets and personal data from logs
  37. Observability readiness review before a launch
  38. Alert fire drill in staging
  39. Monitoring watch plan for a peak traffic day
  40. Observability vendor contract renewal
  41. Audit log evidence for a security assessment
  42. Minimum viable monitoring for a team of one
  43. Inheriting a service with no monitoring
  44. Monitoring batch jobs and scheduled pipelines
  45. Monitoring serverless functions and managed services
  46. Observability tour for engineers joining the team
  47. Running observability as a shared platform service
  48. Continuous profiling in production
  49. Kernel-level visibility with eBPF
  50. Anomaly detection on business metrics

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Telemetry inventory of production services

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most teams have more monitoring than they think and less than they need: three log tools, a dashboard nobody owns and one service that emits nothing at all.

First tasks

  • Export the list of running services from the deployment platform
  • Check in each observability tool which services sent data this week
  • Mark every service that has no alert or no dashboard
  • Publish the inventory in the team's documentation space

Structured logging standard and field names

Free-text log lines are readable by a person and almost useless to a query engine, and every service inventing its own field names means nobody can search across them. A short written standard for JSON logs, with agreed names for timestamp, level, service, request ID and user-facing error codes, makes logs from every team searchable the same way.

First tasks

  • Collect five real log lines from different services and compare their fields
  • Draft the required field list using an existing semantic convention
  • Write one sentence per log level saying when it should be used
  • Ship the shared logger configuration to two services

Correlation IDs across every request path

When a customer reports a failed checkout, the first question is which log lines belong to that one request, and without a shared ID the answer is guesswork across five services. Propagating a single request or trace ID from the edge through queues and background jobs lets anyone pull the full story of one request with a single search.

First tasks

  • Pick one user action and list every service and queue it passes through
  • Add trace context headers at the edge proxy or load balancer
  • Carry the ID through message metadata for each queue consumer
  • Follow one real request end to end and note where the ID went missing

Make it yours.

Install Observability & Monitoring, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.