TroubleShooting Documentation

[turetske]

It was brought up in the debugging at scale session that we don't have troubleshooting documentation or information on how to debug issues at all.

This documentation should include information such as how to get debug information, change the logging level, and where debugging information goes.

Common errors that occur and their solutions.

Common steps to take to see where the issue might be occurring (curl the director, cache, origin, etc.)

How to interpret the web-ui portals for information.

[CannonLock]

I would remove How to interpret the web-ui portals for information.

This is going to be a moving target and the UI shouldn't need separate guide to be interpreted.

If there are things that are confusing lets create another ticket for them and I will rework to address.