DevOps

Here’s what the industry is getting wrong about APM

IBM APM Application Process ManagementRecently, you may have seen news about recent consolidation in the application process management (APM) space. Some might see this as the industry making big bets on combining network management with application management.

But I see it differently. This is an area that has not yet yielded results because the personas using these tools have very different needs and expectations. Let me explain.

IBM has been in the application monitoring space for more than 20 years. I see a very different trend emerging. As applications get more complex in today’s cloud era, the data processed in the monitoring space is growing exponentially. To support hybrid applications and infrastructure, you must have solutions that provide useful visibility and insight into data performance with features such as predictive analytics and cognitive ChatBots.

Cognitive technologies are replacing labor-intensive techniques to help practitioners sort through data and prioritize the analytical options. The industry is beginning to see the true value of cognitive capabilities, including gathering historical application data, making predictions and fixing problems automatically.

The shift to hybrid applications and DevOps methodologies are also impacting who uses APM and they use it. With rapid innovation and continuous delivery becoming a priority of many digital businesses, the need for APM to be introduced in the early stages of development and testing phase has become a growing trend.

As a result, APM is “shifting left” to become an integral part of application development and testing—beyond its continued use as a monitoring tool post-launch. I’ve seen planning for monitoring and management being done before the first line of code is being written.  Smart. It is critical for APM solutions to adapt to DevOps needs and deliver value to DevOps users to be successful in the future.

Some companies may see value by investing in monitoring and transaction profiling for IT Operations teams. But to me the trends show that APM users seem most interested in DevOps and cognitive technologies. One key to making users happy is to automate problem prevention and avoiding “war rooms.” This is a huge improvement over traditional uses cases of speeding up problem resolution.

Not every vendor can provide the solutions, integrations and insight to help companies keep up with the future of APM. But IBM can. IBM APM offers a deep view your infrastructure, application and user-experience to identify, isolate, diagnose and automatically resolve problems before they start affecting your users. With advanced cognitive capabilities, you’ll uncover source code problems long before an issue creates consequences. And you can diagnose problems using correlated log search and analysis and predictive insights.

Don’t settle for old fashioned, siloed application management when you can jump on the spaceship to the future.  Check out what IBM APM has to offer here. And for more on the industry’s best expertise on APM and its future, join us at InterConnect 2017 this March.

Share this post:

Share on LinkedIn

Add Comment
One Comment

Leave a Reply

Your email address will not be published.Required fields are marked *


Ben Stern

Nice blog Ankita. I completely agree that shifting left and planning/implementing APM earlier in the lifecycle of an application is important. Regarding cognitive, what you have stated is true and important. But, cognitive can play a much broader role. For example, automatically analyzing Event and Ticking data to reduce the number of problems that need to be addressed; finding root cause events; and mining the data to understand historical trends. For example, by analyzing historical trends in events and tickets, I can identify that a specific version of operating system or middleware is the cause of significant number of actionable events. There are many places where analytics can be applied to improve application performance and availability and to reduce MTTR.

Reply
More DevOps Stories

Why you shouldn’t choose between agile and DevOps approaches

You may hear your IT department talking about implementing agile or DevOps development. Both promise better and faster software development through collaboration. How are they different, and which is better for your business? Agile software development principles enable developers to deliver new functionality quickly while responding to changing business requirements. Development teams deliver incremental features frequently, perhaps […]

How to unleash agile, responsive development with APM and DevOps

Digital transformation has profound ramifications for your organization. The new landscape is disrupting business models, raising customer expectations and creating new channels to do business. I bet you’re seeing the impact of digital transformation on your organization’s application development cycle as well. The rate of development probably isn’t decided entirely by you anymore. Instead, it’s […]

Sleep easier with availability monitoring

Necessity is the mother of invention. Anything that can fend off the Saturday 2 AM call to my fellow developers, or even just reduce the pain of late-night troubleshooting, is worth the invention. If your team uses DevOps practices, offers your organization continuous delivery and is responsible for delivering always-on code, you know what I […]