Things change. Your ability to see them shouldn’t.
Containerized application architectures are engineered for constant change. That’s why they’re perfectly suited for DevOps processes like continuous delivery.
But it’s a challenge to identify critical changes in topology, code and attributes, and how each can impact application performance. When one container goes down, another can pop up in its place, but if failure happens consistently, there will be a degradation of service. At the same time, constant change results in greater complexity, and if it’s not managed, it can result in burnout, downtime, and frustration.
The result is an annoying “now you see it, now you don’t” scenario for monitoring. What’s needed is real-time insight.
Container monitoring helps you to understand the impact of changes on application performance within context of your own team’s tasks and activities. Changes to application code, infrastructure, and topology can be tracked across time, enabling you to quickly pinpoint and prevent problems, as well as identify conditions that correlate to increased performance.
Source: Omnichannel, Microservices, and “Modern” Applications: How are you Managing User Perceptions and the Customer Experience, Enterprise Management Associates, January 2016
Podcast: Future-Proof Docker with Modern Monitoring
The New Stack Makers featuring Sushil Kumar, SVP Product Management, CA Technologies
Traditional monitoring tools still work for traditional infrastructures, but newer cloud-based offerings should be supported by monitoring solutions that are as scalable as the services being built and monitored. No matter what solution or service you use, you still need to know how you’re going to collect the metrics you’re looking to monitor.
Read this chapter now to get:
Source: Gartner Market Guide for Container Management Software - 10 August 2017 - G00321084
