User repository on GitHub
- Forks
- 0
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Integrations & Adapters
Jevtraces
Alpha OpenTelemetry Collector processor that scores operation metadata with three Jev noul questions, caches the result, and writes it onto later matching spans as jevtraces.operation annotations.
- Stars
- 0
- Language
- Go
- License
- APACHE-2.0
- Published by
- Community
- Author
- ishantanu
- Last verified
- Oct 2026
About this project
Jev inference over operation metadata, delivered as OpenTelemetry span annotations. jevtraces is an alpha OTel trace processor. It asks Jev whether representative traces containing an operation are likely useful for diagnosis, business-critical, and worth retaining. It caches those judgments and annotates later matching spans. The jevtraces processor retains every span, regardless of the returned probabilities.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- Go
Highlights
- It annotates, it does not sample: the processor retains every span regardless of the probabilities, and only the opt-in experiment branches into two pipelines.
- Three independent noul probabilities, diagnostic_value, business_criticality and keep_probability, appear only on spans in the scored state.
- Local rules bypass inference entirely, marking error status, slow duration and exact protected_operation names, and local protection outranks a cached score.
- Cache identity is a hash of the exact request state, so two spans with identical descriptors share one assessment despite different trace and instance IDs.
Watch out
Alpha, and annotate is the only mode that validates: reduce and other modes fail validation, so nothing here reduces trace volume. Annotations add storage and indexing volume and the README states this version provides no volume reduction. The processor assesses operation metadata, not a complete trace or a specific request's outcome, a trace can contain spans with different assessments, and a low operation score is explicitly not permission to discard that span or its trace. Already-exported spans are never updated retrospectively and workers emit no additional spans, so a one-shot operation may only ever appear as pending. The request sends the span name unless include_span_name is false, the span kind and status code, the scope name and version, and the values of explicitly allowed resource and span attributes; unlisted attributes, URLs, query text, status messages, event names and payloads, links, IDs, timestamps and raw durations are not sent, but URLs and queries would go out if an operator added their attribute keys to an allow-list. Only scalar values are accepted, individual string fields cap at 512 bytes, max_state_bytes bounds the serialized state excluding the fixed question definitions, and each allow-list holds at most 64 keys, with oversized or unsupported metadata marked skipped without an API request. The jevtraces attribute namespace is reserved and existing attributes in it are replaced so stale scores are not forwarded. Building requires Go 1.26.0 or newer and Collector Builder v0.161.0, and the Prometheus names come from the example's internal exporter, which omits the _total suffix. Our README copy is truncated at the end of the cache-identity section, so anything beyond it, including the adaptive-sampling policy details kept in a separate document, is not documented here. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
It adds attributes. The processor retains every span regardless of the probabilities it returns, it does not buffer traces, change sampling flags, rewrite IDs, sample spans, or perform whole-trace retention, and the README says this version provides no volume reduction while annotations add storage and indexing volume. The value is that the scores become available to a sampling decision you make, which is what the separate opt-in adaptive-sampling experiment is for.
Not from this processor. That is the separate experimental configuration, and it is opt-in and explicitly experimental with documented policy, clustering and late-span limits. In that experiment the sampled branch retains protected or uncertain traces and keeps a 10% baseline of traces whose received spans all have low operation scores, while a full-input branch allows comparison. In the example both branches export to debug, so you configure backend exporters yourself.
The span name unless you set include_span_name to false, the span kind and status code, the scope name and version, and the values of attributes you explicitly allow-list. Everything else is withheld: URLs, query text, status messages, event names and payloads, links, IDs, trace state, timestamps and raw durations. The catch is that URLs and queries are only withheld because you did not list them, so add keys deliberately. The README recommends normalized names and route templates, and redacting upstream, since names and allowed values can carry sensitive data.
Because annotations are not retroactive. On a cache miss the span is forwarded immediately carrying the pending state while background work is queued, and once a span has been exported it is never updated. Workers do not emit additional spans either, so an operation that occurs exactly once may only ever appear as pending and never acquire the three probability attributes, which are present only in the scored state.
An Error status, a duration at or above slow_span_threshold, an exact protected_operation name, or missing start times and reversed timestamps mark a span protected or invalid_timing. Local protection outranks a cached model assessment and bypasses inference.
Run python3 scripts/smoke-traces.py. It starts a temporary local Jev stub and Collector, sends OTLP traces, checks cached annotations, protected spans and metric passthrough, then stops both processes.
Counters and a latency histogram such as jevtraces_spans_processed, spans_annotated, spans_protected, inference_requests, cache_hits, queue_rejected and inference_duration. The example serves them at localhost:8888, and the example's exporter omits the _total suffix.
More Jev resources like this
5GitHub stars
Experimental OpenTelemetry Collector processor that asks Jev about metric metadata and applies explicit keep or drop policy, starting in annotate mode.
Jev Integrations & Adapters#community#awesomejev#catalog-import
Communityishantanu/jevmetricsGo
ishantanu/jevmetricsGo69GitHub stars
Provider-neutral TypeScript runtime for System One decisions: write choice, noul, and score code once, then run it on TypeSafe Jev, local Reflex, any compatible /v1/systemone endpoint, or a custom provider.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
iamaamir/system-oneTypeScript
iamaamir/system-oneTypeScript25GitHub stars
Agent runtime with a terminal UI and a messaging gateway that keeps memory, self-built skills, session search, scheduling, and subagents across Telegram, Discord, Slack, WhatsApp, Signal, and CLI.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
wundercorp/lokiPython
wundercorp/lokiPython51GitHub stars
GraphRAG layer that runs a 4-phase ingest-to-answer pipeline over Neo4j, Memgraph, AGE or Kuzu using Laya or Jev decisions instead of per-hop LLM calls.
Jev Integrations & Adapters#community#jevbest#catalog-import
23GitHub stars
Memory-maintenance library that checks every stored memory against each new event with Jev yes-or-no votes, then marks stale facts superseded or contradicted instead of editing them.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
chopratejas/invalidatePython
chopratejas/invalidatePython41GitHub stars
Gateway-side admission control judging incoming requests with a typed decision model, layering cheap rules, synchronous judgment, and an async side path that never blocks responses.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
kiwi0719/jev-edgeLua
kiwi0719/jev-edgeLuaFrom the Jev community
Posts from builders shipping with Jev right now.