►
From YouTube: GitLab Jaeger Integration Overview
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Yeah
in
terms
of
tracing
the
principle
of
what
we
have
today
is
our
it's
the
same
work
that
we
shipped.
It
was
probably
two
and
a
half
years
ago
at
this
point
that
allows
you
to
if
you
have
a
jager
instance
installed
anywhere,
you
point
it.
You
tell
gitlab
where
that
instance
is
the
the
ui
url
and
then
gitlab
will
iframe
that
view
in
within
the
gitlab
application
fairly
straightforward.
You
have
to
do
your
own,
but
not
fairly
straightforward
fairly,
rudimentary.
You
have
to
do
your
own
instrumentation
to
ship
traces
to
yeager.
A
You
have
to
have
your
own
install
prior
to
the
deprecation
of
git
lab,
managed
apps.
We
had
a
managed
app
for
jager
that
you
know
installed
the
boilerplate
version
jaeger
has
that
was
with
helm.
Jaeger
has
since
created
like
an
operator,
so
it's
probably
more
robust
to
do
an
operator
based
install
on
a
kubernetes
cluster
or
wherever
you
can
also.
I
think
you
can
get
a
managed
hosted
jager
instance
from
grafana
cloud
or
grafana
labs.
A
You
can
just
spin
one
up
and
point
it
at
that
url.
I
think
that's
true,
although
they
might
have
deprecated
that
for
tempo
their
own
tracing
tool,
but
yeah.
That
would
be,
I
think,
specifically
for
your
use
case.
What
you
would
want
to
do
is
spin
up
one
in
a
kubernetes
cluster.
Attach
it
and
then
you
get
the
iframe.