►
From YouTube: The Level Up Hour (E50) | Red Hat Insights
Description
Need better visibility into your OpenShift cluster? On today's show, we get to dive into Red Hat Insights with John Spinks, Senior Principal Product Marketing Manager from the OpenShift team. We'll discuss how to get started with Red Hat Insights on OpenShift, cover the importance of health checks, and take a look at some new and upcoming enhancements. We'll also look at how we can best leverage analytics data about our applications and services. So if you have any questions or want to learn more, don't miss this episode.
Follow us:
Scott McBrien https://twitter.com/stabby_mc
Randy Russell https://www.linkedin.com/in/randy-russell-0312243
Jaafar Chraibi https://twitter.com/ChraibiJc
What is the Level Up Hour?
Every Wednesday at 9am ET we stream live demos on how Red Hat Enterprise Linux (RHEL) users and admins can benefit their organizations and improve their careers by learning how to use containers, Kubernetes, and Red Hat OpenShift.
Learn more at:
https://red.ht/leveluphour
http://red.ht/3ayHlHI
How to participate in the The Level Up Hour:
Watch on YouTube every Wednesday at 9amET
Chat with us on Discord https://discord.gg/5VMVGJt
Check out our GitHub repo https://github.com/level-up-hour/
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
https://www.openshift.com/
https://github.com/openshift/
#RedHat #OpenShift #tluh
B
C
B
B
A
Hey
randy,
hey
scott
great,
to
be
on
the
show
today,
and
I
am
technical
marketing
manager
for
insights
and
for
anybody
not
familiar.
It
is
a
managed
service
whose
purpose
is
to
continually
analyze
platforms
and
applications.
In
order
to
help
you
manage
your
hybrid
cloud
environments
and
that
when
we
say
platforms,
it
works
for
rel.
As
you
mentioned,
it's
also
available
on
openshift
and
ansible
automation
platform.
A
A
B
A
I'll
answer
the
unasked
question:
first
for
rel:
we've
had
it
around
for
about
six
years,
so
it's
been
out
there
for
a
while,
it's
pretty
stable.
We
only
recently
announced
it
officially
for
both
openshift
and
ansible
automation
platform,
but
it's
been
available
within
openshift
on
on
command
cluster
manager
for
probably
about
a
year
and
a
half
to
two
years.
So
it's
been
available
out
there.
It's
just
been
hidden
and
a
little
bit
in
the
background
and
at
summit
this
year.
Actually
we
made
the
announcement
that
it's
available
for
all
of
our
major
platforms.
B
Great
well
so
here's
here's
the
question
to
get
this
capability
to.
You
know,
look
with
the
red
hat
glasses
at
you
know
your
all
your
systems
that
are
running
you
know
these
particular
platforms
and
so
on.
How
exactly
does
it
work?
I
mean
how?
How
does
that
actually
manifest
itself?
I
mean
I
can.
I
can
imagine
sort
of
a
a
portal
that
would
give
me
that
information.
A
Collected
it
varies
a
little
bit
depending
on
the
platform
that
you're
using,
because
there
are
differences
in
the
platforms
themselves
and
the
way
that
they
operate
so
we're
going
to
have
to
handle
each
platform
individually.
So
rel
is
the
oldest.
It's
been
around
the
longest.
It
uses
a
client
that
client
is
installed
by
default
on
most
versions
of
rel,
so
it's
in
there
it's
part
of
the
package.
A
So
if
it's
not
installed,
you
have
to
yum,
install
or
dnf
install
it
and,
if
you're,
using
a
newer
version
where
it's
already
installed,
you
just
turn
it
on
insights,
client,
dash
dash
register
and
that's
going
to
start
the
process
of
collecting
facts
and
metadata
on
the
system
itself.
We
upload
a
collection
packet,
the
average
size
last
I
looked
was
around
384
kb,
so
very
small
size
that
we're
looking
at,
and
we
do
an
analysis
on
that.
A
Actually
in
the
cloud
and
give
back
to
you
the
data,
it's
of
course
fully
supported
by
our
gdpr
practices.
You
have
full
control
and
can
see
everything
that's
collected
and
you
can
redact
or
remove
anything
that
you
have
even
greater
concerns
about.
So
if
you're
like
hey,
I
don't
want
anything
about
my
host
name
going
out.
That's
a
simple
switch!
Yes!
No,
if
you
don't
want
anything
about,
maybe
a
particular
string
command
pattern.
A
B
A
And
you
can
do
that
collection
on
your
side
without
ever
sending
anything
to
red
hat,
look
at
it,
inspect
it
and
then
go
yeah
cool
yeah.
That's
no
big
deal
I
mean
we
have
to
run
commands
like
you
know.
What's
your
up
time,
you
know
what
version
of
rel
is
this:
what
packages
are
installed
and
running
and
what
are
the
versions
of
those
packages?
So
again
it's
kind
of
metadata
level,
but
we
need
to
know
things
like
that.
A
If
we're
going
to,
for
example,
look
for
an
issue
where
a
certain
version
of
the
kernel
and
a
certain
version
of
a
package
over
time
will
collide
and
maybe
cause
some
downtime
or
cause
some
issues
like
we
need
to
know
those
version
numbers.
So
we
can
give
you
that
analysis
and
say
hey
there,
this
potential
issue
in
the
making-
and
you
should
be
aware
of
it-
and
hopefully
we
give
that
to
you
before
you
encounter
any
downtime
or
trying
to
stop
that
3
a.m.
Phone
call.
B
Yeah
yeah
well
so
in
some
ways
it's
it's
the
cis
admins
dream
to
have
that
level
of
insight
and
so
on,
but
it's
also
a
bit
of
a
change.
So
so
what
sort
of
you
know
adoption
have
we
seen
if
we're
looking?
First
with
that
longer
term,
red
hat
enterprise
linux,
you
know
use
case.
Has
it
been
widely
adopted?
B
A
We're
not
in
that
model
we're
in
a
model
where
there's
something
that
is
a
feature
of
what
you've
already
bought-
and
this
is
true
for
rel,
for
openshift
for
ansible,
if
you've
already
paid
us
for
the
subscription,
you
have
this,
but
you
have
to
turn
it
on.
It's
almost
in
some
way,
like
I
don't
know,
get
a
car
with
one
of
those
remotes
and
if
you
like,
hit
the
unlock
button
and
then
hold
it
down,
it
will
roll
down
your
windows,
but
you're
only
going
to
find
out
about
that.
A
If
you
really
delve
through
the
documentation
and
read
it
like
it's,
it's
one
of
these
little
kind
of
hidden
features,
and
we
don't
want
it
to
be
hidden.
We
want
it
to
raise
the
awareness
and
let
people
know
that
this
is
something
that
you
know
anybody
has
access
to
and
can
use
documentation.
What's
that.
C
A
That
used
to
be
a
real
slog.
I
mean
login
to
every
system,
one
at
a
time
or
you
know,
go
write
a
script
and
says:
hey,
I'm
looking
for
the
presence
of
this
package,
oh
gosh!
If
we
got
thousands
of
systems
that
takes
a
long
time
versus
if
you
have
something
like
insights
in
place,
your
your
systems
are
registered
click,
the
link
print
out
the
report.
A
B
Ooh
that
sounds
kind
of
like
a
demo.
Doesn't
it
well
so
before
we
before
we
get
to
that?
Let's
just
sort
of
clarify
and
reiterate
something
about.
This
is
again
it
comes
with,
and
you
know
it's
really
ironic
to
me
that
the
thing
that
comes
with
it
might
be
free
that
might
not
actually
have
as
much
awareness
as
something
that
we
we
have
somebody
selling
as
an
add-on.
So
yeah,
you
know,
take
advantage
of
this.
It
comes
it
comes
with.
A
Yeah
so
rel
I
mentioned
a
little
bit
about
it.
There's
a
client
that's
available
on
the
host.
You
have
to
register
with
that
client,
so
it's
100
an
opt-in
process
for
rel
ansible
works
very
much
the
same
way
on
your
ansible
tower
or
your
ansible
controllers,
they're
rail-based
on
the
back
end.
So
it's
a
very
similar
process.
A
We
estimate
that
it's
worth
this
much
an
hour
in
savings
and
you've
saved
this
many
thousands
or
hundreds
of
thousands
of
dollars.
So
all
of
that
can
be
gleaned
from
the
analytics
of
ansible.
Openshift
is
a
little
bit
different
because
it
expects
with
openshift4
a
connected
experience.
There's
remote
health
checks,
remote
monitoring
and
an
insights
operator,
and
all
of
that
is
connected
essentially
by
default,
because
we
expect,
with
openshift
you're
opting
into
that
higher
level
of
analytics
and
a
connected
experience
where
we
can
tell
you
ahead
of
time.
A
Hey
your
cluster's,
not
quite
working
the
way
it
should
there's
something
going
on.
We
can
inform
you
of
that
and
that's
very
similar
to
model.
I
used
to
work
for
a
storage
company
previous
to
this
and
they
had
a
you
know.
An
automatic
support,
type
operation
work
very
much
the
same
way
or
if
you
have
a
hard
drive
started
to
fail.
You
get
one
in
the
mail
and
it
just
shows
up
on
your
front
door.
It's
a
very
similar
model
that
we're
following
with
openshift.
B
So
one
of
the
things
that
I
found
interesting
here
is
the
idea
that
if
there
is
some
sort
of
corrective
action
that
needs
to
be
taken
by
insights,
is
that
it'll
actually
hand
you
back
an
ansible
playbook
now
now?
Is
that
something
that
will
apply
across
all
platforms?
Or
is
it
something
that
just
applies
for
for
red
hat
enterprise,
linux.
A
Right
now,
it's
primarily
for
rel
and
ansible,
because
again
ansible
relies
on
rel
as
a
back
end
for
the
tower
of
the
controller
they're.
Also
doing
that
same,
I
started
to
call
it
automation,
but
it's
not
end-to-end
automation,
but
you
know
it
creates
that
playbook
for
you,
where
it
can
give
you
the
intelligence
to
prescriptively
say
this
is
what
you
need
to
do
to
fix
it.
A
So
we
just
generate
a
playbook
and
on
rel,
if
you
also
have
a
satellite
or
if
you
have
a
smart
management
subscription,
you
can
actually
run
that
playbook
right
from
insight,
so
it
even
goes
beyond
creating
the
playbook
for
you
to.
If
you
have
appropriate
permissions
it
lets
you
execute
that
playbook.
B
All
right,
well
yeah,
so
it's
it's
very
interesting
to
see
how
these
particular
three
platforms
are
sort
of
evolving
in
parallel
side
by
side,
sometimes
in
a
very
complementary
way.
You
know,
especially
something
like
you
know,
ansible
as
the
means
to
actually
you
know,
perform
these
improvements
both
on
itself
and
on
rail,
and
I
would
expect
at
some
point
that
this
becomes
something
that
we
see
in
terms
of
openshift
as
well
right,
yeah,.
A
I
should
mention
as
well
the
the
ansible
changes
some
of
the
new
services
were
announced
at
ansible.
Fest
they're
not
actually
live
right
now,
they're
in
production,
but
they're
in
what
we
call
beta
so
they're
available
to
everybody
today
and
when
we
again
jump
into
the
demo
I'll
show
you
how
you
can
turn
on
the
beta
mode,
and
you
can
see
everything
that's
coming,
because
it's
out
there
it's
available,
they
just
won't
flip
the
switch
and
turn
it
into
production.
Until
ansible
automation,
platform
2.1
gets
released.
B
A
All
right,
so
what
I
have
on
the
screen
right
now
is:
I
have
gone
to
red
hat's,
hybrid
cloud.
This
is
cloud.redhat.com.
If
you're
not
familiar
with
it,
it
uses
the
exact
same
credentials
as
what
you
might
use
to
file
a
support
case
or
go
view.
A
knowledge
base
article,
it's
the
access.redhat.com
red
hat
sso.
So
it's
the
exact
same
thing.
So
I've
just
gone
to
cloud.redhead.com.
A
So
it's
right
there,
I'm
going
to
click
on
that
I
logged
in
earlier
today.
My
sso
is
probably
still
cached,
so
it
didn't
prompt
me
for
a
username
or
a
password
if
I
hadn't
done
that
it
would
have
said
hey.
What's
your
what's
your
red
hat,
login
id
and
again
that's
the
same
one
that
you
would
use
elsewhere
on
a
red
hat
property
just
to
log
in
so
here
I
am
on
the
main
page
of
the
hybrid
cloud
console
you
can
see.
On
my
left
hand,
navigation
bar
over
here.
A
A
A
So
if
I
go
to
that
settings
menu,
I
mentioned
earlier
that
some
stuff
is
in
beta
and
we've
got
two
different
environments
here
for
insights.
There's
a
beta
environment
in
a
production
environment.
We
treat
them
both
like
production
from
a
developer
standpoint
because
they're
available
to
you
all
of
the
time.
A
But
if
I
click
at
any
point
use
the
beta
release,
it's
going
to
show
me
whatever
the
latest
is,
so
you
should
see
a
visual
ui
change
right
there,
as
I
switch
to
the
beta
mode,
we're
trying
to
make
this
even
more
instinctive
intuitive
to
use
and
maybe
a
little
bit
less
wordy.
So
we
can
get
all
of
the
findings
across
the
hybrid
cloud
console
to
you
easily
and
quickly
I'll
pause.
There
questions
so
far.
B
A
Before
I
dive
into
the
platforms,
I
want
to
talk
just
a
little
bit
more
about
what
it
takes
to
get
on
this
console.
You
just
have
to
have
that
sso,
login
and
within
the
settings
menu
itself.
So
I'm
going
to
go
to
that
gear
again
and
I'm
going
to
go
to
settings
within
this.
We
do
have
role-based
access
control,
so
I
can
see
here
under
my
user
access
what
I
have
access
to
I'm
logged
on
here,
because
I
want
to
be
able
to
show
you
everything.
A
I've
got
pretty
much
full
access,
so
I
can
see
all
of
the
different
services
across
all
the
different
platforms
here,
but
within
user
access
there
is
concepts
of
users,
roles
and
groups.
The
users
are
the
same
users
that
your
account
has.
So
anybody
within
your
organization
that
has
a
red
hat
sso,
can
access
this
and
then
within
the
groups.
A
What
you
probably
want
to
do,
if
you
want
to
restrict
this
access,
is
go
into
that
default
access
group
and
say
you
only
want
a
certain
subset
of
your
population
that
has
a
credential
to
access
this
console.
You
can
go
into
the
default
access
and
you
can
remove
some
of
this
access
say
you
don't
want
them
to
have
access
to
compliance
or
advisor,
and
I
can
talk
a
little
bit
more
about
what
their
services
are
in
a
moment.
You.
B
A
Yeah
and
so
by
default,
it's
it's
most.
Things
are
open
to
you,
because
we
do
want
to
encourage
users
of
insights,
but
the
big
one-
that's
not
available
to
you
unless
you
opt
into
it.
Unless
you
have
somebody
go
in
and
create
you,
an
access
is
remediation
because
we
don't
want
you
to
be
able
to
actually
take
actions
on
these
hosts
like
physically
manipulate
them
in
any
way,
unless
you've
been
exclusively
granted
that
permission,
so
that
is
not
part
of
our
default
access.
A
But
if
you
go
into
the
roles,
there's
a
pretty
good
list
of
roles
here
so
for
most
of
the
services
and
capabilities
they're
listed
on
here-
and
you
may
even
see
some
that
aren't
currently
available,
because
we
also
have
the
concept
of
private
beta.
So
I've
got
a
few
things
that
you'll
see
later
on,
but
you
may
not
have
access
to
and
that's
okay
and
that's
expected
well
kudos.
B
C
To
point
out,
especially
with
the
red
hat
sso
system,
so
there's
there's
basically
like
two
sets
of
settings.
One
is
the
insight
settings
that
john
is
showing
us
that
are
separate
from
the
account
settings
in
your
organization.
So
as
an
organizational
administrator
for
a
red
hat
set
of
accounts,
you
can
choose
things
like.
Can
this
person
open
support
cases?
Can
this
person
download
product
can
this
person
register
systems
with
subscription
manager
and
those
settings
are
independent
of
the
insight
settings?
C
So
you
can
actually
grant
someone
in
fact,
in
the
lab
that
we
linked
in
the
chat
earlier,
the
user
account.
That's
used
in
that
lab,
has
no
privileges
for
subscription
red
hat
services
downloads,
but
can
access
the
insights
console
and
look
at
insights
data
and
pull
reports,
and
things
like
that
so
between
the
two
you
can
set
some
really
fine
grained
controls
over
how
much
access
someone
within
your
red
hat
organization
should
have.
A
My
other
user,
I
tried
switching
to
a
different
tab,
didn't
even
have
user
management,
but
I've
got
a
higher
level
permissions
here
on
access.redhat.com,
so
my
user
has
it
the
other
demo
user
that
I
had
open.
Another
tab
did
not
so
yeah
within
this.
I
can
go
into
a
particular
user
and
I
can
give
them
that
access
that
that
scott's
talking
about
so
we
can
go
in
here
and
you
know
actually
give
them
different
levels
of
access
inside
of
access.redhat.com,
and
this
is
100
separate
from
what
I
was
doing
over
on
insights.
A
A
Yeah
yeah,
so
this
particular
user
I'm
looking
at
is
you
know
a
pretty
limited
user.
They
don't
have
a
whole
lot
of
access
to
things,
but
I
could
absolutely
change
their
permissions
to
let
them
open
support
cases
or
do
any
of
these
other
items.
But
this
is
separate
from
what
I'm
doing
over
here
right,
so
cool.
A
Well,
I
know
we
delved
in
kind
of
deep
to
our
back,
but
it
was
level
up
power.
So
we
wanted
to
make
sure
that
we
were
showing
you
some
of
these
a
little
bit
more
advanced
things
while
I'm
in
here
before
I
leave.
I
do
want
to
highlight
that
we
also
have
sources.
So
if
you're,
a
public
cloud
user,
you
can
set
up
integration
with
your
public
cloud
provider
from
right
here:
azure
google
aws
that
enables
some
advanced
features
such
as
gold
images.
A
If
you
have
a
appropriate
subscription,
it
enables
auto
registration
and
of
course
it
enables
use
for
insights
and
our
services
within
it.
Integration
is
also
going
to.
I
don't
have
any
setup
right
now,
but
it's
going
to
allow
you
to
set
up
web
hooks
or
do
some
other
kind
of
advanced
integration.
So
if
I
wanted,
for
example,
a
slack
notification
whenever
I
got
a
an
issue
popping
up
inside
of
insights,
I
could
do
that
through
a
web
hook
here
and
then
notifications
is
where
you're
going
to
do
email
notifications.
A
A
And
future
growth
we're
looking
on
in
some
some
built-in
integrations,
particularly
you
know,
potentially
with
like
a
servicenow
type,
but
that's
future,
that's
not
today,
but
it's
something
that
we're
definitely
looking
into
like.
Can
we
build
into
some
of
these
really
common
workflows
and
make
it
a
lot
easier?
So
you
don't
have
to
go
the
web
hooks
route?
Can
we
build
in
a
native
service
now
type
integration,
but
that's
all
future
state.
B
A
Cool,
so
all
right,
so
we
talked
about
some
of
the
advanced
features
before
we
talked
about
some
of
the
basic
features,
but
you
guys
haven't
so
all
right.
I've
gone
back
to
the
main
page
here,
I'm
logged
in
I'm
still
in
beta
mode,
I'm
going
to
go
ahead
and
go
into
red
hat
enterprise
linux,
and
what
we're
going
to
talk
a
little
bit
about
is
one
of
our
services
that
actually
crosses
all
three
platforms.
The
advisor
service,
the
advisor
service,
is
the
og
service
within
insights.
A
It
used
to
just
be
one
service
that
was
advisor.
Whole
thing
was
called
insights.
Its
purpose
in
life
is
essentially
to
prevent
that
3
a.m,
phone
call
to
identify
issues
that
might
pop
up.
But
you
know
let
you
know
about
them
before
you.
You
have
any
problems,
so
it's
got
a
big
integration
with
our
support
team.
It's
a
rule-based
type
engine
where
I
think
of
it
as
a
if
this
than
that
type
model.
Where,
if
we
know
a
situation
might
exist,
we
can
look
for
it.
A
We
can
identify
it
and
we
can
let
you
know
about
it
before
it's
impacting
within
the
rel
space.
Everything
is
a
is
part
of
insights
and
we
have
split
these
up
into
operations,
security
and
business.
If
you
look
on
those
tabs
across
the
right,
so
we've
kind
of
taken
those
out
and
parsed
them
into
themes,
hopefully
to
make
them
a
little
bit
easier
to
find
and
a
little
bit
more
of
interest
and
then
the
dashboard
itself.
A
There
is
a
lot
going
on
here,
because
there's
a
lot
of
different
things
that
we're
finding
inside
of
insights
so
again
vulnerability.
If
I
scroll
down
compliance
remediations
patch,
these
are
all
different
services
that
we
have
within
insights.
But
I'm
going
to
look
at
this
advisor
service
and
what
it's
telling
me
over
here
on
the
right-hand
panel.
I've
got
two
incidents
detected.
We
within
insights
call
an
incident,
something
that
is
actively
affecting
your
system
right
now.
So
this
is
not
a
potential
problem.
A
This
is
an
actual
problem,
that's
occurring,
so
those
are
probably
something
you
want
to
address
pretty
quickly
and
then
by
total
risk.
We've
got
a
you
know,
nine
important,
five,
moderate
issues,
and
then
I
can
see
them
by
category
down
here
as
well.
So
that
just
gives
me
a
little
bit
of
a
way
to
parse
this
information.
That's
presented
to
me
from
that
advisor
service
going
over
to
the
left
bar.
If
I
expand
out
advisor,
there's
three
different
areas.
I
can
view
this
from
the
perspective
of
a
recommendation.
A
So
if
I
want
to
look
at
a
particular
support
issue,
I
can
start
there
and
see
how
many
systems
are
impacted
by
that
issue,
or
I
could
go
to
a
systems
view.
Maybe
I
want
to
look
at
a
specific
system
and
see
what
issues
exist
or
I
could
look
at
topics
and
topics
are
essentially
things
like.
Let
me
look
at
all
issues
having
to
do
with
sap
or
microsoft,
sql,
server
or
even
ansible
automation
platform.
A
A
If
I
scroll
down
the
list
here,
I've
got
three
top
level
areas.
I
can
look
at.
My
biggest
improvement
here
around
is
around
availability.
This
affects
three
systems.
It's
one
of
the
incidents,
so
it's
actively
affecting
my
issues,
there's
also
some
important
stability
issues
that
are
shown
up
here,
so
we
can
see
what
they
are
and
we
can
also
see
whether
or
not
they
require
a
rebound
just
at
a
very
top
level.
So
again,
this
is
trying
to
guide
you
a
little
bit
into.
A
If
it
doesn't
affect
you,
do
you
really
care
to
appoint,
but
we
do
get
a
lot
of
people
that
say
how
many
recommendations
are
there,
and
where
can
I
see
the
total
list?
Maybe
I
want
to
search
to
see
if
there's
an
open,
ssh
issue
or
something
of
that
nature.
If
you
do
ever
want
to
see
the
whole
list
this
flag
right
here
system
is
impacted.
You
just
click
the
little
x
that
clears
the
filter
and
it's
going
to
show
you
everything.
A
So,
within
the
advisor
service,
we've
currently
got
1059,
enabled
recommendations
and
I
say
enabled
because
it's
also
possible
for
you
to
disable
some
of
them
notice.
I
still
have
an
enabled
filter
here.
So
if
I
wanted
to
see
the
full
list,
I
could
clear
that
filter
out
as
well,
and
then
I
see
everything
I
don't
know
if
I
have
any
disabled
or
not.
A
I'm
going
to
turn
that
back
on
systems
impacted
one
or
more,
because
I
really
only
care
about
the
ones
that
are
currently
impacting
my
systems
and
I'm
just
going
to
take
a
quick
look
at
these
notice.
I
have
the
name.
I
can
expand
one
of
the
name.
You
know
any
of
the
names
here.
I
get
just
a
little
bit
more
information
from
this
view.
A
You
can
see
how
old
it
is,
what
category
it
is,
but
all
the
way
over
here
on
the
right.
It
also
tells
me
whether
or
not
there's
an
ansible
playbook
available
to
resolve
this
issue.
So
this
one
I'm
highlighting
it's
an
incident.
It's
actually
happening
right
now,
I'm
going
to
select
it
to
go
into
a
little
bit
more
detail.
A
This
is
going
to
show
me
which
systems
are
affected
by
this
issue.
So
if
I
scroll
down
the
list
here,
I've
got
five
total
systems
and
notice.
They
vary
across
different
operating
systems.
So
here
it's
not
telling
me
how
to
fix
it,
because
the
actual
particulars
of
how
to
fix
this
issue
will
probably
differ
between
a
rel,
eight
two
system
and
a
rel73
system.
A
So
if
I
want
to
know
how
to
fix
this
issue,
I'm
gonna
have
to
go
one
level
deeper,
select
that
specific
host
and
now
this
is
going
to
give
me
that
prescriptive
level
of
information
about
this
issue
and
particularly
the
steps
to
resolve
it,
and
we
can
either
resolve
it
using
a
simple
yum
update
or,
alternatively,
we
can
go
into
the
sshd
config
here
and
we
can
change
from
the
lines
and
restart
the
service.
So
you've
got
two
different
ways
that
you
can
potentially
fix
this
issues
here,
for
this
particular
version
of
rel.
B
So
I
mean
I
love
the
the
very
tailored
guidance
on
a
release
basis,
because
things
do
tend
to
change
just
a
little
bit
from
even
you
know,
one
dot
release
to
another,
but
I
also
like
the
fact
that
it's,
it
still
leaves
the
control
in
your
hands
as
to
whether
you're
actually
going
to
jump
in
with
that
fix
or
not
because,
as
we
know,
there's
always
side
effects
right
and
you
want
to
be
able
to
have
that
opportunity
to
go
okay.
This
sounds
like
a
good
idea.
B
I
see,
I
see
the
issue
that's
being
raised.
Let
me
think
about
the
particular,
maybe
sometimes
even
ill-advised.
I
don't
know
things
that
we
might
be
doing
in
our
environment.
That
will
get
all
blown
up.
If
I
take
this
step-
and
it
gives
gives
me
as
that
person
looking
at
this
report
the
opportunity
to
go
okay,
let
me
think
about
this.
Let
me
think
it
through.
I,
you
know
I'm
not
going
to
have
to
research.
B
You
know
some
of
that
in
this
particular
case,
arcane
sshd
config,
you
know
changes
that
I
would
need
to
do.
It's
telling
me
what
to
do,
but
at
least
it
lets
so
I
I
sort
of
cut
ahead
on
the
research
part,
and
now
it's
really
is
this
something
that
actually
has
an
impact
that
I
need
to
think
about.
Okay,
I
think
this
is
good.
I
hit
go
yeah.
A
A
So
I
do
want
to
show
you
the
next
step
of
this.
Is
I've,
showed
you
hey?
Here's
how
you
look
at
a
specific
machine
and
how
you
address
it,
but
I'm
just
gonna
fix
all
of
these
systems
and
we
can
do
it
by
just
clicking
the
check
box.
I've
selected
all
five
systems,
and
I
can
click
this
remediate
button
over
here
and
what
this
is
going
to
do
is
actually
create
a
playbook.
For
me.
A
All
right
so
create
a
level
up
fix
it.
I'm
going
to
review
the
systems.
This
is
just
what
we
looked
at.
There
are
five
systems
that
are
selected
click.
Next,
it's
going
to
summarize
for
me
what
I
need
to
do
in
order
to
resolve
this.
It's
also
going
to
tell
me
that
I
do
not
require
a
reboot.
So
if
I
submit
this,
what
I've
essentially
just
done
is
created
a
playbook
within
the
insights
context,
so
this
playbook,
I
can
see
it
from
within
the
ui
I've.
A
I
clicked
the
hyperlink
and
it
just
redirected
me
on
the
left
hand,
side.
If
I
scroll
down,
there's
a
remediation
section
and
within
this
particular
playbook
I
can
again
scroll
down
here's
one
action
across
five
different
systems.
Now,
if
I
want
to,
I
could
go
and
add
a
bunch
of
other
actions
in
here.
So
if
I
want
to
fix
a
lot
of
things,
I
want
to
do
like
a
quarterly
patching
cycle.
A
Utility
to
extract
it
all
right
and
then
I'm
going
to
open
the
yaml
file,
and
hopefully
this
is
visible
on
your
screen,
but
this
is
the
playbook
that
I
just
generated
and
I
can
see
the
information
about
it.
Here's
the
host
that
I
selected,
we
do
include
in
the
event
that
you're
going
to
run
this
playbook
from
insights.
A
A
If
we
need
to
enable
any
repos,
we
would
do
that.
We
have
a
mix
of
rail,
7
and
rail
8
in
this
playbook,
so
we're
handling
both
of
these
individually
and
then
at
the
end.
What
we
do
is
we
run
insights
again
that
generates
a
new
collection,
sends
it
on
to
insights
and
that
way.
Well,
we
can
see
in
the
ui
that
we've
cleared
up
that
issue,
so
I
can
take
that
playbook
after
downloading
it,
and
I
can
use
that
playbook
on
my
own.
A
A
B
A
Yes,
so
the
execute
playbook
button
is
the
only
thing
that
I
will
talk
about
today.
That
requires
an
additional
subscription,
so
everything
else
I've
touched
everything
else
you
see
in
this
ui
is
all
part
of
insights.
It's
all
part
of
either
your
rel
subscription,
your
ansible
automation,
platform
subscription
or
your
openshift
subscription.
A
The
only
exception
to
this
is
the
execute
playbook
button.
It
requires
a
smart
management
subscription,
so
many
customers
probably
already
have
this.
If
they're
already
using
a
satellite,
for
example,
you've
already
got
smart
management,
you've
got
everything
you
need
and
what
you
would
want
to
do
is
click
this
little
doc
link
on
how
to
use
cloud
connector.
So
smart
management
currently
includes
two
components:
it
includes
satellite
and
it
includes
cloud
connector.
So
those
are
your
two
you
put
them
together
and
that
enables
this
execute
playbook
button.
A
So
what
that
really
means
is
on
the
satellite
itself.
You
just
enable
cloud
connector,
it's
a
built-in
playbook,
that's
on
the
satellite
host.
Already
you
click
it.
It
does
everything
it
needs
to
do
on
the
satellite
end
and
then
it
creates
a
connection.
Basically
a
websocket
between
your
satellite
and
insights.
A
B
A
B
A
Let's
do
it:
let's
talk
a
little
bit
just
super
quick
about
all
the
items
on
this
left-hand
side,
because
there
is
a
ton
of
stuff
and
insights
and
if
you
hear
anything
of
interest,
you
want
to
know
more
about
just
stop
me
and
ask,
but
the
drift
service
is
essentially
there
for
the
purpose
of,
I
want
to
compare
a
system
to
another
system
or
I
want
to
compare
a
system
to
a
baseline.
So
this
is
your.
You
know:
standard
operating
environment,
kind
of
methodology,
but
super
simplified.
A
Where
I
know
I
expect
a
system
to
look
like
this.
Let's
compare
to
how
it
actually
looks
like
and
you
can
even
compare
it
to
historical
profiles,
so
you
come
in
monday
morning
and
something's
not
working
and
it
worked
perfectly
fine
on
friday,
you
can
compare
the
status
of
the
system
on
monday
versus
friday
and
see
exactly
what
changed
from
like
a
package
level
that
doesn't
go
down
to
the
file
level,
though
it's
like
a
package
metadata
type
level.
B
Right
well,
okay,
so
there's
there's
a
certain
irony
here
in
that
I
think
the
more
you
actually
use
insights
and
the
capabilities
that
you
have
probably
the
less
drift
you're
going
to
have.
But
at
the
same
time
it
also
has
the
ability
to
track
that
drift
and
and
help
you
correct
when
it
does
happen.
A
Is
you
can
now
actually
subscribe
systems
to
the
baseline,
so
I've
for
this
particular
one,
which
I
call
baseless,
because
I
have
a
very
poor
sense
of
humor
and
I
subscribe
three
systems
to
it
and
then
I
get
notified
in
my
email
I
think
once
a
week
or
is
it
once
day
I
remember,
but
whenever
a
system
drifts
off
of
it,
I
get
a
notification
telling
me
that
you
know
hey.
This
system
has
changed
from
the
baseline
and
I
can
go
in
here
and
inspect
it
and
see
what's
happening.
A
Image
builder,
this
is
one
of
the
things
that's
in
a
private
beta,
so
not
everybody
is
going
to
see
it.
So
we're
not
going
to
talk
about
it
a
whole
lot,
but
the
idea
here
is
that
you
can
create
an
image
and
use
that
image
in
the
public
cloud.
So
this
is
very
similar
to
your
on-prem
image
builder
inventory.
A
This
is
a
list
of
all
of
the
hosts
that
you
have
registered
to
your
insights
environment.
This
is
my
lab
test
environment.
I
do
get
other
people
using
this
with
workshops
and
stuff,
so
I'm
only
at
20
systems
right
now,
but
it
will
balloon
up
or
down
just
depending
on
the
usage
and
from
this
inventory
you
could
actually
go
into
a
host
and
if
you
wanted
to
see
specific
findings
from
any
of
the
services
or
some
of
the
specific
facts
that
we
collect,
you
can
see
it
all
from
here.
A
C
A
Yes,
so
within
that
collection
that
you're
doing
on
insights,
we
will
definitely
be
able
to
say
hey.
You
know,
I
don't
want
anybody
to
know
about
my
networking
stack.
You
can
hide
your
entire
networking
stack
the
problem
there,
because
we
can't
give
you
any
insights
into
what's
going
on
in
that
networking
stack,
we
had
a
one
of
the
technical
account
managers
or
tams
that
we
have
at
red
hat,
told
me
a
story
about
one
of
their
customers
that
was
testing
out
insights.
A
They
got
a
notification
about
network
bonding.
Like
your
network.
Bonding
is
misconfigured
and
the
customer
is
like
you.
You
guys
need
to
check
your
software.
We
don't
use
network
bonding,
so
this
is
obviously
a
false
positive
and
he
went
let's
look
into
this.
It's
reporting
this
for
a
reason.
Let's
dig
in
a
little
bit
and
figure
out.
Why
turns
out
that
one
of
the
admins
had
accidentally
tightened
nm,
cli
command
and
partially
enabled
network
bonding
and
didn't
even
realize
it
so
wow
like
it's,
it's
those
things
that
you
don't
anticipate
like.
A
A
All
right,
I'm
going
to
jump
into
the
security
theme,
real
quick.
This
is
where
we
get
a
lot
of
interest,
and,
quite
frankly,
this
is
what
draws
a
whole
lot
of
people
to
insights.
It
was
that
conversation
that
we
had
a
little
bit
earlier
talking
about
cves
and
hey.
I
want
to
know
what
systems
are
affected
by
any
common
vulnerabilities
and
exposures.
A
This
one
of
the
new
features
is
the
known
exploit
feature
where
we
can
identify
if
any
of
your
systems
are
affected
by
a
cve
that
have
a
known
exploit.
This
does
not
mean
that
you
have
been
exploited.
This
means
that
the
particular
cve
has
a
public
exploit
available
that
somebody
could
potentially
take
advantage
of.
So
this
is
a
little
bit
higher
impact,
so
we
definitely
want
to
let
you
know
about
it.
A
You'll
also
see
something
in
here
called
a
security
rule.
This
means
that
the
cve
has
a
little
bit
more
information
where
a
team
within
red
hat
has
gone
in
really
dug
into
the
issue
and
determined
that
hey,
there's,
there's
more
here
that
we
really
want
to
tell
you
about.
This
could
be
associated
cves.
This
could
be
some
real,
specific
behaviors,
but
this
just
means
that
it's
a
cve,
that's
impactful
and
we've
done
a
lot
of
extra
due
diligence
on
it
to
inform
you
about.
A
What's
going
on
and
just
like
with
advisor
like
any
of
these
click,
the
box
click
remediate
and
we
will
be
fixing
this
stuff
for
you,
because
vulnerabilities
and
cves
tend
to
be
a
lot
deeper
scrutinized.
We
also
give
you
the
option
here
to
provide
a
business
risk
so,
like
we
say
at
red
hat
that
this
particular
cve
is
moderate,
but
maybe
you're
like
for
us.
A
A
So
that's
super
important.
We
gotta
address
that
one
and
then,
as
you
actually
go
through
the
status
of
fixing
these
issues,
maybe
boss
says
so,
but
we
we
gotta
do
a
little
bit
more
due
diligence
on
it
than
that.
Unfortunately,
so
we
can
start
it
out
in
review.
That
just
means
we're
going
through
the
process
of
looking
more
into
the
cve.
A
Maybe
then,
once
we
say
it's
good
we're
scheduling
it
for
a
patch
and
then
eventually
that
we're
going
to
resolve
this-
or
we
could
just
say,
hey
like
we're,
accepting
the
risk
we've
resolved
it
just
via
other
mitigation,
so
you've
got
the
options
to
go
in
here:
walk
through
the
cve
remediation
steps.
However,
you
like,
so
this
is
one
of
those
those
services
that
gets
a
a
lot
of
interest.
A
lot
of
scrutiny.
A
B
Just
anticipated
my
next
question,
which
was
okay,
so
we
have
these
capabilities
for
tracking
the
cves
mitigating
in
a
way
that
makes
sense
for
us,
based
on
the
the
level
of
risk.
All
of
those
kinds
of
things
somebody
outside
of
our
insights,
console
somebody
north
of
us
in
the
food
chain
in
our
in
our
in
our
corporate
organization,
reads
something
in
the
paper
and
says
I
want
to
know
what
we're
doing
about
you
know
about
vulnerabilities
here
and
maybe
everything's
very
well
in
hand,
but
you
need
to
produce
that
report.
B
A
It
and
there's
a
few
different
ways
that
we
can
do
reporting
within
insights
itself.
I
went
back
a
step
to
the
cves
any
of
these
view,
our
wysiwyg.
What
you
see
is
what
you
get.
So
if
I
go
in
here
and
I
apply
a
bunch
of
filters-
maybe
I
say
like
I-
I
really
only
want
to
see
things
with
security
rules
and
I
really
only
want
to
see
maybe
a
cvss.
That's
the
common
vulnerability
scoring
system.
I
only
want
to
see
css
issues
between
a
six
and
a
ten,
so
I'm
going
to
pick.
C
C
So
for
things
like
importance
or
criticals,
a
lot
of
times,
they're
remotely
executable
or
remotely
vulnerable,
whereas,
like
moderates
or
lows,
you
have
to
have
local
credentials
on
a
system
or
locally
running
processes
on
a
system.
So
there's
a
whole
bunch
of
of
decision
criteria
that
go
into
setting
what
these
scores
are
and
for
a
lot
of
the
products.
I
can
only
speak
for
rel.
C
C
Yep
there
is
sometimes
a
difference
between
red
hat's
cvss
score
and
like
miter's
cvss
score,
and
the
reason
for
that
is
that
our
product
security
team
will
look
at
things
and
go.
Oh,
this
is
mitigated
by
essay
linux.
So
for
us
this
is
a
moderate
or
low,
even
though
for
someone
else,
this
could
be
a
high
or
important
and
security
scanning
software
and
things
that
you
might
run
into
in
the
corporate
environment
doesn't
always
account
for
that
differential.
C
A
A
We
summarize
it
right
here
on
the
page
for
you,
but
you
can
always
click
that
question
mark
and
get
more
details
about
what
that
breakdown
is.
But
the
point
I
was
making
within
this
view,
what
you
see
is
what
you
get
at
any
point.
You
click
this
little
button.
You
can
export
it
out
to
csv
json
pdf.
So
if
you
customize
this
to
show
what
the
boss
wants,
you
can
do
it
this
way.
We
also
have
this
reports
view
and
we've
got
the
executive
report.
A
A
It
has
graph
it's
not
a
great
graph,
but
it's
got
a
graph
and
then
it's
summarizing
which
ones
and
then
I
think,
there's
another
graph
on
the
second
page.
There
you
go
so
we've
got
graft,
but,
along
with
this
executive
report,
we
know
that
some
people
want
to
see
the
data
in
a
certain
format.
We've
got
the
ability
to
create
your
own
custom
report
again.
A
I
know
we're
running
out
of
time,
so
super
quick
compliance
looks
at
regulatory
compliance.
This
is
your
things
like
your
pci,
your
hipaa,
so
you
can
compare
your
systems
against
any
of
those
regulatory
compliance.
This
is
probably
one
of
the
most
full-featured
open,
scap
reporting
compliance
services
that
we
have
anywhere
within
red
hat.
A
The
policy
service
allows
you
to
create
your
own
custom
policies,
so
these
are
things
is
the
firewall
enabled?
If
somebody
turns
that
firewall
off,
let
me
know
because
our
corporate
policy
says
that
things
turned
on
or,
conversely
do
any
systems
have
wireshark
enabled.
Oh,
we
don't
allow
that
here,
like
nobody's
sniffing
our
trap,
somebody
puts
a
wireshark
package
on
notify
me.
You
can
create
any
of
those
kind
of
things
here
as
well
and
then
patch
do
my
systems
need
patch.
Are
there
any
advisories
that
are
applicable
to
my
systems?
A
A
So,
within
the
subscription
service
we
can,
we
can
tell
you
here
like
what
subscriptions
am
I
consuming
hard
refresh
fix
that
and
it
will
actually
compare
it
to
your
subscription
threshold.
So
if
I
look
here
on
october,
20th,
I'm
using
19
public
rail,
five,
virtualized,
rail,
no
physical
rail
and
I
can
again
export
this
out.
This
makes
subscription
management
easy.
This
is
the
number
of
sockets
that
I'm
consuming
and
I
can
even
see
which
systems
are
you
know
consuming,
which
socket
and
even
in
which
public
cloud.
So
I
can
see
that
tower.
A
A
Very
nice,
and
finally,
if
you're
interested
in
this
one
we've,
we
just
spent
all
our
time
on
rel
and
we
didn't
even
mean
to
you
want
to
know
how
to
register
your
systems
to
red
hat
to
insights.
You
can
go
right
in
here
and
there's
a
pretty
much
a
guided.
Step-By-Step
choose
your
own
adventure
of
what
version
of
rel.
How
do
you
want
to
manage
the
systems
and
do
you
want
to
use
something
like
an
ansible
playbook
to
register
them?
A
A
A
So
here
I've
got
the
list
of
all
of
my
open
shift
clusters.
Let
me
see
here
I
need
to
search
for
my
dmn
cluster.
I
believe
it
is
so
if
I
go
into
my
acm
hub
for
tmm
within
the
context
of
the
cluster,
I
could
see
a
few
different
things
here,
such
as
under
monitoring.
I've
detected
an
issue,
so
this
is
part
of
our
remote
health
checks.
We've
got
high
individual
control,
plane
cpu
going
on
and
then
within
the
insights
advisor
service.
A
A
We've
got
a
system
memory
issue
here,
we've
exceeded
90
of
the
reservation
and
then
we've
got
some
prometheus
data.
So
if
I
click
into
any
one
of
these
again
view
details
and
remediation
steps,
so
I
can
see
how
to
remediate
and
the
reason
that
we've
encountered
this
issue
so
which
nodes
it's
on.
So
this
is
that
same
feel
of
the
advisor
service,
all
within
the
openshift
context.
Now
again,
I'm
in
beta.
A
The
next
thing
I'm
going
to
do
is
not
going
to
work
and
that's
expected
because
I'm
in
beta,
what
we're
trying
to
do
is
up
level
all
of
these
advisor
findings.
So
you
don't
have
to
go
into
each
individual
cluster
and
then
click
the
advisor
tab.
We're
trying
to
bring
this
into
the
left-hand
navigation
bar,
so
we've
got
advisor
listed
right
here.
So
if
I
go
into
advisor,
what
we
want
to
see
in
the
future
is
all
the
recommendations
listed.
The
way
that
I
showed
you
in
rel
right
now,
it's
not
going
to
work.
B
C
B
A
If
it
had
actually,
if
it
had
worked,
that
would
have
messed
you
up
that
would
have
come,
I
would
have
been
train
wrecked.
Yes,
I
would
not
know
what
to
do
so
yeah
these
two
aren't
working
yet,
but
we
just
want
to
highlight
that
what
we're
trying
to
do
here
is
take
all
of
these
findings
from
the
advisor
servers
for
openshift,
bring
those
up
and
make
them
easier
to
consume.
A
If
you
weren't
in
the
beta
context,
you
would
not
see
this
on
the
left-hand
nav
bar,
but
since
I
am
you
do
we
also
have
a
subscription
service
here,
much
like
the
one
that
I
showed
you
on
the
rel
end.
So
it's
a
little
bit
different,
because
rel
only
counts.
Sockets
open
shift
can
count
either
sockets
or
cores
depending
on
your
particular
subscription.
A
So
what
I'm
doing
here,
I'm
gonna
I've
got
a
ton
of
subscriptions,
I'm
not
consuming
anywhere
near
what
I
have
so
I'm
gonna
remove
the
subscription
threshold,
and
then
we
can
get
a
better
feel
for
what
I'm
consuming
so
on
october,
23rd
31
cores
today
17
cores,
and
we
can
change
this
to
a
quarterly
graph,
a
monthly
graph.
So
again,
this
just
makes
it
a
lot
easier
to
track
your
utilization
of
of
your
subscriptions
within
red
hat.
A
The
cost
management
service
is
another
one.
We
got
this
one
is
specific
to
openshift.
I
think
we're
probably
going
to
bring
it
to
rel
in
the
future,
but
this
is
hey
you're
using
this
thing
in
the
public
cloud.
What's
it
costing
me
like
what
what?
Where
are
my
costs?
Where
are
they
today?
Where
are
they
forecasted
to
be?
So
you
can
see
a
lot
of
this
information
within
the
cost
management
tool,
so
this
particular
openshift
cluster
so
far
has
cost
me
127.89,
but
we're
only
in
the
third
day
of
the
month.