Error metrics | fortrabbit docs

The errors group of the metrics tab counts the responses with an error status code: not found, unhandled errors, PHP busy and PHP too slow.

Error counts

Each error metric counts the responses with that status code, for PHP and static files alike. A sample holds the responses since the sample before, a bar is the sum of its samples. In the box, the bare number is the count for the whole time frame, max and min are the busiest and the quietest hour or day.

Links below each chart open the access log filtered to that status code, for 500 and 504 also the PHP error log.

Metric	Status	Usual cause	Read more
404 errors	Not found	Missing file, broken link, crawler	404 errors
500 errors	Internal server error	Unhandled error in the code	500 errors
503 errors	Service unavailable	All PHP processes busy, or PHP down	503 errors
504 errors	Gateway timeout	PHP took longer than the time limit	504 errors

Labels and lines

The values each metric shows in one bar, for the time frame, and on the summary page, and the lines drawn across the chart:

Metric	One bar	Time frame	Summary	Lines
Web storage	max, last, min, avg	last, max, min, avg	last	Plan sizes
Traffic	sum	sum, max	sum	–
Static requests	sum	sum, max, min	sum	–
MySQL storage	max, last, min, avg	last, max, min, avg	last	Plan sizes
PHP response time	max, avg / med / 99ile	max, avg / med / 99ile	avg	Fast 150 ms, Good 350 ms, Slow 700 ms
PHP requests	sum	sum, max, min	sum	–
PHP memory	max, typical peak	max, typical peak	max	Plan sizes
PHP opcache	max	last, max	last	Nearly full 90%
OOM kills	sum	sum	sum	–
Jobs memory	max, typical peak	max, typical peak	max	Plan sizes
Jobs OOM kills	sum	sum	sum	–
404 errors	sum	sum, max, min	sum	–
500 errors	sum	sum, max, min	sum	–
503 errors	sum	sum, max, min	sum	–
504 errors	sum	sum, max, min	sum	–

# Error counts

# Labels and lines

Error counts

Labels and lines