►
From YouTube: Observability - Exploring Errors within GitLab
Description
How to use the GitLab Observability Platform to explore errors stored in an external Sentry datasource.
Product direction: https://about.gitlab.com/direction/monitor/observability/
A
Hi,
this
is
a
demo
of
using
the
gitlab
observability
platform
for
error,
tracking,
specifically
how
to
configure
a
Sentry
data
source
and
explore
errors.
This
feature
is
currently
in
active
development
and
only
available
to
a
few
gitlab
team
members
who
are
testing
it
so
I'm,
currently
in
the
observability
menu.
There
are
already
two
data
sources
here
which
were
automatically
provisioned
for
this
project.
In
this
demo,
I'm
going
to
set
up
a
new
data
source,
in
this
case
gitlab's
own
self-hosted
Sentry
instance.
A
So
I'm
going
to
select
gitlab
error
tracking
here
and
provide
a
URL
to
our
Sentry
instance.
The
org
is
gitlab
I'll,
give
it
a
name
and
just
use
the
URL
for
that
the
auth
token
is
an
API
token
that
I
generated
within
Sentry
and
now
I
can
save
and
test
my
data
source.
The
test
was
successful:
I
can
go
to
explore
Telemetry
data
and
here
in
the
drop
down
I'll
select
my
new
data
source.
There
are
a
few
things:
I
can
explore.
A
I'll
start
with
stats,
I
need
to
pick
a
project,
I'll
go
with
rails
and
I'll.
Look
at
errors
over
time,
I'm
going
to
look
at
the
last
30
days,
so
here
I
can
see
errors
over
time
for
this
project.
I
can
see
some
spikes
in
January
there
I
can
zoom
in
and
maybe
notice
any
kind
of
patterns
or
more
specific
details.
A
I
can
also
look
at
list
of
issues
directly
and
sort
them
by
events.
This
will
give
me
the
most
occurring
errors
for
for
this
project,
so
the
main
one
seem
to
be
about
active
record.
What
I
can
do
as
well
is
filter
with
a
query.
So,
for
example,
if
my
team
owns
this
autofix
worker
component,
I
can
add
this
to
the
query
here.
A
Look
back
in
the
past
seven
days,
maybe
and
have
a
look
at
the
errors
that
this
component
was
triggering,
and
this
will
help
me
to
prioritize
any
error
fixes
that
I
want
to
do
so.
That's
it
it's
worth
noting
that
a
user
can
bring
their
own
data
source
and
already
get
insights
into
their
errors
from
within
gitlab
without
needing
to
migrate
any
of
their
data.
Alternatively,
they
can
use
the
integrated
error
tracking
and
not
have
to
manage
or
pay
for
their
own
Sentry
instance,
and
what's
next,
for
this
feature,
is
to
work
on
the
visuals.