►
From YouTube: GitLab 14.4 Kickoff - Monitor:Monitor
Description
Monitor 14.4 Planning Issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/79
A
And
this
is
our
14
by
0.4,
kickoff,
kickoff
call
so
kind
of
gonna
just
give
a
summary
and
then
dive
into
some
details.
A
So
we
are,
we
are
kind
of
doing
just
a
general
focus
on
some
tech
debt
and
wanted
to
make
sure,
just
in
a
general
effort
that
we
are
have
a
focus
on
reliability.
We
are
almost
done
with
that,
and
then
we
will
be
wrapping
up
some
of
the
items
for
manually
created
incidents
and
lastly,
amelia
is
going
to
talk
about
some
of
the
great
things
that
she's
doing
for
ux.
A
A
We
are
going
to
going
to
surface
paging
status
on
the
incident
list,
and
this
will
help
teams
better
get
a
better
overview
of
what's
going
on
with
all
of
their
different
incidents
and
allow
for
a
little
bit
better
incident.
Triage
we're
also
going
to
be
adding
some
things
directly
to
the
incidents
themselves.
A
That'll
include
the
the
status
drop
down,
so
when
a
user
is
notified
of
an
incident
via
an
escalation
policy,
the
user
needs
a
way
to
acknowledge
or
resolve
the
page
on
the
incident,
and
then
we
are
going
to
add
escalation
policy
drop-downs
in
the
ui.
So
users,
what
we
found
is
users
need
an
ability
to
trigger
notifications
and
escalations
for
manually
created
incidents,
unlike
when
you
receive
an
alert
and
it
automatically
kicks
off
an
escalation
policy.
B
We
were
lucky
enough
to
have
one
of
the
growth
product
designers,
complete
a
ux
scorecard
for
on-call
scheduling
and
they've
highlighted
a
number
of
opportunities
for
improving
the
onboarding
experience
for
on-call
scheduling,
and
the
goal
for
these
fixes
would
be
to
reduce
the
barriers
to
adopting
on
call
scheduling
in
gitlab
and
therefore
to
increase.
Adoption
of
the
feature
set
more
generally
and
and
the
next
thing
that
we're
going
to
be
looking
at
a
little
bit
more
is
around
permissions
and
roles
in
get
lab.
B
And
this
is
going
to
be
a
longer
term
effort
that
we're
just
going
to
get
started
in
the
next
milestone
that
will
likely
have
an
impact
all
across
gitlab
as
more
customizable
roles
and
more
granular.
Permissions
are
things
that
people
have
been
asking
for
for
quite
some
time,
and
it
will
also
help
with
adoption
of
incident
management,
because
people
will
be
able
to
define
who
can
interact
with
alerts
and
incidents
within
their
organizations.
A
So
we
I'm
gonna
be
working
with
amelia
she's
gonna.
Let
me
partner
with
her.
This
is
my
first
one,
but
we're
going
to
do
problem
validation
around
slack
and
incident
management
workflows,
so
we've
heard
from
customers.
We
know
that
we
have
homegrown
tools
internally,
that
incorporate
slack
workflows
and
we
are
seeing
competitors
from
enterprise
companies
to
startups
continue
to
invest
in
slack
workflows
for
incident
management.
We
want
to
validate
that.
This
is
something
useful
to
start
defining
a
solution
that
will
work
for
our
internal
teams
and
for
customers.