►
From YouTube: GitLab 13.4 Kickoff - Monitor:Health
Description
Monitor:Health 13.4 Planning Issue: https://gitlab.com/gitlab-org/monitor/health/-/issues/25
A
Hi
welcome
to
the
13.3
kickoff
video
for
the
monitor
health
team.
My
name
is
sarah
weldner
senior
product
manager
for
the
health
group
in
13.3.
Our
main
focus
will
be
building
out
the
interface
for
incidents
in
gitlab,
we'll
be
adding
features
that
enable
and
streamline
investigation
of
I.t
incidents
by
on-call
responders.
A
We've
heard
many
times
over
in
many
customer
interviews
that
the
main
pain
point
for
them
during
investigation
and
remediation
and
keeping
stakeholders
updated
is
the
fact
that
they
have
to
navigate
in
between
different
tools
and
different
tabs.
So,
let's
take
a
look
at
the
mux
see
what
different
features
we
have
queued
up
and
I
apologize.
This
is
a
13.4
kickoff,
video,
not
13.3.
A
So,
as
I
just
said,
we're
going
to
be
building
out.
Incidents
in
gitlab
take
a
look
at
the
overall
vision
for
what
incidents
are
going
to
look
like
and
then
13.4
we're
going
to
be
focused
on
a
handful
of
things
here.
First
off
is
going
to
be
this
new
highlight
bar.
So
what
this
does?
It
gives
the
responder
a
high
level
view
immediately
easy
to
visually
consume
of
what
the
severity
is.
When
did
the
alert?
A
The
next
part
is
we're
going
to
be
building
out
this
tabular
structure
here.
So
this
gives
someone
access
to
a
lot
of
different
resources
when
they're
responding
to
an
incident
without
having
to
change
tools
or
interfaces,
and
they
can
stay
relevant
to
the
point
in
time
or
the
state
of
the
thing
they're
working
on.
So
first
tab
is
going
to
have
the
highlight
bar
and
a
summary
which
is
going
to
be.
The
body
of
the
alert
that
came
in.
A
The
next
two
tabs
are
embedded
metrics
and
then
embedded
logs,
so
both
of
these
are
for
specific
prometheus
alerts.
If
you're
using
get
lab
apm
product,
we
are
going
to
be
pulling
in
and
automatically
displaying
the
chart
for
the
particular
threshold
that
was
breached,
giving
someone
a
very
easy
place
to
start
with
investigation
and
identify
what's
been
going
on,
since
the
alert
was
triggered
in
other
tools
and
other
products
and
experiences.
You
have
to
go
to
a
different
tool
to
get
this
and
instead,
we've
embedded
it
directly
in
the
incident.
A
In
terms
of
keeping
stakeholders
updated,
it's
important
that
the
response
team
or
the
incident
commander
be
updating
the
status
page
as
often
as
there's
progress
or
changes.
So
as
soon
as
there's
an
incident
and
someone's
been
paged
and
they're
able
to
look
at
that
in
gitlab
we're
adding
the
ability
to
publish
this
directly
to
a
status
page
from
the
incident
interface.
A
That
also
allows
other
people
to
see.
Yes,
this
is
published.
Stakeholders
are
aware
and
can
see
all
of
our
updates
and
then
post
comments
and
publish
those
to
the
status
page,
so
it
provides
a
single
source
of
truth
for
everybody
who's
aware
of
the
incident.
So
those
are
the
highlights
for
13.4
thanks
for
watching.