Lumis SDK 0.1.0 / experimental proof of concept, open source
Diagnosis you can inspect, line by line.
A proof of concept of the Lumis investigation core: a read-only Python framework, open source under Apache-2.0. It reports to a person; it never changes your systems. Other Lumis products and services are separate.
GitHubInstall
Start in four commands.
Python 3.11 or later. The http extra adds the telemetry connectors and agent the optional investigator. The scaffolded project is a small synthetic check: it needs no cluster and no API key, and makes no model call.
- 01 · Create a project
lumis init --directory my-lumis - 02 · Check the configuration
lumis doctor --project my-lumis/lumis.yaml - 03 · See what Lumis can read
lumis discover --project my-lumis/lumis.yaml - 04 · Investigate an incident
lumis incident --project my-lumis/lumis.yaml \ --incident my-lumis/incident.json \ --observations my-lumis/observations.json - Expect a report for human review, not a fix. Add
--use-agentto opt in to the investigator once a model and credential are configured; configuration alone makes no paid call.
What is in 0.1.0
Checks first.
Evidence decides.
Sources in YAML
Kubernetes, Prometheus, Loki, Tempo, Prefect, SQL, and Git or rollout change records. Read-only.
An operational graph
Declared and discovered services, data and changes, scoped to the incident at hand.
Deterministic triage
Signatures run first against registered facts. A terminal match needs no model.
One bounded investigator
Optional and opt-in. Approved queries, change records and allowlisted code, within budgets. OpenRouter, OpenAI, Anthropic or Gemini.
Mechanical assessment
Every hypothesis is checked against evidence the run collected. One supported cause, or “insufficient evidence”.
Audit records
Each investigation and its human resolution is kept in local SQLite.
Not included: no remediation executor, no rule promotion, no incident-memory retrieval, no hosted service. Those remain research.
Read-only
Runs where you work. Shows every step it took.
No hosted account. Reports, evidence receipts and audit records are files you can open, diff, and question.
Worked example
GridCast, our reference estate.
A synthetic electricity-forecasting estate on Kubernetes with fifteen reproducible failures. Its Lumis project is one YAML file and a small harness, and every experiment and transcript is public.
Using Lumis on a smaller project
You do not need an estate like GridCast. One service with Prometheus or a log source is enough to start; cookbooks for small setups will follow.