Let Jev Score OpenTelemetry Logs Before a Bigger LLM Sees Them

Description and use

Jev Logs triages OpenTelemetry logs, scoring each for value and priority, routing only high‑value logs to an expensive LLM, reducing costs and improving analysis efficiency.

Problem

Sending every OpenTelemetry log to an expensive LLM causes unnecessary cost and noise before investigation starts.

Outcome

Reduced LLM usage by filtering out low‑value logs, cutting costs and improving signal-to-noise ratio in log analysis.

Workflow

• 1. Install jevlogs via npm or npx.
• 2. Run npx jevlogs --live to start a local OTLP receiver.
• 3. Point your application’s OTLP exporter to http://127.0.0.1:4318/v1/logs.
• 4. Jev Logs evaluates each log, assigns diagnostic value, priority, actionable probability, and a route (analyze/retain).
• 5. Low‑priority, low‑value logs are retained without LLM call; high‑priority logs are forwarded to the LLM for deeper analysis.
• 6. Optionally add custom rules to skip health checks or other noise.
• 7. Review annotated logs and adjust rules as needed.

Evidence

Jev Logs makes the first decision: how useful is this log, how urgent is it, and does it deserve a more expensive model?

Source

A log may skip deeper analysis only when all three are true: priority is low, value is 25 or below, and actionable probability is under 0.1.

Source