✳flâneur — a map of the web's best reading

Logging, Tracing, Monitoring, et al.

alexandruburlacu.github.io · 3,019 words · saved by 1 readers

Wait, before you do, ask yourself this question: If something goes south, how will I know what exactly happened? A good question, indeed. A more seasoned engineer might say: I will use logs!!! But what if I tell you, logs are only the begging? [Disclaimer Time] This article is not about some concrete technology, framework, or library, although it references some of these. It’s more of an overview/tips about what logging/tracing/et al are and how to approach these when designing and operating software systems. The information here is based mostly from my own experience, but also from information available in papers and industry blog posts. You might need to google some stuff while/after reading it, especially if you’ve never operated a system running in production. So, what exactly is a log? Technically, this is a log, but I want to talk about other kinds of logs. Logs are a record about some event in a system Pretty abstract, huh? A log is like an entry in a journal about something tha

So, you want to launch your code/app/system in production? Wait, before you do, ask yourself this question: If something goes south, how will I know what exactly happened? A good question, indeed. A more seasoned engineer might say: I will use logs!!! But what if I tell you, logs are only the begging? [Disclaimer Time] This article is not about some concrete technology, framework, or library, although it references some of these. It’s more of an overview/tips about what logging/tracing/et al are and how to approach these when designing and operating software systems. The information here is ba

Explore this link on the map →

saved by

related reading