►
From YouTube: GitLab 15.4 Kickoff - Monitor:Respond
Description
Monitor 15.4 Planning Issue: https://gitlab.com/gitlab-org/monitor/respond/-/issues/140
A
So
in
this
milestone,
we
are
going
to
start
the
technical
breakdown
for
our
slack
app
to
replace
woodhouse
and
we're
going
to
continue
to
iterate
on
incident
timelines.
We
have
an
mvc
that
has
been
shipped,
but
we
want
to
continue
to
do
work
on
editing
the
timeline
event,
adding
adding
a
timeline
event
from
comment,
and
we
also.
We
also
have
one
zeus
impacting
issue
that
we
want
to
make
sure
that
we
addressed
at
least
one
of
those
in
each
milestone.
A
So,
let's
dive
into
the
slack
app
this
milestone
our
goal
and
our
deliverable
is
to
have
the
technical
breakdown.
So
the
slack
app
is
a
pretty
large
piece
of
work
and
we
want
to
make
sure
before
we
start
engineering,
that
we
know
what
some
of
the
issues
could
be
and
better
understand
and
break
down
the
issues
and
the
scope.
So
this
is
this
is
our
general
template
and
sarah
will
be
working
on
that
this.
This
iteration
again
just
a
reminder.
B
Amelia
great
I'll
share
my
screen
real
quick,
so
we
talked
about
this
in
last
milestones:
kickoff
video
a
little
bit
but
in
case
you're
interested
in
checking
it
out.
Here's
where
all
of
our
issues
are
going
to
be
for
the
our
improvement
to
the
gitlab
slack
app
and
we're
essentially
going
to
be
introducing
an
incident
management
workflow
to
the
newly
updated
gitlab
slack
app
that
the
ecosystem
team
has
been
working
on
and
I'll.
B
Just
show
you
a
little
bit
about
what
that's
going
to
look
like
one
of
the
big
things
that
we're
going
to
do
is
to
allow
people
the
ability
to
easily
create
incidents
from
slack
and
again.
This
is,
as
alana
mentioned,
pulling
some
of
the
wood
house
functionality
over
in
to
get
the
product.
So
when
someone
creates
an
incident
from
slack
they'll
be
able
to
automatically
populate
that
incident
with
important
and
relevant
information,
for
example,
they
can
set
the
severity
they
can
set
the
status
pick
and
assign
an
assignee
add
labels.
B
B
When
that
incident
has
been
created,
we'll
have
an
instant
new,
instant
notification
in
slack
and
we're
also
going
to
be
allowing
people
the
ability
to
configure
a
specific
channel
for
incidents
and
separate
from
issues.
So
a
team
that
is
only
focusing
on
incidents
can
have
one
place
for
all
of
their
incident
notifications
to
appear
and
again
this
is
a
wood
house
feature
currently
that
we
are
kind
of
bringing
over
into
the
main
gitlab
slack
app
and
then
once
that
incident
is
has
been
created
from
slack.
B
Any
information
that
was
populated
from
slack
will
automatically
be
added
to
the
incident
at
the
time
of
instant
creation.
So
if
there
is
a
zoom
meeting,
room
added
or
a
slack
channel
created,
all
of
that
information
will
be
automatically
populated
in
the
incident
when
it's
created
and
then
we're
also
going
to
be
introducing
ways
to
selectively
send
content
from
gitlab
to
slack
and
from
slack
to
gitlab.
A
I'm
I'm
so
excited
about
some
of
the
stuff
that
is
in
here
and
I'm
excited
for
the
team
to
start
looking
at
and
building
slack.
So
back
to
our
planning
issue.
I
wanted
to
highlight
that
one
of
our
okrs
for
this
quarter
is
to
increase
internal
usage
for
dog
fooding
of
incident
management
features.
We
work
pretty
closely
with
our
infrastructure
team,
on
better
understanding
their
process
and
something
that
has
come
up.
A
Multiple
times
is
they're
not
able
to
use
git
lab
alerts
a
lot
of
times
they
come
in
and
they're
just
really
noisy,
and
they
don't
necessarily
have
a
good
way
to
relate
alerts
to
incidents.
So
we
are
taking
our
approach
in
doing
the
first
iteration
of
this
in
a
boring
solution
in
a
very
manual
way,
and
that
is
adding
the
ability
to
add
alerts
directly
to
incidents
so
that
way,
when
they're
using
they're
using
incidents,
they
can
see
what
alerts
are
related
to
it.