Logging Section

Fields

name	type	description
name	string	name sink
pattern	string	useful information to save in the log
filepath	string	file to save the log
console.output_enabled	bool	display log in console
level	unsigned int	level log
trace_updates.interval	uint16_t	interval to display the log
type	string	log type (daily, rotation)
daily.max_size	uint16_t	maximum size for file type daily
daily.time	uint16_t	time of the day when a new log file will be created.
daily.truncate	bool	truncate file
rotation.max_size	uint16_t	maximum size for file type rotation
rotation.max_files	uint16_t	maximum files

I recommend you study spdlog, we use it as a lib for the engine, so these settings are based on it

Log level -

TRACE	0
DEBUG	1
INFO	2
WARN	3
ERROR	4
CRITICAL	5
OFF	6

Log type -

• daily

• rotation

Log pattern -

Allows customizing log message formatting using a pattern. This pattern can be configured in a infinity.conf , for example:

pattern = "[%Y-%m-%d %H:%M:%S] [%n] [%^%l%$] %v"

Each marker in the pattern has a specific meaning:

• %Y – Year with four digits (e.g., 2024)

• %m – Month with two digits (01 to 12)

• %d – Day of the month (01 to 31)

• %H – Hour in 24-hour format (00 to 23)

• %M – Minutes (00 to 59)

• %S – Seconds (00 to 59)

• %n – Logger name

• %^ – Start of color formatting for the log level

• %l – Log level (e.g., info, error, debug)

• %$ – End of color formatting

• %v – Log message

Example of formatted output

If the pattern is [%Y-%m-%d %H:%M:%S] [%n] [%^%l%$] %v and the application generates a log, it may appear as:

[2025-02-18 01:04:21] [engine] [info] Preparing gateway analysis routes ...

Customizing the format

You can modify the pattern as needed. For example, to add milliseconds and the thread ID:

pattern = "[%Y-%m-%d %H:%M:%S.%e] [%t] [%n] [%^%l%$] %v"

Where:

• %e – Milliseconds (000 to 999)

• %t – Current thread ID

This could result in a log like:

[2025-02-18 14:30:45.123] [12345] [engine] [info] Processing request.