What
Document and verify the production feature matrix for logger_system integrations and optional capabilities.
Part of kcenon/common_system#684.
The 2026-05-21 analysis found several production-relevant toggles that should be explicit for release consumers: standalone std::jthread async mode, optional thread_system integration, OpenSSL encryption, compression, structured logging, network writer, and OTLP export.
Why
logger_system is a mid-tier dependency used by higher-level systems for diagnostics and auditability. The default feature set and optional integrations affect binary dependencies, security posture, and runtime behavior. Consumers should not have to infer production support from CMake options alone.
Where
cmake/options.cmake
cmake/dependencies.cmake
README.md
docs/CONFIGURATION.md or equivalent configuration docs
include/kcenon/logger/**
- Integration tests covering optional features
How
Approach
- Build a matrix of logger capabilities: async mode, thread_system integration, encryption, compression, structured logging, network writer, OTLP, monitoring integration, and crash handling.
- For each row, record default value, required dependency, vcpkg feature if any, production support level, and verification command.
- Ensure README and configuration docs match the CMake defaults.
- Mark any example-only or placeholder capability explicitly.
- Open follow-up implementation issues for any production-claimed capability lacking tests.
Acceptance Criteria
Verification
What
Document and verify the production feature matrix for
logger_systemintegrations and optional capabilities.Part of kcenon/common_system#684.
The 2026-05-21 analysis found several production-relevant toggles that should be explicit for release consumers: standalone
std::jthreadasync mode, optionalthread_systemintegration, OpenSSL encryption, compression, structured logging, network writer, and OTLP export.Why
logger_systemis a mid-tier dependency used by higher-level systems for diagnostics and auditability. The default feature set and optional integrations affect binary dependencies, security posture, and runtime behavior. Consumers should not have to infer production support from CMake options alone.Where
cmake/options.cmakecmake/dependencies.cmakeREADME.mddocs/CONFIGURATION.mdor equivalent configuration docsinclude/kcenon/logger/**How
Approach
Acceptance Criteria
Verification