Expand description
AI-powered error monitoring for Rust applications.
use oluso::{Client, Options, Severity};
let client = Client::new(Options::new("your-api-key"));
client.install_panic_hook();
client.add_breadcrumb(oluso::NewBreadcrumb::new("user started checkout"));
if let Err(err) = do_checkout().await {
client.capture_error(&err).await;
}Structs§
- Assertion
Options - Breadcrumb
- A single event on the trail leading up to an error (a request started, a button was clicked, a query ran). Attached to the next error report, then cleared.
- Client
- The Oluso client. Cheap to clone (everything inside is either
Copy, anArc, or a handle type that’s already internally reference-counted), but is normally held asArc<Client>– viaClient::new– sinceClient::install_panic_hookneeds a'statichandle it can move into the global panic hook. - Error
Context - Error
Report - Heartbeat
Options - Monitor
Receipt - Monitor
Workflow - NewBreadcrumb
- A breadcrumb as given to
add_breadcrumb– the timestamp is filled in automatically, so callers don’t provide one. - Options
- Configuration for a
crate::Client. Construct withOptions::new, which fills in every default; override individual fields with the builder methods. - Request
Context - Info about the request in flight when the error was captured. Framework integrations build this; there’s nothing generic enough in std to derive it from automatically.
- Server
Context - User
Context - Workflow
Event Options
Enums§
- Breadcrumb
Level - Monitor
Reference - Monitor
Request Error - Severity
- How severe a captured error is. Mirrors the string values the other
Oluso SDKs send (
critical/high/medium/low) so the ingestion API treats reports from every language the same way. - Transport
Error