📝 spdlog — Logging for C++ that actually gets out of your way

[marcelschmall@infosec.exchange]

spdlog — Logging for C++ that actually gets out of your way

When you’re writing a Linux server in C++ close to the hardware, the last thing you want is a logging library that slows you down — at build time, at runtime, or when reading the code.

That’s exactly where spdlog shines.

Header-only — zero build ceremony
Drop the headers into your project, #include "spdlog/spdlog.h" and you’re done. No linking against extra libraries, no CMake gymnastics, no ABI headaches. For embedded systems or minimal server builds this alone is worth a lot.
And because spdlog supports C++11 and up, it runs happily on older GCC toolchains — exactly the kind you find in Linux BSP environments and long-lived server codebases.

Logging should be fast AND readable
spdlog uses the {fmt} library under the hood, which means your log messages are formatted at compile time where possible. Instead of stringing together cout-style streams, you write:

spdlog::info("Connection from {} on port {}", client_ip, port);

Clean, readable, and significantly faster than printf or std::cout at runtime.

🪣 The Sink System — one logger, many destinations
The real power comes from sinks. A sink is simply a destination for log output — and you can attach as many as you want to a single logger.

→ stdout_sink for live debugging in the terminal

→ rotating_file_sink to write to disk with automatic file rotation

→ syslog_sink to feed directly into the Linux system journal

In a hardware-near server this means you can log to syslog for production monitoring AND to a rotating file for post-mortem debugging — with a single log call in your code. No duplication, no extra logic.

Log levels keep noise under control
spdlog supports the classic hierarchy — trace, debug, info, warn, error, critical. You set the minimum level per sink, so your rotating file might catch everything from debug upwards while syslog only sees warn and above. Perfect for production servers where log volume matters.

For C++ server development on Linux, spdlog hits a rare sweet spot: trivial to integrate, fast enough for hot paths, and flexible enough for real production setups.

#Cpp #Linux #SystemsProgramming #ServerDevelopment