Security gateway

Troubleshooting captures

When something breaks, capture full requests for a limited time and scope, then purge them.

What it is

An explicit, time-limited session that records request and response bodies for requests matching a filter. Captures download as tar.gz, singly or in bulk with a JSONL index.

Why you want it

Prompts are private by default, which leaves admins blind when a request fails. Captures give targeted evidence without turning on logging for everyone.

A support bot request fails with a 400 error. An administrator turns on a troubleshooting capture limited to the Support team and errors for 30 minutes, and the captured request shows the full system prompt, messages, tools and the provider's error. REQUESTS 200chat · support-bot1.2 s 200embeddings · docs-search0.3 s 400chat · support-bottool call rejected Troubleshooting capture team = Support · errors only 30 min CAPTURED REQUEST system: You are Acme's support assistant. user: Refund order #4417, it arrived broken. tools: lookup_order, issue_refund assistant → issue_refund( amount: "$40.00") provider 400: amount must be a number The whole context in one place. Purge it when you're done.

How it works

  • Default 24 hours, at most a week; include (OR), require (AND) and exclude (NOT) rule groups
  • Credentials and cookies always redacted; bodies optionally encrypted at rest
  • Stored in the database or on disk; retention by age, count or size, plus a purge button
  • Bulk export includes captures.jsonl and an Athena DDL

In the product

Janus Troubleshooting capture screen with demo data
Troubleshooting capture

Who and what to capture, for how long, and how long to keep it.

Actual Janus interface · Demo identities and synthetic usage

See it on your own network.

The Community edition is free for up to 25 people. The 30-day Business trial unlocks every Business feature.