ShieldGate Docs

Config & ops

Analytics

Traffic overview, security events, and live dashboard metrics.

Goal

Use analytics to validate WAF and rate-limit changes.

Prerequisites

  • analytics.read.
  • Proxy emitting metrics (always-on middleware; Redis or HTTP batch ingest).

Steps

  1. Open Overview → Analytics.
  2. Inspect overview, timeseries, and top paths/IPs.
  3. Open Security events after Detect/Enforce changes.
  4. Use live views (SignalR hub) when troubleshooting active incidents.

What the Proxy records

Counters for allowed/blocked, latency, bandwidth, status, path, IP, attack type—plus sampled security events on deny paths. Analytics failures fail open and never break requests.

Verify

  • Generate known traffic; dashboards move within a minute.
  • Blocked lab requests appear as security events.