►
From YouTube: GitLab 12.7 Kickoff - Monitor:Health
A
The
issue
I
will
post
in
the
description
of
the
YouTube
video,
but
let's
go
ahead
and
jump
in
the
big
theme
for
this
release
is
about
moving
our
error
tracking
capability,
our
kind
of
product
category
to
viable.
It's
been
in
a
minimal
stage
for
some
time
and
so
Sara
and
the
team
have
planned
a
number
of
great
issues
to
advance
it
to
viable
through
the
course
of
this
release.
So
first
one
is
when
you're
viewing
a
an
error.
One
of
the
common
things
to
do
is
kind
of
ignore
that
error.
A
You've
recognized
that
it's
an
error
that
maybe
is
temporary,
because
it's
a
result
of
some
recent
improvement
or
you're
working
in
a
dev
environment.
You
can't
just
want
to
dismiss
it
or
ignore
it.
So
we've
added
the
ability
to
ignore
there's
a
function
within
sentry
directly
into
get
lab.
You
can
see
that
both
in
the
list
view
and
error
detail
page
here,
so
that
will
be
one
of
the
high
priority
items
we'll
work
on
and
those
kind
of
frequent
requests
from
users.
A
The
next
one
is
resolved,
sentry
errors,
phone
within
get
lab,
and
so
that
resolved
the
issue
is
similar
to
ignore,
but
resolve
kind
of
suggests
that
the
error
is
done
completely,
so
it
doesn't
ignore
it
for
some
period
of
time
and
it
resolves
it
permanently.
So,
similarly,
you
can
see
that
resolved.
Workflow
is
both
in
the
detail
page
here
you
see
it
next
to
ignore,
as
well
as
in
the
list
page
that
I
just
showed.
A
Next,
we
have
that
there
is
some
detail
about
the
an
error
that
might
be
represented
in
sentry
directly
in
the
get
web
error
detail.
Page
specifically,
we're
talking
about
the
level
of
the
error
and
the
language
that
that
error
was
generated
from
these
are
similar
to
you'll,
see
tags
in
centuries
interface
itself,
but
in
this
case
we're
bringing
those
the
display
of
that
information
directly
into
the
gate,
lab
generation
of
the
error
right
here
inside
of
get
lab.
A
Next,
we
have
linking
to
a
gate
lab
commit
in
the
error
detail
page
so
again
on
the
theme
of
more
detail
in
that
error
page
when
you're
looking
at
it,
not
just
the
tags
like
we
just
discussed,
but
also
a
recent
get
lab
commit
the
most
recent
give
up
commits
to
that
project
before
the
error
was
seen.
That
will
help
you
target.
Maybe
what
is
causing
the
error
if
you
can
dive
into
what
has
changed
during
that
commit
what
code
was
changed
during
that
commitment?
A
Next,
we
have
another
detail
in
the
error
detail
page
linking
to
the
file
blame.
So
not
only
are
you
in
this
case
sort
of
seeing
the
exact
commit,
but
you
can
also
then
look
at
the
history
of
that
file
when
you're
looking
at
the
stack
trace.
So
you
can
see
this
column
for
view
file
that
will
show
you
the
this
specific
file
that
the
trace
is
coming
from.
The
get
blame
history
of
that
file,
which
can
help
you
understand
what
recent
changes
have
occurred
beyond
just
this
commit.
A
The
next
issue
is
about
today
in
get
lab,
you
have
the
ability
to
link
issues
between
get
lamp
and
a
get
lab
issue,
and
a
sentry
error.
We're
now
trying
to
sync
that
issue
back
into
sentry
itself,
so
that
you
have
a
more
robust
connection
between
a
gate,
lab
and
sentry
when
handling
errors,
and
the
last
one
is
a
UI
improvement.
Today,
if
you
were
to
have
already
created
an
issue
from
a
sentry
error,
it
would
still
give
you
a
button
that
says
create
issue.
A
So,
in
summary,
a
number
of
different
improvements
to
our
error
tracking
category,
both
in
the
types
of
actions
that
you
can
perform
on
errors,
both
in
the
ListView
and
in
the
error
detail
page
as
well
as
the
types
of
information
that
is
displayed
directly
in
error,
detail
page
to
help
those
who
are
reviewing
the
errors
in
taking
action
to
resolve
or
improve
them
do
that
more
quickly.
So
those
are
the
issues
and
the
scope
for
we're
planning
for
the
12.7
release.
I,
look
forward
to
Sarah
being
back
and
walking
through.