graflog 1.6.1

Structured JSON logging for Rust applications optimized for Grafana ingestion
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119

# graflog

Structured JSON logging optimized for Grafana ingestion. Clean enum-based configuration.

## Features

- JSON-only structured logging
- Grafana-optimized field naming
- Thread-safe file appending
- Zero-configuration setup
- Consistent timestamp formatting
- Service and component tagging
- Distributed tracing with spans
- Clean enum-based configuration

## Installation

```bash
cargo add graflog
```

## Usage

```rust
use graflog::{init_logging, app_log, app_span, LogOption};

fn main() {
    // Simple logging
    init_logging!(&log_path, "payment-service", "api", &[LogOption::Debug]);
    
    // Silent rocket with console disabled
    init_logging!(&log_path, "api0", "uploader", &[
        LogOption::Debug,
        LogOption::RocketOff,
        LogOption::NoConsole
    ]);
    
    // Multiple filters in any order
    init_logging!(&log_path, "service", "component", &[
        LogOption::ActixWarn,
        LogOption::Info,
        LogOption::HyperOff
    ]);
    
    // Custom filter
    init_logging!(&log_path, "service", "component", &[
        LogOption::Debug,
        LogOption::Custom("my_crate::module=warn".to_string())
    ]);
    
    // Log with automatic service/component tags
    app_log!(info, "Server started on port 8080");
    app_log!(error, "Database connection failed", error_code = 500);
    
    // Log with custom service/component
    app_log!(debug, "user-service", "auth", "Login attempt", user_id = 12345);
    
    // Create spans for distributed tracing
    let process_span = app_span!(
        "process_payment",
        user_id = %user_id,
        amount = amount
    );
    let _enter = process_span.enter();
}
```

## Configuration Options

### Log Levels
- `LogOption::Trace`
- `LogOption::Debug` 
- `LogOption::Info`
- `LogOption::Warn`
- `LogOption::Error`

### Framework Filters
- `LogOption::RocketOff` - Turn off rocket logs
- `LogOption::ActixOff` / `LogOption::ActixWarn` - Control actix_web logs
- `LogOption::HyperOff` / `LogOption::HyperWarn` - Control hyper logs  
- `LogOption::TokioOff` / `LogOption::TokioWarn` - Control tokio logs

### Console Control
- `LogOption::Console` - Enable console output (default)
- `LogOption::NoConsole` - Disable console output

### Custom Filters
- `LogOption::Custom("target=level".to_string())` - Any custom filter

## Grafana Integration

Logs are formatted with consistent fields:
- `service`: Service identifier
- `component`: Component within service  
- `timestamp`: RFC3339 formatted timestamp
- `level`: Log level (trace, debug, info, warn, error)
- Custom fields from your log statements

Perfect for Grafana Loki queries:
```logql
{service="payment-service"} | json | level="error"
{service="auth-service"} | json | component="jwt"
```

## Migration from Previous Versions

Old syntax:
```rust
init_logging!(&log_path, "service", "component", "debug", "rocket::server=off", false);
```

New syntax:
```rust
init_logging!(&log_path, "service", "component", &[
    LogOption::Debug,
    LogOption::RocketOff, 
    LogOption::NoConsole
]);
```