►
From YouTube: OpenShift Commons Briefing #87: Monitoring DevOps Tool Chain for Continuous Delivery & Feedback
Description
Companies today are facing a multitude of challenges that they need to address in order to remain competitive in their markets. The pace of change in the business environment has increased dramatically, and getting products and services out to customers quickly has never been more important. Automation of the Continuous Delivery pipeline has shown to be an important capability to enabling these initiatives, and Red Hat OpenShift has proven to be key for automating developing, deploying, and maintaining containers within the idea-to-delivery pipeline.
Another critical piece is the continuous feedback loop, in order to measure business value across the idea-to-delivery pipeline. Organizations tried to solve this problem by bringing together metrics from various tools across the idea-to-delivery pipeline, but the lack of automation made these metrics less optimal and, many times, resulted in creating silos of key metrics. Learn how CollabNet are helping customers leverage lean concepts like value stream management with OpenShift to enable continuous monitoring and feedback across their idea-to-delivery toolchains for projects, applications and services.
A
B
C
D
B
Saying
thanks.
So
what
I
like
to
do
is
start
off
with
a
company
overview
and
then
I
love
topics
I'm
going
to
talk
about
before
we
introduce
the
solution.
I
really
want
to
get
home
on
the
importance
on
I'm
staying
in
touch
service
autonomy,
the
importance
of
accelerating
this
concept
of
DevOps
idea
to
delivery
pipeline.
Why
is
that
important?
B
Why
is
it
important
to
remove
bottlenecks
and
to
really
move
that
might
is
delivery
pipeline
to
realization
next
I'll
talk
about
a
concept
that
customers
are
using
and
Industry
starting
to
use,
as
far
as
to
be
able
to
measure
that
I'm,
this
is
the
concept
of
lean
value.
Value
screen,
basically
be
able
to
measure.
D
B
Okay,
so
climbing
it
at
a
glance,
so
I'm
that's
been
around
for
founded
in
1999
massage
headquarters
in
San
Francisco
we've
been
the
leader
in
the
application,
lifecycle,
management,
agile,
devops
and
clapper
solutions.
Many
you
may
know
us
from
up
subversion
and
we
were
run
up.
The
first
open
source
version
control
solution
is
out
there
in
the
market.
We
have
over
10,000
customers
and
we
have
over
250
employees
across
the
globe
and,
of
course,
we're
a
redhead
technology
partner.
B
So
I
really
like
to
talk
about.
Yet
what
is
our
definition
around
the
DevOps?
You
know
everybody
has
their
definition
and
I
kind
of
start
off
with
the
the
camp.
The
camp
second
is
versus
that
acronym
describing
the
core
values,
the
DevOps
movement,
meaning
you
remember,
it
was
coined
by
the
Annette
words.
I
will,
as
DevOps
days
about
view
back
in
2010.
Some
of
you
may
be
of
lucky
enough
to
be
able
to
witness
that.
C
B
A
lot
of
folks
have
already
started
down
the
path
of
the
culture
aspect,
which
is
really
around.
You
know
breaking
down
these
barriers
with
the
team
and
how
to
reduce
waste
among
among
the
teams
of
the
processes
among
those
team
and
and
from
there
automation
became
perhaps
the
most
visible
aspect
of
the
DevOps
and
many
people
use
that
to
focus
on
productivity
gains
and
it's
one
of
the
main
drivers
to
top
DevOps.
But.
B
C
B
C
B
Container
based
sensor
measurement
is
one
I
really
want
to
focus
on,
because
I
think
that's
one
now
that
customers
are
really
starting
to
look
at
and
really
start
to
identify
and
measurement
is
really
around.
How
can
I
have
continuous
improvement
without
the
ability
to
measure
that
improve
right?
How
do
I
know
if
that
automation
tasks
is
really
worthwhile?
Alright,
so
it's
about
how
can.
B
This
information
collect
this
data
and
be
able
to
take
action
on
it.
Sharing
is
a
piece
where
it's
also
kind
of
core.
Now
a
lot
of
people
see
this
as
sharing
us
for
us,
not
a
vegetation
of
culture.
Similar
needs
finding
people
with
so
many
users
across
the
organization
being
able
to
capture
these
best
practices,
and
what
I
want
to
talk
about
is
how
we're
able
to
capture
these
best
practices,
but
in
context
of
your
process
and
context
of
your
tools
grow
from
improvement
and
as
all
pars
tying
into
that
that
the
measurement
enablement.
B
C
B
Words,
how
do
I
quickly
remove
the
bottlenecks,
so
that
idea
can
be
realized
by
the
customer,
because,
as
soon
as
is
realized
by
the
customer,
that's
where
the
value
comes
in
right
and
also
key
part
of
this
is
I
want
to
be
able
to
get
feedback,
so
I've
got
some
eyes
process,
not
just
feedback
from
a
customer
but
feedback
throughout
my
process.
My
dealer
I
did
two
livery
pipeline,
because
if
I
can
get
feedback,
I
can
remove
bottlenecks.
B
I
could
take
action
immediately
on
that,
it's
kind
of
similar
to
how
if
I
wanted
to
get
from
location,
a
to
location,
B
I
have
Google
Maps
and
Google
meskan,
not
that
up
for
me
and
now
our
newer
technologies
now
even
have
a
car
I
like
they
drive
it
right.
But
what
happens
when
I
have
they
have
roadblocks
in
there
right
I
know
about
those
ahead
of
time.
B
I
could
alternate
my
my
my
destination
path
there,
where
I'm
able
to
still
reach
my
destination
based
upon
the
time
that
I
have
set
I
can
optimize
that
delivery,
and
so
this
is
constantly
being
able
to
revise
its
feedback
across
this
idea
to
delivery
pipeline.
The
continues
to
improve
the
application
delivered,
the
environments
are
being
deployed
and
an
overall
application
environment
delivery
process.
B
B
B
Oh,
it's
part
of
my
value,
this
value
stream
that
we're
talking
about
you
write
all
about
how
do
I
get
that
that
requirement
and
those
requirements
quickly
into
the
hands
of
those
features
into
the
hands
of
the
customers
and
provide
that
feedback
overall.
Now
part
of
this
process
is
what
makes
this
a
little
bit
challenging
is
for
each
one
of
these
steps
that
I
have
that
I
see.
C
B
C
B
B
C
B
Of
my
development
tools,
build
tools,
release
and
release
and
deployment
capability,
especially
around
retainers
right
and
our
collecting
has
been
organizing
the
business
such
a
way
where
I
can
optimize
my
process
very
quickly,
especially
utilizing
the
source
to
image
destroyed
technology
very
quickly.
Thank
you
to
my
repository
and
getting
getting
this
application
out
and
deploy.
B
What's
key
here
is
I
have
other
tools
that
are
part
of
my
process.
I
may
sit
outside
of
the
overshift
realm
right,
but
this
key
piece
as
part
of
my
value
stream.
So
it's
very
important
for
me
to
be
able
to
connect
holistically
all
my
tools
together
in
context
with
the
overshift
platform
as
well.
What's
up
me
what
to
get
this
data
I'm
now
officially
monitoring
my
entire
tool
chain
from
planning
through
operations,
and
now
what
I
could
do
is
I
could
start
executing
rule
bonus
and
do
alerting
and
take
actions
on
this.
C
B
A
B
Looking
and
what
are
your
potential
bottlenecks
that
I
need
to
start
identify
or
looking
at
in
privity
that
are
HIPAA
naming
from
just
from
releasing
this
application?
Okay,
so
one
is
tourchiering
integration,
automation,
bin
collections.
Do
that
continuous
monitoring
piece
and
the
three
is
a
root?
Is
the
reporting
aspect?
Okay?
D
B
Got
multiple
tool
chains
and
I
got
one
that
is
utilizing
this
set
of
tool
chain,
the
first.
What
you
see
here,
I
got
a
stuck
one
s
utilizing
tool
chain.
I
may
be
leveraging
tools
that
may
be
hosted
within
overshift
or
may
exist.
That's
not
over
ship
I
have
the
connection
to
it
as
part
of
that
coding
all
the
way
to
that
monitoring
type
of
process
here.
B
But
what
what
we
allow
you
to
do
is
those
projects
and
those
applications
that
you
have
within
with
a
bishop
will
allow
you
to
group
them
together
into
value
stream
right.
So,
for
example,
we
have
pet
store
and
test
sort,
main
applications
up.
Epic,
multiple
applications
that
or
we've
entertain
multiple
projects
within
overshift
that
allow
me
to
tie
that
together.
But
what's
nice
is
I'm
tying
in
at
my
bringing
in
external
tools
into
the
mix
as
well.
Right,
like
my
planning
tools
up
top
like
my
JIRA.
A
B
Let's
say
my
operational
tools,
maybe
some
setup
tools,
maybe
ServiceNow
I,
can
now
start
bringing
them
into
the
picture
and
start
measuring
information
like
pledge
deploy
cycles
through
to
resolve
deployment,
free,
Christine
and
I
just
start.
Comparing
this
one
of
the
other
interesting
things
is
I
may
have
a
value
stream
or
just
tool
chain
here.
C
B
Red
Hat
out
of
place
Florida
table
tools
well,
so
once
you're
able
to
do
that.
What's
nice
here
is
that
I
can
have
a
dashboard
and
a
high
level
that
shows
my
planning
all
the
way
to
my
operations
in
a
current
state
here
right
so
immediately,
I
could
start
getting
alerts
for,
as
you
know,
OpenShift
just
a
sort
of
deploy
we
had
looked
like.
We
had
a
little
issue
with
kubernetes.
We
could
do
a
corrective
action
there
that
you'll
see.
B
Another
key
piece
here
is
the
rules,
but
what's
nice
here
is
that
I
can
have
rules
based
of
events
to
drive
alerts
right,
so
I
think
have
alerts
that
say:
hey
I
want
to
know
when
a
user
story
is
blocked,
right,
I
have
one
bill.
Failure,
that's
not
really
too
interesting,
but
I
have
multiple
ones.
I,
really.
B
Find
out,
what's
going
on
here,
alright
and
understand
better
I
mentioned
remediation,
tie
procedures
or
run
books
right
we're
going
to
showcase
that
I
may
want
to
open
up
a
service.
Bistec
I
may
want
to
notify
me
a
chance
of
any
of
the
conditions
of
the
rules.
I
sent
right
and
I
may
want
to
know
like,
for
example,
if
I
get
a
security.
B
In
context
of
my
about
my
process,
well
right
so
I
can
set
basically
needs
events.
I
can
set
these
rules,
and
this
is
where
the
knowledge
sharing
comes
into
play,
because
now
I
could
start
collecting
best
practices
that
I
could
use
across
my
my
tool,
changes
by
your
streams.
Well,
the
other
key
piece
of
this
is
some
metrics.
Now.
B
C
B
C
B
How
of
how
much
does
feature
that
I'm
working
on
how
much
an
extra
cost
me?
How
many
rework
is
actually
costing
me
as
well?
Information
I
can
now
have
visibility
into
I'm
across
across
that
okay.
So
what
I
want
to
do
so?
I
want
to
turn
that
over
to
to
Don,
and
what
he's
going
to
do
is
he's
going
to
do
a
walk
through
it.
B
Due
to
open
chef,
but
may
be
external
ones
that
are
not,
but
we're
still
able
to
give
you
visibility
into
it
and
then
also
linking
into
your
container
the
container
management.
So
extending
the
monarch
to
great
monitoring
that
you
already
have
within
read.
Within
the
overshift
platform,
they
stick
an
a
out
to
external
type
tools
and
bringing.
C
B
A
D
D
Right
great
so,
like
Eric,
said,
I'm
gonna
walk
through
an
end-to-end
demo,
where
we
go
through
an
entire
lifecycle
for
a
particular
feature
spanning
a
lot
of
tools.
In
this
example,
we
bring
in
tools,
of
course,
the
open
shift
platform
as
well
as
tools
outside
such
as
JIRA
Splunk
ServiceNow
and
those
types
of
things,
so
just
to
show
how
we
can
manage
through
value
streams
in
the
entire
lifecycle.
So
here
around
our
sample
application.
D
Here
we
can
see
that
it's
deployed
it's
out
to
one
pod
right
now,
and
this
is
this
is
the
application
that
will
be
interacting
with
during
this.
This
demo
now
Eric
showed
in
his
slides
our
value
stream
dashboard,
but
we
have
the
concept
of
value
stream
cards
where
I
can
quickly
see
the
value
streams
or
the
solutions
or
services
that
I'm
monitoring
with
dlm
and
I
can
see
high-level
KPIs
for
those
value
streams
to
understand.
D
You
know
how
they're
currently
performing
I
can
also
quickly
see
the
health
of
those
value
streams,
both
the
value
stream
health,
as
well
as
activity
health
value
stream.
Health
means
that
my
KPIs
are
staying
within
their
thresholds
or
their
SL
A's
activity.
Health
means
that
have
maybe
some
alerts
or
some
issues
that
have
been
identified
and
they
may
or
may
not
currently
be
impacting
my
value
stream
health.
So
this
is
the
value
stream
dashboard.
These
are
the
value
stream
cards
and
the
one
that
will
focus
on
this
demo
is:
is
the
pet
store
value
stream?
D
Maybe
some
informational
alerts
telling
me
what's
what's
taking
place,
so
this
is
that
console,
Eric
show
this
and
his
slides
as
well
and
I
can
quickly
see
in
all
the
phases
of
my
life
cycle
plan
code,
build
tests,
etc
exactly
what's
happening.
Currently,
things
are
all
green.
We've
detected
new
alerts,
so
that's
good
Eric
mentioned
rules
in
that
same
deal
in
console.
I
can
go
into
our
rules
console.
This
is
where
I
can
create
and
edit
rules
that
will
either
alert
own
events
flowing
from
the
tools
or
they
can
take
action.
D
D
So,
as
you
know
that
at
the
beginning
of
the
lifecycle
in
the
planning
phase,
there's
typically
a
tool
such
as
JIRA,
which
will
you
know,
outline
what
feature
or
fix
needs
to
take
place,
we
integrate
with
burea
and
we
have
what's
called
a
traceability
view
and
currently
it's
blank
because
we're
at
the
beginning
of
the
lifecycle.
But
at
the
end
of
this
demo,
we'll
come
back
to
this
view
and
what
you'll
see
is
all
the
events
that
were
triggered
that
we
correlated
back
to
that
user
story.
D
D
D
All
right
so
going
back
to
the
open,
shipped
console,
we
can
see
that
the
new
build
has
has
kicked
off
there.
We
see
the
build
is
running
in
a
moment,
we'll
see
the
deployment
start
to
take
place
now,
I've
made
it
to
where
it's
currently
resource
trained,
so
that
during
the
deployment
we're
actually
going
to
encounter
a
problem,
you'll
see
that
it
kind
of
got
stuck
deploying
to
the
new
pod.
D
If
we
look
at
the
alert
details,
what
we
actually
bring
in
the
knowledge
base
from
kubernetes
to
show
how
it
can
be
resolved,
of
course,
we're
going
to
autumn
remediate
that
by
d
LM
calling
kubernetes
to
perform
these
steps
will
call
the
coop
control
commands
and
do
andrey
pool
it,
and
things
like
that
which
will
then
allow
the
deployment
to
continue.
So
if
we
go
back
to
the
overshift
console,
we'll
see,
in
fact
that
it
actually
did
deploy
out
to
the
new
pods
now.
D
Build
deploy,
ok
now,
since
they
completed
successfully,
we
also
see
that
it
completed,
and
so
we
automatically
resolve
the
prior
learn
about
the
kubernetes
error,
and
we
see
that
there
was
a
successful
deployment,
do
the
open,
shipped
environment
and
that
successful
deployment
event
also
kicked
off,
match
to
rule
and
DLM
to
kick
off
a
workflow
or
script
to
execute
security
scans
against
that
new
deployment.
Here,
we're
using
zap,
which
is
kind
of
an
open
source
tool.
Diane
mentioned
earlier
aqua
security
we're
currently
integrating
with
aqua
security
as
well
as
well
as
some
others.
D
Like
contrast,
security,
though,
we
actually
kicked
off
the
security
scan.
Once
we
saw
a
successful
deployment,
we
can
go
into
details
for
one
of
those
such
as
does
app
scan
report,
and
there
you
see
a
URL.
We
can
kick
off
kick
off.
Click
on,
and
here
we
can
see
all
the
security
alerts
that
are
exceptions
that
were
detected
by
Zapp
and
look
at
the
report
as
well.
D
D
D
So
there
it
is
for
the
shop
dogs,
bad
URL,
that
we
generated,
and
if
we
go
back
again
to
DL
M,
we
will
see
as
part
of
our
value
stream
monitoring
that
ODS
did
detect
a
problem
with
our
application.
So
if
I
refresh,
we
also
see
other
events
came
in,
but
if
I
refresh
we
can
see
the
404
page
not
found
error
again
when
that
event
came
in
that
matched
a
rule
within
DLN
to
create
the
alert
as
well
as
we
created
automation,
to
automatically
open
a
service
desk
ticket
in
ServiceNow.
D
Okay,
so
we're
also
monitoring
other
events
coming
from
OpenShift,
so,
for
example,
if
auto
scales
configured
for
our
project
and
OpenShift
detects
that
memory
or
CPU
kind
of
exceeded
their
their
thresholds,
you
see
it
just
scaled
up
to
from
one
pod
to
four
pods,
and
if
I
refresh
we
see,
we
see
that
we
got
the
four
pods
notification
that
it
was
automatically
scaled.
Also
when
it
scales
back
down,
we
can
notify
about
that
and
other
and
other
things.
D
If
we
go
back
to
that
juror
user
story,
remember
I
told
you
that
when
we
looked
at
that
blank
traceability
view
now,
if
we
look
at
it,
we
can
see
all
the
events
that
occurred
as
part
of
that
lifecycle
that
we
just
went
through.
So
we
see
the
user
story,
we
see
the
commits
took
place,
the
build
the
binary.
You
know
that
it
was
deployed,
and
then
we
see
some
health
events
at
the
bottom.
You
know
that
were
generated
by
the
monitoring
tool.
D
We
talked
about
automation,
we
talked
about
monitoring
and
alerting
that
the
third
thing
that
Eric
talked
about
is
metrics.
You
know
we're
collecting
those
events
so
that
we
can
also
report
on
them.
So
here
we
can
look
at
our
reporting
dashboard.
We
see
mean
time
to
resolution
dead
cycles
to
resolution.
I
can
also
click
on
financial
analysis,
and
this
will
give
me
some
of
the
financial
reports
that
Eric
talked
about.
So
I
can
see
how
much
you
know.
Iterations
are
costing
me
based
on
the
hours
and
and
sizings
based
on
those
iterations.
D
B
The
first
one
is
I
taught
we
talked
about
that
I.
You
know
the
importance
of
accelerating
that
DevOps
idea
to
delivery
pipeline.
This
is
usage
right,
especially
as
the
drive
now
to
be
able
to
customers
now
to
be
able
to
see
very
competitive,
new
features
coming
out
capabilities
releases.
The
days
of
me,
taking
three
months
or
six
months
to
release
or
over
right
and
over
ship
now
makes
it
a
lot
easier,
especially
when
I'm
moving
into
the
newer
type
of
deployment.
A
technology
is
like
containerization
major.
B
D
D
C
B
A
B
C
B
A
I'm
really
thrilled
that
you
actually
you
came
and
did
this
because
it's
it's
been.
It's
been
very
interesting,
enlightening
because
I
actually
haven't
used,
adam2
myself
so
and
I
and
I've
always
wondered
since
you
know,
I'm
on
I'm,
at
Red,
Hat
and
I'm
always
espousing
new
technologies
and
I
constantly
see
new,
like
years
act,
securities
new
to
me
and
I'm
active
security
like
how
enterprises
deal
with
all
these.
Just
you
know
not
the
spirit
but
separate
tools
in
and
all
the
incoming
messaging.
A
You
know
and
and
alerts
and
everything,
and
so
it
always
seemed
to
me
like
that.
You
know
you
pick
your
favorites
like
Splunk
or
whatever.
It
is,
and
you
know
just
stick
with
them
and
put
this
whole
dlm
umbrella
process
that
it
is,
is
awesome
and
I
hadn't
seen
it
demo,
quite
as
obviously
successfully
on
openshift
as
I
have
today.
So
I
really
appreciate
that
the
question
I
have
is
because
there
are
so
many
tools
out
there.
A
A
D
D
We
have
to
create,
what's
called
the
transformation
so
that
we
can
take
that
raw
data
that
raw
event
from
that
tool
and
transform
it
to
an
event
that
we
understand
within
our
platform
within
our
rules
engine
and
things
like
that,
the
most
of
the
modern
most
of
the
newer
tools,
a
support
web
hook,
type
functionality-
almost
all
of
them-
support
some
kind
of
REST
API,
where
we
could
at
least
periodically.
You
know,
pull
and
go
query
for
events
that
have
happened
in
the
last
30
seconds
or
whatever.
D
A
That's
awesome
and
it
really
was
a
great
overview
for
me
and
I'm
sure
for
the
rest
of
the
audience,
because
there
were
no
other
questions
and
you
know
the
other
thing
that
was
really
impressive
was
when
you
popped
up
the
kubernetes
knowledge
base
messaging.
That's
probably
the
first
time
I've
seen
someone.
Do
it
a
decent
job
of
making
those
pop
up
at
the
right
moment.
A
That
was
that
was
great.
So
I
I
really
appreciate
you
guys
taking
the
time
today
to
walk
through
this
and
become
part
of
our
community
and
look
forward
to
seeing
more
features
and
seeing
you
at
upcoming
events
as
well,
and
when
you
have
another
release
or
another,
offering
that
you'd
like
to
walk
through
please
reach
out
and
I'm
sure
there'll
be
other
folks
who
are
interested.
If
people
want
to
get
a
hold
of
you
guys
is
there
what's
the
best
way
to
do
so
so.
B
The
best
way
to
do
so
is
I
have
our
links
here.
I'll,
link
information
here
and
if
they
dial
directly
I
think
I'm
still
sharing
is
that
there
yep
yep?
That's
it
this
way
there
and
the
first
light,
and
then
there
we
have
because
we're
technology
company
10
up
there,
where
you
can
directly
connect
to
me
for
questions.
If
you
like
well.
A
Thank
perfect
Eric.
Thank
you
very
much.
Thank
you.
Don
and
Thank
You
Franco
for
being
here
this
morning,
and
this
webinar
will
be
up
on
the
blog
that
openshift
comm
family
in
a
day
or
so,
and
we
will
get
these
links
adding
in
as
well.
So
thanks
again
and
we
look
forward
to
hearing
more
from
you
thank.