►
From YouTube: GitLab 15.0 Kickoff - Monitor:Respond
A
A
These
are
previously
deprecated
capabilities
that
we
plan
to
replace
within
obstrace,
and
we
will
complete
some
cleanup
with
regards
to
gitlab
managed,
proteus
prometheus
and
their
associated,
alerting
functionality
and
kind
of
shifting
gears
and
moving
to
feature
development.
We've
been
a
little
bit
delayed
in
shipping,
the
mvc,
for
instance,
timeline.
So
we
hope
to
finally
ship
that
capability
in
15.0
and
we're
really
excited
about
this
capability
as
a
single
source
of
truth
for
any
given
instance
and
in
terms
of
stretch
goals
beyond
the
mbc.
A
So
let
me
walk
you
through
what
we're
thinking
for
incident
timelines,
real,
quick
so
for
the
nbc
we
plan
to
add
a
new
tab
in
the
incident
issue.
Types
and
you'll
be
able
to
see
the
facts
relating
to
an
incident
in
a
single
view,
and
we
believe
this
is
really
useful,
because
lots
of
activities
will
be
happening
within
the
incident
and
to
have
a
single
place
documenting
all
the
most
pertinent
facts.
A
We
hope
to
enable
the
ability
to
edit
any
items
within
the
timeline
and
do
things
like
add
instant
events
directly
from
system
notes,
such
as
when
the
incident
is
open
when
an
incident
is
closed,
a
large
status
being
updated
by
a
person
who
was
it
updated
by.
We
believe
these
are
important
things
that
feeding
to
an
incident
timeline
and
we
hope
to
automate
that,
in
terms
of
the
links
widget,
what
this
is
is
we
are
hoping
to
add
this
resource
links
that
you
see
on
the
on
the
mock-up
right
here.
A
It's
not
show
zoom
links,
slack
channels,
potentially
google
docs
as
resources
that
an
instant
response
team
need
to
respond
to
instant
and,
of
course,
this
link
switcher
can
also
be
applied
to
other
use
cases
beyond
incident,
so
we're
going
to
try
to
build
it
in
such
a
way
where
it's
a
widget
that's
available
for
incidents
and
potentially
beyond
that,
since
this
is
also
the
15.0
kickoff,
I'm
going
to
take
some
time
to
kind
of
talk
in
a
future
future
looking
way,
what's
in
our
future
for
get
lab,
monitor
response
group.
A
So,
first
of
all,
we
think
about
incident
management.
To
date,
we've
been
thinking
about
incident
management
as
a
complete
workflow
from
triggering
alert
assigning
people
to
be
on
call
when
things
happen
to
triaging
the
alerts
to
starting
an
incident
to
working
in
the
incident
to
resolving
the
incident.
This
is
a
this
is
a
pretty
comprehensive
and
large
workflow
and
certainly
having
a
single
tool
that
can
do
all
those
things
is
really
really
useful
for
potential
users.
A
What
we've
learned
and
where
we
are
currently
in
terms
of
both
product
development
and
what
we're
doing
in
gitlab
is
we
realize
that
after
alert
has
been
triggered
after
instant
responders
have
the
page?
There's
this
whole
series
of
steps
that
takes
place
in
order
to
resolve
the
incident.
We
can
call
that
process
instant
response
and
at
getlab
we're
trying
to
improve
that
internally,
so
we
get
more
efficient
in
terms
of
responding
to
incidents.
This
is
also
a
product
opportunity
that
we
have
currently
so
over.
A
The
next
few
milestones
we
really
kind
of
hope
to
double
click
into
incident
response.
We've
mapped
out
the
stages
that
any
incident
response
process
goes
to,
starting
with
preparation.
This
kind
of
exists
outside
of
that
where
the
incident
happens,
this
is
about
having
your
process
documented
and
getting
all
the
responders
ready
to
trained
and
ready
to
go.
When
an
incident
actually
happens.
First,
you
identify
where
that
incident
comes
from.
Was
it
an
alert
that
triggered
it?
Was
it
someone
reporting
it
after
that?
You
impact
you
assess
the
impact?
Is
it
to
all
your
customers?
A
What
priorities,
what
severity
is
it
after
that
you
start
investigating
what
went
wrong?
What
are
potential
ways
to
solve
or
resolve
this
incident,
and
you
start
to
contain
what
the
impact
is
eventually
leading
to
remediation
once
the
incident
is
remediated,
you
look
for
ways
to
permanently
recover
from
the
condition
and,
of
course,
that's
not
the
end
of
it
for
to
prevent
this
from
happening
again
and
to
make
your
organization
more
resilient.
A
So
this
process
is
what
we'll
be
focused
on
over
the
next
few
milestones.
In
addition
to
that,
we
are
still
going
to
focus
a
little
bit
on
continuous
verification.
Recently,
we
did
an
update
to
our
jobs
to
be
done,
and
these
really
crystallize
what
problems
we're
trying
to
solve.
What
is
continuous
verification
it
is
about
when
deploying
an
application.
A
You
have
the
knowledge,
the
information
and
the
confidence
that
your
deployment
has
gone
through
successfully,
but
beyond.
Just
knowing
that
it's
it
went
well,
it's
all
about
it's
also
about
knowing,
when
is
a
good
time
to
deploy,
and
what
to
do
when
deployments,
don't
go
well
and
the
ability
to
automate
some
of
those
processes.
So
it's
both
pre-deployment
as
well
as
post
deployment,
so
we'll
be
digging
more
into
this
problem
in
the
next
several
milestones.
One
of
our
other
teams
here
at
the
lab
will
actually
be
shipping
the
nbc
on
continuous
verification
here
fairly
soon.
A
So,
if
you're
interested,
please
take
a
look
at
group
releases.
15.0
kickoff
they'll
have
more
information
there.
Thanks
for
watching,
everyone
have
a
good
one.
Bye.