jevbooks

← All projects

jev-logtriage

jyatesdotdev/jev-logtriage

Jev decides if a batch of logs is worth acting on.

What it is

A Python tool for on-call operations that collapses Loki log batches into a single Jev call, then maps answers to suppress, watch, review, notify, or page. Nothing is executed.

How it uses Jev

One System One call per source asks six typed questions (Noul, Score, Choice) about routine noise, severity, impact, action need, auto-remediability, and category. Answers feed code gates that route to suppress, watch, review, notify, or page; low confidence goes to review.

Primitives:choicescorenoul

Technique worth stealing

Speculative fan-out: ask all six questions up front, ignore answers that do not apply.

Try it

uvx --from jev-logtriage logtriage --demo (needs TYPESAFE_API_KEY).

View on GitHub

judged by Jevjev-1.13.0

Evidence

Each line is one question put to Jev about the README. ≥ 0.60 reads as yes, ≤ 0.40 as no; in between Jev is not making a call.

  • Jev-centricyes0.96
  • Shows a System One patternyes0.96
  • Handles uncertaintyyes0.87
  • Measuredno0.04
  • Runnableyes0.84
  • Worth recommendingyes0.63
  • Model replicano0.04
  • Problem scopescore on a 0–2 scale1.64
  • About Jevyes0.98

Signals by Jev jev-1.13.0, card written by DeepSeek V4.1 Flash from the README on 20 Sept 2026.