Agents & developers

Semantic log filter

Find payment failures even when the logs use different wording.

For developers investigating incidents

Jev AI playground

Checking availability…

Text

285 / 50,000

Try different inputs · Semantic log filter

Load an input to edit it. Tokens are used only when you run it.

Normal input

Match a payment failure described as a rejected capture.

Ambiguous input

Without the operation type, this may be a payment or a different transfer.

Missing information

An unexplained code does not establish a payment failure.

Different wording

Recognize a declined authorization as relevant without relying on the word timeout.

Questions2

Yes / NoDoes the record indicate an event covered by the stated filter, even if the words payment or failed do not appear?⌄

Question

choiceClassify the event shown in this record. Use unclear when a code or truncated message cannot be interpreted from the supplied context.⌄

Question

Answer options

Advanced: edit JSON

Edit or paste a question configuration.

[
  {
    "id": "keep",
    "type": "noul",
    "instructions": "Does the record indicate an event covered by the stated filter, even if the words payment or failed do not appear?",
    "options": []
  },
  {
    "id": "category",
    "type": "choice",
    "instructions": "Classify the event shown in this record. Use unclear when a code or truncated message cannot be interpreted from the supplied context.",
    "options": [
      {
        "label": "payment_failure",
        "description": "A charge, capture, or settlement attempt did not complete successfully."
      },
      {
        "label": "payment_success",
        "description": "A payment completed successfully."
      },
      {
        "label": "authentication",
        "description": "Login, session, or identity verification event."
      },
      {
        "label": "other",
        "description": "A different event with a clear meaning."
      },
      {
        "label": "unclear",
        "description": "Too little context to determine the kind of event."
      }
    ]
  }
]

Runs use input tokens and are saved to your account.

Results

Your answers will appear here.

Add your text and questions, then run Jev.

Probabilities express model confidence, not a guarantee of correctness.

Set up this template

Find logs describing the same kind of event, even when they use different words.

What to provide

A plain-language filter and a log line; expand ambiguous codes when the meaning is known.

Write the event meaning you want to keep.
Supply one complete log line, with context if an identifier is ambiguous.
Reuse the same questions across rows in Batch.

Outputs and rules

keep · Yes / No

Whether the line matches the semantic filter.

Does the record indicate an event covered by the stated filter, even if the words payment or failed do not appear?

category · choice

The event type used to group matching and excluded records.

Classify the event shown in this record. Use unclear when a code or truncated message cannot be interpreted from the supplied context.

payment_failure: A charge, capture, or settlement attempt did not complete successfully.
payment_success: A payment completed successfully.
authentication: Login, session, or identity verification event.
other: A different event with a clear meaning.
unclear: Too little context to determine the kind of event.

Try different inputs

Normal input

Match a payment failure described as a rejected capture.

Filter: Keep log lines indicating an unsuccessful attempt to charge, capture, or settle a customer payment, including rejection and timeout events. Exclude successful payments and unrelated login events. Log: checkout.capture rejected: processor timeout; order=ord_82; retry scheduled.

Ambiguous input

Without the operation type, this may be a payment or a different transfer.

Filter: Keep log lines indicating an unsuccessful attempt to charge, capture, or settle a customer payment, including rejection and timeout events. Exclude successful payments and unrelated login events. Log: funds movement pending; upstream unavailable; operation=op_41.

Missing information

An unexplained code does not establish a payment failure.

Filter: Keep log lines indicating an unsuccessful attempt to charge, capture, or settle a customer payment, including rejection and timeout events. Exclude successful payments and unrelated login events. Log: operation=op_41; code=E17.

Different wording

Recognize a declined authorization as relevant without relying on the word timeout.

Filter: Keep log lines indicating an unsuccessful attempt to charge, capture, or settle a customer payment, including rejection and timeout events. Exclude successful payments and unrelated login events. Log: issuer declined authorization for order=ord_91; no charge created.

Use the result

Inspect matching records with adjacent events. Use categories to narrow investigation, and keep unclear rows available for manual review.

Limits to keep in mind

A match points to a relevant event, not necessarily its cause. Check the original line and nearby logs when investigating.