August 11, 2016 | Written by: Marcel Karman
Share this post:
Part 1 – Agile IT
In 2014 Gartner predicted that “75 percent of IT organizations will be bimodal 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. Whereas speed 1 is traditional IT being managed by IT operations personnel, speed 2 is considered “agile IT”: Within the organization, developers and line-of-business personnel are involved to get the most out of the digital innovations that flood our daily lives.
One thing that these people all have in common is a need for monitoring. In this first portion of the blog post I’ll focus on the needs of the developers and line-of-business, and in Part 2 I’ll focus on IT operations and bring everything together.
Obviously a developer wants to build nice applications or cloud services. They want to build apps quickly like startups do without being bogged down by testing and support, and they want to spend time on improving things rather than on fixing things.
The requirements for a developer are that they want to be sure that their application is running and performing well for their users. And if it’s not functioning properly, then they need monitoring to help them find the problem. Very important: the monitoring tool should not be intrusive and should be very simple to use. Tools should fit the startup mentality workflow!
IBM Monitoring and Analytics Service on Bluemix
As an example, IBM Bluemix is a perfect environment for coding developers, with many services offered. One of these services is the Monitoring and Analytics Service. You just bind it to your newly developed application, and it provides instant details on the performance of that application. If the new application is not performing as expected, you can use embedded analytics to search through log and metric data. So by using this Monitoring and Analytics Service, developers can innovate faster as they spend less time fixing bugs and addressing performance issues and more time developing new features.
You can say that the line-of-business (LOB) represent the organization`s customers. They want to improve customer satisfaction and to be able to see which services are successful and which ones are not. A requirements of the LOB is often visibility into the customer experience of applications and services.
Application performance management SaaS
The LOB acts like the developers; they also want to move fast. So when there is a need to monitor a new application, the LOB can move to a public cloud provider when IT operations are not able to deliver quickly. As an example, IBM Application Performance Management (APM) has a software-as-a-service (SaaS) solution that enables the LOB in such a way that they can set up monitoring for their applications very quickly. With APM the LOB can identify bottlenecks and quickly get to the root cause of application problems. Furthermore, APM can help to avoid application outages by using predictive insights capabilities, which allow the LOB to automatically detect anomalies within the application before customers are impacted.
In the second installment of this blog post I’ll focus on IT operations.
To be continued… until then stay interested by exploring the future of APM with a Gartner short film.