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

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

Share this

The Latest

July 22, 2016

More than $1 trillion in IT spending will be directly or indirectly affected by the shift to cloud during the next five years, according to Gartner, Inc. This will make cloud computing one of the most disruptive forces of IT spending since the early days of the digital age ...

July 21, 2016

One of the most common problems network monitoring tools are employed to solve are problems with bandwidth. Availability is critical for IT departments of all sizes, and slow bandwidth creates productivity problems and even outages that have a real effect on businesses. Identifying the problems behind bandwidth drains can be difficult, so to help, I’ve put together a list of the five most common causes of sudden traffic spikes ...

July 20, 2016

In 2014 Gartner predicted that "75 percent of IT organizations will be bi-modal in some way by 2017." We are in the midst of this two-speed IT approach that organizations are adopting at an increasing rate to stay relevant for their customers. Speed 1 is the traditional IT that is being managed by the IT Operations persona and Speed 2 is the agile IT where within the organization especially the Developer persona and the Line of Business Persona are involved to get the most out of the digital innovations that flood our daily lives. One thing that these personas have in common is that they have a need for monitoring. In this blog I will focus on the needs of the various personas ...

July 19, 2016

While shoppers enjoy the bargains on Prime Day – a 24-hour sale on Amazon – few may realize that the success of such massive events hinges on network and application performance ...

July 18, 2016

I am constantly hearing the common theme that organizations want to make their IT-dependent employees and customers top priority in order to better support business growth. However, what I then find contradictory is while the desire is there, it's a significant challenge for organizations to actually achieve this. Here are four common barriers to business transformation initiatives – and suggested steps enterprises can take to overcome them ...

July 15, 2016

You already see the potential of adopting an Internet of Things model into your enterprise, but are you doing it in the best way? The following are four questions you and your team should be answering to determine how to find the right opportunity in the IoT space for your business ...

July 14, 2016

Cloud is no longer a new topic for IT, or for IT service management (ITSM). But its impact on how ITSM teams work, as well as on how IT works overall, has probably never been greater. Leveraging EMA research on the future of ITSM and on digital and IT transformation, this blog looks at data relevant to the impact of cloud on ITSM teams and addresses the following questions ...

July 13, 2016

The correct response within the expected time – those are the two main benefits your data center provides. If you don't provide those benefits your business loses customers. It will filter down to you through sales, then marketing, then the CIO then – what are you going to do now?

July 12, 2016

By participating in identifying and implementing tools that fill employees needs while providing quality experiences, IT departments can support employee productivity rather than hinder it. At the same time, they’ll be able to more easily and securely govern the plethora of consumer applications inundating the enterprise. Here are examples of software characteristics and user experience best practices that can provide workers with efficient workflows yet also meet the functionality requirements of IT administrators ...

July 11, 2016

APM tools must evolve to focus on the problems that users and customers are seeing from their perspective and give insight as to how to continuously diagnose and correct the digital user experience for them ...