Today is: 05/18/2012

Home > Resources > Best Practices for Application Transaction Monitoring

Best Practices for Application Transaction Monitoring

When implementing an application transaction monitoring solution, it is critical to follow industry best practices. These best practices should be followed throughout the entire process, including testing, data analysis, documentation, implementation and change management.

Developing a Testing Plan for Application Transaction Monitoring

While often overlooked, developing a specific testing plan for application transaction monitoring is an important part of application transaction monitoring best practices. The testing matrix needs to be completely spelled out down to the granular level before any testing commences. The test plan for application transaction monitoring will define the expectations of the system to everyone involved in the process. By developing specific expectations prior to data analysis in a collective process, Monday-morning-quarterbacking will be avoided. Additionally, developing a specific testing plan will provide information that can be used to develop documentation for change management moving forward.

The testing plan should include testing configuration, testing process, data to be collected and result review. The ultimate goal of application transaction monitoring testing is to get an accurate, unbiased view of a system's performance. Based on the data collected, planned changes or adjustments could include coding and development changes, capacity planning and overall system and server architecture.

It is equally important that the testing plan include a long-enough time span that will provide a complete view of potential traffic level issues, bottlenecks and lag points. The overall time testing decision will vary depending on the ultimate goals of the system and the company.

Application Transaction Monitoring Testing Review and System Implementation

Once application transaction monitoring testing is complete, the group should meet to collectively review the data collected and propose any potential changes that may be required. All of these discussions should be well documented. If there are major changes that are required, once implemented, another round of testing is wise to ensure the changes provided the expected outcome.

Once the tested changes are proved successful, all settings, development adjustments and the acceptable level of ongoing results are determined, all the information should be well documented. It is also smart to develop a specific change management plan in case future changes are required.