Runbook

High 4xx Errors on Traffic Server

Back to Runbooks

Overview

This incident type occurs when the number of 4xx errors on Traffic Server is at an anomalous level, higher than usual. It could be an indicator of an issue with the server or an increase in traffic that is causing errors. It requires investigation and resolution to ensure the server is functioning correctly and not impacting users.

Parameters

Debug

Check if the affected pod is running

Check the logs of the pod for any relevant error messages

Check the status of the deployment

Check the status of the service

Check the logs of the Traffic Server container

Check the number of 4xx errors in the last 15 minutes

Check the configuration file for Traffic Server

Repair

Set the namespace where Traffic Server is deployed

Set the name of the Traffic Server pod

Set the name of the Traffic Server container

Set the path to the Traffic Server log file

Get the logs from the Traffic Server pod and container

Search for 4xx errors in the log file

Check the exit code of the grep command to see if any 4xx errors were found

Increase the server capacity to handle the increased traffic, if applicable.

Optimize the Traffic Server configuration to improve performance and reduce the number of 4xx errors.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.