Classifier Health

Classifier cascade, breaker, fail-safe and latency.

Classifier cascade, breaker, fail-safe and latency.

This screen belongs to the Secure deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Classifier Health → choose window → Refresh.
  2. Check source, generated_at, requests and fail-safe rate.
  3. Correlate timeline with top policies and tier latency.
  4. Give the operator the period and request IDs, then repeat synthetic inspection after recovery.

Every control and its meaning

Control / parameterValues, units and effect
Window / Tier 0–3Window selects history; tier indicates cascade depth. Window selection does not change runtime max tier.
Fail-safe timeline / Top policiesWhen/which policies encountered inspector failure. Fail-safe is not simply a detected threat.
Latency p50/p75/p95/p99Tier latency percentiles in ms; slow_count uses the configured threshold. Observational, not a timeout control.
Circuit breakerClosed/open/half-open is inspector breaker state. Operator configures thresholds/cooldown.

Verify the result

Successful inspection should produce an actual verdict and expected tier. A green breaker is not an integration test.

Errors, disabling and reverting changes

Unavailable report PostgreSQL does not prove classification stopped. Restore prior operator parameters to revert and test a protected call.

Classifier health: actual report · actual staging
Classifier health: actual report · actual staging
2026-10-15 · Working staging interface, unretouched original pixels. Metrics and warnings belong to a test stand and are not a benchmark. Protection was not disabled; batch form shown before submission.
  1. 6 ч
  2. 24 ч
  3. 48 ч
  4. 7 д
  5. Обновить

Detailed security settings · Traffic analysis · FAQ · All application sections