mirror of https://github.com/aya-rs/aya
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
a4a69a6bcf
- Replace all `#[repr(usize)]` with `#[repr(u8)]`; this saves 3*(sizeof(word)-1) bytes per log message. - Encode payload length as u16 rather than usize; this saves sizeof(word)-1 bytes per log message. This is safe because the maximum size of a log message is less than (1 << 16 - 1). This changes `level` to a require field in every log message. It was already always present, but was treated as optional when reading. |
2 years ago | |
|---|---|---|
| .. | ||
| src | 2 years ago | |
| Cargo.toml | 2 years ago | |
| README.md | 2 years ago | |
| release.toml | 3 years ago | |
README.md
aya-log - a logging library for eBPF programs
Overview
aya-log is a logging library for eBPF programs written using aya. Think of
it as the log crate for eBPF.
Installation
User space
Add aya-log to Cargo.toml:
[dependencies]
aya-log = { git = "https://github.com/aya-rs/aya", branch = "main" }
eBPF side
Add aya-log-ebpf to Cargo.toml:
[dependencies]
aya-log-ebpf = { git = "https://github.com/aya-rs/aya", branch = "main" }
Example
Here's an example that uses aya-log in conjunction with the env_logger crate
to log eBPF messages to the terminal.
User space code
use aya_log::BpfLogger;
env_logger::init();
// Will log using the default logger, which is TermLogger in this case
BpfLogger::init(&mut bpf).unwrap();
eBPF code
use aya_log_ebpf::info;
fn try_xdp_firewall(ctx: XdpContext) -> Result<u32, ()> {
if let Some(port) = tcp_dest_port(&ctx)? {
if block_port(port) {
info!(&ctx, "❌ blocked incoming connection on port: {}", port);
return Ok(XDP_DROP);
}
}
Ok(XDP_PASS)
}