Web Stats: RPS and Error Rate

Reading Time: < 1 minute

When to use

Web Stats is used for operational monitoring of HTTP traffic and early detection of anomalies in the web circuit.

What the page shows

  • Current request stream (RPS/RPM).
  • Distribution by response codes: 2xx / 3xx / 4xx / 5xx.
  • Error rate as a share of 4xx+5xx from the total flow.
  • Forensic PDF report on error IP for 7 days for incident analysis.
  • Top URLs by number and response time.

Steps

  1. Open the server and go to Web Stats.
  2. Make sure the channel is connected and the data is being updated.
  3. Monitor the dynamics of RPS and error rate in real time.
  4. Check top URLs if 4xx/5xx or latency are increasing.

What to check

  • After changes in the web service, the error rate returns to the baseline level.
  • Request peaks have a clear origin (release, campaign, bot traffic).
  • For suspicious activity, there is a correlation with incidents and audit.

Forensic PDF report on error IP

If the error rate increases in Web Stats and you need an evidence base for action, generate a 7-day forensic PDF report. Detailed step-by-step script: Forensic PDF report on error IP (7 days).

Operational case

The combination of RPS growth and a 4xx/5xx spike allows for early detection of pick-and-scan attempts before an incident escalates.

Scroll to Top