►
From YouTube: Keptn Community Meeting - February 3rd, 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
How
awesome
I
guess
they
don't
need
to
watch
it?
Life
right,
I!
Think
I'm
good
with
just
me,
hello,
everyone
to
today's
community
webinar
Keplinger!
Well
within
our
February
30
2020
with
me
Jurgen
good
morning,
everyone
good
morning,
I
we're
actually
just
sitting
at
just
a
couple
of
hundred
meters
across
in
Las
Vegas,
because
we're
all
here
for
the
analyze
perform
2020.
They
put
us
in
two
different
hotels.
That's
why
we
said
we'll
just
do
it
from
the
one
from
the
east
and
gentlemen
from
the
west
side
of
the
Las
Vegas
Boulevard.
A
7
a.m.
here
in
Vegas,
hey
you
again.
We
wanna
make
this
Swift,
even
though
it's
a
lot
of
content,
but
we
want
to
go
through
it
fast.
The
main
focus
of
today
is
to
announce
and
show
captain
0.6
released
its.
It
went
GA
just
a
couple
of
days
ago,
and
we
want
to
just
introduce
the
audience.
206
show
the
highlights
and
show
a
couple
of
other
things
that
people
should
be
aware
of.
We
want
to
kick
it
off
with
right.
A
If
you
haven't
seen
it
go
to
captain
dot
SH
and
get
your
hand
on
it,
you
can
use
it
a
great
blog
post
and
actually
want
you
to
speak
to
it.
Your
one
was
called
my
top
5
favorite
improvements,
and
maybe
you
can
just
quickly
you
know
I
will
scroll
down.
Just
let
me
know
what
excites
you
about.
Oh
six,
okay,
yeah.
B
Thanks
so
406,
in
my
opinion,
there
are
a
lot
of
great
new
features
and
improvements,
but
I
just
picked
a
couple
of
them
and
roll
the
blog
about
it.
So
I
can
more
or
less
also
let
other
people
know
what
they
might
pay,
particularly
a
particular
attention
to.
But
maybe
there
are
some
other
favorites
for
for
for
others
out
there,
and
if
so,
just
let
us
know,
but
for
me,
like
the
Koala
gates,
standalone
installation
is
quite
quite
one
of
the
highlights
highlights.
B
It
really
gives
you
the
possibility
to
include
captain
in
your
own
CI
or
CD
workflow
and
just
use
the
captain
quality
gates.
The
cool
thing
here
is,
we
heard
this
from
the
community
and
we
work
together
with
the
community
to
provide
this,
and
it's
really
I
think
that's
one
of
one
of
the
first
approaches
that
how
to
kind
of
work
together
with
the
community
by
extending
and
also
adapting
captain
to
the
use
cases.
We
see
that
the
community
wants
to
have
yeah.
A
You're
going
to
actually
just
a
question
that
comes
in
and
I
think
that
actually
makes
a
lot
of
sense.
We
talk
about
stand
alone,
so
stand
alone
really
means.
Well,
you
still
install
captain
right,
but
you
give
it
the
option
with
the
use
case
flag
here
we
say
you
don't
want
to
install
full-blown
captain.
You
want
to
install
captain,
but
only
with
those
services
that
support
that
use
case
quality
gates,
as
you
just
explained,
this
is
driven
by
the
community.
That
said,
kept
this
great
end
to
end,
but
some
of
our
users
said
well.
A
We
only
need
a
particular
piece
of
it,
which
is
the
quality
gates
capability
to
integrate
it
in
existing
Jenkins
github
pipelines.
We
get
let
pipelines
there's
a
couple
of
folks
that
have
played
around
with
it.
That's
why
what
stand-alone
means?
It
just
means
you
install
captain,
but
it's
basically
a
smaller
version
of
it
that
those
has
a
smaller
footprint
that
is
arm
basically
just
providing
the
quality,
get
use
case.
B
Yes
exactly,
but
the
cool
thing
about
captain
is
when
you
install
it
and
you
use
it
fully
fledged
there's,
not
a
lot
of
configuration
you
have
to
do
so,
for
we
just
provided
a
different
version
of
the
Installer
or
a
different
version
of
captain.
So
you
can
only
use
the
quality
gates
use
case
and,
as
you
said,
it's
just
a
smaller
version
and
you
can
integrate
it
in
your
already
having
workflows
perfect.
What
about
the
next
thing?
Your
enhanced
self-healing
capabilities?
A
Is
a
CP
yeah
and
then
you
can
correct
me
if
I'm
wrong,
but
I
will
also
highlight
it
later.
You
recorded
three
new
videos:
three,
no
demo,
videos
that
are
now
on
the
captain,
YouTube
channel,
and
so
people
can
just
watch
how
the
auto
remediation
capability
and
self-healing
capability
actually
works.
So
we
also
have
the
links
in
the
proceedings
later
on
and
we'll
also
show
it.
What
is
this
here?
Captain
bridge
overhaul.
B
Yeah,
actually
that's
more
or
less
twofold,
because
the
one
thing
is
that
the
captain
bridge
the
QI,
a
version
in
0.6
got
a
big
overhaul.
So
it's
now
impossible
to
see
more
of
the
details
which,
as
willows,
have
actually
been
validated.
What
is
the
actual
result?
So
if
you
want
to
investigate
even
more,
you
can
just
click
on
all
these
click
click
on
those
buttons,
and
then
you
get
more
information
in
your
campus
bridge.
But
that's
not
the
only
thing
yes
exactly
here.
B
So
this
is
the
part
where
you
can
kind
of
investigate
a
little
bit
more
into
the
technical
details.
If
you
are
interested
in
board
well,
I
did
it
actually
fail,
for
example
the
evaluation,
but
the
captain
team
actually
is
very
busy
in
improving
it
even
more
so
there
is
now
a
new
bridge,
a
completely
new
bridge,
coming
up
a
new
version
of
it
and
we
already
have
an
early
access
program.
I
would
say
so.
We
provided
the
link
here.
There
is
a
great
documentation
available
on
the
capital
dock
section.
B
So
here
we
can
see
a
screenshot
here
and
if
you
want
to
try
it
out,
there
is
always
the
possibility
to
try
it,
but
also
go
back
to
the
previous
version
expected
yeah.
If
you
want
to
try
it
out,
give
it
a
try.
It's
here:
I,
don't
have
a
timeline
yet
when
it
will
be
GA
but
yeah,
it's
already
a
way
I
like
it
a
lot
big
fan
of
the
new
version
and
yeah.
If
you
want
to
give
it
a
try,
just
check
it
out
here.
B
So
the
kilometer
is
one
of
the
components
you
might
have
heard
already
a
couple
of
times.
It's
now,
let's
say
renamed
or
actually
superseded
by
the
lighthouse
and
the
captain.
Lighthouse
is
now
the
component
where
all
the
evaluation
basically
is
happening.
So
it's
it's
more
mature.
It
can
take
a
couple
of
different
or
you
can
fetch
data
from
a
couple
of
different
SLI
providers,
as
seen
here
in
the
picture
like
dynaTrace
premier,
first
meters
and
then
the
lighthouse
service,
we'll
do
the
evaluation
based
on
the
service
level
objectives.
B
So
it's
basically
the
implementation
of
the
captain
quality
gate.
The
lighthouse
services
also
can
be
configured
on
the
project
level,
but
you
get
also
like
if
you
already
familiar
with
the
concept
of
the
potometer
I
would
say:
there's
not
a
lot
where
you
have
to
change
like
the
mind
set
is
still
the
same.
It's
just
a
new
component
and
it
superseded
the
the
previous
pedometer
and
so.
B
A
So
it's
obviously
the
core
component
of
the
quality
gates
and,
as
you
said,
you
know,
thanks
to
all
the
feedback
we
received
from
the
community,
we
decided
to
rewrite
this
component
and
then
doing
to
include
all
the
requirements
that
we've
seen
over
the
last
couple
of
months.
Awesome
and
I
think
this
is
pretty
exciting
for
the
whole
team
right.
We
are
growing
the
community
and
we
have
been
included
in
the
CN
CF
landscape
for
F,
F
and
D
and
development.
So
I
think
that's
pretty
cool
yeah.
B
That's
really
one
of
this
really
big
achievement.
I
would
say
it's
one
of
my
favorites
I
put
it
on
the
very
last
like
to
to
end
with
the
Wow,
but
it's
that's
really
cool.
So
we
are
in
very
good,
like
in
very
good
in
the
very
good
neighborhood
of
other
CI
CD
solutions.
We
we
made
it
into
the
CN
CF
I
think
it
gives
us
great.
Great
visibility
will
grow
the
captain
community
and
yeah.
A
B
Io,
so
you
can
take
a
look
there
about
everything
that's
going
on
and
we
are
also
using
a
lot
of
other
CN
CF
projects,
so
I'm,
just
the
naming
here
held,
is
still
crowd
events.
So
if
there's
any
other
CN
CF
projects,
you
want
to
see
like
incorporated
into
Captain
or
used
by
Captain.
Just
let
us
know
we'll
take
a
look,
and
it's
just
it's
just
great-
to
see
the
captain
community
growing
and
we
have
other
contributors
that
help
us
grow
the
captain
community.
B
So
actually,
with
our
dock,
we
just
did
delay
the
last
community
meeting,
which
was
pretty
great
Citrix,
will
be
coming
up
there.
They
have
a
great
compute
contribution
in
the
works.
New
tools
were
also
also
already
guests
in
our
community
meeting.
So
yeah
awesome
we're
happy
to
see
the
family
grow,
good.
A
So
Jurgen
thanks
for
the
blog.
So
if
folks,
the
link
is
in
the
community
meeting
notes
on
the
Google
Doc,
but
you
can
also
find
it
on
median
captain
Oh
sick.
So
my
top
5
favorites.
The
next
thing
we
want
to
highlight
because
there's
also
been
a
lot
of
effort
put
in
to
make
it
easier
to
evaluate
so
I'll
have
a
look
at
captain.
So
we
have
Quick
Start
guides,
but
we
always
had
Quick
Start
guides,
but
we
updated
them
a
little
bit
and
I.
Think.
A
What's
really
cool
is,
if
you
actually
go
to
the
captain
website
when
you're
this
age,
then
you
will
notice
there's
a
new
link
called
Quick
Start,
with
credits
on
cheeky,
so
we
work
with
Google
and
if
you're
actually
evaluating
and
testing
captain
on
cheeky,
you
know
if
you
sign
up
for
a
Google
accounts,
you
actually
get
three
hundred
dollars
initial
credit
anyway,
but
then
for
the
captain
community.
You
get
an
additional
200
credits
that
you
can
apply
to
your
account.
It
seems.
A
Henrik
is
actually
working
as
you
can
see
how
they
pop
up
on
the
right
on
my
scene.
I
guess
I
need
to
turn
of
all
the
notifications
in
the
future.
Hendrik
is
also
one
of
the
contributors
of
the
captain
project.
That's
what
I
want
to
highlight
in
my
name,
so
make
sure
you
walk
through
the
the
QuickStart
guide
and
if
you
decide
to
do
it
on
cheeky,
don't
forget
about
the
$200
additional
credits.
The
other
thing
we
did,
especially
for
that
particular
you
know
it's
a
partnership
that
we
have
with
Google.
A
We
also
just
release
the
blog.
That's
actually
called
quick
start
to
autonomous
cloud
with
captain
on
cheeky
it.
Actually
it
tells
people
again.
You
know
what
is
captain
which
problems
does
it
solve,
especially
with
our
own
of
our
first
adopters
addict,
the
one
who
did
the
session
last
week
or
two
weeks
ago,
and
then
we
actually
have
the
Quick
Start
Guide
step.
One
set
up
the
cluster
install
the
CLI
and
you
can
here
are
the
videos
that
you
have
recorded
right.
A
There
embedded
there
also
in
YouTube,
but
we
kind
of
you
know
it's
a
couple
of
steps
so
install
the
cluster,
install
the
captain's
Eli
and
then
your
first
video
shows
how
to
actually
set
up
a
multi-stage,
continuous
delivery
pipeline
and
how
you
are
basically
defining
a
shipyard
file
and
then
the
pipelines
get
set
up.
How
you
deploy
a
service
then
the
second
step
would
be.
How
can
we
add
s
ellos
for
the
quality
gate
evaluation,
so
you
also
have
a
separate
video
that
is
just
focusing
on.
A
If
you
have
a
pipeline,
how
can
you
add
quality
gates
by
defining
SLI
sana
solos
and
if
the
last
step
is
enabling
all
the
remediation
again
a
separate
video
that
just
walks
through
the
use
cases
of
leveraging?
In
this
case
the
unleash
framework
to
toggle
feature
flags
in
your
app
and
in
case
you
toggle
the
feature
flag
that
in
that
causes
a
problem
later
on
for
your
users.
It's
detected
in
this
case
by
dynaTrace,
then
captain
will
auto
remediate.
A
The
problem
for
you,
so
right
have
make
sure
make
sure
you
check
out
this
blog
as
well.
It
just
came
out,
so
it's
on
the
dynaTrace
block
last
thing.
Well,
last,
actually
not
we
already
mentioned
it
really
make
sure
to
leverage
the
early
access
program
for
the
captain's
bridge,
because
it's
it's
a
major
step
forward
and
we're
just
collecting
some
last
feedback
before
I
would
assume
with
them
included
in
to
the
next
conversion
s
default
bridge
and
the
videos
here
as
well.
There
you
can
record
it
they're,
also
embedded
in
the
blog
post.
B
A
Right
cool
folks,
I'm
doing
a
quick
demo.
I
also
make
sure
that
you
ask
questions
if
you,
if
anything
comes
up,
you
know
along
the
way.
So
what
do
I
have
I
have
kept
it
installed
on
my
in
this
case,
actually
kubernetes
cluster
on
ETS
I
use
my
project
that
I
have
on
github.
It's
called
the
captain
quality
gate
project.
Here's
the
shipyard
file
right
for
those
people
that
have
never
seen
captain.
A
This
is
all
I
really
need
to
do
in
order
to
specify
what
does
my
delivery
pipeline
look
like
how
many
stages
to
have
what's
my
deployment
strategy?
What's
my
test
strategy
and
what's
my
remediation
strategy,
this
is
there's
no
other.
You
know
coding
in
pipelines
anywhere
there's
no
logic
in
in
pipeline
code.
It's
all
declarative
and,
and
captain
takes
care
of
it.
So
what
I've
done
I
have
also
enabled
dynaTrace
monitoring,
there's
also
I,
think
a
great
enhancement
with
cap.
A
A
It
will
connect
dynaTrace
alerting
with
captain,
so
everything
is
fully
done
automatically
and
the
only
thing
you
need
to
do
in
the
end
is,
if
you
have
a
new
artifact
captain
sent
event
new
artifact
for
a
particular
project,
so
I'm
using
my
simple
node
service
and
earlier
I
prepared
when
I
prepared
for
this
community
webinar
I
already
deployed,
build
1,
2,
3,
4
and
then
went
back
to
3
and
now
I'm,
just
saying,
hey
captain,
please
I
want
to
deploy,
build
4
again
of
my
version
right.
So
what
captain
will
do
now?
A
It
will,
as
you
can
see
here,
it
will
make
configuration
changes.
I've
also
set
up
the
notification
integration,
in
my
case
for
slack.
It
also
works
for
other
messaging
tools.
Like
we
heard
from
our
dock.
They
have
included
integration
with
WebEx
teams.
We
can
also
do
ms
teams
and
I
think
I'm
missing,
which
is
general
webhook.
So
you
can.
You
can
send
notifications,
so
what
captain
is
doing
in
this
case
I'm,
just
switching
over
to
my
slack
channel
I,
can
see
it
updated.
My
configuration
in
git
because
remember
we're
get
ops
driven.
A
That
means
all
the
configuration
files
that
initially
uploaded
my
helm
charts.
My
in
this
case,
my
help
charts
will
automatically
be
updated
with
the
configuration
change,
but
in
this
case
changing
it
to
version
4.
After
this,
the
deployment
should
happen
fully
automatically
triggered
and
then,
after
this,
the
test
will
happen
and
then
the
evaluation,
so
the
full
workflow
will
run
through.
B
A
A
Think
it's
well
documented.
Thanks
for
the
question.
That's
awesome,
I!
Think
if
you
go
to
let's
go.
Let's
put
this
something
away
here.
If
you
are
going
over
to
6,
install
captain,
there's
a
whole
section
on
upgrading
captain
there's
an
upgrade
from
oh
six:
oh
five,
two!
Oh
six
and
there's
also
an
upgrade
from
oh
six
beta
to
two.
Oh
six,
G
a
so
that's
all
there
for
some
questions.
Thank
you.
Alright
I
hope
so
too,
and
you
know
remind
it's
a
reminder.
You
know
put
your
questions
out
there.
A
So
what
I
want
to
show
you
I
showed
you
that
the
only
thing
that
it
is
you
know
data
is
sent
your
defect
event.
Of
course,
in
in
in
another
environment,
let's
say
typical
enterprise
environment.
You
would
probably
send
this
event,
maybe
not
for
the
CLI,
even
though
you
can
do
it.
You
would
fully
automated
this
through
web
hooks.
A
So
if
you
make
a
code,
a
configuration
change
or
if
a
new
artifact
is
built
from
your
CI,
then
at
the
end
of
your
CI
you
can
just
make
a
call
to
captain
to
kick
off
the
new
artifact
event.
Alright,
so
the
first
thing
I
want
to
show
you
is:
where
is
it
the
new
captain's
bridge,
so
here
I've
actually
already
updated
or
opted
in
for
the
new
bridge?
That
is
available?
It's
really
access
or
early
adopter
program,
as
we
call
it.
The
first
thing
that
you
will
notice
you
can
actually
select
the
project.
A
A
What's
the
last
version
that
was
actually
deployed
so
that's
great
and
if
I
open
it
up,
I
see
a
full
history,
a
full
trail
of
all
the
configuration
changes
that
have
made
so
all
the
deployments,
all
the
problems
that
have
been
detected
along
the
way-
and
you
can
you
said
you
liked
it
I
liked
it
as
well.
What
I,
particularly
like
I,
can
look
at
every
single
version
here
and
thanks
to
these
tags,
I
see.
A
How
far
did
this
version
actually
make
it
in
the
delivery
pipeline
until
you
go
to
stage
and
did
he
go
to
production?
Was
there
any
problem?
So
I
can
see
version
number
four
earlier
this
morning,
when
I
deployed
it
at
6:31,
not
sure
why
I
was
updated
really
well
that
we
know
because
of
the
community
meeting
version
four
made
it
through
staging,
but
then
in
production
had
an
issue
right.
What
I
also
like
to
see
what
I
would
also
like
about
it
on
the
right
side
now,
I
can
see.
A
Can
the
full
trace
the
full,
the
full
chain
of
tools
that
have
been
involved
in
delivering
that
artifact
through
the
different
pipelines,
so
it
started
with
staging
where
the
help
service
was
used
to
deploy.
Then
the
tests
were
executed,
I
use
jmeter
tests
after
the
tests,
the
lighthouse
service
was
retrieving
the
SL
ice,
and
then
this
is
also
new
right.
Then
the
evaluation
was
done
and
what's
nice
here,
I
can
actually
see
the
performance
output
or
in
this
case
the
the
result
of
the
quality
gate
similar
to
you
can.
A
What
you
showed
is
the
improvement
in
the
bridge
that
the
GA
s
with
with
O
six,
you
can
also
do
show
SLI.
So
that
means
you
have
to
fool
visibility
in
what
what
this
allows
were
actually
evaluated
and
what
I
also
really
like
is
this
year
you
actually
see
each
individual
metric,
each
individual
SLI
that
was
evaluated
and
also
how
it
evaluated
against
the
SLO,
whether
you
meet
the
criteria,
yes/no
and
so
on.
So
in
this
case
everything
was
good.
A
That
means
a
configuration,
change
event
was
executed
to
promote
it
to
the
production
stage,
because
I
decided
to
automate
a
promotion
and
improv
similar
thing.
Configuration
change,
so
change
things
in
get
deploy,
run
the
tests-
and
here
is
it's
interesting,
now
very
build
number
four.
In
my
case
it
has
the
problem,
a
performance
issue
in
production,
so
I
did
a
Bluegreen
deployment.
Captain
tests,
the
Bluegreen
deployment
and
then
evaluates
the
quality
gate
again,
and
the
bridge
immediately
tells
me
well
I
didn't
score
enough
points.
A
It's
really
actually
bad,
and
it
actually
tells
me
what
the
issue
was.
It
was
really
the
error
rate,
so
I
had
a
huge
increase
in
in
errors
in
my
particular
build,
and
that's
why,
at
the
end
of
the
evaluation
captain
said
well,
I'm
not
going
to
keep
this
right.
It's
discarding
this
particular
build
and
therefore
switches
back
between
blue
and
green,
blue
and
green.
All
right
makes
sense.
You
can
make
sense
future.
Yes,.
B
I
still
still
love
the
new
version
of
the
captain's
bridge.
It's
like
the
level
of
detail.
It's
not.
You
know,
oh
well,
by
all
the
information
I
think
it's
just
a
nice
way
to
reflect
what
is
really
going
on
and
also
we
have
still
the
possibility
to
drill
into
the
details
at
this
institution
exactly.
A
Now
folks,
talk
community
out
there
make
sure
that
you
try
it
out
and
you
give
us
feedback.
We
know
there's
still
ways
to
go.
We
can
make
this
much
better,
even
though
it's
already
a
great
help
from
what
we
have
before,
but
the
more
feedback
we
get,
the
better
it's
gonna
be
for
us
in
the
future.
So
what
else
do
I
have
for
you
also.
B
A
B
A
B
A
A
Perfect
cool,
so
what
I?
Basically
showing
you
is
it's
very
easy
to
set
up
captain
now,
there's
a
couple
of
more
steps,
obviously
along
the
way
to
upload
your
tests,
your
helm,
charts
and
any
other
supporting
files.
But
this
is
all
covered
in
the
tutorials
and,
as
I
said
earlier,
you
can
you
did
a
great
job
in
creating
all
these
videos,
so
it's
really
easy
to
follow
once
you've
done
it.
You
just
say
captain
there's
a
new
art
effect
and
push
it
through
I,
really
love
the
bridge
to
get
feedback.
A
I
also
really
love
my
integration,
for
instance,
with
slack
where,
with
you
know,
it
could
be
any
other
tool
through
the
notification
service
that
we
have.
The
captain
notification
service
allows
us
to
push
events
to
these
external
tools
and
you
can
push
it
as
I
said
anywhere,
because
there's
also
generic
web
hook,
integration
where
you
can
push
it
anywhere.
So
that's
great.
A
The
other
thing
is
so
captain
works
on
the
underneath,
obviously
very
closely
with
monitoring
tools
to
give
feedback
and
the
one
that
I'm
using-
and
this
is
thanks
to
dynaTrace-
who
actually
allow
us
to
do
all
this
work.
This
is
also
the
one
I
want
to
show
you,
so
what
you
also
get
with
the
dynaTrace
integration.
Once
you
set
up
captain
and
you
configure
it
for
dynaTrace,
it
will
automatically
create
dashboards
for
your
individual
captain
projects.
So
this
is
such
a
dashboard
when
I
initially
set
it
up
right
for
a
simple
project.
A
Captain
creates
this
dashboard
called
simple
project
head
captain
on
the
top.
It
gives
me
a
link
to
the
captain's
bridge
on
the
bottom
I
get
to
see
all
of
my
different
services
in
the
different
stages
right
in
this
case
the
stages
map,
my
kubernetes
namespaces,
because
the
way
cap
doesn't
it
what
I.
Additionally
added.
This
is
also
the
nice
thing
with
the
experts
in
dynaTrace.
A
You
can
obviously
customize
them
very
easily,
so
I
just
added
and
some
some
additional
synthetic
tests,
because
I
want
my
environments
to
be
constantly
evaluated
from
the
outside,
as
well,
not
just
by
the
health
checks
that
kubernetes
provides
out
of
the
box,
which
is
doing
internal
health
checks.
I
use
the
damage
with
synthetics
features
to
figure
out.
If
my
production
in
my
staging
environment
is,
is
up
and
running
all
the
time
and
on
the
bottom
you
also
get
links
to
my
actual
app
when
did
I
have
so.
These
are
the
two.
A
This
is
staging
and
production,
so
you
can
see
here
staging
build
number
four
and
in
production
it's
build
number
three.
So
it's
going
to
be.
You
know
bill
number
four.
It's
still
I
think
the
testing
phase
in
staging,
and
hopefully
by
the
end
of
this
webinar
when
the
tests
are
done
and
the
evaluation
is
done,
we
should
see
it's
being
promoted
now,
instead
of
switching
back
between
two
frames.
I
typically
use
this
here.
Right
I
have
my
two
frames
next
to
each
other
and
they
refresh
every
three
seconds.
A
So
now
it
is
four
in
staging
three
in
production
and
in
a
minute
or
two
it
should
swap
over,
wants
to
test
to
them,
while
I'm
waiting
for
this
I
want
to
show
you
a
couple
of
more
things,
because
I
think
this
is
for
a
true
good
integration
of
your
continuous
delivery
with
monitoring
the
way
captain
does.
This
is
something
we
all
need
to
think
about
doing
it.
So
I
have
my
staging
I
click
on
it
read
in
dynaTrace.
We,
let
me
just
zoom
in
a
little
bit
here
in
the
ANA
trace.
A
We
talk
about
services
that
we
detect
automatically
thanks
to
the
one
agent
that
is
automatically
also
installed
by
captain.
So
if
you
install
captain
and
enable
the
dynaTrace
integration
captain
takes
care
of
that,
the
manager
is
one
agent
gets
deployed
on
that
kubernetes
cluster
monitor
is
everything
not
only
that
captain
also
configures
all
the
tagging
rules,
so
that
means
it
passes
metadata
over
to
the
pots
about
which
project
this
container
belongs.
A
To
which
service
it
is
which
stage
it
is,
and
what
type
of
deployment
strategy
and
dynaTrace
will
automatically
pick
this
up
as
Tex
tags
in
the
ANA
trades
are
used
for
filtering,
as
well
as
for
access
control,
and
so
that's
greater
and
it.
This
is
why
I
actually
know
this
is
the
service
the
Tanager
is
monitored
for
this
particular
equipment
service
that
belongs
to
this
project
has
been
deployed
into
this
stage,
and
it's
done
with
the
thyroid
deployment
strategy.
A
On
top
of
that,
we
also
have
some
naming
rules,
so
this
makes
it
easier
for
me
to
actually
figure
out.
Okay,
simple
note,
staging
direct.
This
is
my
service
that
is
in
staging
and
last
but
not
least,
on
the
bottom
here.
I
think
this
is
what
I
want
to
say.
Very
important
captain
is
also
sending
events
to
dynaTrace.
So
every
time
we
deb
captain
execute
an
action
as
part
of
the
lifecycle
management
of
an
artifact
like
deploying
we're
starting
a
test
or
stopping
a
test
or
promoting
an
artifact.
This
event
is
automatically
sent
over.
A
This
is
part
of
the
best
practices
that
we've
came
up
with
over
the
years.
It's
all
done
automatically
right,
I
know
exactly
who
when
did
captain
deploy,
which
particular
version
in
which
particular
environment
when
what
test
started?
When
did
they
stop?
When
was
the
artifact
promoted?
Yes,
you
know
and
I
think
that's
pretty,
that's
pretty
sweet.
A
What
else
is
there
from
a
dynaTrace
perspective?
Maybe
one
last
thing
because
I
know
we
have
a
lot
of
folks
that
actually
using
dynaTrace,
if
you
do
the
deployment
events,
we
also
see
them
here
in
the
charts,
so
when
this
also
makes
it
easier
if
you're,
if
you're
analyzing
data
in
the
chart,
you
see
okay,
this
was
the
moment
when
we
deployed
this
build
versus
the
other
build,
and
the
last
thing
I
want
to
show
you
here.
A
We
also
follow
the
best
practices
we
are
executing
in
mikesh
g-meter
tests,
and
the
analyst
has
integration
options
where
the
test
tool
can
actually
pass
context.
Information
about
the
tests,
the
virtual
user
information,
the
step
name
and
so
on
the
transaction
ID
over
to
dynaTrace
is
a
logical
name.
So
this
is
actually
why,
if
you
look
at
this
here,
LS
n
and
t
SN
and
l
TN,
these
are
the
names
that
I
have
specified
in
my
test
script.
Now
we
have
integrations
with
jmeter
also
with
neo
load.
A
They
all
do
this
and
and
captain
takes
care
of
all
the
configuration
behind
the
scenes
that
everything
just
works.
All
the
box
there's
no
additional
configuration
you
need
to
set
up
in
order
for
this
integration
to
work.
So
that's
pretty
cool
right,
so
I
can
see.
Allama
individual
test
stage
is
doing
and
then
I
can
also
configure
my
slice
and
my
SLO
is
based
on
individual
tests
and
transaction
names.
So
that's
also
pretty
sweet
good.
Now,
let
me
just
go
back
to
actually
double
check
my
app.
B
Anything
else
we
have
a
question
from
the
community
yeah.
The
question
is
it's
related
to
dynaTrace,
so
all
this,
if
we
can
go
back,
maybe
to
your
Energy's
tenant
yeah
these
events,
we
can
see
it
here
as
the
gray
dots
or
also
as
the
list
on
the
service
details
yeah
if
they
are
also
used
by
Davis
by
the
dynaTrace.
A
is.
A
There's
a
couple
things
thanks
for
that.
The
first
thing
I
want
to
show
is:
if
I
go
to
my
problems
overview,
maybe
alright.
So
you
know
in
production
environments,
especially
dynaTrace,
does
a
pretty
pretty
good
job
in
you
know,
detecting
in
case
there
is
an
impact
on
angels
experience
on
your
essays
on
availability,
so
in
in
all
these
cases,
time
and
trades
opens
is
such
so-called
problem
ticket.
So
in
this
case,
at
5:42
there
was
a
problem:
open
impacted
only
two
users,
because
you
know
my
sample
a
there's,
not
a
whole
lot
going.
B
A
Still
it
detected
that
my
simple
node
staging
direct
had
an
increase
in
failure
rate
by
13%
and,
what's
now,
I
think
to
answer
this
question
on
the
root
cause
side.
I
actually
get
to
see
all
these
events,
so
in
this
case
and
I
can
see
that
it
was
billed
number
two
that
was
deployed
and
I
also
see
this
case.
It's
my
staging
environments,
I
also
see
the
additional
events
that
captain
is
sending
in
that
hey.
A
This
was
when
we
executed
the
load
test,
so
all
of
these
events
are
automatically
correlated
into
the
problem
the
dynaTrace
detects.
So
that
means
what
was
the
impacted
component
and
then
all
the
information
on
the
root
cause
side.
That
means
where
did
we
see
the
slowdown
in
the
code
and
what
else
happened
in
this
particular
environment?
In
this
case
it
would
be
all
the
events
we
were
sending
in
and
and
then
obviously
from
here.
We
can
then
directly
go
into
the
error.
A
The
Diagnostics,
its
failure
rate,
so
I
get
a
direct
link
to
well
show
me
why
all
of
these
you
know
builds
have
failed.
You
can
see
it
here
was
all
HTTP
500
errors
that
my
ape
is
throwing
and
I
also
get
to
see,
basically,
which
particular
API
endpoint.
If
you
have
multiple
API
endpoints
and
then
you
will
actually
see
error
rates
broken
up
by
by
API
endpoints
right
and
last
but
not
least,
we
also
have
the
individual
pure
paths.
A
So
this
is
the
first
answer.
How
does
Davis
use
these
events,
so
it
correlates
up
with
problems,
but
the
other
thing
that
maybe
not
everybody
unknown
is.
We
also
have
a
virtual
assistant
that
we
can
actually
see
as
the
virtual
virtual
assistant,
like
a
virtual
team
member
and,
let's
see
I,
want
to
make
sure
I'll
switch
over
to
my
environment
here,
where's,
my
guy,
so
every
every
damages
user
has
access
to
this.
Now
this
is
our
our
own
chat
interface.
A
We
have
a
select
pot,
we
have
an
Alexa
integration,
we
have
Google
assistant
and
we
have
MS
teams
integration,
so
you
can
turn
on
the
chat
pod
as
well.
Now
the
nice
thing
is,
you
can
ask
what
was
my
last
deployment
and
then
hopefully,
if
everything
works
well,
it
actually
tells
me
hey.
The
last
deployment
you
made
was
version
number
four
of
a
simple
note:
service
in
production
was
a
canary
deployment
and
then
I
can
click
on
it.
A
If
I
want
to
right,
which
means
just
do
this
click
on
it
and
it
then
directly
gets
me
to
the
particular
screen.
So
that's
another
thing
where
this
make
sense
right.
When
was
my
last
deployment,
so
I
get
this
information
then,
and
I
get
the
link,
and
the
last
thing
I
want
to
show
here
because
I
like
it
as
well,
what
is
the
respawn?
What's,
for
instance,
what's
the
response
time
of
service?
Was
he
call
again?
A
It's
the
simple
note
thought
protoss
canary
that's
why
it's
great
to
actually
have
the
nice
naming
the
the
human
understandable
naming
of
my
services
so
I.
This
is
for
me
what
I
call
monitoring
as
a
self
service
I
just
say:
hey
dynaTrace
Davis,
give
me
the
data
that
it
needs
and
I
don't
always
want
to
go
into
the
monitoring
tool
itself.
A
Yeah,
so
it's
automatically
deployed
now.
The
interesting
thing
with
build
number
four
is
and
not
sure.
If
you
want
to
wait
it
out,
but
I
can
show
you
the
history
earlier
right.
Build
number
four
is
now
deployed
blue
green.
That
means
build
number
three
in
production
is
still
there,
but
it
doesn't
receive
traffic.
So
now
captain
goes
into
this
evaluation
phase
and
tries
to
figure
out
is
to
switch
between
blue
and
green
actually
good
enough.
By
evaluating
my
solos,
my
a
solos
are
also
stored
and
maintained
in
my
git
repo,
so
that
means
for
production.
A
If
I
go
in
here
right,
this
is
my
config
repo.
Then
I
have
per
service
my
a
solos,
so
here
this
is
where
I
spot.
What
we
saw
earlier
in
the
in
the
captain's
bridge.
This
is
where
specified
in
production.
I
want
to
make
sure
that
the
error
rate
is
you
know
below
1%,
to
pass
or
below
2%
in
the
warning.
I
also
gave
error
rate
I
await
why,
with
SLI
Sonesta
lows
by
default,
every
SL
is
the
same
weight,
so
they
get
equally
treated
treated,
but
you
can
increase
the
weight
of
individual
metrics.
A
If
they're
more
important
for
you
and
for
me,
error
rate
is
very
important,
so
I
gave
it
a
higher
weight.
Okay,
so
that's
why
now
captain
will
evaluate
and
if
I
go
back
to
the
captain's
bridge
and
I
go
back
to
the
previous
example
of
building
number
four:
let's
have
a
look
at
the
current
example.
This
thing
has
refreshed
it's
currently
deployed
and
now
it's
basically
running
a
test
against
and
then
evaluating
and
I
assume
it
will.
You
know
the
same
will
happen
as
with
the
previous
time
I
deploy
build
number
four.
A
So
let
me
just
go
back
here:
let's
go
down
to
prod.
This
is
what
I
showed
you
earlier.
So
it
deployed
blue
green.
It
ran
some
tests
and
then
based
on
my
solos,
it
says:
hey,
you
know
what
error
rate
is
really
bad
and
all
red
is
very
important
for
you.
That's
why
I'm
kicking
and
kicking
this
build
back,
I'm,
discarding
it
and
we'll
switch
back.
This
is
God's
going
to
happen.
A
B
Not
right
now,
I
think
so,
I
think
it's
just
like.
We
already
presented
captain
dot,
6
beta
2
in
the
previous
meetings,
so
the
the
things
that
really
change
is
like
a
lot
of
improvements
under
the
hood.
If
it's
more
mature,
it's
more
stable,
we
showed
now
a
couple
of
like
really
new
features.
The
early
access
program
is
really
great
for
for
the
captain
bridge,
so
also
you
showed
it
because
I
think
also
EULA
you
like
it.
B
It
just
gives
a
little
bit
more
detail
while
still
providing
you
a
very
nice
navigation
through
everything
and
yeah.
As
we
can
see
here,
we
have
a
couple
of
YouTube
videos
on
our
YouTube
channel.
This
also
the
channel
where
we
broadcast
all
of
the
all
of
the
community
meetings,
and
we
put
in
here
some
tutorials
how
to
really
get
started.
So
it's
really
a
step-by-step
tutorial.
There
is.
B
We
are
really
not
skipping
anything
here.
We
might
skip
like
30
seconds
or
30
or
like
a
five-minute,
wait
time
for
class
the
provisioning
or
these
kind
of
things.
But
it's
really.
You
can
follow
this
step
by
step
and
you
didn't
it
guides
you
through
to
set
up
your
your
own
captain
cluster
and
then
find
out
awesome.
A
So,
what's
coming
up
just
some
outlook,
an
LZ
reminder
for
the
captain,
enhancement
proposal
get
repo.
So
if
you
have
enhanced
and
proposals,
please
follow
our
process
and
put
them
in
and
we
will
discuss
them.
So
in
the
next
community
meetings
we
will
see
what
a
new
enhancement
proposals
are
out
there
that
need
discussion
and
approval.
Then
we'll
do
this.
Also,
we
have
a
couple
of
things
lined
up
of
users
that
wanted
to
show
the
stuff
that
they've
been
doing
the
cleped
air
quality
gates
stand
alone
use
case.
A
We
mentioned
the
earlier
Christian
from
ERT
who
is
actually
going
to
present
this
integration
this
week
here
in
Vegas
at
the
dynaTrace
conference,
he
has
he's
agreed
on
doing
one
of
these
community
webinar,
showing
his
integration
with
KITT
lab
pipelines.
Then
you
are
working
with
so
ie
from
Citrix
on
the
slack
pot,
so
we're
going
to
have
this
as
well
and
then
Hendrik
from
neo
tests.
He
is
also
going
to
show
up
his
latest
integration
with
neo
loads
into
the
quality
gates
capability
yeah.
I
think
I
think
that's
it.
A
B
A
B
Me
just
find
it
really
quick,
so
the
next
one
is
coming
up
on.
The
19th
of
february
is
actually
in
the
city
center
of
San
Francisco,
it's
at
a
very
famous
company
called
Twitter
and
they
are
hosting
they
are
doing
their
s.
Re,
Meetup
and
I
will
talk
about,
as
always
like
site,
reliability,
engineering,
and
we
already
talked
about
this
in
meetings.
B
How
captain
targets
this?
Then
there
is
another
one
coming
up
on
the
27th
of
February
in
San
Diego,
a
cloud
native
Meetup,
so
it
will
be
with
our
friends
from
the
cat
lady's
Community
Foundation,
and
there
is
last
one
which
is
now
finalized.
It's
on
the
fourth,
no
it's
on
the
yeah,
it's
on
the
4th
of
March
and
it's
called
everything
is
broken
and
it's
in
Seattle.
B
A
Test
Buster's
in
Vienna
and
waiting
for
two
more
confirmations
in
other
cities,
but
folks
make
sure
you
check
out
they
meet
up
scene
as
well
and
I
think
the
best
to
get
to
get
to
know
about
these
is,
if
you
just
follow
the
Twitter
handle
of
of
captain,
hit
captain
project
exactly
San,
Francisco,
yeah,
perfect,
then
our
just
follow.
You
know
us
grab
my
handy
or
you
can
get
sister
for
on
Twitter
cool
your
again.
Thank
you
and
thanks
for
the
community.
Thanks
for
the
questions
and
we'll
see
you
in
two
weeks,
yeah
thank.