21 Jun 2026
Manage Diagnostics Without Restarting
Runtime logging control is especially important for production services. Detailed debug logs are most useful when something has already gone wrong. However, keeping them enabled all the time is usually not acceptable. Verbose logs create noise. They increase file size. They can slow down hot code paths. In some cases, they may also expose details
17 Jun 2026
Collapse Macros in logme: How to Reduce Duplicate Log Errors
Why Duplicate Log Errors Are a Problem Duplicate log errors are one of the most annoying problems in production diagnostics. Sometimes the real issue is not that there are too few logs. The issue is that there are too many of them. When the same error is written in a loop, on every reconnect, on
18 May 2026
Trace Points in C++: Diagnosing Production Systems Without Restart
One of the goals behind trace points in the C++ logging library logme was solving a very practical production problem. The logs available during an incident are usually not the logs developers actually need. Production issues almost never happen when developers are actually prepared to investigate them. During development everything works correctly, test environments appear
07 May 2026
Logging Subsystems in C++: Why They Matter and How to Use Them
C++ logging subsystems become necessary as a project grows, even though almost nobody thinks about them at the beginning. Most projects start with simple logging. A few levels — debug, info, warning, error — and that is enough to understand what is happening. While the codebase is small, the log reads almost like a linear