Version: 1.0.2

Overview

LogIt++ is a header-only, macro-first C++ logging library. The core and most native backends support C++11; OTLP, the Prometheus HTTP server, and MDBX use C++17 through their CMake feature options.

#include <logit.hpp>
 
int main() {
    LOGIT_ADD_CONSOLE_DEFAULT();
    LOGIT_INFO("service started", 42);
    LOGIT_WAIT();
}

Documentation map

Quick start and documentation map — quick start, installation paths, and public API boundary.
Installation guide — complete CMake, vendored, installed-package, and package-manager setup.
Backend matrix — backend, platform, dependency, and packaging matrix.
OTLP/HTTP logger — OTLP HTTP and callback exporters.
Prometheus Logger — Prometheus payload and HTTP server backends.
TaskExecutor Implementation Notes — shared executor, dedicated workers, and lifecycle.
Queue Back-Pressure Controls — queue policies and drop counters.
Performance and benchmarks — benchmark methodology and historical snapshot.
API reference and concepts — detailed macro, formatting, configuration, and extension reference.
Comparison with other C++ logging libraries — comparison with other C++ logging libraries and trade-offs.
Architecture decisions — the source repository's docs/adr/ records the rationale for public boundaries, executors, snapshots, and compatibility.

Feature summary

Macro families cover direct, printf-style, stream, conditional, throttled, tagged, and scope-timer logging.
Console, file, unique-file, memory, crash, system, OTLP, Prometheus, and MDBX backends are available behind their documented feature options.
MDC/NDC context, structured records, stored-log readers/subscribers, queue backpressure, and runtime log-level controls are supported.

Application code should include the public umbrella headers and use the LOGIT_* macros. The logit::detail namespace and implementation headers are internal and carry no source or API compatibility guarantee.

See the source examples/ directory for complete, buildable examples. The full reference page is intentionally separate so this landing page remains a concise entry point.