►
From YouTube: GitLab 12.8 Kickoff - Monitor:Health
Description
Overview of issues the Monitor: Health group will be working on in 12.8
A
Hello,
my
name
is
Sarah
loner
and
I.
Am
the
product
manager
for
the
health
group
was
on
the
monitor
stage?
I'm
gonna
be
talking
about
the
initiatives
that
the
Health
Group
is
going
to
work
on
in
milestone,
12.8,
so
to
start
off
over
the
holidays,
get
labs
community
gift
to
the
public
was
to
move
the
three
pillars
of
observability
to
core,
so
this
encompasses
metrics
login
tracing,
as
well
as
our
alerting
functionality.
A
So
in
12.8
the
Health
Group
is
going
to
be
supporting
this
initiative
and
moving
all
of
our
alerting
functionality
from
the
ultimate
pricing
tier
into
our
core
pricing
tier.
So
when
this
issue
is
completed
and
we
release
that
alerting,
we'll
be
available
for
all
pricing
tiers,
this
was
really
important
to
get
loud
for
a
few
reasons.
A
Making
observability
available
to
all
customers
as
part
of
our
stewardship
model.
Observability
belongs
in
core
because
it's
not
just
the
enterprise
companies
that
are
concerned
about
maintaining
and
making
their
services
available
and
reliable.
This
is
important
for
companies
of
all
sizes,
no
matter
the
service
they
provide,
and
additionally,
as
we
mature
monitoring
throughout
the
next
months
and
years,
we
really
want
your
feedback
on
it.
A
So
this
issue
is
for
a
moving
alerting
part
of
that
observability
package
core
the
next
few
initiatives
that
we'll
be
working
on
our
to
wrap
up
our
work
on
era
tracking
at
the
end
of
12th
IAEA,
our
tracking
will
be
at
the
viable
maturity
level.
So
the
last
few
pieces
of
work
that
we
have
have
to
do
with
the
aerialist
and
then
some
cleanup
objectives
around
with
the
area
detail
page
looks
like
so
this
particular
issue
is
adding
the
ability
to
further
filter
the
error
list.
My
statuses
ignored,
resolved
and
unresolved.
A
So
in
12.7
we
added
the
ability
to
take
action
on
these
errors,
specifically
the
ability
to
ignore
or
resolve
these
errors.
This
was
really
important
because
errors
are
difficult
to
sort
through
manual.
Triage
takes
a
lot
of
time
and
so
being
able
to
remove
those
from
your
view.
If
either
they
don't
recall,
they
don't
need
any
action
or
you
fix
the
problem
and
it's
been
resolved
so
that
you
can
solely
focus
on
the
ones
that
are
important.
A
The
next
part
of
the
era
tracking
project
is
adding
colors
to
indicate
error
severity
levels.
So
when
you
look
in
sentry
and
you're,
looking
at
an
error
list,
they've
got
different,
color
indicators
that
tell
you
if
it's
critical,
if
it's
warning,
if
it's
just
for
information,
we
want
to
copy
those
colors
in
to
get
labs
so
that
your
experience
transitioning
from
the
Sentry
interface
into
the
kit
lab
interface
is
much
more
streamlined
and
you
have
more
context
to
what
you're
looking
at
again.
A
This
is
to
help
with
visualization
when
you're
manually
triaging
those
error
lists
the
next
one
is
a
small
improvement
on
the
arrow
tracking
detail
page.
So
right
now
we
are
linking
all
errors
to
an
Associated
gitlab
issue.
If
one
has
been
created
for
that
error
right
now,
we're
displaying
it
and
that's
raw,
u
RL,
and
we
want
to
convert
that
to
using
git
live
flavored
markdown
format,
so
that
the
UI
within
the
air
detail
page
is
consistent
with
the
rest
of
Killa
all
right.
A
The
next
two
issues
have
to
do
with
embedding
metrics
within
github
issues,
and/or
incidents.
So
in
a
few
milestones
ago
the
health
team,
out
of
the
ability
to
embed
metric
charts
in
issues
for
help
triaging
incidents
and
getting
a
better
idea
of
the
problem
and
what
happened
the
time
the
incident
was
triggered.
This
is
all
manual
at
this
point.
With
the
release
of
this
issue,
we
will
be
automatically
embedding
metric
visualizations
charts
for
metrics,
where
an
alert
has
been
triggered
to
remove
the
manual
piece
of
that
workflow.
A
This
will
help
the
responder
be
able
to
focus
first
most
on
investigation
versus
trying
to
change
context,
search
for
that
visualization
and
then
add
it
back
to
the
issue
to
share
findings
and
the
final
large
focus
of
this
milestone
is
going
to
be
the
ability
to
remove
those
charts
from
the
issue.
So
unfurled
images
can
often
get
in
the
way
of
reading
or
consuming
other
information
that
someone
needs
in
an
issue
and
we
want
to
provide
them
an
easy
way
to
remove
those
if
they've
already
consumed
the
information
or
if
it's
not
showing
anything.
Useful.