How We Tested InTrust 9.0

By Cameron Sturdevant  |  Posted 2006-01-23 Print this article Print

One of the first things an IT manager must be clear about when evaluating a log management tool such as Quest Software Inc.'s InTrust 9.0

One of the first things an IT manager must be clear about when evaluating a log management tool such as Quest Software Inc.s InTrust 9.0 is the main business purpose for the product. Because so many IT managers are struggling to get their hands around regulatory compliance, we spent most of our time testing InTrust 9.0 to see how well it could track events for an outside audit.

Click here to read eWEEK Labs review of InTrust 9.0.
The trick to effectively using InTrust 9.0—and pretty much every other event-log management tool—is learning what data can be collected and how to turn that data into effective reports. eWEEK Labs spent a great deal of test time learning what information InTrust 9.0 could gather, including Linux account creation and deletion, as well as changes to group memberships. After collecting the data, we worked with InTrust to turn it into informative reports.

After using InTrust in our labs for a couple of weeks, it became clear that the built-in reports were more than sufficient to give us the insight we needed to successfully monitor our test machines. We struggled a bit when creating some custom reports, but, at the end of the day, the reports worked quite well for us.

This test scenario also showed the importance of testing log management tools against the actual systems IT managers will monitor in their production networks.

During our testing, we turned up several special cases where we needed to make adjustments to either the way we deployed monitoring agents or the frequency with which we generated reports.

We installed InTrust agents on all the systems in our testbed to thoroughly evaluate the usability of real-time reporting. When we made changes to user groups and other senders, we were immediately alerted.

Check out eWEEK.coms for the latest news, views and analysis on servers, switches and networking protocols for the enterprise and small businesses.
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel