# Logging best practices

DevFeed: [Logging best practices](<https://devfeed.tech/articles/logging-best-practices-38932.md>)

Original publisher: [Read original article](<https://idea.popcount.org/2013-12-31-logging-best-practises>)

Author: Marek

Published: 2013-12-30T23:00:00Z

Content type: opinion

Language: en

Sources: [Marek Majkowski](<https://devfeed.tech/sources/marek-majkowski.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [systems](<https://devfeed.tech/topics/systems.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [practices](<https://devfeed.tech/tags/practices.md>)

## AI overview

An opinionated guide to logging in larger systems. It distinguishes critical startup errors, debug messages, and access logs, and recommends treating critical failures separately while keeping logging volume and verbosity manageable.

## Source excerpt

Logging best practices Every serious program has some kind of logging infrastructure. Sometimes it's trivial (); sometimes it's sophisticated and highly configurable. Unfortunately, many programs use logging inconsistently. The logging infrastructure is usually grown organically and not thought through. Many programs repeat the same mistakes with regard to logging. Let's take some time to talk about logging in larger systems.