►
From YouTube: Manage Keptn with a Slackbot
Description
In this webinar, we are showcasing how to interact with Keptn via a Slackbot.
Learn how to use our Slackbot to get answers from Keptn and also to trigger tests and quality gate evaluation with all results directly delivered to Slack! No need to ever leave one of your favorite tools again.
Check out the source: https://github.com/keptn-sandbox/slackbot-service
Slides: https://dynatrace-my.sharepoint.com/:p:/p/juergen_etzlstorfer/EQ318uf0OIxDhXS8AB_8xzsBDu4IwJJ6N-WXx5_Vh3CUdA?e=GAMq56
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
A
To
another
captain
webinar
this
time
is
my
pleasure
to
have
our
friends
from
Citrix
here.
Welcome
master
welcome,
survived
great
to
have
you
here,
and
the
topic
of
today's
webinar
is
how
to
manage
captain
with
a
slack
bot.
So
we've
been
working
together
for
the
last
couple
of
months
and
we
are
happy
to
present
our
last
features
and
how
to
manage
captain
how
to
interact
with
captain
Meyer
slack
bot.
So
you
don't
have
to
leave
slack
anymore.
A
You
can
control
a
lot
of
features
of
captain
now
directly
within
your
slack
environment
and
I
know
that
Citrix
is
also
using
slack
very
heavily
in
their
own
environments,
and
they
are
also
they
have
been
presenting.
Also
at
the
diner
is
performed
conference
earlier
this
year
and
we
did
already
a
webinar,
so
they
also
earlier
this
year.
So
I'm
really
excited
to
have
you
here
again
and
to
talk
a
little
bit
about
our
newest
improvements
to
the
slack
board
and
also
a
little
bit
of
the
story
around.
A
Why
slack
is
so
important
and
why
check
ops
and
like
all
this
kind
of
automation,
is
so
important
at
Citrix.
Welcome.
Also,
everyone
in
the
is
a
webinar
participants.
Let
me
just
share
the
information
that
please
use
the
Q&A
feature
off
soon,
so
I
can
forward
the
questions
to
our
panelists
here
and
with
this
I
would
just
ask
you
Nestor
and
sorry
to
just
quickly
introduce
yourself
and
tell
us
a
little
bit
about
the
background
of
chat
offs
and
the
power
of
slack
bots
on
at
Citrix.
C
Sure
Thank
You
uragan
for
the
opportunity
and
I'm
glad
to
join
now.
My
colleague
and
a
good
friend
is
owed
him
as
well.
Well,
my
name
is
Nestor
Zapata
and
I
am
the
manager
at
Citrix
for
computing
cloud
services.
What
that
entails,
basically
is
all
of
our
global
data,
centers
or
storage
services
and
architecture,
along
with
our
private
and
public
cloud,
including
Asia,
AWS
and
juicy
team.
C
B
Thanks
Esther
thanks
Sharon,
so
I'm
so
helpless.
An
americorps
citrix
devops
in
jr
I,
mainly
focus
on
our
automation,
see
ICD
process,
ma
I
and
always
continue
to
improve
existing
processes,
Esther
and
I.
We
have
actually
worked
a
lot
on
on
chat,
ops
and
how
we
actually
implemented,
and
all
these
sort
of
things
actually
give
us
a
huge
return
and
saving
tons
of
our
words
on
daily
basis
and
yeah.
That's
it
so
I'll
hand
over
to
your
gonna
Nestor
to
continually
presentation,
yeah.
C
C
One
of
them
as
you'll
see,
is
the
automation
of
the
releases
before
it
would
take
us
hours
to
get
these
releases
out
the
door
we've
been
able
to
reduce
this
from
four
and
a
half
five
hours
now
15
20
minutes
of
our
release
has
to
be
done
and
before
we
should
do
releases
once
a
week.
Wednesday's
was
our
dear
choice.
C
Then
we
went
on
to
two
days
and
now
we're
able
to
do
releases
practically
every
day
and
in
the
lower
environments,
pretty
much
all
day
every
day,
sometimes
even
twice
within
the
hour
monitoring
as
a
social
service,
very
important
for
us
as
well
that
very
key
to
find
out
not
just
if
the
system
is
up
or
down
green
red,
but
also
empowering
the
user
or
freeing
that
data.
So
the
users
can
enable
themselves
to
be
able
to
grab
that
information
for
themselves
and
figure
out
where
their
application
stands,
how
it's
performing
all
on
their
own.
C
With
the
power
of
the
check
ups
that
we
have
and,
of
course,
integration
with
the
dynaTrace
platform
as
well
in
the
self-healing
of
the
apps
we
move
over
to
the
future.
We
move
over
into
micro
services.
We
move
over
into
cloud
the
more
environments
we
have
the
harder
it
is
to
maintain,
and
we
do
want
to
make
sure
that
we're
able
to
incorporate
aspects
of
the
self-healing,
and
we
wanted
to
do
that
right.
We
wanted
to
see
what
were
the
repetitive
tasks.
C
What
were
the
items
that
we
can
go
ahead
and
take
care
of
and
incorporate
that
in
our
chat
box
and
our
tech
operations
at
Citrix,
and
just
simply
the
automation
of
repetitive
tasks?
We
were
having
to
do
things
over
and
over
again,
and
this
could
be
scary
for
some
of
us.
As
engineer
saying
well
as
a
big
part
of
my
job
is
a
big
part
of
my
role,
if
I
automate
too
much
of
that
all
I'll
be
out
of
a
job.
C
Now,
one
of
the
things
that
we
want
to
highlight
are
the
box
that
we
have
at
Citrix.
Probably
in
the
past
we've
been
able
to
enjoy
some
of
the
presentation
we've
been
able
to
do
at
perform.
If
had
the
opportunity
to
share
these
as
well
and
one
of
them
or
well
a
few
of
them
here,
monitoring
as
a
cell
service,
and
we
see
here
the
box
that
we
have
generally.
C
C
How
was
my
service
how's
this
application
and
we
had
to
start
what
we
were
doing
figure
it
out
for
them
or
maybe
create
a
dashboard
for
them
and
get
that
information
to
them,
but
on
the
fly
we
wanted
to
make
something
readily
available
for
them
and
that's
when
we
figured
out
well,
let's
show
them
the
performance
other
specific
application.
We
were
able
to
incorporate
that
using
the
slack
part
that
we
have
here
on
Ultron
and
pulling
the
information
that
they
wanted
there
and,
of
course,
the
self-healing
of
the
applications.
C
One
of
the
things
that
we
wanted
to
highlight
there
was
the
self-healing
aspect.
It
knew
that
it
was
being
monitored.
It
knew
that
it
could
do
certain
things.
So
what
did
we
do?
Well,
we
knew
that
certain
things
could
crash
and
we
knew
that
we're
starting
it
on
the
fly,
didn't
require
a
change
of
course
and
didn't
require
for
it
to
be
done
specifically
by
human
being.
C
So
when
the
bot
realized
via
demonstrates
that
it
has
a
specific
outage,
what
we
were
allowed
to
go
ahead
and
try
to
remediate
itself
if
we
saw
other
a
specific
tea
service.
This
one
here
in
Azure
was
failing
well
Ultron.
Our
bot
would
go
out
there
and
try
to
fix
that
for
us
and
if
there
was
an
intelligence
behind
it.
If,
after
the
third
attempt
it
checked
itself,
it
said
wall
I
tried
to
fix
it,
I
did
fix
it,
we're
good
to
go.
C
If
it
did
it
after
three
times
and
it
could
not
resolve
the
issue,
well
then,
at
that
point
in
time
it
would
notify
us,
via
slack
or
via
email,
on
the
console
as
well.
He
was
the
antenna
trace
that
just
with
issue
had
not
been
resolved
just
yet,
and
all
something
very
important
and
very
beneficial
for
us
was
the
automation
of
the
performance
testing
using
the
box,
and
this
was
a
little
bit
new.
We
haven't
talked
too
much
about
this,
but
an
integral
part
of
it.
It
was
great
to
deploy
fast.
C
It
was
great
to
get
things
going,
but
what
about
the
testing
a
crucial
part
of
a
co
for
CI,
a
CD
pipeline
and,
of
course,
of
a
production
environment?
Well,
we
do
not
just
want
to
deploy
something
very
quickly.
We
also
want
to
make
sure
that
it
is
stable
and
we
are
giving
the
benefit
to
our
business
users.
You
know
customers,
both
internally
and
externally
and
with
his
automation,
we
were
able
to
have
these
spots.
Take
over
that
testing
now.
Are
we
replacing
a
testing
team?
C
We
replaced
in
a
QA
automation
team,
no,
not
quite,
but
now
we're
having
our
QA
automation
team.
Our
testers
focus
on
enhancing
their
skills,
focusing
on
enhancing
some
of
these
skills
such
that
they
have
for
automation
and
allowing
them
to
be
more
keen
on
what
they
have
to
work
on
with
the
princess
and
in
focus
was
really
important
on.
It
is
refining
that
process,
and
this
is
just
a
tool
that
allows
them
to
do
that
and
on
the
releases
for
the
Box,
something
were
very
very
proud
of.
We
were
able
to
see
their
necessity
alone.
C
We
needed
to
be
able
to
release
code
in
the
lower
environments
in
pre-production.
In
keyway,
these
developers
were
used
to
deploying
code
9:00,
10:00,
11:00
p.m.
and
9:00
when
we
had
a
shift
in
the
organization.
There's.
Oh
hey
myself
at
that
time
took
over
that
that
team
and
we
didn't
have
the
manpower
when
it
came
to
support
others
and
that
level
of
service
that
they
were
expecting
and
the
business
was
demanding
more
and
more.
We
cannot
so
developer.
C
Well,
you
can't
deploy
at
10
11
o'clock
at
night,
because
there's
nobody
available
for
you
and
you
shouldn't
be
calling
the
production
on
call.
So
we
figured
out
how
to
allow
them
to
be
able
to
deploy
via
ServiceNow
and
eventually
we
thought
that
and
integrated
into
slack
and
they
were
able
to
deploy
directly
from
slack
calling
into
service
Nam.
We
took
that
mindset
and
we
pushed
it
on
into
our
production
environment
and
what
it
does
not
I
checked
everything
the
permissions
that
you
have.
C
It
checks
whether
you're
allowed
to
deploy
into
production
using
ServiceNow
platform,
and
all
this
was
done
from
our
messaging
application
in
slack
and
with
either
that
it
gives
you
a
status
of
doing
everything.
And
again
we
went
from
deploying
once
a
week
to
not
deploying
every
day
and
taking
about
four
or
five
hours
for
deployment
to
not
reducing
twenty
thirty
minutes
into
the
application
deployment
cycle
and,
of
course,
including
testing
within
that
as
well.
C
And
we
notice
that
in
the
pre
plant
environment,
our
environments
are
being
used
to
deploy
at
all
time
during
the
night
and
multiple
times
during
certain
hours
as
well.
It
one
of
the
newest
additions
to
our
chat
office
environment
is
the
CIA
CD,
and
we
notice
here
that
we
have
a
full
end-to-end
talking
with
this
part.
C
The
integration
with
this
part
it
prepares
to
release
it,
monitor
the
forest,
create
this
branch
and
updates
these
triggers
in
the
CI
pipeline,
and
even
let's
just
know
when
it's
been
done
on
the
DevOps
pipeline,
specifically
in
Azure
DevOps
here
for
a
specific
release,
so
nothing
very
integral.
We
started
with
something
very
basic
and
that's
what
you
always
want
to
encourage.
We
started
with
something
very
basic,
such
as
checking
a
service.
Then
we
moved
on
to
wall.
A
Thank
you
so
much
Lester
for
for
sharing
your
your
story
of
Citrix
that
that's
really
impressive,
and
we
already
saw
a
couple
of
icons
there,
like
a
trip.
Backups
captain
is
also
working
with
Ezra
backups
we
saw
Jenkins
you're
using
captain
is
also
working
with
changes,
so
it's
great
to
see
also
the
ecosystem
that
you're
using
in
Citrix,
and
we
are
using
in
how
captain
how
we
want
also
captain's
integrate
into
different
kinds
of
ecosystems
that
we
we
see,
that
all
those
software
tools
and
solutions
they're
really
valid
for
big
and
huge
enterprises.
A
So
what
we
thought
about
the
last
couple
of
weeks
and
months
when
we
work
together
with
with
you
from
Citrix
how
to
actually
make
it
slack,
but
we
already
had
how
to
make
it
more
mature
how
to
making
more
useful
for
people
to
interact
with
with
capital,
and
we
thought
about
things
like
hey
captain.
What
are
my
projects?
So
if
someone
starts
to
use
captain,
maybe
he's
not
so
much
a
tech
guy
he's
not
so
much
used
to
use
a
Scylla
or
an
API.
A
So
why
not
just
use
slack
and
ask
slack
asked
why
it's
like
what
are
actually
my
projects
that
are
already
available
inside
captain?
What
are
my
onboarding
services
that
are
already
managed
by
captain
and
then
how
to
actually
get
the
evaluation
of
my
service?
What's
the
quality
of
my
service,
will
it
pass
a
quality
game?
If
I
want
to
release
it,
would
it
pass
the
coordinates
and
do
everything
inside
your
slack
that
trigger
everything
from
slack
and
get
the
results
or
a
kickback
to
slack?
A
So
you
don't
have
to
mean
it
was
like
and
also
taking
it
a
bit
further
also
trigger
captain
to
also
trigger
tests.
Fire
captain
to
tell
captain
hey
I,
just
avoid
a
new
version.
Maybe
I
did
it
with
the
bots
that
Nestor
was
just
describing
so
I
just
deployed
a
new
version,
and
now
I
want
to
ask:
how
can
he
please
trigger
some
tests
for
me
and
come
back
to
me
once
the
performance
evaluation
off
test
is
done
and
it's
ten
minutes,
it's
fine.
A
If
it's
one
hour,
it's
fine
just
send
me
the
results
directly
into
slack,
so
I
don't
have
to
wait
for
and
take
a
look
at
dashboards,
but
I
will
I
would
have
everything
inside
one
environment
and
we'll
show
this
also
in
the
demo,
but
before
the
demo.
I
just
want
to
show
a
little
bit
more
about
the
background
here,
because
you
might
have
already
kind
of
champions
pipeline.
A
Captain
will
reach
out
to
the
data
provider
and
it
can
be
improved.
Ina
trace.
You
can
be
premiered
voice.
Captain
we
don't
do
an
evaluation
of
the
quality
gate,
comparing
it
to
the
previous
runs.
Compare
me
to
the
previous
quality
then,
besides,
it
will
give
you
a
score
and
it
will
decide
if
it's
a
pass
or
a
fail
or
something
in
between
like
a
warning
and
based
on
this,
then
you
can
decide
if
you
want
to
promote
it
to
staging
or
not,
but
the
whole
evaluation
and
the
check
if
the
quality
is
actually
sufficient.
A
This
is
done
by
captain
quality
gate
based
on
service
level,
objectives
that
you
refine,
declaratively,
and
with
this
you
can
really
decrease
this
time,
where
you
will
manually
prove
it
because
you
have
to
take
a
lot
of
different
metrics.
You
can
really
decrease
this
time,
basically
coming
down
to
only
one
minute,
because
captain
will
reach
out
to
the
data
provider.
I
said
final
traits
or
parameters
will
fetch.
A
The
data
will
do
the
evaluation
and
within
mostly
within
one
minute,
to
come
back
to
you
with
the
evaluation
directly
in
slack
and
then
you
can
decide
what
to
do,
and
this
is
what
we
use
case.
We
also
want
to
demo-
and
I
think
it's
already
it's
not
yet
demo
time.
Let
me
just
explain
what
we
are
going
to
demo
and
how
we
set
it
up.
So
so
I
we'll
take
over
for
the
demo.
A
A
It's
let's
say
it's
a
small
kubernetes
cluster
within
one
binary.
We
just
use
this
as
a
runtime
for
captain
captain
was
designed
to
be
cloud
native
and
to
run
in
kubernetes
environments,
but
for
this
demo
we
only
need
the
captain
control
plane
and
extended
with
captain
services
like
a
Catholic
extension,
the
terms
of
the
slack
pot,
but
we
don't
need
a
fully
fledged
kubernetes
cluster.
So
we
just
use
a
small
Linux
box.
We
prove
our
keys
environment
up
there.
We
install
captain
in
this
environment.
A
We
extend
captain
with
a
slack
bot
and
we
have
a
very
small
demo
application.
It's
basically
just
a
shopping
cart
with
a
database
where
it
stores
all
the
items
we
put
into
it
into
the
shopping.
Cart-
and
this
is
our
demo
environment
and
we
connect
the
styling
environment,
of
course,
to
slack
so
we
can
interact
with
slack
with
this
environment.
So
now
with
this,
let
me
stop
my
sharing
and
let
me
hand
it
over
to
so
hi
and
we'll
see
a
little
bit
of
slack
all
in
action.
B
Yeah
sure
thanks
Juergen
thanks,
Nestor
I'm,
actually
sure
my
screen
and
let
me
actually
demo
what
and
you're
going
to
explain
and
of
course
all
this
inspiration
came
from
our
slack
box.
We
have
our
Citrix
and
that's
a
huge
contribution
by
Nestor
and
myself.
Do
you
have
this
up
and
running
and
so
let's
actually
work
the
bot
to
the
channel
first.
B
Okay,
part
is
already
there,
it's
complaining
to
understand
me
so
if
I
say
and
captain
at
help,
it
will
return
all
the
all
the
commands
that
can
understand
right.
So
start
evaluation
amends
it.
You
can
understand
if
we
provide
all
the
project
services
and
stay
each
information
in
there
and
also
unable
to
do
the
deployment
finish
event.
And,
of
course
we
can
carry
normal
services
get
project
service.
So
if
you
want
to
just
get
started
with
it,
I
think
the
first
come
on
is
health.
B
The
health
will
actually
gives
you
what
it
can
do,
what
functions
it
it
has
installed.
Basically,
so
if
the
first
thing
I
would
like
to
see
what
projects
are
running
am
in
my
captain,
so
if
I
say
get
projects,
it
will
return
the
project
we
have
running
right.
So
there's
two
projects
running
under
captain.
We
have
a
hipster
shop
and
sock
shop
and
also
is
it's
playing
and
what
stages
in
those
projects
right.
B
This
schooner
is
going
to
return.
It
has
a
contained
only
one
service
called
carts,
so
that's
great!
So
now,
basically
I
have
the
project
name.
Services,
name
that
I
need
in
order
to
run
the
deployment
finish
event
or
you
know,
start
evaluation
event.
So
all
the
information
that
we
have
right
from
a
slack
but
not
leaving
it.
You
know
not
limas
lag
at
all.
We
can
do
from
our
phone
as
well.
So
so
first
thing
I
would
like
to
do.
B
I
think
I
will
actually
do
the
deployment
finish
event
right
so
deployment
event
when
the
captain
Watson
raid
and
this
event
basically
gonna
send
a
clown
event
to
Captain
control
plan
and
it's
gonna
actually
and
it's
gonna.
Do
the
deployment
finished
event
and
jorgen
can
talk
more
about
later
how
this
deployment
finish
event
and
how
what
was
doing
in
the
background,
but
just
say,
let's
just
run
the
command.
So
if
I
say
deployment
finished,
project
name
is
sock,
shot
which
we
know,
because
we
just
Curie
from
the
captain
and
service
service
is
the
card.
B
What
stage
right?
So,
if
we
look
at
this
stage
and
they're
our
project
you
can
see
in
contains
the
hardening
stage,
if
we
just
give
that
stage
in
there
and
now
the
next,
we
will
have
our
performance
what
kind
of
performance
test
we
want
to
run.
So
those
performing
tasks
are
like
the
G
meter
tests
and
they
are
GM
x
files,
they're
uploaded
to
the
captain,
and
so,
if
we
so,
we
have
for
this
two
performance
tests
we
have
for
this
project
and
the
one
I
would
like
to
run
with
just
bit
quicker.
B
So
performance
underscore
light
right
and
no
I
need
to
give
the
deployment,
URL
and
so
I
happen
to
have
in
my
clipboard,
that's
the
deployment
URL,
and
so
at
this
stage
what
captain
is
gonna
do
the
captain
bar
gonna
do
is
gonna
create
the
cloud
event.
It's
gonna,
take
all
the
dis
data
and
just
send
it
to
the
captain.
You
start
the
just
to
start
those
tests
right
and
now
you
will
see
an
action
running.
A
lot
of
live
demos
are
always
risky.
Let's
do
it
so
there
you
go,
it
has
to
figure.
B
It
has
triggered
the
tests
now
in
the
background.
The
board
is
just
waiting
for
test
results
right,
but
at
I
mean
at
the
same
time
is
saying:
hey.
You
can
actually
look
all
the
progress
from
the
bridge
as
well
enemy.
The
test
fail
kind
of
returned
back,
we're
saying
with
the
result.
It
has
failed.
It
comes
with
the
bridge
URL
as
well
along
in
here,
and
we
can
actually
see
it
in
there
to
see
what
happened.
A
Yeah,
as
you
explained,
the
cool
thing
here
is
really
that
you
can
just
trigger
the
tests
and
we
have
to.
We
have
prepared
the
demo
here
to
run
two
different
kinds
of
tests,
so
it's
either
the
performance
tests,
which
is
a
full
test
with
a
couple
of
I,
think
hundreds
of
virtual
users
in
jmeter
and
the
performance
light
test
is
just
less
users
and
less
loop
count.
So
it
should
be
finishes
very,
very
fast
and,
as
we
can
see
here,
it
did
fail
and
we
can
inspect
why
it
did
fail.
A
There
basically,
two
ways:
how
to
inspect
it.
Why
it
did
fail
is
the
first
one
is
destroyed,
is
showing
us
this
right.
Now
we
can
take
a
look
in
the
captain's
bridge.
If
we
scroll
down
on
the
right
hand,
side,
we
will
see
the
evaluation
result.
We
would
see
everything
that
was
going
on
inside
captain
and
we
can
see
that
basically,
it
was
failing,
because
it
might
be
that
the
there
was
too
much
it
could
not.
Can
we
click
on
the
icon?
A
A
B
B
A
B
A
Yeah,
we
should
also
see
everything
running
in
the
captain's
bridge,
so
we
can
here
me
your
different
different
performance
tests
and
we
have
made
this
to
be
configured
within
captain
so
with
your
chain,
X
Files.
If
those
JMX
files
they
provide
some
parameters,
you
can
configure
it
by
a
captain.
So
in
this
case
it's
very
nice
to
also
tell
these
kind
of
things
within
captain
to
tell
captain.
B
Yeah,
that's
good,
so
we
run
the
normal
performance
test.
We
should
take
a
couple
of
minutes
to
run
so
the
bots
came
back
after
a
minute
saying
it
has
completed
kind
of
Garth.
Ii
got
the
results
back
again,
good.
It's
passed
right.
There
was
a
performance
test.
You
know
we
can
the
same
thing
on
the
bridge.
We
can
see
that
passed
right.
So
these
are
the
service
level
indicators.
They
were
set
it
up.
The
response
time
should
be
less
than
600
millisecond.
So
that's
good!
B
That
kind
of
fall
under
the
threshold
to
prematurely
fallen
to
threshold,
so
it
just
got
the
full
results
and
we
can
see
in
the
heat
map
the
very
last
one
passed.
So
that
is
great,
and
the
the
power
from
here
is
that
we
can
actually
do
right
from
the
slack
bot
right
and
there
is
one
more
and
evaluation
I
think
we
can
actually
start.
We
can
do
another
one
by
executing
these
chart
evaluation
event
from
the
captain
bot,
so
start
evaluation
is
just
gonna
talk
to
you
monitoring.
So
in
this
scenario,
is
a
Prometheus.
B
It's
gonna
pull
all
those
metrics
and
just
cook
those.
It's
just
gonna
just
doing
the
evaluation
or
the
performance
it
has
already
and
performance
metrics
in
there
in
monitoring.
So
this
time
it's
only
the
evaluation,
so
we
can
actually
do
that.
So
start
your
valuation
and
I'm
gonna
say
hey.
This
is
my
project
sock
shop,
service,
kala,
cart,
and
this
is
the
stage
right.
B
I
just
want
to
run
for
Allah
asks,
let's
say
10
minutes,
I
can
say
60
minutes,
I
can
say
and
then
20
minutes,
whatever
I,
like
so
I
could
say
for
last
10
minutes,
and
you
know
it
has
triggered
notes
waiting
for
all
the
results
to
come
back,
so
that
should
be
fairly
quick.
There
you
go,
I
came
back
fine
if
it's
passed
and
I
can
see
in
the
captain
bridge.
It
was
executed
331
my
time.
So
that
is
the
start.
C
A
That's
that
Devin.
Can
you
show
us
one
more
thing,
because
what
we
already
saw
how
to
trigger,
and
especially
like
that,
the
last
part
to
trigger
also
the
evaluation.
So
if
there
is
already
some,
let's
see,
there's
some
life
on
your
service
right
now,
you
don't
have
to
trigger
additional
tests.
You
want
you
just
want
to
have
the
evaluation.
How
is
my
service
behaving
right
now?
Will
it
pass
the
quality
gate?
Is
there
any
error
rate
I
should
take
care
of,
because
maybe
you
have
a
monitoring,
then
it's
not
automatically
detecting
these
kind
of
things.
A
So
in
that
matrix
we
do
have
these
kind
of
things,
but
in
chromophores
you
would
have
to
define
alerts
based
on
this.
So
if
you
say,
if
you
have
your
quality
gates
and
you
just
want
to
run
the
qualitative
elation
whenever
you
feel
like
it,
you
can
do
with
a
start
evaluation
command
in
captain,
and
you
can
also
take
a
look
at
the
very
detailed
evaluation.
If
you
scroll
up
a
little
bit,
you
might
have
seen
that
there
is
an
answer
like
the
captain.
A
A
We
are
kind
of
hiding
it
in
this
inner
reply,
so
it
doesn't
spam,
your
your
slack
conversations,
but
you
have
all
the
information
you
have
here
and
we
know
that
folks,
like
you
to
just
take
this
information
copy
paste,
it
intend
take,
take
a
detailed
look
or
just
use
this
and
do
some
more
automation
with
it.
So
you
can
actually
get
all
the
information
back
into
slack
and
you
don't.
B
And
this
JSON
we
know
this
is
not
really
that
human
friendly
to
read-
and
this
is
one
of
the
enhancement
we
will
do
and
down
the
line
just
make
it
more
friendly
to
you,
you
to
read
yeah
so
with
that
you're
gonna
do
like
to
take
over
for
the
next
I
think
for
the
slack
board
demo
wise,
we're
good.
We
were
able
to
be
able
to
do
the
health.
We'd
know
what
commands
we
can
execute.
We
started
with
our
projects.
B
We
started
with
our
service
to
see
what
services
are
in
their
project
and
then
we
were.
We
trigger
our
performance
test
by
by
triggering
the
deployment
finish
event
with
that
we
actually
run
the
evaluation
Piper
Piper
by
giving
the
number
of
minutes
the
evaluation
we
want
to
run.
So
with
that
I
will
hand
over
to
a
gherkin.
He.
A
Thinks
meanwhile,
I'm
taking
over
here
I
also
want
to
answer
one
questions
we
have
here
in
the
chat.
Where
is
the
slack
bot
actually
running,
and
can
you
already
see
my
screen
again?
Yeah
I
think
so.
So
this
lack
part
means
the
the
slack
bot
service
itself.
It's
running
in
the
keys
cluster
in
this
small
kubernetes
binary
and
I
will
show
you
how
to
actually
get
started
and
how
to
do
this
if
it
not
enters
the
question.
A
Please
leave
again
the
some
remark
in
the
Q&A
section
thanks
for
this
question
and
we
have
a
couple
of
insulation
options
for
for
our
captain
watt.
So
what
we
did
in
the
demo
is.
We
went
for
option
number
two,
but
let
me
just
explain:
option
number
one
first,
so
the
captain
slack
but
itself
lives
in
our
github
repository
in
our
captain
sandbox,
which
holds
like
new
external
services
that
interact
with
the
captain
control
plane.
So
also
the
slack
bot
service
is
one
of
those
services.
A
You
will
find
all
the
source
code
there
and
you
can
install
it
from
there,
so
we
will
provide
a
kubernetes
manifest
how
to
install
it.
The
only
thing
that
you
have
to
provide
us
basically
API
token
from
slack,
so
in
slack
you
would
create
in
slack
application
and
you
would
basically
go
for
a
bot
integration
and
you
will
create
API
token
that
you
give
to
the
slack
of
service.
So
it
can
connect
to
the
right.
It's
like
instance.
A
That's
basically
everything
you
have
to
do
and
it
was
rock
in
your
kubernetes
cluster
for
option
number
two.
We
use
a
very,
very
small,
kubernetes
cluster
and
said
our
key
is
installation
k3s,
and
this
installation
option
comes
already
with
a
CLI
flag
to
install
it
with
a
slack
bot,
and
we
just
have
to
provide
a
slack
bot.
Touken
is
an
environment
variable
that
it's
picked
up
by
the
installation
by
the
Installer
here
and
we
will
do
the
installation
with
the
slack
pod.
So
let
me
just
switch
over
through
my
tcp
instance.
A
So,
right
now,
I'm
connected
to
a
fresh
cheesy
big
instance.
There
is
nothing
running
up
here
and
what
I
want
to
do
is
I'm
going
to
install
captain.
The
latest
version
of
this
captain
on
k3s
I
will
fetch
the
Installer
I
would
put
the
installing
into
the
bash
and
I
will
execute
it
with
a
couple
of
flags
here.
A
First
I
will
install
it
with
premiere
voice,
so
I
already
have
chrome
efis
as
a
data
collector,
and
the
data
backend
I
will
also
install
it
with
slack
with
the
slack
bot
and
I
just
telling
this
installer
I'm
running
on
TCP.
So
it
knows
how
to
fetch
the
environment
variables
and
the
external
IP
address.
So
there
are
other
options
like
if
you
want
to
go
with
dynaTrace,
you
can
specify
with
dynaTrace
instead
of
with
prometheus.
If
you
want
to
install
others,
there
is
like
a
whole
Help
section
for
this.
A
So
now
what
it
does
is
it's
creating
the
keys
environment.
It's
also
installing
the
cats
and
control
plane
on
the
keys
environment.
So
it's
basically
already
rolling
out
the
Nets
operator.
Then
it's
needed
for
the
messaging
in
our
captain
environment.
So
it's
rolling
out
the
Nets
operator
which
is
going
to
next,
which
is
going
to
spin
up
the
next
server.
It
will
install
all
the
services
that
are
needed
in
the
captain
control
plane
and
it
will
go
ahead
and
create
all
the
external
services
that
has
been
defined
with
our
common
line.
A
Flags
like
the
Prometheus
and
the
slack
block,
and
we
will
be
able
to
see
once
the
slack
what
is
up
and
running.
We
will
also
see
in
our
slack
I've,
already
created
the
webinar
demo
here,
so
I've
created
the
API
token
and
a
small
application,
so
we
can
see
it's
offline
captain
bought.
This
is
the
one
that
so
I
just
showcased
and
we
have
the
webinar
demo,
and
this
is
not
running
right
now.
So,
if
I
type
something
here,
you
would
not
succeed
because
it's
not
up
and
running.
A
We
just
wait
for
the
installation
to
be
finished.
So
we
see
the
captain.
Installation
is
right.
I
forgot
to
put
on
the
stopwatch
I
assume
it's
faster
than
three
minutes.
So
now
it's
already
creating
the
slack
bot
slack
bot
is
now
being
the
slack
bot
service
is
now
being
downloaded
to
the
cluster
and
the
pot
is
coming
up.
So
we
can
actually
take
a
look.
It
was
k3s
you
to
CTL
get
parts
in
our
captain
namespace.
We
will
find
all
the
services
that
have
been
installed.
A
You
will
also
get
a
couple
of
tokens
you
will
find
here.
So
no
needs
to
take
a
look
at
these
tokens
and
use
them
afterwards,
because
I
will
destroy
the
instance
right
after
the
webinar,
but
we
can
see
the
slack
bot
services
right
now.
It
will
fetch
the
the
container
image
and
it
will
spin
up
the
pot
for
us
all.
The
other
services
are
already
running
slack
book
service
was
just
the
last
one
that
has
been
invoked
to
start.
A
Let's
check
again
it's
already
running
and
we
should
be
able
to
see
in
slack
now
it's
up
and
running
and
I
can
ask,
as
also
where
it
showed
you
I
can
ask
the
help.
I
can
do
the
help.
Function
and
I
can
also
ask
for
all
the
projects
that
are
already
on
boarded
and
I.
Think
it's
no
surprise
that
it
says
no
projects
found
it's
a
fresh
installation,
so
there
right
now
no
projects
but
from
a
very
fresh
Linux
box.
A
C
A
B
Just
want
to
say
this
installation
is
so
great
when
this
is
so
handy
when
I
think
the
previous
Jurgen,
the
initial
installation.
We
did
remember
the
amount
of
configuration
we
had
to
done.
You
know
all
those
EML
files,
and
you
know
this
actor
thing
insulin
just
with
adding
a
one
extra
flag
and
it
will
give
you
the
full
board.
Installation
I
think
this
is
really
awesome.
Yeah.
A
Yeah
I
also
really
happy
to
have
this
installation
option.
We
still
provide
the
previous
installation
option
with
the
manifest.
If
you
want
to
install
it
in
your
already,
existing
command
is
clustered.
You
can,
of
course,
do
this
everything
that
we
have
showcased
today.
You
will
find
it
in
the
git
repository.
So
take
a
look
at
the
slack-jawed
service.
In
our
git
repository,
you
will
find
all
the
environment
variables
you
can
set,
or
some
of
those
you
have
to
provide,
like
the
slack
token,
of
course,
otherwise
without
the
API
tow
and
it
won't
work.
A
But
if
you
have
some
ideas
how
to
extend
it,
we
got
some
requests
that
we
should
do
a
little
bit
of
improvement
of
the
of
the
payload
of
the
actual
cloud
events
to
make
a
little
bit
more
human-friendly
I've
already
explained
this,
so
we
will
take
care
of
this,
but
just
visit
us
or
visit
this
project
on
on
github.
Also,
let's
star
us
on
github
or
just
leave
an
issue.
There
leave
a
comment
there.
Let
us
know
which
improvements
you
would
like
to
see
when
you're
using
this.
A
Also,
if
you
want
to
get
in
touch
with
our
captain
developers,
if
all
the
with
all
the
friends
of
Captain
using
captain
and
all
this
kind
of
eco
circo's
ecosystem
services
like
blackboard
or
tea,
video
services
or
DevOps
integration,
effort
level
situation,
then
you
will
find
all
of
them
all
those
folks
on
slack
captain
dot
SH,
that's
our
officials
like
channel.
You
will
also
find
us
on
Twitter.
We
have,
of
course,
our
website,
and
if
you
want
to
learn
how
to
use
captain,
take
a
look
at
our
new
tutorial
help.
A
C
A
To
bring
a
full
kubernetes
cluster
in
basically
any
valid
it
can
be
in
TCP
aw.
Yes,
sure
we
can
be
an
open,
shipped
cluster.
You
will
bring
your
own
kubernetes
cluster
and
you
will
install
the
captain,
control,
plane
and
execution
plane
on
this
panellist
cluster,
and
then
you
can
add
more
services
like
the
slack
bolt,
so
you
just
go
ahead.
First,
install
captain
with
the
captain's
you
lie
and
then
install
the
slack
bot
service
with
the
kubernetes
manifest.
B
A
Yeah,
of
course,
the
another
question
everything
also
reflect
what
service
is
open
source.
So
all
the
source
is
available
on
github
thanks.
So
much
sorry
for
for
doing
a
lot
of
work
on
the
slack
bot
and
I
think
we
also
happy
to
receive
more
input
from
the
community
feedback
from
the
community.
So,
if
there's
anything,
you
would
like
to
see
just
let
us
know
with
this
I'm
just
trying
to
get
to
post
a
sharing
here
and
to
get
the
final
link
to
also
share
the
slides
people
requested
to
also
take
a
look
at
the
slides.
A
That's
of
course,
we
are
happy
to
also
provide
the
slides
here.
Let
me
just
put
in
a
link
to
the
slides
into
the
chat
box,
and
with
this
you
have
thanks
a
lot
so
I,
even
thanks
a
lot
Nestor
for
joining,
which
is
trying
to
find
if
there
are
more
questions,
just
ask
them
in.
Please
ask
them
in
the
chat
or
in
the
Q&A
section.
By
the
way,
this
webinar
will
also
be
life,
has
been
recorded
and
will
be
on
YouTube,
together
with
our
other
webinars
and
with
this
I
think
we
are.
C
We're
good
here,
I'm,
just
a
point
of
advice,
start
small.
It's
a
lot
of
cool
things.
We've
been
able
to
do,
but
it
was
a
lot
of
work.
Like
you
mentioned
your
again,
they're,
not
a
work
with
sohave.
A
lot
of
more
team
members
involved
were
just
representing
here
that
part
of
the
organization,
so
starting
small,
taking
the
baby
steps.
If
you
will
and
then
moving
on
to
the
bigger
and
greater
things,
and
that
way
you
don't
get
discouraged
on
doing
that,
but
reach
out
to
any
of
us.
B
That's
great,
that's
great
advice
by
Nestor,
that's
exactly
when
we
started
developing
Ultron
and
Nestor
and
I
we
used
to
cuddle.
If
you
discuss
what
use
cases,
we
need
to
implement
I
think
that's
a
great
wise,
I'll.
Just
start
very
small,
a
very
you
know
a
small
use
case
that
just
gives
your
you
know,
hands
dirty
feet
and
then
you
just
add
on
the
top
of
it.
So
that's
great
blows
thanks,
Esther
and
yeah,
nothing
for
me,
I'm
good.