BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.evolutio.pt//djangocon-europe-2026//L9XBYZ
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20001029T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-djangocon-europe-2026-DLX7N7@pretalx.evolutio.pt
DTSTART;TZID=EET:20260416T110500
DTEND;TZID=EET:20260416T113500
DESCRIPTION:Most Django developers have been there: something is slow\, use
 rs are complaining\, and the first instinct is to sprinkle `print()` state
 ments or scroll through server logs hoping for a clue. Without proper obse
 rvability\, diagnosing performance bottlenecks in a Django application (or
  any application\, for that matter) is guesswork.\nObservability is the pr
 actice of understanding what is happening inside your application by looki
 ng at the signals it produces: traces\, metrics\, and logs. While the conc
 ept is well-established in infrastructure and DevOps circles\, it remains 
 under-explored in the day-to-day workflow of many Django developers. Yet D
 jango's middleware architecture\, ORM\, and request/response cycle make it
  particularly well-suited for instrumentation.\n\nIn this talk\, I will wa
 lk through how to add observability to a Django app using Pydantic Logfire
 . I'll cover the **Four Golden Signals of observability** (latency\, traff
 ic\, errors\, and saturation)\, explain why they matter for your Django ap
 p\, and show how to expose them with minimal setup. Through a live demo\, 
 you will see how to use metrics dashboards in action to monitor your syste
 m. You'll also see how to leverage AI to query your logs and traces in nat
 ural language or with SQL.\nAttendees will leave this talk with a practica
 l\, reproducible workflow for adding observability to their own Django pro
 jects\, along with an understanding of which signals to monitor and why.\n
 \nPrerequisites: Attendees should be comfortable with Django basics. No pr
 ior experience with observability tooling is required.\nOutline breakdown:
 \n* 0–3 min **The problem**: Why print() and log scrolling don’t scale
 .\n* 3–7 min **Observability 101 for Django developers**: The Four Golde
 n Signals (latency\, traffic\, errors\, saturation) explained with Django-
 specific examples.\n* 7–12 min **Setting up Observability - Instrumentin
 g observability in a Django project**: logging handler\, Django instrument
 ation\, PostgreSQL instrumentation. Live demo: showing traces appearing in
  the Live view.\n* 12–19 min **Built-in dashboards and system metrics**:
  Enabling system metrics. Walkthrough of System Metrics dashboard. Mapping
  charts to the Golden Signals (CPU → saturation\, process count → traf
 fic). Building custom error charts with SQL queries. Live demo.\n* 19–23
  min **Putting it all together**: How to think about what to monitor. Prac
 tical tips for setting thresholds and correlating signals across dashboard
 s.\n* 23–25 min Wrap-up: Summary\, resources\, and where to go next.\n* 
 25-30 min: Q&A
DTSTAMP:20260502T004122Z
LOCATION:AMPHITHEATRE
SUMMARY:Beyond print(): Observability to debug you Django apps - Laís Carv
 alho
URL:https://pretalx.evolutio.pt/djangocon-europe-2026/talk/DLX7N7/
END:VEVENT
END:VCALENDAR