Build an application-centric monitoring topology

Monitoring at the microservice level provides visibility into the total state of application environments. Quickly reach root causes of incidents for both containers and VMs, regardless of cloud provider or volume of clusters, from a single control point. Improve efficiency with targeted event management and automated runbooks to remediate issues without any direct team involvement, eliminating the need to manually identify the pods and clusters generating issues.

How customers use it

1. Set up Kubernetes monitoring

The Kubernetes data collector built into IBM Cloud Pak® for Multicloud Management will gather detailed information about the performance of the Kubernetes cluster, generate alerts on abnormal behavior and automatically import performance and topology information.

Kubernetes monitoring dashboard

2. Set up synthetic monitoring

Set up a synthetic PoP (point of presence) agent to test web pages and rest APIs to ensure applications and microservices run within expected response times.

Response time dashboard

3. Instrument other cloud native resources

Use lightweight data collectors to gain visibility into the application topology to understand and analyze performance characteristics. Runtime data collectors can also provide visibility into the topology and transactional flows within the microservice.

Golden Signals dashboard

4. Set up traditional monitoring agents

Monitor on-premises applications and infrastructure alongside cloud native resources with built-in monitoring agents for databases, application servers, hypervisors and more.

Traditional agent monitoring dashboard