# Writing Useful Logs For Production

> A hands-on workshop on structured logging: what to capture, how to structure it, and how to stay informed so your next incident has a paper trail.

**URL:** https://sentry.io/resources/logs-workshop/

---

**Type:** Workshop | **Date:** ON-DEMAND

**Tags:** Logs, Workshop

**Presented by:** Kyle Tryon

In this workshop we went deep on structured logging: what to capture, how to structure it, and how to stay informed so your next incident has a paper trail.

We covered:

* **What's worth logging** (and what isn't): State transitions, request boundaries, external call failures, auth decisions and why string-based console logs mostly just eat your quota.
* **Structured log best practices**: Treating logs like application data
* **Structured logging in practice**: Adding attributes that make logs searchable, connecting them to traces and errors so you can move from "something broke" to "here's exactly what happened".
* **Tuning Signal to Noise**: How to filter logs to keep important signal while reducing the firehose of noise.

By the end, you'll have a practical logging strategy that costs less, tells you more, and makes your next production incident a lot more informed.

---

*Source: [sentry.io/resources/logs-workshop/](https://sentry.io/resources/logs-workshop/)*