kala13x/slog

SLOG - Logging Library

SLog is cross platform and thread safe logging library for C/C++ with possibilities to easily control verbosity levels, tag and colorize output, log to file, on the fly change configuration parameters, optional log callback for log collection and many more. Read src/slog.h file to check out what release version do you have.

Installation

Installation is possible with Makefile.

git clone https://github.com/kala13x/slog.git
cd slog
make
sudo make install

CMakeLists.txt file is also included in the project.

git clone https://github.com/kala13x/slog.git
cd slog
mkdir build && cd build
cmake .. && make
sudo make install

Usage

If you want to use slog in your C/C++ application, include slog.h header in your source file and link slog library with -lslog linker flag while compiling your project. See example directory for more information.

Logging flags

SLog has it's own logging flags to control log levels and to display messages with tagged and colorized output.

• SLOG_NOTAG
• SLOG_LIVE
• SLOG_INFO
• SLOG_WARN
• SLOG_DEBUG
• SLOG_TRACE
• SLOG_ERROR
• SLOG_FATAL

Simple API

At first you should initialize slog:

int nEnabledLevels = SLOG_NOTAG | SLOG_ERROR;
nEnabledLevels |= SLOG_WARN | SLOG_FATAL;

/* Setting SLOG_FLAGS_ALL will activate all logging levels */
// nEnabledLevels = SLOG_FLAGS_ALL;

slog_init("logfile", nEnabledLevels, 0);

• First argument is the name of the file where we want to save logs.
• Second argument is the logging level flags which are allowed to print.
• Third argument is a thread safety flag (1 enabled, 0 disabled).

If thread safety flag is greater than zero, function initializes mutex and every other call of any slog function is protected by lock.

With the above slog initialization example only errors, warnings and not tagged messages will be displayed because there are no other flags activated during initializarion. Any logging level can also be activated or deactivated after slog initialization by setting the flag with the slog_enable() and slog_disable() functions.

/* Enable all logging levels */
slog_enable(SLOG_FLAGS_ALL);

/* Disable trace level (trace logs will not be displayed anymore) */
slog_disable(SLOG_TRACE);

/* Enable trace messages again */
slog_enable(SLOG_TRACE);

/* Disable all logging levels */
slog_disable(SLOG_FLAGS_ALL);

Deinitialization needed only if the nTdSafe and/or nKeepOpen flags are greater than zero.

slog_destroy();

Function destroys the mutex context, closes output file and resets thread safety flag to zero.

Print and log something in the file

Here is an example on how use slog:

slog("Simple message");

You can use old way logging function with a bit more control of parameters

slog_display(SLOG_DEBUG, 0, "Simple debug message without new line character");

• First argument is a log level flag of current message.
• Second argument is the flag to add new line character at the end of the output (1 add, 0 don't add).
• Third argument is the formated string which we want to display in the output.

Macros

SLog has cleaner option to log messages without the need to provide the flag parameter.

Here are defined macros based on the logging levels.

• slog()
• slog_live()
• slog_info()
• slog_warn()
• slog_debug()
• slog_error()
• slog_trace()
• slog_fatal()

Even shorter macros:

• slogl() same as slog_live()
• slogi() same as slog_info()
• slogw() same as slog_warn()
• slogd() same as slog_debug()
• sloge() same as slog_error()
• slogt() same as slog_trace()
• slogf() same as slog_fatal()

Each macro takes a formated string and has the another definition that does the same without newline characters.

• Format tags prototype follows the same rules as the C standard library function printf().
• Definitions without new line character begin with original names and end with the _wn string.

slog("Simple message");
slog_wn("Simple message without new line character\n");

slogd("Debug message")
slogd_wn("Debug message without new line character\n")

slog_debug_wn("Another debug message without new line character\n")
slog_debug("The %s contains between %d and %d billion stars and at least %d billion planets.", "Milky Way", 200, 400, 100);

In addition, there are several options to print the corresponding file name and line number where a slog macro was called. This rule follows the macros which relate to a fatal or trace flag, and shown bellow:

• slog_trace()
• slog_fatal()

Display message with trace tag and print source location:

slog_trace("Trace message throws source location.");

With expected output to be:

2017.01.22-19:03:17.03 - <trace> [example.c:71] Trace message throws source location.

It can also trace source location wothout any output message:

slog_trace();

With expected output to be:

2017.01.22-19:03:17.03 - <trace> [example.c:72]

Output, taken from example directory:

Configuration

Since version 1.8.* config file is no longer supported by slog but there is a way to change configuration parameters at runtime.

Variables of slog_config_t structure:

Any of those parameters above can be changed at runtime with the slog_config_set() function.

Example:

slog_config_t slgCfg;

/* Setup configuration parameters */
slgCfg.eColorFormat = SLOG_COLORING_TAG;
slgCfg.eDateControl = SLOG_TIME_ONLY;
strcpy(slgCfg.sFileName, "myproject");
strcpy(slgCfg.sFilePath, "./logs/");
slgCfg.logCallback = NULL;
slgCfg.pCallbackCtx = NULL;
slgCfg.nKeepOpen = 1;
slgCfg.nTraceTid = 1;
slgCfg.nToScreen = 1;
slgCfg.nUseHeap = 0;
slgCfg.nToFile = 0;
slgCfg.nFlush = 1;
slgCfg.nFlags = SLOG_FLAGS_ALL;

/* Tread safe call to update slog configuration */
slog_config_set(&slgCfg);

If you want to change only few parameters without resetting other ones, you can thread safe read current working configuration and update only needed parameters.

slog_config_t slgCfg;
slog_config_get(&slgCfg);

/* Update needed parameters */
slgCfg.nTraceTid = 1;
slgCfg.nToFile = 1;

/* Tread safe call to update slog configuration */
slog_config_set(&slgCfg);

Dynamic allocation

If output message is larger than slog default message limit (8196 bytes) there is a possibility to enable dynamic allocation and use heap for output messages:

slog_config_t slgCfg;
slog_config_get(&slgCfg);
slgCfg.nUseHeap = 1;
slog_config_set(&slgCfg);

slog_debug("Your too big output message here");

Coloring

SLog also has coloring control possibility to colorize whole line, just tag or disable coloring at all.

slog_config_t slgCfg;
slog_config_get(&slgCfg);

/* Colorize only tags */
slgCfg.eColorFormat = SLOG_COLORING_TAG;
slog_config_set(&slgCfg);
slog_debug("Message with colorized tag");

/* Colorize full line */
slgCfg.eColorFormat = SLOG_COLORING_FULL;
slog_config_set(&slgCfg);
slog_debug("Message with full line color");

/* Disable coloring at all */ 
slgCfg.eColorFormat = SLOG_COLORING_DISABLE;
slog_config_set(&slgCfg);
slog_debug("Message without coloring");

Time and date

SLog gives you possibility to control time and date format in log output.

slog_config_t slgCfg;
slog_config_get(&slgCfg);

/* Disable time and date in output */
slgCfg.eDateControl = SLOG_TIME_DISABLE;
slog_config_set(&slgCfg);
slog_debug("Message without time and date");

/* Enable only time in output */
slgCfg.eDateControl = SLOG_TIME_ONLY;
slog_config_set(&slgCfg);
slog_debug("Message with time only");

/* Enable date + time in output */ 
slgCfg.eDateControl = SLOG_DATE_FULL;
slog_config_set(&slgCfg);
slog_debug("Message with time and date");

Example output:

Message without time and date
02:11:33.36 - <debug> Message with time only
2021.05.23-02:11:34.36 - <debug> Message with time and date

Thread ID tracing

If you are looking for additional information about threads while debugging, you can trace thread IDs and display in the output.

Here is an example:

slog_config_t slgCfg;
slog_config_get(&slgCfg);
slgCfg.nTraceTid = 1;
slog_config_set(&slgCfg);

slog_debug("Message with thread id");

With expected output to be:

(15203) 2017.01.22-19:03:17.03 - <debug> Message with thread id.

Where 15203 is a thread identifier from which the message was printed.

Indentations

With enabled indentation flag, slog will automatically adjust the spacing between the information and the message.

slog_config_t slgCfg;
slog_config_get(&slgCfg);
slgCfg.nIndnets = 1;
slog_config_set(&slgCfg);

/* You can also enable indents like that */
slog_indent(1); // Any value except 0 will enable it

With indentations enabled:

Without indentations enabled:

Callback

If you want to collect logs for any purpose, use a callback function pointer. If this pointer is set, any log will be passed to the function this pointer points to.

int log_callback(const char *pLog, size_t nLength, slog_flag_t eFlag, void *pCtx)
{
    (void)nLength; // Log message length
    (void)eFlag; // Logging flag of this message
    (void)pCtx; // Optional pointer passed to the callback

    printf("%s", pLog);
    return 0;
}

int main()
{
    slog_init("logfile", SLOG_FLAGS_ALL, 0);

    slog_config_t slgCfg;
    slog_config_get(&slgCfg);
    slgCfg.logCallback = log_callback;
    slgCfg.pCallbackCtx = NULL; // Optional pointer passed to the callback
    slog_config_set(&slgCfg);

    slog("This message will be passed to the callback function");

    slog_destroy();
    return 0;
}

If you return -1 from the callback function, the log will no longer be printed to the screen or written to a file by slog. If you return 0, the log will not be written to the screen but still to a file (if nToFile > 1). If you return 1 the logger will normally continue its routine.

Version

Get slog version with the function slog_version(). The argument uint8_t nShort is a flag to get short or full string of the version (1 short, 0 full).

Usage:

printf("slog version: %s", slog_version(0));

Output will be something like that:

slog version: 1.8 build 22 (Dec 14 2020)

There are also definitions that can be used to check the version without using the function.

• SLOG_VERSION_MAJOR - Major version of the library.
• SLOG_VERSION_MINOR - Minor version of the library.
• SLOG_BUILD_NUMBER - Build number.

Output

Here is en example of the log file context created by slog:

Simple message without anything
02:11:34.36 - Simple message with time only
02:11:34.36 - Simple message with our own new line character
02:11:34.36 - <debug> Old way printed debug message with our own new line character
02:11:34.36 - <error> Old way printed error message with auto new line character
02:11:34.36 - <warn> Warning message without variable
02:11:34.36 - <info> Info message with string variable: test string
02:11:34.36 - <note> Note message with integer variable: 69
(8180) 02:11:34.36 - <debug> Debug message with enabled thread id tracing
(8180) 02:11:34.36 - <error> Error message with errno string: Success
(8180) 02:11:34.36 - <debug> Debug message in the file with full line color enabled
(8180) 02:11:34.36 - <trace> [example.c:105] Trace message throws source location
(8180) 02:11:34.36 - <fatal> [example.c:108] Fatal message also throws source location
(8180) 2021.05.23-02:11:34.36 - <debug> Debug message with time and date
(8180) 2021.05.23-02:11:34.36 - <debug> Disabled output coloring
(8180) 2021.05.23-02:11:34.36 - <trace> [example.c:124] 
(8180) 2021.05.23-02:11:34.36 - <debug> Above we traced source location without output message