By John Lim, CTO
When it comes to tech, most of us don’t have the need to look too deep into the systems we’re using. We go about the day using the system in place and don’t have to think twice about what’s going on under the surface.
But when something goes wrong and all of a sudden a server goes out or a system crashes, we hope that there are some precautions and hidden tricks up the sleeves of our IT company.
Enter: logs.
Device logs, systems logs, event logs, and error logs to name a few.
When setting up a system, TekTegrity implements log monitoring systems and that begin to track action history. A list of events begins to build and compound as the system is used. These records not only establish a history of normal patterns but also provide a valuable resource in both the troubleshooting process and in the prevention of future issues.
For example, a server goes out and your system is down. The technician can begin by searching through the logs for any seemingly significant event that may have caused this issue. Perhaps on the switch log, there’s a record of the server being disconnected at a specific time that correlates with the onset of the problem. This immediate clue can provide insight into possible causes and speed the troubleshooting process. Logs save time and sanity.
Compiling action history is not only useful in troubleshooting, but also in preventing future problems. For instance, if storage space on a hard drive is filling up, logs can provide an alert that space is running low. If a firewall has a sudden spike in bandwidth, this increased activity is cause for immediate investigation. Through frequent monitoring of these logs, we are able to be more proactive. By establishing tracking systems and ensuring that there is an underlying history in place we can streamline the detective work and protect the functionality of the system. Who would have thought that a bunch of lines that say “this happened at this time on this date” would be so useful!