Showing posts with label correlsense. Show all posts
Showing posts with label correlsense. Show all posts

Tuesday, February 10, 2009

Do not Confuse BTM with Traditional Tools!

Even experienced IT professionals can confuse traditional monitoring tools and the newer generation of transaction monitoring tools. In today's market, all of the marketing messages are the same so it is very hard to differentiate between the old and the new. The following provides insight into the difference which needs to be understood before considering the purchase of any monitoring tool.

Disclaimer: There is nothing wrong with traditional tools, they do their job well and all of the vendors that have been listed are good competent vendors. As with any technology, newer generations tend to improve on the old ones. Additionally, BTM has yet to fully mature and vendors of traditional tools are bound to jump to the newer generation at some point.

Traditional Monitoring:

Traditional Tools monitor the performance of each component individually and display all of these metrics on a "single pane of glass".

"End to end" performance monitoring means that you can see the performance of every component in a single centralized console. So for example you see the resource consumption of your servers, the threads that your application is running, the throughput of your network components and the calls to your database all displayed in their own section.

When traditional tools monitor transactions what they do is pick up various segments of transactions throughout the data center without stitching them together into one full transaction flow.

For example: The database monitor picks up all of the SQL statements that it sees and displays them on the central dashboard along with their response times, while the real user monitor picks up all of the requests that are sent out to the datacenter and displays them on the same dashboard along with their response times. Now say that an application slow down occurs and both monitors (including the application server monitor which was not mentioned) are showing erratic response times for various "transactions" – the real user measurements only show that the user is experiencing a problem but cannot show where the problem is within the datacenter – and the silo specific tools do not have the context of the CICS program names, SQL statements, web service calls which are showing erratic performance. The IT professional is stuck with a glut of confusing information on the dashboard that is not connected.

How to identify traditional monitoring tools: Vendors
that provide these tools typically sell them as suites. What they will do is develop or acquire separate server monitoring tools, network monitoring tools, application performance management tools and real user measurement tools - and then offer them bundled as an end to end package. These tools tend to be pricey and hard to implement not to mention their limited visibility due to the lack of correlation between tiers. On the up side they can provide more thorough metrics within the tier – that is why the new generation seeks to complement the traditional tools as opposed to replacing them.

Some examples of vendors: Opnet, Compuware, Quest, NetScout, CA, IBM

The New Generation of Monitoring Tools:

The new tools connect every single process within the datacenter to a click of a user within the application that initiated all of the activity within the datacenter.

"End to End" means that the user request and the related activity within the proxy, web server, app server, database server, MQ and mainframe are all connected as a single transaction instance.

The resource consumption at each component can still be seen – but at the granularity of a single transaction segment.

For Example: If service levels are starting to degrade, this new generation of tools not only pick up the performance degradation that the user is experiencing but they also immediately know what is causing the specific degradation down the line.

Some examples of vendors: Optier, Correlsense, HP Transaction Vision, SeaNet

Sunday, October 19, 2008

Definition of Business Transaction Management

Now, since this is a relatively new term that lacks a formal definition, we here at the BTM blog will attempt the audacious task of defining Business Transaction Management. Let us begin by taking a look at how Business Transaction Management has been defined across the industry.

BTM in Wikipedia

The first Wikipedia article that was written about Business Transaction Management was deleted a year ago because it was A " Non-notable neologism about a freshly coined (''new category'') three letter acronym". The current Wikipedia article is just a seed and needs some work.
Wikipedia Affiliate Button

BTM according to IDC Research

In their comprehensive technological assessment "Business Transaction Management: Another Step in the Evolution of IT Management", Dan Yachin, the author of the paper, began the definition with a note on Bristol Technology and how their acquisition demonstrated the interest of major IT management vendors and then continued by stating that "BTM can be considered as bridging two major trends in the IT management space". The two trends he lists are:

  1. "The need for more granular application management…"
  2. The need to manage from a business prospective

Another statement from IDC, that provides a more concise definition, to be noted is - "BTM is aimed at detecting and resolving problems at the granular level of interactions between IT elements that form a business transaction (e.g., online stock trade, travel booking)."

BTM according to EMA research

In their latest White Paper titled "Business Transaction Management for SOA Environments", EMA – not unlike IDC – provides a vague definition of BTM. EMA states that their IT maturity models show that "…most enterprises still struggle with monitoring applications and services at the transaction level". They also state that "Many business critical services remain a "black box" in terms of understanding transaction performance and failures". In the line after this quote they state that EMA calls this discipline Business Performance Management.

Other EMA White Papers do not provide much of a definition other than; Business Transaction Management means to plan, monitor and control IT processes from a business prospective.

Business Transaction Tracing (BTM synonym) according to Gartner research

In their white paper titled “The Four Dimensions of Application Performance Monitoring” Gartner labels “Business Transaction Flow Tracing” as one of the four “functionalities have emerged to circumvent some of the APM difficulties associated with modular, distributed, interdependent and context-sensitive applications”.

Will Cappelli leads off the definition by stating how when a problem with the availability of an application pops up, monitoring component-level health is less helpful when it comes to determining the root cause, and “Used in conjunction with an application dependency map, a report showing a cluster of component latency degradations could be used to guess at the source of the performance issue. More often than not, an insufficient number of components are instrumented and/or the topology plus performance degradation is too ambiguous to be helpful.”

Mr. Cappelli then continues to state that Business Transaction Tracing fills the Application Performance Management void that simply monitoring component-level health leaves by following these steps:

·         “First, members of the operations or application support team would be required to instrument path-critical components in the stack and infrastructure, supporting the application being monitored with what amount to sensors.”

·         “Second, they must define, package and mark a sequence of interactions at an application's interface — defined as a "business transaction." An instance is executed and the mark is passed through the application's components as it is exercised and sensed, and progress of its path is reported on in real time or near real time. This makes it possible to trace a performance problem's root cause, particularly when used in conjunction with health statistics gathered by the third type of APM functionality.”

·         “Finally, it would, once again, be prohibitive to place sensors on more than a few components. Thus, having a good application dependency map is critical to the effective deployment of this type of APM functionality.”

Once again, this is not a clear cut definition of Business Transaction Management, but another thing to think about when attempting to provide a definition.

BTM according to Vendors

Although most Vendors tend to list the benefits of Business Transaction Management as opposed to defining it for their clients, the definition may be inferred from these benefits.

BMC – Ziff Davis Media Survey

In their White Paper "Transaction Management – the Next Step in Service Oriented IT", an understanding of what Transaction Management needs to be was obtained through a survey of 1,190 technology decision makers. They concluded that Transaction Management systems need to – "…look across components in a sophisticated technology stack to determine how the pieces are involved in and contribute to complex business transactions".

Optier – E-Commerce Times Article

Optier does not really define BTM on their web site; rather they use the term as though it speaks for itself (valid point). Though their CTO, Amir Alon, wrote an article that gives a quasi definition, which essentially states that BTM provides transaction visibility, detects and resolves issues rapidly and assures that technology outages are connected to a business context. He also writes that BTM provides a real time record of all transactions which are to be mapped to the underlying infrastructure.

HP

HP has a White Paper titled "What Happened to My Transaction" in which they define BTM by quoting IDC and giving their own explanations: "Business is conducted at the level of individual transactions—and IT needs visibility into and control over these transactions and their impact on business outcomes in order to properly support the larger organization it serves."…"BTM helps IT understand how the components in the IT infrastructure relate to the business transactions they support."

Correlsense

Correlsense begins its definition by providing a chart that shows the Business Transaction Management approach in relation to traditional monitoring and continues by stating: "…Transaction Management tools view everything from an application perspective. In the world of transaction management, an application is considered as a collection of transactions and events, each triggering actions on the infrastructure. The goal is to track every transaction end to end and correlate to the information collected from the infrastructure."

Help Create a Definition for Business Transaction Management

Defining this term should not be a "one Blog job", help give this term a formal definition by leaving a comment. We at the Business Transaction Management blog will propose a definition in a future post.