►
From YouTube: Monitor Health July Speed Run: Triage Workflow
Description
Speed demo of triage workflow in GitLab using tools from the Alert and Incident management categories. Recording includes demo as well as points out areas that need to be improved.
A
Hi,
my
name
is
Sarah
Waldner
and
I'm.
A
senior
product
manager
within
the
monitor,
C
ticket
lab
today
speed
run,
is
going
to
be
on
a
triage
workflow,
which
involves
alert
management
and
incident
management,
two
categories
which,
within
the
monitor
health
group,
so
I've
gone
ahead
and
triggered
a
get
little
alert
using
the
curl
command,
which
you
can
find
in
the
gale
of
documentation
and
I'm,
going
to
respond
to
it
so
I'm
within
the
Tanooki
Inc
project
within
get
lab.
A
This
is
a
demo
application
that
we
use
for
testing
and,
if
I'm
an
incident
responder
or
the
incident
commander
within
my
team,
I
want
to
make
sure
that
the
Tanooki
web
service
that
were
responsible
for
is
up
and
running,
and
so
within
the
operation
section
I've
got
access
to
all
of
my
alerts.
It's
not
so
much
exception.
A
So
I've
actually
had
a
couple
of
alerts.
Come
in
I've
got
a
critical
one
from
one
week
ago
that
nobody's
taking
care
of
so
I
should
probably
make
sure
it's
still
on
the
trigger
state.
So
I'm
going
to
go
ahead
and
acknowledge
that
see.
If
I
understand
anything
about
this,
the
overview
tab
doesn't
give
me
a
ton
of
information.
All
I
know
is
that
it
came
in
from
prometheus,
and
that's
right.
Database
service
probably
need
to
add
some
more
information
to
make
this
page
a
bit
more
useful
under
the
alert
details.
A
Looking
for
any
information
that
might
give
me
a
sense
of
impact.
Okay,
the
description
is
giving
me
more
information
about.
What's
going
on,
so
it
looks
like
it's.
Some
proce
Postgres
replicas
that
have
been
delayed
potentially
need
to
move
that
higher
up
higher
up
in
the
list
and
I'm
going
to
access
to
a
run
book,
which
is
not
a
clickable
link.
So
we
need
to
make
that
one
clickable
as
well
we're
going.
We
got
a
decent
amount
of
information.
Oh
and
this
particular
alert.
A
A
A
A
Kind
of
be
nice
if
I
could
comment
to
him
unless
alert
the
one
I
came
in
nine
minutes
ago,
I'm
going
to
take
care
of
so
acknowledge
to
sign
it
to
myself,
because
I'm
going
to
take
care
of
this
one.
It's
nice
that
I
get
indication
that
I've
done
that
we
want
to
add,
probably
need
to
add
events
here
for
when
I
change
the
status.
So
it's
affecting
CI
runners,
the
alert
details,
I've
got
more
information
in
the
description
which
we
need
to
move
up.
A
A
A
So
what
I'm
seeing
is
the
summary
house
rendered
in
here,
but
I
don't
have
access
to
the
alert
payload?
That's
something
else
that
I
want
to
add
is
easy
access
to
the
alert
from
the
incident
and
then
inviting
those
details.
Incidents
because
now
I
have
no
access
back
to
the
alert
from
the
incident
from
here
I'm
going
to
go
ahead
and
get
a
team
member
involved.
A
And
also
gonna
publish
to
the
status
page
so
that
our
our
community
knows
what's
going
on.
Did
you
have
to
reload
the
page,
but
when
I
do
so
I
get
indication
here
that
allows
me
to
access
the
status
page
and
then
this
is
something
that's
publicly
available
for
people
to
look
at
and
then
I'm
going
to
go
ahead
and
grab
the
zoom
link.
What
I'm
working
on
now,
so
that
I
can
involve
some
other
people.
A
Yeah,
this
is
not
real
life
of
datings.
You
need
to
refresh
the
page,
but
once
we
do
that
we
have
the
zoom
meeting,
so
I've
involved
bumped
a
team
member
incident.
Oh
and
I've
got
it
published
to
the
status
page
and
I've
got
a
red
book
here
for
the
team
to
start
to
remediate
as
we
go,
it
might
keep
a
timeline
and
they
should
comments
or
in
my
document
that
in
the
description
are
there
ways
a
little
bit
manual
all
right
thanks
for
watching
that's
the
triage
workflow
as
it
is
today,
Angela.