Shulou(Shulou.com)05/31 Report--

This article analyzes "how to understand the priority of the APM model in Gartner". The content is detailed and easy to understand. Friends who are interested in "how to understand the priority of the APM model in Gartner" can follow the editor's train of thought to read it in depth. I hope it will be helpful to you after reading. Let's follow the editor to learn more about how to understand the priorities of the APM model in Gartner.

Some time ago, I combed the knowledge points of APM and combed the basic concepts of APM. For this thing put forward by Gartner, there are still a lot of things that I do not understand in the specific application landing scene. Many people intuitively understand that APM is a monitoring, or just a monitoring alarm. Even when I first came into contact with this concept, I thought so.

However, with the continuous carding of this part of things, it is found that the concept covers a wide range of areas, and the early definition is also very vague and not so clear, resulting in most of the so-called APM products on the market still stay at the monitoring level, rarely go deep into specific applications to do definition, analysis and in-depth data collection and comprehensive analysis.

The business needs to have matching automatic alarm, which gives birth to the application performance management. APM has many advantages if it is designed and implemented correctly. It is very important to manage whether the application is running properly or not, and whether the performance is running ok or not.

Gartner defines five dimensions of application performance management. This article describes the understanding and understanding of each dimension by the Automation Club, which is a summary of our experience in dealing with various situations in order to better support the business over the past 6 years.

It is important to understand that the dimensions and priorities of applications deployed by different developers are different. When you implement it, I suggest that some priority areas should be given priority. It is the "primary concern" mentioned below, and the low-priority dimension is called "secondary concern".

Where do I start to say APM? Take a look at APM's conceptual framework to help you prioritize your next step.

End-user experience (primary concern)

Real-time application monitoring is a kind of top-down monitoring, and it is also the most basic and effective way to monitor the end-user experience. In our experience, real-time user monitoring technology provides at least 80% visible APM value to the business and provides the basis for performance trends and predictive analysis.

To achieve top-down monitoring, there are two ways, passive and active. Passive monitoring is an agentless way, which is relatively low-cost in the implementation of network port monitoring. Usually this way can be set up and run in 2 days, and can provide detailed application performance data. When considering an agentless approach, the key is to look at the ability to support multiprotocol analysis (for example, XML,SAP,ABAP,SQL), because most companies have more than just web applications.

On the other hand, active monitoring integrates self-written probes and web robot programs, which can report system availability and predefined business events. This is a good complement to the passive approach, which, combined with the passive approach, can provide more data during the application trough.

Runtime application architecture (secondary concern)

The minimum solution here is to ensure that all nodes and services in your environment are fully monitored. At the same time, with reference to bottom-up monitoring, this will be a key factor in achieving a full runtime architecture solution.

Provides transaction path snapshots to help integrate top-down and bottom-up monitoring. There will also be a better service dependence topology diagram to understand the network topology of the application architecture. Keep in mind that the runtime view is something you can focus on after building a reliable application using user experience, business transactions, and escalation analysis dimensions.

Business transactions (Primary)

Using a subset of a set of business transactions to illustrate, we focus on user-defined transactions or URL page definitions that make sense to the community business. There may be 200 to 300 different page definitions for any given application; we will divide them into 8-12 advanced business transaction categories. This clearly describes the service level and quality of the service, and can predict the alarm in advance before most users perceive the decline in service performance.

Once your APM solution is mature, you can discover the meaning of business transactions in your other APM models. Keep it simple and optimize it constantly starting with rough noodles.

In-depth component monitoring (secondary)

This requires the installation of an agent, which is generally aimed at web, applying Chen Xu and message service middleware. It gives you a run-time view of the J2EE and .NET stacks and links to user-defined business transactions. A robust solution gives a clear path from the code execution point to the RUL execution to the user request.

Since this part is closely related to the second part of the APM model, you will find that many products in this area provide application dependency graphs (ADDM) as part of their larger solution.

Analysis / escalation (main)

Collecting raw data from other tool sets is a good practice, which allows you to deal with a variety of performance problems. Most products summarize or aggregate detailed data for reporting and archiving, but this is not enough to solve problems that have accumulated over a long period of time. It is also possible for a product to find an open data interface on its own toolset. This gives others the flexibility to create reports and be self-sufficient in responding to performance questions.

It is very important to set a set of common metrics for each application to collect and report. Although each application may run on different technologies and platforms, it is possible to standardize how to display real-time performance data in the form of monthly quality of service standards reports.

You'd better use a 5-minute average as a real-time performance alert and percentage the overall application analysis and service level management. In other words, keep it simple: focus on the average and analyze the percentage.

The following figure shows the ITIL process related to APM.

In general, your APM strategy is associated with multiple ITIL-related processes. I see APM and the continuous service improvement model as two sides of the same coin. They are all related to service design, service transaction processing and service operations, which can help improve the operational excellence of the IT department.

So much for the understanding of the priority of the APM model in Gartner. I hope the above content can improve everyone. If you want to learn more knowledge, please pay more attention to the editor's updates. Thank you for following the website!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.