os_observatory 0.1.1

Independent, no-deps observability toolkit for OS development: logging, tracing, and panic reporting designed for no_std environments.
Documentation
  • Coverage
  • 91.53%
    54 out of 59 items documented2 out of 29 items with examples
  • Size
  • Source code size: 30.64 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 795.92 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 4s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • alisio85/os_observatory
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • alisio85

os_observatory

Independent, no-dependency observability toolkit for operating-system development. Provides:

  • Structured logging macros targeting pluggable sinks
  • Lock-free ring buffer sink for text output
  • Fixed-capacity event tracing buffer for low-overhead instrumentation
  • Panic reporting helpers
  • Small memory utilities
  • Build metadata capture

Highlights:

  • no_std first, std optional for host tests
  • Zero external dependencies
  • Heavily documented APIs for docs.rs
  • MIT licensed — created by an AI Assistant (GPT-5-medium) from an idea by alisio85

Quickstart:

use os_observatory::sink::RingBufferSink;
use os_observatory::logging::{Logger, Level};
use os_observatory::{os_log, os_error};

static SINK: RingBufferSink<1024> = RingBufferSink::new();
let logger = Logger::new(&SINK).with_level(Level::Info);
os_log!(&logger, "Boot OK");
os_error!(&logger, "oops code={}", 7);

See docs/ for detailed manuals and integration guides.