IBM Cloud Application Monitoring

Challenge

How might customers transition away from legacy monitoring software?

Outcome

A platform to help meet current customer needs and guide them towards future technologies

Role

User experience designer, system architecture and front-end developer

Our Problem

This...

IBM's current monitoring solution was criminal. The design was not intuitive and would also leave users lost in a series of menus.

We tackled the problem by first understanding all the facets of a cloud/on-premise application, and how these variables might affect an application's performance.

Approach

After we came to an understanding of all the hidden variables we created a robust data structure for presenting all of the variables in an "glance-able" way. The goal was to give a DevOps professional a dashboard where they would be able to diagnose performance issues quickly, and perhaps even catch them before they occur. This meant giving the entire environments highly "suspect" metrics to the user in a concise and consumable data drive graph.

This product took a look at infrastructure from the bare metal up. Rather than looking at monitoring from an application level, we designed a system for understanding the entire scope of your application infrastructure in the cloud. These tools, coupled with the insights from BAM, would give you a robust set of tools for application and infrastructure monitoring in a multi-cluster Kubernetes environment.

The entire application also provided robust tools for fixing and alerting the appropriate parties that something has gone wrong.

A small prototype I built: Prototype

* A couple interactions are broken because the project was sunset before I had a chance to finish

Demo Video