►
From YouTube: GitLab 13.9 Kickoff - Monitor:Monitor
Description
Monitor 13.9 Planning issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/49
A
Hi
everyone
and
welcome
to
the
13.9
milestone
kickoff
for
the
monitor
stage.
My
name
is
sarah
waldner
and
I'm
involved
and
I'm
the
senior
product
for
the
monitor
team
in
13.9.
We've
got
nine.
We've
got
two,
so
our
first
priority
is
going
to
be
adding
array
support
for
our
new
custom
mapping
feature
we
just
added
to
the
suite
of
integrations
available
for
alerting
sources
and
get
lab
and
then
the
other.
The
second
priority
for
13.9
is
going
to
be
a
series
of
improvements
that
we're
making
making
the
incident
management
experience
as
a
whole.
A
A
Next,
one
is
something
that
we've
heard
from
a
lot
of
users:
we've
been
gaining
significant
usage
on
the
incident
management
category
and
people
need
the
ability
to
change
the
type
of
an
issue.
So
whether
you've
created
an
issue-
and
you
meant
for
it
to
be
an
incident-
something
a
team
needs
to
respond
to,
or
someone
on
your
team
created
an
incident
by
accident.
A
The
next
improvement
for
incidents
is
simple,
but
meant
to
help
solve
the
problem
we
just
discussed,
which
was
when
you
create
a
type
of
issue,
and
you
meant
to
create
a
different
type,
we're
adding
some
clarification
when
someone
selects
the
incident
type
in
the
selector,
so
that
it's
really
clear
what
they're
creating
so
now,
when
someone
selects
incident,
they
get
this
pop-up.
That
gives
the
definition
of
how
gitlab
defines
what
incidents
are
and
links
the
documentation.
A
When
we
first
released
this
feature
set,
we
did
it
for
reporters
and
everyone
above
that,
and
we're
going
to
restrict
it
to
developers
and
up
to
help
to
reduce
the
number
of
mistakes
that
we
are
seeing.
Our
users
make
and
gather
feedback
on
that
experience,
and
last
but
not
least,
back
by
popular
demand
is
the
milestone
feature
on
issues.
There
is
a
feature
in
the
sidebar
which
allows
you
to
select
a
milestone
for
scheduling
that
issue.
A
Previously,
it
was
assumed
that
that
feature
was
not
applicable
to
incidents
and
we're
finding
that
that
is
not
the
case.
Many
response
teams
want
the
ability
to
indicate
what
time
frame
in
which
an
incident
happened
or
for
lower
severity
incidence.
The
ability
to
schedule
things
out
so
we'll
be
adding
that
back
to
incidents
in
13.9.
Thank.