Six pillars of an observability platform — running on one box.
Oleus bundles metrics, logs, distributed traces, alerting, and security into a single binary, pre-wired with shared auth, a unified query layer, and a common schema. Each capability is production-grade — we just stop you from gluing them together.
Metrics that scale to a billion samples on a $48 box.
PromQL- and MetricsQL-native. Drop-in replacement for Prometheus with 10× cardinality and 7× compression.
by (status_code, service)
- Query languagePromQL · MetricsQL · SQL via export
- Ingest formatsPrometheus remote-write · OTLP · InfluxDB · Graphite · CSV
- Cardinality10M+ active series on a single 4-core node
- RetentionHot tier: local SSD · cold tier: S3-compatible object store
- FederationCross-cluster
vmselectfor global views - Migration
oleus import prombackfills from a Prometheus 2.x snapshot
SQL-native logs. Year-of-data queries in under a second.
Columnar storage means you can GROUP BY across a billion rows without crying over a $30k bill.
quantile(0.99)(latency_ms) AS p99,
count() AS req
FROM logs
WHERE ts > now() - INTERVAL 1 DAY
GROUP BY service
ORDER BY p99 DESC;
- Compression10–30× vs. Splunk on equivalent data
- Ingest formatsOTLP · syslog · journald · Fluent-bit · vector · raw JSON
- SchemaAuto-inferred or declared. Add fields without migrations.
- SearchFull-text via
tokenbf_v1indexes · regex · structured - RetentionTTL per stream · hot/warm/cold tiering · S3 offload
- JoinsLogs ↔ metrics ↔ traces by trace_id and service.name
Distributed traces. End-to-end correlated.
OTel-native from the ground up. Every span is linked to logs, metrics, and security events sharing the same trace_id.
- ProtocolOTLP gRPC · OTLP HTTP · Zipkin · Jaeger thrift
- SamplingHead-based · tail-based · adaptive (rate-limited per service)
- RetentionDefault 14d · S3-backed for longer
- Storage~1KB / span average, indexed by service + operation
- CorrelationClick any span → tail logs, see metrics, view security events for that
trace_id - SDKsAuto-instrumentation for Node, Go, Python, Ruby, Java, .NET, Rust
PagerDuty-grade routing. Without the bill.
Define alert rules in PromQL. Route by severity, team, or label. Schedule on-call rotations. Open source.
histogram_quantile(0.99, rate(http_duration_bucket[5m])) > 0.5api-gateway rolled into one alert · severity = pageplatform · rotation = primary · escalates after 5m- Rule languagePromQL · MetricsQL · ClickHouse SQL (for log-based alerts)
- RoutingTree-based on labels · grouping · inhibition · silencing
- SchedulesRotations · overrides · holiday calendars · per-team escalation
- ChannelsSlack · Discord · email · SMS (Twilio) · webhook · PagerDuty
- ReliabilityActive-active HA · gossip protocol · zero notification loss across restarts
- RunbooksMarkdown links per rule · auto-attached to every page
Security in the same pane as performance.
Host-based intrusion detection, file integrity monitoring, and CIS-benchmark scanning — sharing infrastructure with your metrics and logs.
- Detection3,000+ built-in rules · MITRE ATT&CK mapping · custom rules in YARA
- FIMReal-time file integrity monitoring · diff capture · inotify-based
- ComplianceCIS · PCI-DSS · HIPAA · GDPR · NIST 800-53 templates
- Vulnerability scanningCVE database · OSV · per-host package scanning · daily refresh
- Active responseBlock IP via firewall · kill process · disable user · all scripted
- Agent footprint~35 MB RAM · <1% CPU · supports Linux, Windows, macOS, AIX, Solaris
oleus — your stack, in a pipe.
A 24MB Go binary that talks to the entire platform. Tail logs, run queries, manage alerts, push dashboards — without ever opening a browser.
Single binary · zero dependencies · auto-completion for bash/zsh/fish
jq