Code Quality Rank: L4
Programming language: C++
License: MIT License
Tags: Logging    
Latest version: v1.1.5

plog alternatives and similar libraries

Based on the "Logging" category.
Alternatively, view plog alternatives based on common mentions on social networks and blogs.

  • spdlog

    9.7 8.9 L1 plog VS spdlog
    Fast C++ logging library.
  • glog

    C++ implementation of the Google logging module
  • Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
    Promo www.influxdata.com
    InfluxDB Logo
  • Easylogging++

    C++ logging library. It is extremely powerful, extendable, light-weight, fast performing, thread and type safe and consists of many built-in features. It provides ability to write logs in your own customized format. It also provide support for logging your classes, third-party libraries, STL and third-party containers etc.
  • easyloggingpp

    C++ logging library. It is extremely powerful, extendable, light-weight, fast performing, thread and type safe and consists of many built-in features. It provides ability to write logs in your own customized format. It also provide support for logging your classes, third-party libraries, STL and third-party containers etc.
  • log4cplus

    log4cplus is a simple to use C++ logging API providing thread-safe, flexible, and arbitrarily granular control over log management and configuration. It is modelled after the Java log4j API.
  • loguru

    A lightweight C++ logging library
  • G3log

    5.7 7.4 L3 plog VS G3log
    G3log is an asynchronous, "crash safe", logger that is easy to use with default logging sinks or you can add your own. G3log is made with plain C++14 (C++11 support up to release 1.3.2) with no external libraries (except gtest used for unit tests). G3log is made to be cross-platform, currently running on OSX, Windows and several Linux distros. See Readme below for details of usage.
  • quill

    Asynchronous Low Latency C++ Logging Library
  • reckless

    Reckless logging. Low-latency, high-throughput, asynchronous logging library for C++.
  • Boost.Log

    Boost Logging library
  • Blackhole

    Yet another logging library.
  • mini-async-log

    Non bloated asynchronous logger
  • lwlog

    Very fast synchronous and asynchronous C++17 logging library
  • Description

    Mini async log C port. Now with C++ wrappers.
  • logog

    logog is a portable C++ library to facilitate logging of real-time events in performance-oriented applications, such as games. It is especially appropriate for projects that have constrained memory and constrained CPU requirements.
  • uberlog

    Cross platform multi-process C++ logging system
  • xtr

    A Fast and Convenient C++ Logging Library for Low-latency or Real-time Environments
  • Serenity Logger

    Yet another Fast and Efficient logging framework. The goal is to be nanosecond level fast with extensibility (inspired by loggers such as spdlog, nanolog, and fmtlog and heavily influenced by the formatting used in fmtlib and <format>). This uses a built-in formatter that can be swapped out for <format> or fmtlib if desired.
  • templog

    A very small and lightweight C++ library which you can use to add logging to your C++ applications. [Boost]
  • Log4cpp

    A library of C++ classes for flexible logging to files, syslog, IDSA and other destinations. [LGPL]

Do you think we are missing an alternative of plog or a related project?

Add another 'Logging' Library


Plog - portable, simple and extensible C++ logging library

Pretty powerful logging library in about 1000 lines of code Build Status Build status CircleCI Build Status


Hello log!

Plog is a C++ logging library that is designed to be as simple, small and flexible as possible. It is created as an alternative to existing large libraries and provides some unique features as [CSV log format]((#csvformatter)) and wide string support.

Here is a minimal hello log sample:

#include <plog/Log.h> // Step1: include the headers
#include "plog/Initializers/RollingFileInitializer.h"

int main()
    plog::init(plog::debug, "Hello.txt"); // Step2: initialize the logger

    // Step3: write log messages using a special macro
    // There are several log macros, use the macro you liked the most

    PLOGD << "Hello log!"; // short macro
    PLOG_DEBUG << "Hello log!"; // long macro
    PLOG(plog::debug) << "Hello log!"; // function-style macro

    // Also you can use LOG_XXX macro but it may clash with other logging libraries
    LOGD << "Hello log!"; // short macro
    LOG_DEBUG << "Hello log!"; // long macro
    LOG(plog::debug) << "Hello log!"; // function-style macro

    return 0;

And its output:

2015-05-18 23:12:43.921 DEBUG [21428] [main@13] Hello log!
2015-05-18 23:12:43.968 DEBUG [21428] [main@14] Hello log!
2015-05-18 23:12:43.968 DEBUG [21428] [main@15] Hello log!



To start using plog you need to make 3 simple steps.

Step 1: Adding includes

At first your project needs to know about plog. For that you have to:

  1. Add plog/include to the project include paths
  2. Add #include <plog/Log.h> into your cpp/h files (if you have precompiled headers it is a good place to add this include there)

Step 2: Initialization

The next step is to initialize the Logger. This is done by the following plog::init function:

Logger& init(Severity maxSeverity, const char/wchar_t* fileName, size_t maxFileSize = 0, int maxFiles = 0);

maxSeverity is the logger severity upper limit. All log messages have its own severity and if it is higher than the limit those messages are dropped. Plog defines the following severity levels:

enum Severity
    none = 0,
    fatal = 1,
    error = 2,
    warning = 3,
    info = 4,
    debug = 5,
    verbose = 6

Note: messages with severity level none will be always printed.

The log format is determined automatically by fileName file extension:

The rolling behavior is controlled by maxFileSize and maxFiles parameters:

  • maxFileSize - the maximum log file size in bytes
  • maxFiles - a number of log files to keep

If one of them is zero then log rolling is disabled.


plog::init(plog::warning, "c:\\logs\\log.csv", 1000000, 5);

Here the logger is initialized to write all messages with up to warning severity to a file in csv format. Maximum log file size is set to 1'000'000 bytes and 5 log files are kept.

Note: see Custom initialization for advanced usage.

Step 3: Logging

Logging is performed with the help of special macros. A log message is constructed using stream output operators <<. Thus it is type-safe and extendable in contrast to a format string output.

Basic logging macros

This is the most used type of logging macros. They do unconditional logging.

Long macros:
PLOG_VERBOSE << "verbose";
PLOG_DEBUG << "debug";
PLOG_INFO << "info";
PLOG_WARNING << "warning";
PLOG_ERROR << "error";
PLOG_FATAL << "fatal";
PLOG_NONE << "none";
Short macros:
PLOGV << "verbose";
PLOGD << "debug";
PLOGI << "info";
PLOGW << "warning";
PLOGE << "error";
PLOGF << "fatal";
PLOGN << "none";
Function-style macros:
PLOG(severity) << "msg";

Conditional logging macros

These macros are used to do a conditional logging. They accept a condition as a parameter and perform logging if the condition is true.

Long macros:
PLOG_VERBOSE_IF(cond) << "verbose";
PLOG_DEBUG_IF(cond) << "debug";
PLOG_INFO_IF(cond) << "info";
PLOG_WARNING_IF(cond) << "warning";
PLOG_ERROR_IF(cond) << "error";
PLOG_FATAL_IF(cond) << "fatal";
PLOG_NONE_IF(cond) << "none";
Short macros:
PLOGV_IF(cond) << "verbose";
PLOGD_IF(cond) << "debug";
PLOGI_IF(cond) << "info";
PLOGW_IF(cond) << "warning";
PLOGE_IF(cond) << "error";
PLOGF_IF(cond) << "fatal";
PLOGN_IF(cond) << "none";
Function-style macros:
PLOG_IF(severity, cond) << "msg";

Logger severity checker

In some cases there is a need to perform a group of actions depending on the current logger severity level. There is a special macro for that. It helps to minimize performance penalty when the logger is inactive.



IF_PLOG(plog::debug) // we want to execute the following statements only at debug severity (and higher)
    for (int i = 0; i < vec.size(); ++i)
        PLOGD << "vec[" << i << "]: " << vec[i];

Advanced usage

Changing severity at runtime

It is possible to set the maximum severity not only at the logger initialization time but at any time later. There are special accessor methods:

Severity Logger::getMaxSeverity() const;
Logger::setMaxSeverity(Severity severity);

To get the logger use plog::get function:

Logger* get();



Custom initialization

Non-typical log cases require the use of custom initialization. It is done by the following plog::init function:

Logger& init(Severity maxSeverity = none, IAppender* appender = NULL);

You have to construct an Appender parameterized with a Formatter and pass it to the plog::init function.

Note: a lifetime of the appender should be static!


static plog::ConsoleAppender<plog::TxtFormatter> consoleAppender;
plog::init(plog::debug, &consoleAppender);

Multiple appenders

It is possible to have multiple Appenders within a single Logger. In such case log message will be written to all of them. Use the following method to accomplish that:

Logger& Logger::addAppender(IAppender* appender);


static plog::RollingFileAppender<plog::CsvFormatter> fileAppender("MultiAppender.csv", 8000, 3); // Create the 1st appender.
static plog::ConsoleAppender<plog::TxtFormatter> consoleAppender; // Create the 2nd appender.
plog::init(plog::debug, &fileAppender).addAppender(&consoleAppender); // Initialize the logger with the both appenders.

Here the logger is initialized in the way when log messages are written to both a file and a console.

Refer to [MultiAppender](samples/MultiAppender) for a complete sample.

Multiple loggers

Multiple Loggers can be used simultaneously each with their own separate configuration. The Loggers differ by their instanceId (that is implemented as a template parameter). The default instanceId is zero. Initialization is done by the appropriate template plog::init functions:

Logger<instanceId>& init<instanceId>(...);

To get a logger use plog::get function (returns NULL if the logger is not initialized):

Logger<instanceId>* get<instanceId>();

All logging macros have their special versions that accept an instanceId parameter. These kind of macros have an underscore at the end:

PLOGD_(instanceId) << "debug";
PLOGD_IF_(instanceId, condition) << "conditional debug";
IF_PLOG_(instanceId, severity)


enum // Define log instanceIds. Default is 0 and is omitted from this enum.
    SecondLog = 1

int main()
    plog::init(plog::debug, "MultiInstance-default.txt"); // Initialize the default logger instance.
    plog::init<SecondLog>(plog::debug, "MultiInstance-second.txt"); // Initialize the 2nd logger instance.

    // Write some messages to the default log.
    PLOGD << "Hello default log!";

    // Write some messages to the 2nd log.
    PLOGD_(SecondLog) << "Hello second log!";

    return 0;

Refer to [MultiInstance](samples/MultiInstance) for a complete sample.

Share log instances across modules (exe, dll, so, dylib)

For applications that consist from several binary modules plog instances can be local (each module has its own instance) or shared (all modules use the same instance). In case of shared you have to initialize plog only in one module, other modules will reuse that instance.

Sharing behavior is controlled by the following macros and is OS-dependent:

Macro OS Behavior
PLOG_GLOBAL Linux/Unix Shared
PLOG_LOCAL Linux/Unix Local
PLOG_EXPORT Linux/Unix n/a
PLOG_IMPORT Linux/Unix n/a
Linux/Unix According to compiler settings
PLOG_GLOBAL Windows n/a
PLOG_LOCAL Windows Local
PLOG_EXPORT Windows Shared (exports)
PLOG_IMPORT Windows Shared (imports)
Windows Local

For sharing on Windows one module should use PLOG_EXPORT and others should use PLOG_IMPORT. Also be cafeful on Linux/Unix: if you don't specify sharing behavior it will be determined by compiler settings (-fvisibility).

Refer to [Shared](samples/Shared) for a complete sample.

Chained loggers

A Logger can work as an Appender for another Logger. So you can chain several loggers together. This is useful for streaming log messages from a shared library to the main application binary.

Important: don't forget to specify PLOG_LOCAL sharing mode on Linux/Unix systems for this sample.


// shared library

// Function that initializes the logger in the shared library.
extern "C" void EXPORT initialize(plog::Severity severity, plog::IAppender* appender)
    plog::init(severity, appender); // Initialize the shared library logger.

// Function that produces a log message.
extern "C" void EXPORT foo()
    PLOGI << "Hello from shared lib!";
// main app

// Functions imported form the shared library.
extern "C" void initialize(plog::Severity severity, plog::IAppender* appender);
extern "C" void foo();

int main()
    plog::init(plog::debug, "ChainedApp.txt"); // Initialize the main logger.

    PLOGD << "Hello from app!"; // Write a log message.

    initialize(plog::debug, plog::get()); // Initialize the logger in the shared library. Note that it has its own severity.
    foo(); // Call a function from the shared library that produces a log message.

    return 0;

Refer to [Chained](samples/Chained) for a complete sample.



Plog is designed to be small but flexible, so it prefers templates to interface inheritance. All main entities are shown on the following UML diagram:

Plog class diagram <!-- @startuml

class Logger <> { +addAppender(); +getMaxSeverity(); +setMaxSeverity(); +checkSeverity(); -maxSeverity; -appenders; }

package Appenders <> { interface IAppender { +write(); }

class RollingFileAppender<Formatter, Converter>
class ConsoleAppender<Formatter>
class ColorConsoleAppender<Formatter>
class AndroidAppender<Formatter>
class EventLogAppender<Formatter>
class DebugOutputAppender<Formatter>

ConsoleAppender <|-- ColorConsoleAppender
IAppender <|-u- Logger
IAppender <|-- RollingFileAppender
IAppender <|-- ConsoleAppender
IAppender <|-- AndroidAppender
IAppender <|-- EventLogAppender
IAppender <|-- DebugOutputAppender

Logger "1" o-- "0..n" IAppender


package Formatters <> { class CsvFormatter { {static} header(); {static} format(); }

class TxtFormatter {
    {static} header();
    {static} format();

class FuncMessageFormatter {
    {static} header();
    {static} format();

class MessageOnlyFormatter {
    {static} header();
    {static} format();


package Converters <> { class UTF8Converter { {static} header(); {static} convert(); }

class NativeEOLConverter <NextConverter>{
    {static} header();
    {static} convert();


enum Severity { none, fatal, error, warning, info, debug, verbose }

class Record { +operator<<(); -time; -severity; -tid; -object; -line; -file; -message; -func; }

hide empty members hide empty fields @enduml -->

There are 5 functional parts:

  • Logger - the main object, implemented as singleton
  • Record - keeps log data: time, message, etc
  • Appender - represents a log data destination: file, console, etc
  • Formatter - formats log data into a string
  • Converter - converts formatter output into a raw buffer

The log data flow is shown below:

Log data flow <!-- @startuml () -r-> "PLOG macro" -r-> "Record" -r-> "Logger" -r-> "Appender" -d-> "Formatter" -d-> "Converter" -u-> "Appender" -r-> () @enduml -->


Logger is a center object of the whole logging system. It is a singleton and thus it forms a known single entry point for configuration and processing log data. Logger can act as Appender for another Logger because it implements IAppender interface. Also there can be several independent loggers that are parameterized by an integer instanceId number. The default instanceId is 0.

template<int instanceId>
class Logger : public util::Singleton<Logger<instanceId> >, public IAppender
    Logger(Severity maxSeverity = none);

    Logger& addAppender(IAppender* appender);

    Severity getMaxSeverity() const;
    void setMaxSeverity(Severity severity);
    bool checkSeverity(Severity severity) const;

    virtual void write(const Record& record);
    void operator+=(const Record& record);


Record stores all log data. It includes:

  • time
  • severity
  • thread id
  • 'this' pointer (if a log message is written from within an object)
  • source line
  • source file name
  • function name
  • message

Note: Source file name isn't captured by default. To enable it define PLOG_CAPTURE_FILE.

Also Record has a number of overloaded stream output operators to construct a message.

class Record
    Record(Severity severity, const char* func, size_t line, const char* file, const void* object);

    // Stream output operators

    Record& operator<<(char data);
    Record& operator<<(wchar_t data);

    template<typename T>
    Record& operator<<(const T& data);

    // Getters

    virtual const util::Time& getTime() const;
    virtual Severity getSeverity() const;
    virtual unsigned int getTid() const;
    virtual const void* getObject() const;
    virtual size_t getLine() const;
    virtual const util::nchar* getMessage() const;
    virtual const char* getFunc() const;
    virtual const char* getFile() const;
    virtual int getInstanceId() const;

See Stream improvements over std::ostream.

Refer to [Demo](samples/Demo) sample to see what can be written to the log stream.


Formatter is responsible for formatting log data from Record into various string representations (binary forms can be used too). There is no base class for formatters, they are implemented as classes with static functions format and header:

class Formatter
    static util::nstring header();
    static util::nstring format(const Record& record);

See How to implement a custom formatter.


This is a classic log format available in almost any log library. It is good for console output and it is easy to read without any tools.

2014-11-11 00:29:06.245 FATAL [4460] [main@22] fatal
2014-11-11 00:29:06.261 ERROR [4460] [main@23] error
2014-11-11 00:29:06.261 INFO  [4460] [main@24] info
2014-11-11 00:29:06.261 WARN  [4460] [main@25] warning
2014-11-11 00:29:06.261 DEBUG [4460] [main@26] debug
2014-11-11 00:29:06.261 INFO  [4460] [main@32] This is a message with "quotes"!
2014-11-11 00:29:06.261 DEBUG [4460] [Object::Object@8]
2014-11-11 00:29:06.261 DEBUG [4460] [Object::~Object@13]


This is a variant of TxtFormatter that uses UTC time instead of local time.


This is the most powerful log format. It can be easily read without any tools (but slighlty harder than TXT format) and can be heavily analyzed if it is opened with a CSV-aware tool (like Excel). One rows can be highlighted according to their cell values, another rows can be hidden, columns can be manipulated and you can even run SQL queries on log data! This is a recommended format if logs are big and require heavy analysis. Also 'this' pointer is shown so object instances can be told apart.

2014/11/14;15:22:25.048;INFO;4188;00000000;main@32;"This is a message with ""quotes""!"

Note: message size is limited to 32000 chars.


This is a variant of CsvFormatter that uses UTC time instead of local time.


This format is designed to be used with appenders that provide their own timestamps (like AndroidAppender or linux syslog facility).

main@22: fatal
main@23: error
main@24: info
main@25: warning
main@26: debug
main@32: This is a message with "quotes"!


Use this formatter when you're interested only in a log message.

This is a message with "quotes"!


Converter is responsible for conversion of Formatter output data to a raw buffer (represented as std::string). It is used by RollingFileAppender to perform a conversion before writing to a file. There is no base class for converters, they are implemented as classes with static functions convert and header:

class Converter
    static std::string header(const util::nstring& str);
    static std::string convert(const util::nstring& str);

See How to implement a custom converter.


UTF8Converter is a default converter in plog. It converts string data to UTF-8 with BOM.


This converter converts <LF> line endings to <CRLF> on Windows and do nothing on everything else. As a template parameter it accepts another converter that is called next (by default UTF8Converter).


plog::RollingFileAppender<plog::TxtFormatter, plog::NativeEOLConverter<> > fileAppender("NativeEOL.log");

Refer to [NativeEOL](samples/NativeEOL) for a complete sample.


Appender uses Formatter and Converter to get a desired representation of log data and outputs (appends) it to a file/console/etc. All appenders must implement IAppender interface (the only interface in plog):

class IAppender
    virtual ~IAppender();
    virtual void write(const Record& record) = 0;

See How to implement a custom appender.


This appender outputs log data to a file with rolling behaviour. As template parameters it accepts both Formatter and Converter.

RollingFileAppender<Formatter, Converter>::RollingFileAppender(const util::nchar* fileName, size_t maxFileSize = 0, int maxFiles = 0);
  • fileName - a log file name
  • maxFileSize - the maximum log file size in bytes
  • maxFiles - a number of log files to keep

If maxFileSize or maxFiles is 0 then rolling behaviour is turned off.

The sample file names produced by this appender:

  • mylog.log <== current log file (size < maxFileSize)
  • mylog.1.log <== previous log file (size >= maxFileSize)
  • mylog.2.log <== previous log file (size >= maxFileSize)

Also a file name can be changed at arbitrary moment by calling setFileName.

Note: the lowest maxFileSize is 1000 bytes.

Note: a log file is created on the first log message.


This appender outputs log data to stdout. As a template parameter it accepts Formatter.



This appender outputs log data to stdout using colors that depends on a log message severity level. As a template parameter it accepts Formatter.



AndroidAppender uses Android logging system to output log data. It can be viewed with logcat or in a log window of Android IDEs. As a template parameter this appender accepts Formatter (usually FuncMessageFormatter).

AndroidAppender<Formatter>::AndroidAppender(const char* tag);


This appender outputs log data to the windows event log. It can be viewed with the windows event log viewer. As a template parameter it accepts Formatter. The constructor parameter is the event source name - typically it is the name of the application or a subcomponent of the application. It must be unique for the whole system.

EventLogAppender<Formatter>::EventLogAppender(const wchar_t* sourceName);

EventLogAppender must be registered in the windows registry before use (before calling the constructor). There is a helper class for that:

bool EventLogAppenderRegistry::add(const wchar_t* sourceName, const wchar_t* logName = L"Application");
bool EventLogAppenderRegistry::exists(const wchar_t* sourceName, const wchar_t* logName = L"Application");
void EventLogAppenderRegistry::remove(const wchar_t* sourceName, const wchar_t* logName = L"Application");

Registry operations are system-wide and require administrator rights. Also they are persistent so can be performed only once (when the application is installed/uninstalled).


DebugOutputAppender sends log data to the debugger (works only on Windows). As a template parameter this appender accepts Formatter.


Miscellaneous notes

Lazy stream evaluation

Log messages are constructed using lazy stream evaluation. It means that if a log message will be dropped (because of its severity) then stream output operators are not executed. Thus performance penalty of unprinted log messages is negligible.

PLOGD << /* the following statements will be executed only when the logger severity is debug or higher */ ...

Stream improvements over std::ostream

Stream output in plog has several improvements over the standard std::ostream:

  • handles wide chars/strings: wchar_t, wchar_t*, std::wstring
  • handles NULL values for C-strings: char* and wchar_t*
  • implicitly casts objects to: std::string and std::wstring (if they have an appropriate cast operator)
  • supports QString and QStringRef (you need to include Qt headers before plog)
  • supports managed C++ System::String^

Automatic 'this' pointer capture

'This' pointer is captured automatically to log data and can be printed by CsvFormatter. Unfortunately this feature is supported only on msvc 2010 and higher. It's disabled by default (due to some compatibility issues with __if_exists C++ extension), to enable it define PLOG_ENABLE_GET_THIS.

Headers to include

The core plog functionality is provided by inclusion of plog/Log.h file. Extra components require inclusion of corresponding extra headers after plog/Log.h.

Core components are:


Plog is unicode aware and wide string friendly. All messages are converted to a system native char type:

  • wchar_t - on Windows
  • char - on all other systems

Also char is treated as:

  • active code page - on Windows
  • UTF-8 - on all other systems

Internally plog uses nstring, nstringstream and nchar ('n' for native) that are defined as:

#ifdef _WIN32
    typedef std::wstring nstring;
    typedef std::wstringstream nstringstream;
    typedef wchar_t nchar;
    typedef std::string nstring;
    typedef std::stringstream nstringstream;
    typedef char nchar;

By default all log files are stored in UTF-8 with BOM thanks to UTF8Converter.

Wide string support

Whether wchar_t, wchar_t*, std::wstring can be streamed to log messages or not is controlled by PLOG_ENABLE_WCHAR_INPUT macro. Set it to a non-zero value to enable wide string support. By default wide string support is enabled for Windows and disabled for all non-Windows systems.

Note: wide string support requires linking to iconv on macOS.


Plog is not using any asynchronous techniques so it may slow down your application on large volumes of log messages.

Producing a single log message takes the following amount of time:

CPU OS Time per a log call, microsec
AMD Phenom II 1055T @3.5GHz Windows 2008 R2 12
AMD Phenom II 1055T @3.5GHz Linux Mint 17.1 8
Intel Core i3-3120M @2.5GHz Windows 2012 R2 25
Intel Core i5-2500K @4.2GHz Windows 2008 R2 8
Intel Atom N270 @1.6GHz Windows 2003 68

Assume 20 microsec per a log call then 500 log calls per a second will slow down an application by 1%. It is acceptable for the most use cases.

Refer to [Performance](samples/Performance) for a complete sample.

Printf style formatting

Plog supports printf style formatting:

PLOGI.printf("%d %s", 42, "test");
PLOGI.printf(L"%d %S", 42, "test"); // wchar_t version

LOG_XXX macro name clashes

LOG_XXX macro names may be in conflict with other libraries (for example syslog). In such cases you can disable LOG_XXX macro by defining PLOG_OMIT_LOG_DEFINES and use PLOG_XXX.

Define PLOG_OMIT_LOG_DEFINES before #include <plog/Log.h> or in the project settings!


Plog can be easily extended to support new:

Custom data type

To output a custom data type to a log message implement the following function:

namespace plog
    Record& operator<<(Record& record, const MyType& t);

Refer to [CustomType](samples/CustomType) for a complete sample.

Custom appender

A custom appender must implement IAppender interface. Also it may accept Formatter and Converter as template parameters however this is optional.

namespace plog
    template<class Formatter>
    class MyAppender : public IAppender
        virtual void write(const Record& record);

Refer to [CustomAppender](samples/CustomAppender) for a complete sample.

Custom formatter

A formatter that is compatible with existing appenders must be a class with 2 static methods:

  • header - returns a header for a new log
  • format - formats Record to a string
namespace plog
    class MyFormatter
        static util::nstring header();
        static util::nstring format(const Record& record);

Refer to [CustomFormatter](samples/CustomFormatter) for a complete sample.

Custom converter

A converter must be a class with 2 static methods:

  • header - converts a header for a new log
  • convert - converts log messages
namespace plog
    class MyConverter
        static std::string header(const util::nstring& str);
        static std::string convert(const util::nstring& str);

Refer to [CustomConverter](samples/CustomConverter) for a complete sample.


There are a number of samples that demonstrate various aspects of using plog. They can be found in the [samples](samples) folder:

Sample Description
[Android](samples/Android) Shows how to use AndroidAppender.
[Chained](samples/Chained) Shows how to chain a logger in a shared library with the main logger (route messages).
[ColorConsole](samples/ColorConsole) Shows how to use ColorConsoleAppender.
[CustomAppender](samples/CustomAppender) Shows how to implement a custom appender that stores log messages in memory.
[CustomFormatter](samples/CustomFormatter) Shows how to implement a custom formatter.
[CustomConverter](samples/CustomConverter) Shows how to implement a custom converter that encrypts log messages.
[CustomType](samples/CustomType) Shows how to print a custom type to the log stream.
[DebugOutput](samples/DebugOutput) Shows how to use DebugOutputAppender to write to the windows debug output.
[Demo](samples/Demo) Demonstrates log stream abilities, prints various types of messages.
[EventLog](samples/EventLog) Shows how to use EventLogAppender to write to the windows event log.
[Facilities](samples/Facilities) Shows how to use logging per facilities via multiple logger instances (useful for big projects).
[Hello](samples/Hello) A minimal introduction sample, shows the basic 3 steps to start using plog.
[Library](samples/Library) Shows plog usage in static libraries.
[MultiAppender](samples/MultiAppender) Shows how to use multiple appenders with the same logger.
[MultiInstance](samples/MultiInstance) Shows how to use multiple logger instances, each instance has its own independent configuration.
[ObjectiveC](samples/ObjectiveC) Shows that plog can be used in ObjectiveC++.
[Performance](samples/Performance) Measures time per a log call.
[SetFileName](samples/SetFileName) Shows how to change a log file name at arbitrary moment.
[Shared](samples/Shared) Shows how to share logger instances across binary modules.
[SkipNativeEOL](samples/SkipNativeEOL) Shows how to skip NativeEOLConverter.
[UtcTime](samples/UtcTime) Shows how to use UTC time instead of local time.


Competing C++ log libraries

Tools and useful info


Plog is licensed under the MPL version 2.0. You can freely use it in your commercial or opensource software.

Version history

Version 1.1.5 (21 Oct 2019)

  • New: Use NativeEOLConverter by default (#145)
  • New: Add logger instanceId into Record (#141)
  • New: Add support for the printf style formatting (#139)
  • New: Make severityFromString case-insensitive
  • New: Define macro names with "PLOG" instead of "LOG" in order to avoid conflicts with "LOG" names defined in other packages or in system headers (#25, #129)
  • New: Add option for building samples (ON per default) (#125, #126)
  • New: Add CMake installer (#121, #122)
  • New: Add support for QStringRef
  • New: Modernize CMake (#106)
  • New: Allow rollLogFiles to be called manually (#100, #103)
  • New: Add ability to use UTC time (#101)
  • Fix: Disable PLOG_GET_THIS() by default (#120, #132)
  • Fix: Change RegSetValueExW prototype to match windows native declaration (void* -> BYTE*)
  • Fix: Move System::String^ handler to a free function (#131)
  • Fix: Making sure we can build standalone under Windows (#123)
  • Fix: Parse error by ReSharper (#116)
  • Fix: Parse error by Clang Code Model in Qt Creator (#114)
  • Fix: Printing CustomType at begin of the stream (#94)
  • Fix: Make RollingFileAppender work with maxFiles set to 1 (#70)
  • Fix: Clang-tidy nullable issue

Version 1.1.4 (26 Mar 2018)

  • New: Add -Wundef support
  • New: Add RTEMS support (#87)
  • New: Add Intel C++ Compiler support (#84)
  • New: Add FreeBSD support (#83)
  • New: Add -Wnon-virtual-dtor support (#79)
  • New: Support ostream operator<< on Windows as well as wostream (#66)
  • Fix: Fix compilation for Android (#68)
  • Fix: Fix compiling with CMake 2.8

Version 1.1.3 (09 Aug 2017)

  • New: Introduce LOG_ENABLE_WCHAR_INPUT macro to control wide string support
  • New: Add support for managed C++ System::String^ (#63)
  • New: Add missing macros for logging with severity NONE (#61)
  • Fix: Unable to build NativeEOLConverter/UTF8Converter using Visual Studio (#59)
  • Fix: Use WriteConsoleW instead of global setlocale for writing unicode into Windows console (#58)
  • Fix: Mention about linking to iconv on macOS (#55)
  • Fix: IF_LOG macro didn't work for curly braces blocks

Version 1.1.2 (02 May 2017)

Version 1.1.1 (17 Apr 2017)

  • New: Ability to check whether event log registry entry exists (#36)
  • Fix: Update includes (#47)
  • Fix: Get rid of windows.h dependency (#45, #13)
  • Fix: Signed unsigned assignment warning (#40)
  • Fix: Build warning on macOS 10.12 Sierra (#39)

Version 1.1.0 (20 Nov 2016)

  • Fix: Introduce binary compatible interface to Record (WARNING: this is not compatible with 1.0.x version in Chained mode, so don't mix 1.1.x and 1.0.x) (#34)

Version 1.0.2 (19 Nov 2016)

  • New: Default instanceId can be set via LOG_DEFAULT_INSTANCE (#11)
  • New: Support for QString (#30)
  • New: Support for C++Builder
  • New: severityFromString function (#15)
  • New: Capture source file name (disabled by default) (#21)
  • New: Add DebugOutputAppender (#33)
  • New: Add EventLogAppender (#32)
  • Fix: Crash on processing Obj-C function name (#12)
  • Fix: Compatibility with MinGW (#17)
  • Fix: IF_LOG_ macro in if/else leads to miss else branch (#27)
  • Fix: Thread safety for ConsoleAppender/ColorConsoleAppender (#18, #29)
  • Fix: Support for stream manipulators like std::endl (#31)
  • Fix: Compatibility with old Visual Studio versions

Version 1.0.1 (01 Nov 2015)

  • New: Add ColorConsoleAppender
  • Fix: Compatibility with Mingw-w64 (#6)
  • Fix: Log file not created if file name contains Unicode characters in Windows (#7)
  • Fix: Flush stdout (#4)
  • Fix: IntelliSense error: expected an identifier (#3)

Version 1.0.0 (19 May 2015)

  • Initial public release

*Note that all licence references and agreements mentioned in the plog README section above are relevant to that project's source code only.