►
From YouTube: 2023-01-19 meeting
Description
Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room
A
C
D
D
D
D
D
Okay,
here
we
are.
E
E
D
B
D
E
Yeah,
so
my
name
is
Amil
I
work
for
a
specto.
We
do
a
open,
Telemetry,
tracing
and
I
started
experimenting
with
the
Swift
implementation,
because
I
wanted
to
make
sure
that
the
dresses
look.
B
B
E
It
works
so
I
built
like
a
very
simple
application
and
added
the
tracing
and
I
saw
something
that,
like
originally
things
didn't
work
right.
So
I
didn't
see
a
spends
as
I
expected
and
I
started
the
investigating
and
my
findings,
which
might
be
incorrect
because
I'm
not
familiar
with
Swift
and
I.
Don't
have
deep
knowledge
with
the
specific
implementation,
but
I
suspect
that,
like
the
Tracer
provider
is,
should
be
registered
in
the
API
okay.
D
Later
great
so
I
don't
know
if
I
put
your
company
correctly
or
it
okay.
D
Okay,
so
for
last
meeting
actions
we
go
with
the
topics
in
order,
if
you
think.
D
Yeah,
basically
from
the
things
here,
we
release
a
version
with
latest
changes
thanks.
So
that's
there
I
also
in
found
a
pair
of
Frederick's
condition.
Last
week,
I
committed
I
didn't
wait
for
an
approval
because
it
was
when
I
fixed
it
last
time.
I
I
missed
the
correct
name,
so
it
was
not
being
protected.
I
suspected,
so
it
was
quite
quite
direct.
Also
be
not
we'll.
Take
some
Prometheus
issues.
That's
your
topic.
You
added.
C
Yeah
I
saw
that
you
know
in
the
other
reports
they
are
doing
something
similar
right,
I
mean
I,
looked
at
the
Java
one
for
yeah,
so
I
think
that
the
person
who
opened
the
issue
also
has
linked
on.
What
is
the
changes
right?
The
only
thing
is,
we
don't
need
to
add
any
dependency
right.
We
just
just
write
something
that
is
compliant
to
Prometheus.
C
C
D
Follow
in
the
topics
earlier
yeah
about
the
first
topic,
I
added
here-
that's
the
one
Amir
was
referring
to
one
of
the
problems
that
we
have
is
that
when
we
call
a
open,
Telemetry
SDK
instance
in
the
code,
in
the
way
that
it's
currently
implemented
it
two
things,
it's
not
doing
what
we
really
think
it's
doing,
and
if
we
follow
the
the
instructions
that
I
think
that's
the
problem.
Mommy
had
we
see
it
when
when
initializing
it,
it
makes
something
wrong
and
also
another
side.
D
We
are
using,
for
example,
this
call
also
in
the
network
instrumentation
instead
of
using
the
open,
Telemetry
basic
instrumentation.
But
let
me
show
what
I'm
referring
to
when
we
are.
We
we
had
this
open,
Telemetry
SDK
public
extract
that
we
use
basically
to
access
the
instance
as
an
open,
Telemetry,
SDK
class.
D
The
thing
is
that
this
is
a
static
variable
and
it
currently
initializes
the
open,
Telemetry
SDK
and
when
it
calls
it
calls
this
method
so
with
register
default.
Tracer
provider,
SDK
method
providers,
okay
and
the
developer
default
baggage
manager,
and
that
means
that
if
you
previously
have
done
something
like
register
a
tracer
provider
that
you
have
built
with
a
tracer
Pro
with
a
treasure
provider
Builder,
it
will
change
your
Tracer
provider.
For
example,
if
we
go
to.
D
D
Itself,
the
first
time
you
call
it
and
when
you
call
it,
you
change
the
treasure
provider
of
the
initializer,
but
when
you
have
after
that,
if
you
call
open
Telemetry,
SDK
dot
instance,
the
problem
is
that
as
it
doesn't
exist,
it
creates
another.
D
D
D
So
I
think
that
we
should
somehow,
in
order
not
to
break
everything.
B
D
D
A
Think
because
I
think
that
the
actual
spec
is
that
everything
should
be
accessed
through
the
API,
not.
D
D
A
Maybe
just
remove
the
the
stuff
from
the
init
function
and
instead
of
returning
Tracer
provider
sdks,
it
just
returns,
trace
of
provider.
I,
don't
know
if
that
makes
a
big
difference.
D
Maybe,
okay,
I
I
cannot
change
it
here.
Yeah
or
maybe
return
I
mean
maybe
returning
this
if
it
exceeds
and
it's
an
open,
Telemetry
SDK
return
it
optionally
or
something
like
that
or.
D
About
about
maybe
returning
this
casting
to
open,
Telemetry
SDK
here
but
yeah
they
are
yeah.
Maybe
we
should
just
clean
it.
A
E
So
I
managed
to
make
it
work.
The
issue
was
that
the
instrumentation,
the
URL
session
instrumentation,
is
acquiring
a
tracer
from
open,
Telemetry
SDK
dot
instance,
which
means
that
if
I
register
something
to
the
API
I
cannot
use
the
instrumentation
yeah.
D
I
mean
if
you,
if
you
have,
if
you
call
on
open
Telemetry
SDK
instance
before
the
instrumentation,
it
will
work
because
it
will
return
this.
D
D
I
mean
you
can
make
it
work
as
I
told
you
if
you
initialize
first
this,
if
you
call
open
Telemetry
SDK
instance
once
before
any
other
thing
it
will.
It
will
do
this
stuff,
but
that's
not
a
problem
for
you,
because
you
will
call
again
this
with
your
own
Trace
provider
and
whenever
it
calls
here
it
will
return.
Yours.
E
So
I
think
I
tried
it
I,
not
sure,
but
I
think
it
didn't
work,
but
it
doesn't
really
matter
like
I
managed
to
make
it
work.
I
just
wanted
to
bring
it
to
your
attention,
yeah,
so
actually
I
think
it
should
be
changed
in
a
few
other
places.
If
you
open
a
open,
telemetry.io
a
site
and
go
to
the
Swift
documentation,
yeah.
A
E
E
Yeah
but
at
least
for
the
examples,
because
people
this
is
what
they
try
when
they
don't
know
anything,
they
just
recommendation
and
then
it
doesn't
work
so
right,
right,
right.
D
B
B
A
D
D
D
That's
right
because
you
know
that
yeah
that
Swift
is
strongly
typed.
Something
is
a
mess
just
to
have
to
call
this
call
every
time
you
access
the
trace
provider.
Every
time
you
access
whatever
from
open
Telemetry
instance,
is
how
it
cumbersome,
because
they
don't
have
Methods
at
all
so
but
yeah
I
will
try
removing
it
at
least
the
the
instance.
D
A
A
D
Do
that
is
how
I
don't
know
if
you
can
do
that
from
our
framework?
Actually,
you
can
under
construction
of
the
low
at
the
loading
of
the
framework
you
can,
but.
A
D
Recently,
I
have
discovered
that
some
Foundation
methods
don't
work
as
expected.
Oh.
D
B
C
Must
have
you
must
have
touched
I,
think
no,
you
must
have
touched
the
period
the
dot
on
your
yeah,
because
now
GitHub
has
added
this
thing
where
you
know
it'll
automatically
open
visual
visual
code
inside
your
browser,
yeah.
B
D
Will
try
removing
this
and
seeing
where
we
get,
and
also
we
have
to
update
some
documentation
just
to
avoid
using
this
and
in
all
the
instrumentations
that
you
should.
Okay.
E
There
is
another
issue
related
to
it:
I
opened
an
issue
in
the
repo
in
open
Telemetry,
Swift
I
tried
to
initialize
the
instrumentation,
the
URL
session
instrumentation
and,
like
I,
think
it
should
be
initialized
after
the
SDK
right,
because
it's
trying
to
fetch
a
tracer
and
if
not
no
Tracer
provider
is
here
to
registered.
Then
it
will
not
work
right.
That's
correct!
Yeah!
Yes!
So,
like
the
docs,
it
doesn't.
D
E
D
Okay,
so
yeah,
let's
I
will
change
all
the
code,
removing
it
you
can
change
documentation
and
the
other
one
is.
A
Yeah,
so
Amir
is
the
issue
the
default,
like
Tracer
provider,
has
no
exporter.
It
has
a
no-op
exporter
in
it.
So
you
need
it's
not
explicitly
stated
that
you
need
to
actually
like
create
a
an
exporter
that
actually
does
something
if
you
want,
if
you
want
to,
if
you
want
to
instrumentation,
to
work
in,
and
that
needs
to
be
done
before
the
initial.
The
initialization
of
the
instrumentation
is
that
what
you're
saying.
E
I
think
like
I,
think
what
happened
is
that
I
first
initialize
the
installmentation
and
then
in
the
unit
function
it's
it's
time
to
grab
a
tracer
provider,
but
then,
if
I
change
it
later,
then
it
still
uses
the
old
Tracer
provider
without
the
span
boss,
source
and
without
the
resource.
So
the
order
of
creating
them
is
important
right
right.
D
I
think
the
issue
is
due
to
let
me
the
issue.
We
will
now
have
this
import.
No,
it's
instrumentation.
E
A
Yeah,
so
it
won't,
it
won't
change
if
you
change
the
Tracer
provider,
but
the
yeah,
so
it
needs
to
be
that
all
needs
to
be
initialized
before
this,
because
it
you
know
once
it
gets
the
Tracer.
It's
going
to
be
this.
You
know
it's
the
same
one
It's
associated
with,
even
if
you
change
the
Tracer
provider.
E
Then
all
the
instances
that
were
already
fetched,
they
use
the
epoxy
and
they
know
to
to
send
to
the
real
addressable
provider,
but
I,
don't
think
it's
required
you'll
just
noticing
the
readme
that
the
order
is
important
because
otherwise
you
just
don't
see
any
spends,
and
it's
really
confusing
to
understand
the
decision
right.
D
That
you
set
another
Trace
provider
and
then
it
has
already
been.
It
has
created
a
default
Tracer
that
it
that
some
I
know
no
no
operation
Tracer.
D
A
E
And
maybe
one
last
feedback
there's
another
issue
that
I
opened
the
the
examples
they
initialize
the
resource,
but
then
they
don't
register
it
to
lesser
provider.
So
when
I
try
to
install
open,
Telemetry
I
use
the
examples,
they're
really
good,
but
it
will
be
helpful
to
also
show
how
to
register
the
resource
yeah
if
you
open,
like
simple
exporter,
so
in
line
18,
there's
a
net
resources,
but
then
it's
not
used
for
anything
right.
E
So
this
is
a
one
feedback
that
could
really
improve
the
experience
for
new
users
to
show
you
how
to
manage.
D
It
yeah
I
think
these
samples
are
based
on
very
old
code,
so
it
uses
the
open
Telemetry
APK
instance.
Instead
of
instead
of
using
the
open
Telemetry,
I
o
documentation
that
creates
a
tracer
provider,
and
then
it
should
say
that
the
resources
there
right,
if
the
treasure
provider
Builder.
D
D
Yeah
we
didn't
have
addressed
provider
builder,
then
so
yeah
I
will.
C
C
B
C
D
News
of
the
releases
yeah
once
you're
using
the
Tracer
provider
Builder,
it's
quite
automatic
how
to
use
the
resource.
If
not,
you
have
to
update
the
current
Tracer
provider
and
it
yeah
it's
a
bit
cumbersome
and
the
the
good
way
is
the
one
that
that's
documented.
That
yeah
I
will
do
this
okay,
yeah
or
do
you
want
to
do
it
be
not.
C
Yeah
yeah,
you
can
also
look
into
that
yeah.
The
main
example
right,
yes,.
D
One
because
oh
right
right,
some
of
the
all
of
them
are
based
on
the
simple
example
yeah,
when
I
wrote
them
I
just
copy
and
paste
most
of
the
code.
D
Yeah
he
here
is
it
probably
it's
yeah,
it's
just
initialized,
also
in
the
in
the
old-fashioned
way,
so
most
of
them
just
check
that
yeah.
Most
of
them
are
like
that.
It
should
be
quite
easy,
but
okay
I
would
say
that
all
of
them
are
being
initialized.
Yeah
like
this
yeah.
E
Okay,
guys
other
than
that,
it
was
really
easy
and
well
documented
and
fun
experience
to
and
to
use
the
SDK.
So
thank
you
for
the
hard
work
and
for
the
help
thanks
Amir
thanks.
D
Yeah
quality
of
code
should
be
I
mean
apart
from
this
documentation
thing
that
is
probably
a
bit
there
was
no
documentation
one
month
ago
or
so
before.
Bryce
wrote
it
recently.
So
now
it's
much
more
improved,
but
a
quote
should
be
usable
and
production
already
for
a
long
time,
so
yeah,
okay.
C
Let
me
I
actually
quickly
summarize,
because
I
need
to
drop
off
so
so
I
was
looking
at
the
you
know.
Right
now,
summary.
D
This
is
based
on
the
it
uses.
The
sweet
metric
library
from
Apple
and
I
would
say
that
it's
yeah
and
I
would
say
it's
tied
to
or
maybe
not,
two
sweep
metrics.
C
No
I
think
I
saw
in
the
other.
You
know
reports
they
are
using
at
the
Prometheus
client
at
least
for
testing.
So
we
don't
have
any
of
those
dependencies
in
our
report-
okay,
so
yeah,
so
that
is
but
I.
Think
overall,
if
you
just
use
the
package
I,
don't
think
we
need
to
add
any
dependency,
but
yeah
I
I
looked
at
the
Java
one.
They
had
the
from
Matthias
HTTP
client
simple.
What
do
they
have
io.promate
this
simple
client,
HTTP
server?
Yes,
I.
D
Mean
if
you,
if
you
think
that
using
this
is
going,
is
going
to
improve
the
quality
of
code.
This
is
quite
new.
I
mean
it
didn't
exist
before
when
Prometheus
code
was
was
written.
D
Do
you
think
that
using
this
will
will
help
us
to
have
have
a
better
quality
or
better
or
faster
or
whatever?
No.
B
D
Probably
supported
with
the
internal
types
is
probably
is
probably
good
because
for
Prometheus
that's
was.
D
C
So
right
now,
I
think
the
summer
yeah
summary
and
Gage
are
in
the
same
place.
It.
A
C
D
Yeah
I
I
mean
I,
don't
know.
If
you
want
to
use
that
dependency,
we
were
probably
half
a
better
Prometheus
thing.
D
I
mean,
but
we
have
something
really
small
now,
which
yeah
I
don't
know
if
it's,
because
it's
very
limited
or.
C
Yeah,
let
me
let
me
look
into
that.
Let
me
I'll,
we
can
chat
on
slack
or
we
can
talk
next
week.
All
right
see
you
guys
bye.
B
D
So
yeah
we
have
a
very
simple
library
now,
depending
on
something
that
is
bigger
than
what
we
have
now
I.
Don't
know,
maybe
it's
needed
if
anyone.
D
Simplified
I'm
winning
something
more,
no
I,
don't
know.
Okay,.
A
D
That's
true,
but
yeah,
that's
true,
but.
D
D
Great
yeah
Dave
you
can
update
that
documentation.
I
will
try
to
change
yeah.
A
Yeah,
the
problem
is
still
we
need
to
somehow
cast
like
we
need
a
intermediate,
maybe
like
an
extension
or
something
in
the
SDK
I,
wonder
if
we
could
add
that
for
open
Telemetry.
That
casts
those
things
as
the
proper
object.
I,
don't
know
it's
it's
weird.
A
D
A
Yeah,
so
that
we
can,
we
can
cast
it
to
the
proper
to
the
proper
SDK
types
for
the
full
range
of
functionality.
A
Because
that's
essential,
that's
essentially
what
the
SDK
is
doing.
The
open,
Telemetry
SDK
is
just
making
sure
that
the
the
protocol
objects
actually
have
the
the
apis
for
the
like
SDK
objects,.
D
Yeah
that
that
that
that
could
work
yeah
that
that's
a
good
idea,
I
will
I
will
try
that
in
order
to
improve
the
the
usage
or
the
usability
of
the
of
the
thing,
because
I
have
been
also
trying
with
new
language
for
three
days,
three:
some
and
the
any
and
things
like
that
to
for
Builders
to
create
something
generic
and
still
not
possible.
Yeah.
A
D
Yeah,
we
are
a
bit
limited
there
with
the
land.
We
have
to
fight
with
the
language
for
the
okay,
so
there
is
nothing
more
I
think
we
can
end
up
here.
A
D
D
It
there
is
one
a
previous
one,
yeah
yeah
and
instead
of
this
returning,
the
the
other.
That's
the
other
option.
I
mean
the
idea
had
was
pretty,
but
maybe
I
returned
the
open
Telemetry
instance
casted
as
ourselves.
A
D
Android
and
return
from
there,
but
it's
a
bit
it
will
break
less
code,
but
maybe
it's
a
bit
still
adding
more
code
and
added
more
difficulty.
Yeah.
A
D
If
removing
the
code
is
so
painful
with
the
current
examples
and
if
not
yeah
using
the
extension
is
also
a
clean
way
for
it
not
to
be
so
painful,
but
if
not
yeah
but
using
in
the
instance
instead
as
a
class
having
it
as
a
as
a
yes
as
a
cast,
could
be
an
option.
But.
A
A
Oh,
you
can't
do
that,
though,
because
because
then
the
API
would
have
to
know
about
the
SDK.
A
D
D
I'm,
probably
creating
here
everything
sorry,
it
was
not.
This
I
I
was
doing
this
in
the
incorrectly
yeah.
D
Yeah
and
the
problem
is
that
we
are
also
setting
meta
providers
and
things
like
this.
We
are
getting
memory
that
we
are
not
using.
Sometimes.
A
D
A
D
Mm-Hmm,
so
we
are
the
last
one:
yeah,
okay,
all
right.
Japanese
weekend,
yeah.