►
From YouTube: Monitor group incident management vision walkthrough
Description
GitLab Monitor group PMs and Designer walk through vision items for the Incident Management Category. Issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/41
A
Going
to
walk
through
the
four
vision
items
that
we've
created,
which
are
captured
on
this
vision
issue,
and
you
can
reference
them
here
on
this
issue-
are
the
the
four
vision
items
that
we
have
identified
along
with
the
mock-ups
clickable
prototype
and
the
figma
file.
So
all
that
information
is
visible
on
this
issue.
If
anyone
needs
it
and
I'll
start
with
this
first
vision
item-
and
I
guess
I
should
just
say
before
I
walk
through
that
all
of
this
is
the
mock-ups
are
really
to
illustrate
the
general
direction
and
idea.
A
A
We'll
have
the
the
time
stamp
and
you
know
the
system
note
or
whatever
content
will
have
some
sort
of
a
button
to
add
additional
items
to
the
timeline
if
they
want
to
and
some
different
sorting
options
and
again
these
are
all
tbc,
but
some
ideas
just
to
get
us
thinking.
You
know
sorting
by
oldest
newest
comments.
Only
I
don't
know
if
this
is
going
to
be
necessary
or
not,
but
some
people
were
saying
that
you
know
we
might
have
a
lot
of
system
notes
and
it
could
get
very
noisy.
A
Maybe
they
only
want
to
see
the
comments.
So
maybe
we
have
that
be
an
option
and
there
is
also
the
feedback
that
maybe
we
want
to
have
start
items
like
again
if
it
gets
really
noisy.
Maybe
people
want
to
star
specific
items
in
the
timeline
and
then
only
view
those,
so
that's
another
possible
option
that
we
could
do.
B
A
That
that's
a
really
great
point
and
somebody
also
brought
up
like
labels
if
somebody's,
adding
and
removing
a
bunch
of
labels,
they
don't
want
to
see
that
in
their
incident
timeline-
and
I
don't
know
how
much
granularity,
how
much
control
we
have
over
those
system
notes
and
how
easily
we
can
pull
them
in
and
out.
So
that's
definitely
like
a
technical
discussion
we'll
need
to
have,
because
I'm
not
sure
yet
any
other
thoughts
on
this
one.
A
All
right,
so,
the
second
vision
item
is
introducing
incident
reporting,
and
the
goal
here
is
to
allow
people
to
create
an
incident
report
from
an
incident
and
in
the
feedback
there's
some
discussion
about
whether
we
should
be
creating
an
incident
report
automatically
for
people
once
the
status
of
an
incident
goes
to
resolved.
For
example,
when
we've
talked
to
users,
I
don't
know
that
everyone's
going
to
want
to
do
an
incident
review
for
every
incident
that's
created,
so
I'm
not
I'm
not
sure.
A
A
So
the
initial
suggestion
for
the
kind
of
ui
interaction
would
be
to
have
a
an
additional
menu
option
here.
We
already
have
new
issue
and
promotes
epic,
but
creating
an
additional
one
for
creating
a
post,
instant
review,
and
the
hope
is
that
we
could
pull
some
of
this
incident
content
directly
into
the
incident
review
so
that
some
of
that
can
be
automated.
A
When
the
incident
report
is
created,
the
thought
would
be
that
it
would
could
create,
or
it
could
include
the
incident
timeline,
a
section
for
actions
taken
in
action
items
and
also
linked
so
linked
instance
linked
incident
reviews
things
like
that.
At
this
point
I
don't
know
if
this
should
be
an
issue
type
or
an
issue
template
an
essu
template.
Is
you
know
a
lot
easier
for,
especially
for
like
an
mvc
point
of
view,
but
an
issue
type
would
allow
us
a
lot
more
flexibility
in
terms
of
how
we
can
modify
this.
A
For
example,
if
we
have
an
issue
type,
we
can
have
these
sections
b
tabs,
which
might
be
nice
just
in
terms
of
the
incident
timeline
could
be
very
long,
and
that
could
be
a
very
long
issue
description.
If
all
of
that
content
is
in
there-
and
we
can't
do
much
with
it-
maybe
we
can
have
it
be
collapsible
or
something
like
that.
A
So
there's
there's
definitely
some
things
we'll
need
to
consider
here,
but
the
idea
is
that
we'll
include
these
three
sections
for
people
to
populate
and
as
people
are
discussing
in
the
comment
thread,
what
happened
and
what
they
did
and
the
actions
that
they
took.
The
hope
would
be
that
they
could
easily
add
those
those
discussion
points
as
action
items
or
as
action
actions
taken
and
again
I
don't
know
if
this
is
the
best
way
to
do
this.
At
this
point,
I
think
in
the
feedback
some
people
suggested.
A
A
I
think
the
idea
here
is
just
that
we
will
have
an
easy
way
to
add
these
items
from
the
discussion
up
here,
so
that
people
don't
have
to
discuss
them
and
then
like
copy
and
paste
them
up
into
the
discussion,
and
the
hope
would
also
be
that
once
this
is
the
original
incident
and
once
the
incident
report
is
created
that
it's
also
easy
to
add
things
from
the
original
incident
into
the
incident
report
again.
This
is
just
a
suggestion
to
illustrate
the
idea
at
this
point
add
action
item
to
the
review.
A
So
those
are
the
first
thoughts
on
the
incident
review
and
I
guess
one
other
thing
that
the
team
brought
up
is
a
couple.
People
brought
up
the
naming
incident
review
versus
postmortem.
I
know
postmortem
is
also
a
very
standard
term.
I
don't
know
if
we
have
thoughts
on
on
the
naming
there,
but
there
might
need
to
be
a
discussion
with
the
team
or
the
team
might
want
to
have
that
discussion
about.
B
C
B
A
We
could
certainly
make
it
easier
for
people
to
find
those
settings
and
adjust
them
and
to
add
additional
integrations
and
things
like
that
by
adding
a
button
to
the
settings
page
from
the
list
pages
in
terms
of
cleaning
up
the
settings
page
right
now
that
the
setting
settings
section
call
is
called
incidents,
but
it's
actually
all
of
the
incident
management
settings.
So
even
just
updating
that
title,
I
think,
would
be
a
big,
a
big
help.
A
We
also
have,
I
think,
two
different
sections
in
here
like
ones
what
happens
when
an
alert
comes
in
and
another
is
about
the
sla
timer,
but
all
of
those
are
just
kind
of
incident
settings,
so
we
can
kind
of
combine
those
sections
into
one
and
clean
that
up
a
bit
and
you
know
decrease
the
number
of
tabs.
I
know
there's
been
some
discussion
about
grafana.
I
thought
the
authentication
whether
it
should
exist
in
this
section.
A
A
I
would
say
that
the
introduction
of
the
search
bar
at
the
top
of
all
the
settings
page
probably
makes
that
easier
to
find,
regardless
of
where
we
have
it
now,
but
I
think
cleaning
up
this
settings
page,
I
think,
would
also
help
people
as
they're
setting
up
incident
management
and
the
third
one
is
to
introduce
incident
management
permissions.
So
for
certain
actions,
only
people
of
certain
roles
can
can
take
them,
and
I
think
this
would
be
a
pretty
huge
thing
for
for
us.
A
C
A
A
C
A
Each
section
into
each
section,
because
for
me,
that
is
assuming
that
people
are
who
are
using
the
different
pieces
of
gitlab
but
they're
only
using
one
section
of
the
navigation,
which
I
don't
think
is
the
case.
So
for
me
introducing
that
the
link
is
a
more
minimal
and
more
useful
change
than
moving
the
settings.
The
whole
settings
section
up
into
our
little
section
of
the
nav
that
feels
like
a
bigger
and
slightly
more
controversial
move
from
the
perspective
of
someone
who's
using
many
pieces
of
git
lab.
A
A
So
here's
an
example
dashboard
for
incident
management,
kind
of
telling
people
what
the
total
alerts
are
and
the
mean
time
to
resolution
and
having
some
different
metrics
and
the
sequel
report
could
perhaps
link
to
a
table
with
more
data.
So
people
can
really
dig
into
how
things
are
changing
in
tracking
over
time.
A
In
terms
of
your
incident
resolution
and
the
number
of
alerts
that
are
coming
in,
so
people
can
have
more
of
an
overview
and
right
now
I
have
this
under
analytics
section
and
there
was
some
feedback
from
the
team
that
I
think
that
that
might
not
be
the
best
place
for
it.
So
I
think
just
kind
of
flagging
that
we
will
have
to
do
some
more
investigation
in
terms
of
where
these
dashboards
should
live.
B
A
Sure,
yeah
yeah,
I
think
somebody
from
the
one
of
the
engineers
was
saying
that
that's
more
like
they
build
their
own
dashboards
there
or
something
like
that
versus
like
out
of
the
box
ones,
and
would
that
be
changing.
Changing
the
pattern
to
have
an
out
of
the
box
dashboard
there,
and
I
don't
I'm
not
sure
about
those
pieces.
Yet
I
think
we
definitely
need
to
have
more
discussion
around
that.
B
A
Sure
and
the
other
one
is
do
I
have.
I
think
I
have
both
looks
like
I've
saved
both
of
them.
Both
of
them
are
the
incident
management
dashboard
I'll
clean
that
one
up,
but
also
having
a
similar
dashboard
for
on-call
scheduling,
letting
people
know
how
many
people
have
been
on
call
how
long
they've
been
on
call
for
on
average.
In
fact,
I
probably
have
that
here,
which
I
can.
B
Yeah
super
useful
for
management
to
understand
the
load
they're
placing
on
people
and
also
really
helpful
metrics
for
looking
at
the
impact
of
new
tools
or
changing
processes
or
being
able
to
have
data
for
which
managers
can
advocate
for
those
things
for
additional
resources
or
budget
for
new
stuff.
So
cool
thanks,
amelia
sure.
C
Many
teams
now
subscribe
to
the
model
of
having
instant
budget,
so
there's
actually
a
direct
link
to
something
that's
made
a
strategic
and
financial
decision
at
the
e-group
level
and
tying
that
to
to
how
teams
are
responding
and
what
they're
spending
their
time,
how
they're
spending
that
money?
That's
a
that's
a
huge
huge
deal
and
this
to
me
this.
That
goes
directly
to
like
a
very
enterprising
set
of
features.