If you’re someone like me who spends most of their day working on the command line interface (CLI) rather than the graphical user interface (GUI), you understand how easy it can be to overlook the root cause of an incident because you missed an error, a warning, and even important IP addresses, particularly when scrolling through debugging logs, syslog messages, interface lists, routing tables, and so forth. I found myself in that type of situation so often, especially during troubleshooting calls, that I realized I needed to take action. This led me to the customization of iTerm2…