The sixth and final part of a Deno dinosaur runner game tutorial series focuses on adding observability to a production-ready web application. It covers setting up structured JSON logging via middleware, implementing custom OpenTelemetry traces with spans and attributes for key routes (score submission, leaderboard fetch, customization), and leveraging Deno Deploy's built-in Logs, Traces, and Metrics dashboards. The post explains how to correlate logs with traces, use span attributes for filtering, and interpret platform metrics like HTTP latency, CPU usage, and GC time. It also demonstrates using Deno Deploy's tunnel feature to verify instrumentation locally before deploying.
Table of contents
Observability, Metrics, and AlertingWhat you’ll buildThe three pillars of observabilitySetting up the telemetry moduleLogsTracesMetricsViewing it all locally with the tunnelWhat you can see nowWrapping up the seriesSort: