►
From YouTube: GitLab 13.7 Kickoff - Monitor:Monitor
Description
Planning issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/42
A
A
Being
the
person
who
is
responsible
for
helping
restore
service,
outages
is
called
being
on
call
when
a
team
member
is
on
call,
they
need
to
be
available
around
the
clock
depending
on
the
schedule
or
how
that
team
is
set
up.
This
is
a
really
stressful
job
and
to
help
manage
the
stress
and
prevent
burnout
and
fatigue
within
those
operation.
A
Teams,
companies
typically
have
a
team
of
responders
that
are
on
call
that
rotate
this
responsibility
to
manage
this
setup
of
work,
to
guarantee
that
someone's
always
available
to
answer
an
alert
when
it
comes
in
means
that
they
need
to
have
on-call
calendar
and
schedule
management
tools.
So
that
is
what
we're
starting
to
build
in
13.7.
A
When
you
set
up
an
on-call
schedule
in
a
project,
you'll
have
the
option
to
add
multiple
rotations
to
that
schedule,
so
that
you
can
customize
and
create
a
schedule
that
fits
how
your
team
puts
people
on
call.
So
what
we're
looking
at
here
is
a
single
schedule.
We've
called
the
dev
on
call
schedule.
I've
got
the
ability
to
edit
and
delete
it.
A
A
It
appears
for
three
day
increments
at
a
time
for
this
particular
rotation
I'll,
be
able
to
create
a
single
schedule
in
a
project
and
have
multiple
rotations
within
that
schedule.
For
the
mbc
version
of
this
feature
set
if
an
alert
does
come
into
a
kit
lab
project,
while
someone
is
on
call
that
alert
is
going
to
send
an
email
to
that
responder
and
future
milestones
will
be
investing
in
different
paging
methods
such
as
text,
and
call.