4 “No Fail” Best Practices for Enhanced Application Diagnostics
November 11, 2011
Charley Rich

Many things can, and will, go wrong during the development of an enterprise application. These issues underscore the importance of using test cycles to detect potential performance-robbing defects before the application is moved into production. To combat the myriad problems waiting to plague the application lifecycle, developers need to equip themselves with items they can employ to troubleshoot such issues when they arise.

User Acceptance Testing, in theory, is used to utilize the end-user to test the application before it moves on to other stages of the application lifecycle and give their approval, but rarely does an application become exposed to the variety of situations it will experience in production.

Too often, the underlying middleware message layer is often regarded as a “black-box” during this process. And that’s ok, as long as there are no problems. Testers know how long a message or transaction took to transit that layer or the architecture. But if that took too long or was routed to the wrong location, they don’t know why.

This lack of visibility can make it rather difficult to reproduce and then resolve a production problem. Lack of visibility also forces development to manually contact the middleware administrator in shared services and request information about message contents. Certainly, this is an interruption to the middleware administrator and a very inefficient, costly and error-prone process.

As more firms move to a DevOps culture, cooperation in usage of tools across development and production is important. At the very least it gets the two teams speaking the same language, which means time spent in trying to reproduce a problem that is adequately specified can be reduced. At best it can help the joint teams rapidly identify a problem, reproduce it in the test cycle and then develop a resolution.

The following “no fail” best practices are designed for Independent Software Vendors to enforce consistent guidelines for application, middleware and transaction diagnostics in order to rapidly identify, trace, replicate and resolve issues that occur during production.

1. Visibility

Ensure that you have the most detailed visibility into the performance of your applications as possible. Synthetic transactions are not enough. Detailed diagnostics down to the message contents or method level are essential -- you need to see more than just what is being passed into and out of an application as if it were a “black box.”

Instead, ensure you have full visibility of each message and transaction. Use diagnostics at each juncture to proactively provide detailed information when an application’s behavior veers from the expected.

2. Traceability

Knowing when a metric has been breached is an important first step in optimizing application performance during test cycles. Knowing exactly what caused the problem is more challenging. Traditional testing methodologies treat the symptoms looking outside-in, not the root cause which often requires an inside-out viewpoint. Make certain that you can trace the message path in its entirety to uncover the precise moment and environment when the problem occurred.

3. Reproducibility

The key to any successful testing program is the ability to reproduce an error. It is the confirmation of a problem solved, and guarantees that the same problem will never need to be resolved twice.

4. Actionability

Once a problem and its trigger have been identified, and after it has been successfully isolated through replication, developers have all of the tools they need to confidently act on the information and permanently resolve application performance problems. This means they need the tools to -- on their own -- create new messages, re-route them and test their problem resolution.

The ability to identify problems sooner in the application lifecycle will yield better results when the need to remediate issues arises in production. This can only happen when development and production are working together as a team, utilizing a common tool set and when development is enabled with full visibility. This approach will save time and money, as well as helping organizations meet SLAs and drive ROI from these applications.

About Charley Rich

Charley Rich, Vice President of Product Management and Marketing at Nastel, is a software product management professional who brings over 20 years of experience working with large-scale customers to meet their application and systems management requirements. Earlier in his career he held positions in Worldwide Product Management at IBM, as Director of Product Management at EMC/SMARTS, and Vice President of Field Marketing for eCommerce firm InterWorld. Charley is a sought after speaker and a published author with a patent in the application management field.

Related Links:

www.nastel.com

The Latest

April 17, 2015

Unscheduled downtime has a dramatic financial impact on businesses of all sizes, yet most businesses don't have adequate recovery technologies in place, according to an independent national survey of IT professionals conducted by Dimensional Research and commissioned by Axcient ...

April 16, 2015

True Application Performance Monitoring cross-cuts many IT tiers: network infrastructure, physical and virtual infrastructure, databases, mobile devices, etc. An ideal Application Performance Monitoring solution provides visibility over any infrastructure, for any app and any audience ...

April 15, 2015

Everyone presumably loves a good mystery. And in fact the questions “What is a CMDB?” and “What is its relevance in the age of (cloud) (agile) (fill-in-the-blank)?” often provoke such conflicted industry responses that they do suggest the presence of some mystery underfoot. But we didn’t set out to write a mystery novel per se. Instead, CMDB Systems: Making Change Work in the Age of Cloud and Agile is designed to serve as both a guide and a chronicle of real-world experiences — honoring the mystery by sharing different points of view, while trying to help our readers optimize their CMDB planning for what is increasingly becoming a positive and successful initiative ...

April 14, 2015

Part 2 of this series identifies some of the hang ups of adopting Fault Domain Isolation (FDI), as well as best practices ...

April 13, 2015

For many organizations, the task of quickly identifying root cause has become paramount to meeting Service Level Agreements (SLAs) and preventing customer churn. Yet, according to the Emulex Visibility Study, 79 percent of organizations have had events attributed to the wrong IT group, adding confusion and delays to the resolution of these issues.This two-part series will explain a more fact-based, packet-analysis driven approach to Fault Domain Isolation (FDI), which is helping organizations troubleshoot and resolve network and application performance incidents ...

April 10, 2015

Speedier network pipes that carry more information faster than ever before can be a windfall for enterprises looking to derive more business value from their underlying infrastructure. But there's a nefarious lining in there – when things speed up, they can get harder to manage. Packets carrying crucial application information and content whizzing by in a blur can pose real visibility challenges IT pros haven't encountered before. Network and application performance management is undergoing sweeping changes thanks to not only faster networks but also migration to the cloud. And the implication for application and performance management are huge. For the Network Instruments State of the Network Global Study 2015, we recently surveyed more than 300 CIOs, IT directors and network engineers, to get their take on how the migration to higher capacity and faster networks has affected their day-to-day duties monitoring application performance. What we found is ...

April 09, 2015

Business networks today seemingly have more intense loads placed on them every day. And nowhere is this more evident this time of year than the annual March Madness NCAA basketball tournament. What was once a small-screen, low-resolution video is now available in full HD, potentially taxing network resources. With employees from all over the organization wanting to stream the games online, organizations run the risk of their business-critical applications suffering in performance. To determine corporate attitudes toward the situation, Riverbed surveyed employees about who in their organization will be streaming games and what their policies are toward the situation. The survey uncovered that employees of different age and seniority level had varied attitudes about this use of company resources ...

April 08, 2015

Cultural transformation and eliminating IT silos may sound like an impossible dream — and indeed, perhaps “eliminating” is too strong a word. But the reality is that IT organizations must change toward a more responsive, business-aligned culture, as well as toward a more service-aware (versus siloed) way of working. So how do you begin? ...

April 07, 2015

As the holidays are often the most profitable time of the year for retailers, Clustrix conducted the 2014 Holiday Shopping Season Trends Survey in January 2015 to identify the emerging consumer trends specific to the holiday season. Here’s what mattered to online shoppers ...

April 06, 2015

By now, we all know the importance of superior application performance. Applications that are fast, reliable and easy to use delight end-users and lead to greater adoption. But for mainframe applications, performance takes on a whole new level of importance. For these applications, even a few added milliseconds in application load or transaction time can lead to application abandonment and lost revenues ...

Share this