►
From YouTube: 2021-09-02 meeting
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).
B
C
C
B
I
joined
last
week,
but
there
was
just
nacho
there.
C
B
B
You
I
currently
work
for
splunk,
okay,.
C
C
I
don't
know
is,
I
think
rice
was
coming,
at
least
he
didn't
say
the
opposite
today,.
A
Oh
okay,
no
I
thought
bryce
was
gonna,
be
out
for
two
weeks
for
two
weeks:
yeah.
C
Yeah,
okay,
then
we
are
probably
all
of
us
now,
okay,
so
I
was
just
creating
another
document.
Sorry
because
I
have
been
a
bit
full
of
work
today.
A
C
Okay,
do
you
have
any
other
topic?
Do
you
want
to.
A
B
A
C
Okay,
we
can
talk
about
it
later,
yeah,
okay,
okay,
great
last,
meeting
actions.
It
should
be
fast
basically,
because
I
will
review
from
the
two
two
meetings
ago.
It
was
this
was
done.
The
network
status
was
done.
C
C
We
were
talking
about
the
external
dependencies
program.
There
is
an
issue
in
the
in
github
that
we
have
also
continued
talking
this
week
a
bit
about
the
programs
so.
C
So
we
will
have
to
be
clearly
for
that,
so
go
directly
to
that
issue.
So
let
me
yeah
just
for
I
don't
know
vinod!
You
have
been
see
if
you
have
read
this
issue.
C
No,
I
haven't
I'm
reading
it
right
now,
yeah,
okay!
Basically
we
I
had
some
problem
understanding
it
at
the
first
with
john,
so
we
were
talking
about
different
things
for
half
the
meeting
last
week.
Sorry
again
for
that
john
but
yeah,
the
problem
is
that.
C
C
So
it's
a
problem
when
it,
the
project
uses
another
reachability
library
in
a
from
a
cocoapod
dependency,
for
example,
because
the
president's
up
with
two
linking
libraries
with
different
versions
and
as
it
is
using
a
different
linking
a
different
dependency,
because
our
producers,
sweet
package
manager
and
coco
pods
both
ends
up
being
linked
in
the
project
and
if
they
are
not
compatible,
then
you
have
a
problem,
and
just
one
of
those,
usually
the
first
one
that
is
linked
in
the
project
is
the
one
that
is
used
by
both
projects
and
it
they
can
have
different
apis
and
grass,
for
example,
and
the
other
issue.
C
The
other
pain
point
was
when
using
swift
package
manager
that,
even
when
you
don't
use
the
network
status
or
the
network
instrumentation
projects
as
it's
included
in
the
open,
telemetry
general
project
when
xcode
tries
to
solve
the
dependencies-
and
you
have
another
dependency
with
another
version
of
which
ability.
Then
it
ends
up
giving
an
error
because
it
cannot
work
together.
C
B
C
Yeah,
that's
right
so
yeah
those
were
the
the
points.
The
pain
points
that
john
was
facing
with,
I
think,
with
the
customers
of
your
company
or.
B
So
we
encountered
a
similar
problem
with
when
we
tried
to
bring
in
appeal
a
crash
reporter,
both
from
a
swift
package
manager
and
from
a
people
using
it
through
cocoapods
issue
right.
Both
of
these
issues
occurred
yeah
and
the
only
way
I
found
to
fix
it.
I
mean
to
really
fix
it
was
to
say:
well,
it's
an
optional
feature,
our
usage
of
pl
crash
reporter,
and
if
you
want
to
use
it,
that's
cool
we'll
put
it
in
a
separate
repository
as
a
separate
module
package
library.
B
Whatever
you
want
to
call
it,
and
if
you
don't,
then
you
don't
and
we
don't
pull
in
the
dependency
at
all
right.
That's
the
only
way
I've
found
it
to
make
it
such
that
we
don't
pull
in
that
dependency.
Having
separate
targets
inside
the
same
package
still
encounters
this
kind
of
problem
right,
yep,
so.
C
Yeah,
I
don't
really
know
what
what
what's
the
best.
B
B
There's
there's
not
ad
implementation
only
is
good,
except
again
it
doesn't
actually
solve
the
the
swift
package
manager
problem
right,
yeah
and
there's
no
real
way
to
vendor
it
in
right.
There's
no
real
way
to
like.
I
want
to
include
this
under
its
own
namespace
and
treat
it
as
though
weren't
really
going
to
be
shared
with
anything
else
in
swift.
As
far
as
I
can
tell
no
like,
for
example,
in
java,
you
can
rebase
libraries
that
you
you
depend
on
and
put
them
under
another
namespace
and
just
use
them
like
that
right.
That's.
B
C
You
can
somehow
hide
it
if
you
use
the
implementation
on
the
import
that
can
solve
your
linking
issues,
but
you
will
end
up
with
your
first
problem
that
it
ends
up
finding
the
library
twice.
So
you
will
never.
B
Know
which
one
is
gonna
doesn't
solve
b
either
because
again,
no
matter
what
you
start
to
depend,
there's
no
way
to
do
it.
A
package
level
dependency.
That
is,
unless
you
declare
it
as
a
test
dependency,
which
is
not
what
you
mean
here.
Yeah,
that's
right,
yeah,
that's
still
a
problem,
so
I
mean,
in
my
opinion
I
mean
here's.
The
thing
reachability
itself
is
fairly
popular,
but
again
are
people
using
these,
the
exact
specific
I
mean
there
are
several
forks
of
it
out.
B
B
I
do
think
that,
particularly
for
people
that
want
to
use
manual,
instrumentation
and
only
manual
instrumentation,
that
having
the
api
and
sdk
in
one
repository
and
having
all
instrumentations
in
a
separate
repository
and
minimizing
the
surface
area
of
the
api
and
sdk,
and
I
might
even
go
one
step
further
than
that
because,
given
what
we
know,
one
of
the
one
of
the
the
specification
points
about
the
open
commentary.
Client
library
says
that
you
know
a
client
should
be
able
to
use
the
api
without
depending
on
without
using
the
sdk
at
all
right.
B
B
B
C
B
Currently
we're
not
using
any
other
instrumentations
and
if
we
need
to
figure
out
some
way
to
do
these.
This
thing
we
can
do
that.
I'll,
be
honest.
If
if
this
doesn't
get
fixed,
what
I'm
going
to
having
to
do
is
to
essentially
not
fork
but
essentially
provide
another
wrapper.
B
That
is
a
it's
a
repository
that
just
says.
I've
got
a
different
package.swift
that
doesn't
have
any
of
these
dependencies.
I
mean
there's
only
the
one
right
now
right,
that's
really
a
problem
and
I'll
just
maintain
that
separately
as
a
way
to
say
yeah.
We
will
use
these
chunks
of
code,
but
not
these
by
having
a
separate
package.swift
right.
C
I
think,
for
example,
for
I
mean
maybe
the
problem
is
that
in
here
with
reachability,
because
it's
a
long-standing
framework
that
it
has
been
for
a
long
time
here-
probably
it's
the
the
we
are
using
a
very
minimal
thing
of
reachability
that
could
be
probably
solved
by
using
some
of
the
new
network
framework
stuff
in
in
in
ios
right.
B
B
We
should
agree
on
instrumentations
agree
on
semantic
conventions,
all
this
stuff,
so
yeah,
I
you
know
we
got
to
figure
out
a
way,
but
we
also
have
to
figure
out
a
way
to
deal
with
this
problem,
which
again
is
going
to
come
up
again
right
in
ways
that
we
want
to.
B
For
features
but
running
this
problem,
one
long-term
solution
may
be
long-term
solution
may
be
to
work
with
the
swift
package,
manager,
people
and
say
hey.
We
need
a
real
solution
to
this.
We
don't
need
full
necessarily
multi-repo,
but
we
need
at
least
the
package
resolution
process
to
not
to
actually
wait
on
the
package.
The
target
dependency
process
right
yeah.
B
C
C
B
B
C
C
Yeah
properly,
yes,
yeah,
I
don't,
I
don't
know
yeah
it's
a
it's
a
it's
a
tough
problem.
We
have
here
because
yeah,
we
are
limited
by
a
swift
package
manager
functionality
and
it's
not
thought
for
a.
B
Medium
one
one
other
solution
just
to
throw
out
there.
That
might
be
it's
not
you
know
having
if
we
anticipate
having
10
different
instrumentations
right
instead
of
having
10
repositories
is,
have
you
know
core,
which
can
include
sdk
and
api
in
any
instrumentations
that
don't
have
third-party
dependencies
and
then
only
instrumentations
that
require
third-party
dependencies
move
to
either
one
lump
sum.
Other
repository,
yeah.
C
C
But
we
have,
for
example,
some
dependencies
on
third
parties
in
core
currently
like
the
all
the
neo
staff
and
swift
atomics,
for
example,.
B
And
and
the
sdk
to
the
sdk
has
a
legitimate
dependency
on
those
in
the
first
place,
so
yeah,
if
somebody's
using
first
of
all
those
things
themselves,
the
cocoapods
problem
isn't
really
relevant
for
those
right
yeah,
because
they're
swift
package
manager
only
for
those
yeah,
if
we're
depending
on
you,
know,
version
x
of
switch
atomics
and
the
app
is
depending
on
version.
You
know
x,
minus
one
then
yeah
to
use
upper
telemetry
at
all.
You
know,
even
just
the
sdk
they're
gonna
have
to
deal
with
that.
B
They're
gonna
have
to
adjust
their
code
a
little
bit
and
that's
you
know
yeah
okay,
yeah
but
yeah,
but
they
can't
handle
that.
Probably
okay,
again,
I
think.
What's
what's
there
already
in
terms
of
the
choices
of
libraries
we
depend
on
for
to
implement
the
sdk,
I
think
they're,
all
sane
and
sound,
I
think
they're
all
a
good,
fairly
self-contained
surface
area
of
this
problem
right.
I
don't
have
an
issue
with
any
of
that
stuff.
B
C
Yeah,
but
you
probably
can
dynamically
check
out
the
version
and
use
the
proper
structure
that
that's
that's
what
I
was
thinking
about.
Oh
I.
B
It's
a
little
complicated,
but
it's
also,
it
also
doesn't
really
address
the
problem
of
I've
got
I
mean
fundamentally
the
issue
of
the
yeah.
The
cocoapods
issue
is
is
complex
because
you've
got
an
or,
if
you're,
using
carthage
or
something
else
right,
because
you've
got
two
separate
package
managers,
both
with
their
own
views
of
the
world
yeah.
B
C
Yeah,
I
think
we
can't
so
yeah.
Maybe
we
should
limit
all
our
dependencies
in
core
or
in
the
main
package,
only
to
apple
provided
libraries,
for
example,
or
I
don't
know,
for
example,
there
is
also
some
I
added
a
new
dependency
for
compression,
for
example,.
C
We
we
are
really
getting
limited
if
we,
if
we
limit
all
the
dependencies
in
our
projects,
that
that's
my
yeah,
I
don't
know,
maybe
we
we
should
be
much
more
careful
about
what
we
add
and
how.
B
So
right
now
we've
got
open
tracing
which
is
again
not
gonna,
be
a
problem.
We
got
thrift
again.
I
doubt
somebody's
gonna
pull
and
thrift
swift
in
io,
pretty
stable
right
and
again,
if
somebody's
using
an
older
version,
they
can
upgrade
their
app.
C
B
B
C
I
I
was
having
sorry.
C
B
C
Okay,
this
is
the
reachability
one
that
I
don't
think
we
are
using
really
much
right
and
the
rest
are
all
apple
or
old.
Libraries
like
three
thumbnail
penetration
that
shouldn't
change
so
again.
B
Leaving
one
one
approach
to
this
might
be,
like,
I
said,
leaving
the
core
there
and
having
the
the
exporter
that
uses
data
compression
and
the
instrument
and
the
network
status
that
uses
reachability
in
either
one
or
two
separate
repositories
apart
from
core
right
and
just
defining.
That
core
is
going
to
be
just
these.
C
Yeah,
it
makes
sense,
it
makes
sense
not
to
try
to
use
those
things
or
maybe.
B
C
A
Yeah,
well
I
don't.
I
haven't
really
looked
at
in
detail,
so
I
think
I
I
will
let
you
guys
discuss
it
conclusion
on
this
yeah.
I
would
like
to
know.
Can
I
understand
if
you
have
a
different,
you
know
package
managers
and
you
know
they
bring
in
different
versions.
That
is,
you
know
we
had
like
they
saw
this
one
at
some
point.
B
B
C
B
We're
not
talking
about
that.
I
don't
think
we
necessarily
need
to
have
a
decision
right
now
take
some
time
to
reflect.
C
On
it
yeah,
I
think
we
can
think
about
it.
I
would
also
like
to
to
have.
C
Bryce
bryce
buchanan
opinion
that
I
thought
he
was
going
to
be
today.
That
is
the
other.
I
in
fact
he
was
who
added
reachability
to
the
to
the
he
created
the
network
status
staff.
So,
let's
see
what
just
to
ask
is
also
a
committee
in
the
project.
I
would
like
to
have
his
opinion
I
was
trying
to
share.
B
For
your
time,
I
appreciate
you
listening
to
my
my
concerns
about
this
stuff.
Okay,
we're
again
overall,
very
happy
with
hotel
swift.
You
know
it
was
when
we
get
we're
getting
a
mobile
run
thing
going
for
ios.
It
was
very,
very
quick
and
easy
to
just
go.
Oh
hey!
Look
at
that!
We've
got
everything
we
need.
We
got
exporters,
we
got
spain
api,
we
got.
I
mean
it
was
already
in
great
shape.
C
Thanks,
we
will
try
to
to
improve
the
this
this
issue,
so
it's
gonna
work
better.
B
C
C
Okay,
so
we
are
now
both
so.
A
A
C
Packages
yeah:
the
problem
is
that
there
are
three
package
manager
for
ios
or
mac,
as
you
know,
cocoapods,
carthage
and
spm.
C
We
are
using
only
spm
for
our
project
because
we
depend
on
libraries
that
are
only
in
spm,
that
is
the
apple
provided
package
manager
that
everyone
is
moving
on
to
that,
but
still
projects
are
working
with
cocoapods
and
carthage,
and
the
problem
is
that
it
doesn't
handle
well
when
it
it
doesn't
work
with
other
package
manager
and
also
doesn't
work
that
it
tries
to
solve
all
your
dependencies,
whatever
the
tire
uses
for
the
project.
So
that
means
that
just
incorporating
the
project
changes
all
your
all
your
dependencies
and
class
with
other
third
parties.
A
That
was
the
so
so
from
cocoa
pods.
You
can
still
use
this
package
and
and
then,
if,
if
they
add
the
let's
say
the
the
two
packages
that
we
are
talking
about,
the
reachability
and
the
other
one
that
you
had,
then
there
will
be
two
different
versions
is
that
is
that
what
the
problem
is
because
coco
pods
will
so
in
cocoa
pods
if
they
ask
for
the
open,
telemetry
swift,
which
will
get
the
dependencies
along
with
it
right,
yes,
and
then
they
yeah
yeah.
C
The
price,
for
example,
where
I
started
the
dependency
that
the
name
is
reachability,
a
library
that
the
name
is
reachability
that
was
based
on
some
apple
code
from
some
time
ago,
and
the
pro
is
that
it's
a
very.
C
How
would
say
it's
a
very
used
library,
so
many
projects
use
that
library
and
that
project
and
the
print
is
that
we
are
using
one
version
and
if
they
use
another
version
in
cocoapods,
things
can
crash
if
they
use
another
version.
Also
on
an
spm
we
we
can
class
versioning,
so
that
cannot
be
used
and
yeah
so
that
that's
the
that's
the
that's
the
main
issue,
so
it's
not
easy
to
solve,
because
it's
a
project
problem
in
swift
package
manager.
C
You
must
have
different
repositories
to
solve
that
issue,
but
I
wouldn't
like
to
have
10
repositories
for
10
different
instrumentation.
So
people
has
to
know
where
all
those
repositories
are
to
import
the
libraries
and
that
stuff
I
mean
my
main
goal-
was
having
how
to
say
showing
the
user
everything
in
one
place.
C
So
he
knows
what
are
all
the:
what
are
what
all
the
tools
they
have
to
use
in
a
simple
site
instead
of
having
to
search
whatever
projects
or
whatever
things
are,
but
maybe
we
should
separate
some
of
them
move
to
another
repositories
and
from
there
just.
A
C
At
least
you
you
could,
then
you
only
have
the
problem
using
that
instrumentation,
so
you
just
can
avoid
using
that
instrumentation
and
the
rest
of
the
project
works.
The
thing
is
that
now
because
network
instrumentation
is
using
reachability,
even
when
you
don't
use
network
instrumentation,
just
import
the
project
with
the
swift
package
manager
with
open
telemetry,
it
tries
to
solve
the
reachability
library
and
classes
with
the
other
right
right
that
that's.
A
C
Okay-
let's,
let's
see
if
next
week
with
bryce,
we
can
talk
about
it
more.
I
think
he
he
added
that
project.
Maybe
he
has
some
ideas
about
that.
That
also
has
to
I-
and
I
I
think
we
need
his
opinion.
C
He
added
the
library
has
also
experienced
and
can
talk
from
his
experience
also,
instead
of
taking
today
the
the
this
decision.
The
point
is
that
I
told
john
last
week
to
come
to
the
meeting.
C
Understand
his
problem
exactly
at
the
beginning,
so
yeah
it
was
not
very
easy,
but
that
that
thing
the
other
thing
is
the
otlp
example
yeah
yeah.
I
have
been
seeing
your
code.
There
is
something
I
didn't
get
about
that
clearly
I
mean
when
I
just
I
didn't
add
more
to
the
review
just
because
we
were
going
to
see
each
other
now
yeah.
A
Yeah,
let
me
see
so
so
what
what
I
did
was
I
created
two
parents
pants
and
then
I
passed
the
the
span
to
the
do
work.
A
C
Are
here
conversation
we
have
all
our
files
here:
okay,
yeah
mainly.
C
Here,
do
you
what
I
tell
you
is
that
when
you.
C
A
I
think
now
in
github,
if
you
press
a
dot
right,
actually
you
don't
have
to
if
you're
just
going
to
view
it
just
on
on
this
on
this
yeah
do
an
escape.
Don't
yeah
just
do
a
dot
press
dot.
A
Actually,
I
didn't
change
the
keys.
I
was
thinking
you
know
the
keys
are
going
to
be
attributes,
but
anyway,
I
think
that
I
can
fix
it
later
yeah
I
just
yeah.
I
just
followed
yeah
what
you
had,
but.
C
A
Point
is
that
when.
C
C
C
Okay,
yeah,
and
even
when
you
are
cleaning
up
their
method,
as
you
have
set
this
at
the
active
span,
the
child
span
will
take
the
current
active
span
as
a
parent
and.
C
C
C
C
A
C
Key
yeah
yeah,
that's
the
key.
It's
not
documented
anymore.
A
I
actually
followed
the
the
example
that
was
there
in
the
node
otlp
exporter.
A
Exporter
for
most
of
the
other
stuff
yeah,
but
but
I'm
saying
the
the
example
for
the
node
open,
telemetry
node
project
open
telemetry.js
has
has
one
for
the
the
otip
exporter.
So
I
use
the
same
same
logic
there
and
they
are
actually
passing
the
parent
span
yeah,
because
because
we
are
better
than
they
are
no.
C
I
enjoy
it,
we
have
a
very
good
system
of
context.
Passing
you
don't
need
to
pass
it
explicitly
because
we
save
it
in
the
library
and
we
and
we
recover
that
from
the
context.
The
operating
system
has
its
time
in
its
thread.
So
even
if
you
have
a
thread
that
runs
in
another
core,
that
context
is
transmitted
and
will
get
your
parenters
done.
C
Okay,
it's
it's
like
magic
yeah.
You
can
create
a
parent
span
in
a
process
that
loads,
your
library
that
doesn't
know
anything
about
this-
that
this
one
creates
a
span
and
this
created
a
span
and
set
it
at
the
active.
The
first
span
created
here
will
take
this
one
as
the
parent
without
knowing
nothing
it's
of
the
nothing
one
from
the
other.
C
Oh,
how
does
it
do
that
yeah?
I
used
some
system
functionality.
That
was
not
public
available,
okay,
but
it
works
really
well,
but
it's
like
magic,
okay,
yeah.
In
fact,
I
use
that
for
some
testing
instrumentation
I
am
doing
at
data
we
are
doing
ci
visibility
product
and
on
the
testing
instrumentation,
you
just
create
a
span
on
the
test
and
all
the
spans
that
are
created
inside
the
application
that
is
run
by
the
test.
Just
take
this
test
as
this
parent
expander.
C
Okay,
so
that
that's
so
it's
something
that
works
automatically
without
sending
yeah
passing
the.
So
you
don't
need
the
child
doesn't
need
to
know
anything
about
the
parent
right.
If
that
s
pan
is
the
active
one,
it
will
find
it
and
we'll
set
that
okay,
okay,.
C
And
that
that
will
work,
you
will
see
it's
it's,
it's
really.
It
feels
like
magic
yeah,
but
it,
but
it
sounds
like
yeah.
It
sounds
like
magic,
but
it.
C
In
the
system
I
mean
it's
yeah,
no,
not
this
one!
Sorry
context.
Yes,
this
one
here
is
the
code
that
does
that
magic.
There
is
a
context
manager
and
you
have
a
context
provider
that
so
you
we
can
support
different
ways
of
getting
the
active
context
and.
C
Currently,
this
one
that
is
based
on
the
activity
framework
and
with
this
thing
and
this
we
have
to
make
this
function
public
because
it
isn't.
But
after
that
we
can
just
have
a
table
where
we
have
each
span
with
the
status,
so
we
can
recover
them
yeah.
This
is
here
is
the
magic,
active
context
manager.
A
Okay
and
then
the
rest
of
it,
I
think,
is
yeah
very
similar
to
what
the
you
had.
It's
a
combination
of
the
prometheus
example
and
the
simple
exporter
right.
So,
okay,.
C
Yeah,
nice,
so
yeah
just
yes.
That
was
what
I
wanted
to
add
to
your
yeah.
I
thought
was
better
just
to
tell
you
directly
here
and
explain
with
it
with
the
code
so
yeah,
because
my
english
is
not
very
good,
so
I
couldn't
explain.
No,
no!
I
think
I
I
got
it
in
the
no.
No.
I
know
my
english
is
not
very
good,
so
no,
I
understand
that.
Sometimes
I
cannot
explain
what
I
have
in
my
mind
easily,
so
that.
C
I
think
I
wait.
We
can
wait
for
the
next
week
if
you
want
it's,
basically
that
we
talked
about
the
apollo
structure
concurrency
to
the
to
the
language,
but
it
was
coming
only
with
the
newest
version
that
is
coming
in
october.
C
Okay,
but
that
changed
last
week
when
it
looks
like
apple,
is
going
to
support
previous
version.
So
it's
going
to
support
ios
12,
I
think
as
the
first
version
and
we
are
using
ios
11
in
our
library,
but
if
they
support
12,
it's
something
that
everyone
will
use.
So
we
will
have
to
add
support
to
that
for
sure,
because
we
every
project
will
use
async
await
because
it's
so
nice,
so
we
will
have
to
support
that
for
both
network
instrumentation
and
also
for
the
active
context.
A
Yeah,
I
was
actually
you
know
in
the
process
of
I
had
to
return
my
old
laptop.
I
have
all
that
in
there,
so
I'm
gonna,
you
know
upload
it
and
clean
it
up.
So
that's
where.
C
Yeah,
yes,
just
the
same,
I
told
you
if
you've
created
a
parent
spam
when
the
app
starts
you
will
see
how
all
the
network
expands
that
happen
later
will
be
outside
of
your
client
spam.
Even
when
the
network
doesn't
know
anything
about
your
spam,
okay,
okay,
so
you
you
can!
So
that's
something
really
great
to
show
of
open
telemetry
that
you
can
create
a
span
when
you
start
an
activity
like,
for
example,
you
click
up
button
or
you
load
a
web
page,
and
you
can
reference
all
the
network.
A
Yeah
yep
yeah,
but
I
was
actually
I
think
for
now
I'll
just
keep
it
in
my
repo,
because
that
will
you
know
I
need
to
do
play
around
with
this
api.
Some
more
and
you
know
test
it
out,
and
then
we
can
figure
out
where
to
you
know,
show
that
example.
C
A
C
I
can
imagine
they
are
not
even
supported
in
my
company
still
oh
yeah.
They
have
to.
I
think
some
libraries
or
some
tools
that
we
use
must
must
be
updated
for
someone
yeah
you
and
things
like
that.
So
yeah.
A
C
C
C
A
Yeah
yeah,
so
that
I
think
you
know
I
have
some
instructions
read
me.
So
if
you
follow
that
yeah.
C
That's
yeah,
that's
my
idea.
That's
why
I
didn't
approve
it
at
the
beginning,
because
I
wanted
to
I
had
no
time.
I
just
took
a
look
at
the
code,
but
I
wanted
to
just
try
your
your
readme.
A
Yeah
actually
yeah.
That's
that
reminds
me.
This
is
something
I
wanted
to
ask.
So
one
of
the
things
that
I'm
actually
having
problem
with
is
I'm
not
able
to
set
the
service
name.
A
So
you
know
in
the
jaeger
exporter
or
the
zipkin
exporter,
you
pass
the
it
takes
the
service
name.
The
second
parameter
is
taken
in
the
service
name
by
default,
whereas
for
okay.
C
A
This
you
have
to
set
it
as
as
a
result.
A
C
A
Yeah,
so
I
I
was
thinking,
maybe
do
you
have
to
use?
You
know
there
is
something
else
that
you
have
in
the
sdk
called
trace
provider
builder.
C
I
don't
think
it
has
a
service
name,
the
trace
provider.
A
A
So
the
other
you
know
the
the
node
project
when
I
was
looking
at
you
know
where
I
was
following
that
otlp
example.
They
are
using
resource,
but
they
are
using
it
when
you
get
the.
So
let
me
look
at
the
example
again.
A
A
Yeah,
so
this
this
part
right.
So
yes,
instrumentation
name
and
treasure:
sdk
yeah,
yeah
yeah.
So
how
so
this
is,
you
know
just
setting
it
up
and
then
this
is
where.
C
A
No,
no,
my
first
question
is
the
trace
provider
is
where
you
know
you
get
the
tracer,
and
why
is
this
call?
Why
is
it
a
get.
C
Yeah,
because
tracer
yeah
it's,
I
think
it.
A
A
A
C
But
that's
that's
just
the
exporter
yeah,
but
it
could
have
their.
You
mean
having
their
service
name
as
well:
yeah,
yeah
yeah,
so
in
other
projects.
A
A
Yeah
or
the
you
know
you
had
to
pass
and
then
I
also
tried
to
look
up.
You
know
there
is
even
in
the
collector
config
I
was
thinking.
You
know
there
is
a
way
to
set
the
service
name
here.
But
again
this
did
not
did
not
work,
okay,
so
so
it
shows
up.
Finally,
as
a.
C
I
think
both
yeah,
we
might
yeah
that's
right.
We
might
talk
with
bryce
also
he
he
made
both
the
the
resources
library
he
implemented
that
so
maybe
he
he
knows
better
how
to
mix
with
it.
He
also
made
the
otp
some
of
the
stuff
there,
so
yeah,
okay,
maybe
next
next
week,
can
be
a
good
day
too.
Okay
yeah.
I
think
it
should
be
something
in
the
configuration
for
sure.
Okay,
if
I
see
something
I
I
will
try
to
take.