OpenShift 4.2: The New Cluster Overview Dashboard

23 octobre 2019Alex Handy3 minutes (temps de lecture)

Red Hat OpenShift 4.2 is a significant release that brings a number of great enhancements to the Web Console UI, but you'll notice one of the biggest changes as soon as you log in.

The Cluster Overview Dashboard is the new default landing page of the OpenShift Console and provides a birds-eye view of your cluster's current health, inventory, capacity, utilization, and activity to make identifying problems and resolving issues easier and faster.

This post will briefly cover what this dashboard is made of, but we know from using it ourselves these past few months that static screenshots won't quite do it justice. We're really excited for you to try this new dashboard out in your own clusters, and our User Experience Design team would love to hear any feedback and suggestions you have for future improvements.

A window into your cluster

The Overview Dashboard is designed to answer the following at a quick glance:

What am I looking at?
What's in this cluster?
Is everything okay?
Is there enough capacity?
What is the cluster up to?

The Details card in the top-left corner answers the first question with the cluster’s ID, provider, and current version. The Inventory card directly below it includes the quantity and current statuses of the nodes, pods, and persistent volume claims within the cluster, with clickable status counters that act as quick shortcuts to the full list pages of those objects.

The Health card in the center of the dashboard is (hopefully) pretty mundane most of the time, with a green check mark indicating that no degraded systems or actively-firing alerts from AlertManager require your attention.

The Capacity and Utilization cards visualize how much resource headroom is available at the moment and how the cluster's utilization of CPU, Memory, and Disk space has changed over the last hour.

The Events card in the top-right streams in the same cluster-wide events that can be found in the dedicated Events page, with any warning events highlighted.

Finally, the Top Consumers card in the bottom-right corner helps identify the highest consumers of CPU time, Memory, Storage I/O time, and Network bandwidth so that any outliers greatly affecting the cluster's capacity can be addressed.

Surfacing alerts, warnings, and errors

A perfectly happy and healthy dashboard is always great to see, but the value of including all of this information in one place becomes super clear when things in the cluster go wrong.

Any firing alerts from AlertManager are collected within an Alerts section of the Health card. Resolving those alerts is generally the best first step toward restoring the health of the cluster, but the additional context provided by the object statuses in the Inventory card, errors in the Events card, and resource measurements in the Capacity and Utilization cards can often help to better understand the full scope of each problem.

Funnily enough, we know this because the dashboard started to help our internal OpenShift developers identify and troubleshoot issues almost as soon as the first cards appeared! The errors that bubbled up to the dashboard frequently kicked off discussions that tangibly improved the entire OpenShift product family, and seeing it do so was an absolute thrill (that we probably should have expected).

We can't wait to hear how it helps you and your team as well!

What’s next

The introduction of the Cluster Overview Dashboard in OpenShift 4.2's Console UI is just one of the many ways we're improving the observability and management experience of OpenShift, and there's so much more ahead to look forward to. If you'd like a sneak peek, follow the OpenShift Console and OpenShift Design GitHub repositories to see some of the ideas we're thinking about for future iterations.

Our User Experience Design team would love to hear your ideas and feedback on this new dashboard and any other areas of the Console UI. Please fill out this feedback survey or sign up to participate in future research opportunities.

À propos de l'auteur

Alex Handy

Principal Product Marketing Manager

Red Hatter since 2018, technology historian and founder of The Museum of Art and Digital Entertainment. Two decades of journalism mixed with technology expertise, storytelling and oodles of computing experience from inception to ewaste recycling. I have taught or had my work used in classes at USF, SFSU, AAU, UC Law Hastings and Harvard Law.

I have worked with the EFF, Stanford, MIT, and Archive.org to brief the US Copyright Office and change US copyright law. We won multiple exemptions to the DMCA, accepted and implemented by the Librarian of Congress. My writings have appeared in Wired, Bloomberg, Make Magazine, SD Times, The Austin American Statesman, The Atlanta Journal Constitution and many other outlets.

I have been written about by the Wall Street Journal, The Washington Post, Wired and The Atlantic. I have been called "The Gertrude Stein of Video Games," an honor I accept, as I live less than a mile from her childhood home in Oakland, CA. I was project lead on the first successful institutional preservation and rebooting of the first massively multiplayer game, Habitat, for the C64, from 1986: https://neohabitat.org . I've consulted and collaborated with the NY MOMA, the Oakland Museum of California, Cisco, Semtech, Twilio, Game Developers Conference, NGNX, the Anti-Defamation League, the Library of Congress and the Oakland Public Library System on projects, contracts, and exhibitions.

Read full bio