Skip to content

Log and alert triage with decision models

Deciding which log lines, alerts or incidents to suppress, watch, review or page on, so an expensive model or a human only sees what matters.

43 public projects · page 1 of 2

  • Go CLI for managing WordPress sites at scale, with typesafe commands that ask Jev questions and a scan --triage that ranks malware findings.

    ProjectproductionGo
  • Self-hosted Stacks blockchain data service whose Slack gate and fault-triage paths reportedly run on Jev decisions.

    ServiceproductionTypeScript
  • Unix filters (grev, tagv, rank, sortv, cutv, uniqv and more) that select, label and rank lines by meaning with Jev.

    CLIbetaGo
  • Home Assistant integration that runs weekly checks with Jev judgments and turns confident findings into Repairs cards for you to confirm.

    ProjectbetaPython
  • Hermes Agent plugin exposing Jev as four coding-workflow tools: jev_check, jev_route, jev_score and jev_evaluate.

    PluginbetaPython
  • Scores OpenTelemetry logs with Jev for diagnostic value, priority and routing before any expensive LLM analysis.

    ProjectbetaTypeScript
  • Python CLI that analyses JSON, NDJSON and JSONC logs and artifacts with Jev question packs, anchoring each answer to source lines.

    CLIbetaPython
  • Splunk search command that asks Jev typed questions about events and adds probabilities, choices and scores as fields.

    AppbetaPython
  • TypeScript library adding policy, confidence gates, shadow mode, recipes and an eval CLI around Jev answers.

    CLIbetaTypeScript
  • One Jev call per log batch answers noise and severity questions; code maps answers to suppress, watch, review, notify or page.

    ProjectbetaPython
  • On-call tooling where Jev judges alerts and incident hypotheses and plain code decides: alert routing plus a no-LLM root-cause benchmark.

    ProjectbetaPython
  • Spring WebFlux starter: a semantic circuit breaker where Jev flags HTTP 200 responses whose bodies actually encode failures.

    ProjectbetaJava
  • Test-failure triage for coding agents: local rules first, then one batched Jev call labels failures RETRY, FIX_CODE or FIX_ENV.

    ProjectbetaPython
  • Bash-native CLI that filters any stream by meaning with Jev, like grep for semantics, so an agent wakes only for lines that matter.

    ProjectbetaTypeScript
  • Rust streaming event bus whose routing is decided by Jev, one question per subscription, with deliver, review or drop thresholds.

    ProjectbetaRust
  • Rust CLI and TUI that streams Kubernetes logs, applies offline rules and Jev analysis to flag what matters, then hands off.

    ProjectbetaRust
  • Prunes long command output for coding agents by asking Jev which lines matter for the task, keeping original text and order.

    ProjectbetaTypeScript
  • Apache NiFi processor that routes FlowFiles yes, no, review or failure based on a Jev yes/no question and a confidence band.

    ProjectbetaJava
  • CLI that searches code, docs and logs by natural-language condition, asking Jev a yes/no question per candidate with a threshold.

    CLIbetaTypeScript
  • Claude Code skill that hands bulk 'read a lot to decide a little' judgments over files, logs and tickets to Jev and returns a shortlist.

    Agent skillbetaJavaScript
  • ROS 2 robot diagnostics CLI where an optional agent uses Jev to choose which read-only evidence tool to call next.

    CLIbetaPython
  • Unix filter for security alert triage: JSONL alerts in, Jev answers five typed questions, code routes each alert.

    ProjectbetaRust
  • Go utilities for TypeSafe: a grep-like qgrep CLI, a kubectl plugin for asking questions about pod logs, and an SDK.

    ServicebetaGo
  • Two small Python apps: Jev triages failed pipeline tasks into review, retry, page or ticket, and routes support messages to agents.

    ProjectprototypePython
  • Smart-meter fleet dashboard where code pre-filters telemetry and Jev classifies anomalies for remediation across millions of endpoints.

    ProjectprototypeTypeScript
  • Tool that lets code and agents ask Jev typed questions via reusable jevels, mapping answers to act, mark or fall_back.

    ProjectprototypeTypeScript
  • OpenTelemetry Collector processor that asks Jev how useful each metric is from its metadata and applies keep/drop policy.

    ServiceprototypeGo
  • OpenTelemetry trace processor that asks Jev whether an operation is diagnostic, business-critical and worth keeping, and annotates spans.

    ProjectprototypeGo
  • Playwright TypeScript project using Jev for semantic assertions, element picking, goal-driven steps and test failure classification.

    ProjectprototypeTypeScript
  • Browser studio and templates for trying Jev as a System 1 reflex gate in front of frontier LLMs, with code exporters.

    Projectprototype

Related categories

Related coding agents