5 releases
new 0.1.4 | Apr 14, 2025 |
---|---|
0.1.3 | Apr 10, 2025 |
0.1.2 | Apr 7, 2025 |
0.1.1 | Mar 28, 2025 |
0.1.0 | Mar 16, 2025 |
#178 in Debugging
523 downloads per month
Used in book_lib
82KB
2K
SLoC
Loggit
Loggit is a lightweight, easy-to-use logging library for Rust. It provides ready-to-use logger macros that let you start logging with zero boilerplate. You simply import and use it; no additional setup is required for basic usage. However, if you need more control, you can customize the logging format, colors, and minimum logging level.
Features
- Zero Setup: Just import the library and start logging.
- Customizable: Change log formats, colors, and logging levels.
- Macros Provided: Includes
trace!
,debug!
,info!
,warn!
, anderror!
. - Flexible Formatting: Use custom templates with placeholders like
{level}
,{file}
,{line}
, and{message}
. - Saving log to files: Save your logs to files automaticaly by specifying filename format
- File rotation: Rotate your files by specifying time period or size
- Compress used files: Save your space by compressing used log files
Installation
Add LogGit to your Cargo.toml:
[dependencies]
loggit = "0.1.4"
or just write in the terminal:
cargo add loggit
Usage
Basic Logging
Simply import the logger macros and use it in your project:
use loggit::{trace, debug, info, warn, error};
fn main() {
trace!("This is a trace message.");
debug!("Debug message: variable value = {}", 42);
info!("Informational message.");
warn!("Warning: something might be off.");
error!("Error occurred: {}", "example error");
}
Customizing the Log Level
Set the minimum log level so that only messages at that level and above are printed:
use loggit::logger::set_log_level;
use loggit::Level;
fn main() {
// Set log level to DEBUG; TRACE messages will be ignored.
set_log_level(Level::DEBUG);
debug!("This is a debug message.");
trace!("This trace message will not be logged.");
}
Customizing the Log Format
You can adjust the log format globally or per log level. Templates can include placeholders like {level}
, {file}
, {line}
, and {message}
. Colors can be configured by wrapping text with color tags.
Global Format Customization
use loggit::logger::set_global_formatting;
fn main() {
// Set a global custom log format using color tags.
set_global_formatting("<green>[{level}]<green> ({file}:{line}) - {message}".to_string());
info!("This info message follows the new global format.");
info!("The error message as well.");
}
Level-Specific Format Customization
use loggit::logger::set_level_formatting;
use loggit::Level;
fn main() {
// Customize the ERROR log format specifically.
set_level_formatting(
Level::ERROR,
"<red>[{level}]<red> <blue>({file}:{line})<blue> - <red>{message}<red>".to_string()
);
error!("This error message will follow the custom error format.");
}
Enabling Colorized Output
Enable or disable colored output based on your preference:
use loggit::logger::set_colorized;
fn main() {
// Enable colored output.
set_colorized(true);
info!("This info message will be colorized as specified in the format.");
}
Customizing Terminal Output
Control whether messages are printed directly to the terminal:
use loggit::logger::set_print_to_terminal;
fn main() {
// Disable terminal output (for example, if you want to log to a file instead).
set_print_to_terminal(false);
info!("This message will not be printed to the terminal.");
}
Setting up logging to the file
Enable save all your logs to a file
use loggit::logger::set_file;
fn main() {
// provide file name
set_file("file_name.txt");
}
You can choose a format for the file name:
use loggit::logger::set_file;
fn main() {
// provide file name
set_file("{level}-log-on-{date}.txt");
}
Choose how oftenly you change your file
use loggit::logger::{set_file, add_rotation};
fn main() {
// provide file name
set_file("{level}-log-on-{date}.txt");
add_rotation("1 week"); // change the file every week
add_rotation("5 MB"); // max file size 5 MB, then again change of the file
}
Save your space by compressing log files
use loggit::logger::{set_file, set_compression};
fn main() {
// provide file name
set_file("{level}-log-on-{date}.txt");
set_compression("zip");
}
Documenation
A complete user documentation can be found here
Configuration
Internally, LogGit uses a simple configuration structure which holds:
- Log Level: One of TRACE, DEBUG, INFO, WARN, or ERROR.
- Terminal Output: A flag that determines if logs are printed to the terminal.
- Colorization: A flag to enable or disable colored output.
- Custom Formats: Individual formatters for each log level.
- Custom file names: A format of a name that a file will take
- File rotation: How oftenly will the file be changed
- Compression method: To save space, you can specify the compression method.
The default configuration already provides sensible defaults, so you can get started right away. Customization is available for those who need advanced logging setups.
Contributing
Contributions and suggestions are welcome! Feel free to open issues or submit pull requests to help improve LogGit.
Release notes
In order to read release notes for each version, click here
TODO
- getting config from json/env files
License
LogGit is licensed under the MIT License.
Dependencies
~8MB
~139K SLoC