About These Slides

● These slides were derived from the story in this google document.

● The primary audience is a IT Decision Maker along with Enterprise Architecture

● The goal of the slides it to provide a compelling reason to enable Remote Health Monitoring for OpenShift 4
clusters

● There is a backup slide that explains how Red Hat treats the collected data. This is purposely left out of the
main body of the presentation to allow the presenter to speak to it if required. If not, it can be omitted.

1
 Increase Reliability and Save Time
with Remote Health Monitoring

2
 New in OpenShift 4 - Remote Health Monitoring
How Remote Health Monitoring Works

Remote Health Red Hat Support &

analyze Engineering
monitoring service

non-identifying
information contained

- OpenShift version

- upgrade errors

- CPU & RAM configuration

anonymized Proactive Safer Improved
- health condition Resolution Upgrades Experience
data
- underlying infrastructure

3
OpenShift clusters You
 History of Remote Health Monitoring
Red Hat Insights Providing Remote Health Monitoring for RHEL since 2015

Infrastructure Server data anonymization Minimal network impact

Red Hat Insights

Results tailored to each host

+Remediation steps +Playbooks

Red Hat
4 Enterprise Linux
 The benefits of Remote Health Monitoring for RHEL

reduction in time to detect known risks to availability, performance, stability, and

96% security

26% reduction in administrator steps to detect these known risks

less time to track patch status for all systems in environment, versus manual
88% scripted workflow

450% to discover vulnerabilities in a 100-VM environment, versus over 15m when

1m 24s performed manually

Increase in active Insights clients, from January, 2019 to

August, 2020
91% less task completion time to address a vulnerability

Systems under management with Insights number in the

hundreds of thousands.
69% reduction in time to detect a policy violation

Source: Principled Technologies. “Save administrator time and effort by activating Red Hat Insights to automate monitoring” Sept 2020.
 The Connected OpenShift “Fleet”
A growing amount of connected clusters across the multiple footprints

OpenShift 4 Connected Cluster Count OpenShift 4 Deployment Modes

Multi-cloud
405% YoY

6
 Why Remote Health Monitoring?

Proactive Safer Improved

Resolution Upgrades Experience

7
 Proactive Resolution

Fix released earlier because of

faster detection

Red Hat Support can

proactively notify affected
users and provide workaround
if available

error rate spike in the

connected fleet can be
identified prior to spike in
support cases

8
 Safer Upgrades
Red Hat curates the best sequence of updates through a graph database
Simple view Full update graph
● Paths are constantly being tweaked to
$ curl -sH 'Accept: application/json'
'https://api.openshift.com/api/upgrades_info/v1/gr get the best experience
aph?channel=fast-4.4' | jq -r '[.nodes[].version]
| sort | unique[]'
4.3.12
4.3.13 ● Feedback through telemetry, bugs and
4.3.18 automated testing
4.3.19
4.3.21
4.3.22
Versions that can upgrade to 4.4
4.3.23 ● Paths can skip entire sections if safe
4.3.25
4.3.26
4.3.27
4.3.28 ● Admins can force their way through the
4.3.29
4.4.10 cluster’s protections, if desired
4.4.11
4.4.12
4.4.3
4.4.4 Choices to upgrade to within 4.4
4.4.5
4.4.6
4.4.8
4.4.9

9
 Safer Upgrades and Proactive Support (Example)
Paths that are unsafe can be “blocked” to provide clusters a safer upgrade path

March, 2020 March, 2020 April, 2020

4.3.9 4.3.9 4.3.9

4.3.8 4.3.8 4.3.8

X
4.3.7 4.3.7
4.3.7

Issue with new SCC modification check in
4.3.8 identified via telemetry data. Issue caused
10 failures when upgrading to 4.3.9 from 4.3.8.
Effected connected clusters identified and Fix released and path unblocked for
path to 4.3.8 proactively blocked to ensure remaining users.
users do not get “stuck” on 4.3.8. Red Hat
could also propose avoiding version 4.3.8 and
moving to 4.3.9
 Improved Experience
Without Remote Health Monitoring With Remote Health Monitoring

Red Hat 2 Red Hat 2

Customer Customer
Portal sees new case sees new case
Portal
Red Hat Red Hat
1 Support 1 Support
request cluster & Engineering & Engineering
open open
support case information support case
5 3
begins begins
4 troubleshooting troubleshooting
upload Automatic
logs Manual diagnostic
diagnostic gathering
You gathering You
3
gather
info
remote health
monitoring
enabled

OpenShift Clusters OpenShift Clusters

11

* Currently, remote health monitoring collects a subset of information. Red Hat Support may still request
additional information, such as must-gather, from users
 Improved Experience

12
 Remote Health Monitoring
New in OpenShift 4

Proactive Resolution Faster Resolution Safer

Upgrades

● Remote Health Monitoring is enabled by default

● To learn more about how to enable Remote Health Monitoring

if you have disabled it you can reference the
Remote Health Monitoring documentation

13
 Thank you linkedin.com/company/red-hat

youtube.com/user/RedHatVideos
Red Hat is the world’s leading provider of enterprise

open source software solutions. Award-winning support,

facebook.com/redhatinc
training, and consulting services make

Red Hat a trusted adviser to the Fortune 500.

twitter.com/RedHat

14
 About Telemetry Data Collection

Personal Data
Red Hat does not intend to collect personal information. If Red Hat discovers that personal information has been inadvertently received, Red Hat will
delete such information. To the extent that any telemetry data constitutes personal data, please refer to the Red Hat Privacy Statement for more
information about Red Hat’s privacy practices.

Retention
Red Hat retains and stores telemetry data only for as long as it’s needed to for the purposes described above or as otherwise required or permitted by
law.

Data Security
Red Hat employs technical and organizational measures designed to protect the telemetry data.

Data Sharing
Red Hat may share telemetry data with its business partners in an aggregated form that does not identify customers to help the partners better
understand their markets and their customers’ use of Red Hat offerings or ensure the successful integration of products jointly supported by those
partners.

Third-Party Service Providers

Red Hat may engage certain service providers to assist in the collection and storage of the telemetry data.

15
 Further Information

Telemetry and the Insights Operators enable a lot of benefits to the end-user that would otherwise be impossible.

1. Red Hat engineering can observe events that may seem normal to the end-user, but with the perspective of seeing those events across fleets of
users new points of view can more rapidly be surfaced and fixed without the end-user needing to open support cases and Bugzilla tickets.
2. OpenShift has a concept of fast and stable software release channels. The graduation of fast to stable is dependent on the success rate of
updates and the types of events seen during upgrades. With this connected information, we can improve the quality of releases to stable
channels and react more quickly to issues found in the fast channel.
3. This information allows OpenShift to more rapidly release new features and functionality that are focused on parts of the solution that are
used more than other parts. This allows us to focus engineering resources where they can be the most impactful to end-users.
4. Streamlined support experience. Later in the chapter, you will see the support experience that opens up to you if you provide the cluster id of
the cluster you are opening a support ticket on at access.redhat.com. This experience is possible through connected information.
5. Predictive analytics. The Insight that we are able to display for your clusters on cloud.redhat.com are driven by connected information. Red
Hat is investing in applying deep learning, machine learning, or artificial intelligence automation around inference and other applicable
technologies to help identify issues in end-user clusters.

The connected experience is the foundation for future on demand pricing models.

16