Jev log impact scope

Identify which services an incident is affecting

Supply affected instances and services together with monitoring coverage. Distinguish a single-instance issue, one affected service and cross-service impact without inferring scope from severity alone.

log impact scopeLive API
Try an example

Explicit coverage supports isolation.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Read the sanitized incident observations and coverage.

Decision rules and labels
Single instanceOne serviceMultiple servicesReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

The result summarizes supplied observations. It does not discover failing services or establish the cause of an incident.

Missing coverage matters: a log from one worker can coexist with an outage elsewhere. The Review outcome keeps that uncertainty visible.

The linked log-triage project asks about impact scope among several signals. This original demo isolates scope and leaves alerts, thresholds and execution to application policy.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for incident impact scope.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Supply affected instances and services together with monitoring coverage.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Single instance, One service, Multiple services, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Isolated workerSingle instance97.0%
Search serviceOne service89.0%
Two servicesMultiple services91.0%
Only one log feedReview70.0%
Dependency warningReview98.0%
Conflicting checksReview94.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Incident impact scope: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Checking incident summaries before writing a scope statement.
  • Testing how missing monitoring coverage changes an annotation.
  • Identifying summaries that need additional service-health observations.

Outside this demonstration

  • Estimating an unseen blast radius from one error message.
  • Triggering incident severity or paging solely from the model output.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does a high severity log imply broad impact?

No. Severity and scope are separate. A severe failure can affect one instance, and a widespread symptom can appear in low-severity logs.

Why are healthy checks included?

They support claims that impact is limited. Without coverage, the example returns Review rather than assuming the rest of the system is healthy.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.