How to Set Up TeamQuest Monitor to Monitor a Log File
IT professionals need to manage their capacity not only in the long term, but down to the second with triggered alarms and alerts.
For better or worse, the way in which IT capacity management is practiced today is often reactive. By this we mean that as a rule, a majority of companies learn about capacity issues only after the fact — generally, when a customer has alerted IT staff to a problem. Beyond merely being bad for client relations, it isn’t cost-effective for IT departments, who must spend time fighting fires rather than cultivating value-generating initiatives.
The first step to defeating this reactive cycle is to learn about problems the moment that they occur. By setting up automatic email alerts that are triggered at predetermined performance or capacity thresholds, IT professionals can start dealing with potential problem long before they create outages or bottlenecks. If enough time has passed for customers to encounter an issue or for SLAs to be broken, you’ve missed your opportunity. Conversely, any opportunity seized is direct value created for the business.
Here’s how to set up email alerts that will have you dealing proactively with IT capacity issues using the Monitor component of TeamQuest software.
Checking the Logs
TeamQuest Monitor is a shared component that links all of TeamQuest’s software, and it’s typically downloaded onto computers where infrastructure-critical applications can be analyzed. Monitor is useful here because it allows for the efficient use of software in large installations, meaning that configuration policies can span hundreds of instances of TeamQuest software across your IT environment.
You can direct Monitor to identify and report when certain lines of code appear in a system log. For instance, if a system node fails, the software will flag the log text that reports this error and send you an email with the corresponding log content, not only indicating that an issue has arisen, but pinpointing the exact source. Of course, a node failure is only one such condition that you may want to report; sudden changes in IT capacity, response times, or general system health are a few among many issues that you can set as triggers.
Ultimately, setting up such an alert in Monitor is as simple as creating a log agent instance and plugging in some basic commands. Once you have the basics down, it’s easy to tweak the line code for your email server, operating system, or any other desired factor. You can also adjust the email content to include as much or as little information as necessary, as well as automatically forward such alerts to any number of recipients.
Jumping on Alerts
The chief advantage of having such a capacity management capability is that it pushes IT into a proactive, problem-solving role. It’s well known that with the complexity of today’s IT infrastructures, capacity management is getting harder to perform. This makes it essential not only that IT departments stay well ahead of developing problems, but ensure that their capacity management tools grant them the power to do so — that is to say, they can be tailored for their specific IT systems and subsystems.
At the end of the day, the success of IT teams over time will rely on their ability to handle continued disruption and fragmentation of the tech market. Automating simple things like the discovery and communication of problems can go a long way towards helping IT members to stay focused on future efforts. In other words, value is never created by fighting fires reactively; it merely sustains a rocky status quo. To invert that dynamic (or at least solving one piece of the puzzle), IT workers must determine which problems deserve the most attention.