Jev in production › Message and ticket triage
Jevops
SRE log triage tool routes Elasticsearch log bursts through Jev to decide whether to page, digest or resolve; author cites 70-500ms latency (author).
70-500msmeasured, as published by the source
- Use
- Message and ticket triage
- Industry
- IT operations
- Form
- Open-source tool
- Stage
- Beta
- Plugs into
- Elasticsearch
- Listed
- 2026-09-26
- Found via
- github
- Repository
- Mu99Ti/Jevops
- Stars
- 8
- Forks
- 1
- Last push
- 2026-09-24
- Language
- Python
- License
- none stated
The README opens with
SRE log tool built on TypeSafe Jev (typed decision model) with Elasticsearch, Logstash, Kibana, and Grafana integration — two coexisting approaches:
- Mode A — real-time triage: streams logs and decides page / digest / resolve (see below). - Mode B — investigative query: answers "what's important from 8am to now?" by hierarchically drilling chunks of logs with Jev, then having an LLM explain the exact lines with citations and tool calls (docs/hierarchical-query.md).
Badge
For the project's own README, linking back here:
Also used for message and ticket triage
- One (Inbox Run) ~580 conversations/sec
- Jev Orchestrator $0.00003
- SipPulse Meet Capture 300 ms
- jev-oncall 0.87
- hush (emreozyoruk) 78%
- openpoke-meets-jev (0xShin0221) 424 ms
- Surely – AI Triage (Devcore) 74%
- jev-inbox-triage 19/20