►
From YouTube: 2022-10-20 meeting
Description
Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room
B
C
C
So,
instead
of
depending
on
the
context
manager
to
manage
which
view
controllers
is,
which
view
controllers
are
being
traced,
I
just
use
my
own,
like
internal,
like
in
the
instrumentation
I
I
only
want
like
one
Trace
running
when
view
controllers
are
loading
and
so
I
just
I
just
once
one
starts
I
just
use
that
one.
Until
all
the
view
controllers
are
done,
loading
and
then,
instead
of
depending
on
the
Trace
context,
to
provide
me
with
the
active
Trace
yeah.
A
C
C
A
Let
me
connect
with
my
computer,
so
I
can
set
both
my
yeah
I
mean
we
would
have
been
setting
it.
Having
changed
the
camera
operator,
myself
so
probably
forgot
to
connect
the
microphones
okay.
So
let
me
I
will
connect
with
my
computer
to
share
the
the
things
okay
got.
It.
C
A
It's
quite
far
away:
I
think
I
I
forgot
to
connect
a
microphone
or
something
like
that.
Oh.
A
We
don't
have
support
people
of
technicians
here
in
this
office,
so
we
have
more
or
less
put
everything
together.
Oh
I,.
C
A
And
the
developer,
so
we
didn't
do
a
great
work.
Yeah.
B
C
A
That
is
what
we
have:
okay,
so
yeah
I
think
alolita
was
gonna,
join
us.
That's
what
it's.
C
A
Yeah
she
would
do
that
but
Maybe,
maybe
not
so
we
can
go
with
the
usual
topics.
Okay,
so
let
me
sir.
A
Yeah
he
joins
letter.
He
I
mean.
The
thing
is
that
she
contacted
me
through
his
luck
and
told
me
that
she
was
interested
in
in
knowing
what
Apple
could
do
to
help
with
the
Tracer.
So
I
told
her
that
yeah
that
she
could
connect
to
this
meeting
and
chat
with
us
about
this
RC
wanted
to
contact
privately
with
me.
I
also
offered
that,
but
she
talked
to
gonna.
She
would
try
to
connect
to
this
meeting.
Maybe
she
couldn't
do
it
today.
A
Okay,
so
for
those
topics.
A
Sorry
be
not
I,
I
have
to
do
it.
Sorry.
A
I
forgot
I
forgot
that
I
said
told
you
I
I
have
in
the
week
a
bit
crazy
with
the
stuff
I
I
had
we
were
presented
yesterday,
the
one
of
the
features
I
I've
been
working
lately.
That
was
quite
time
consuming,
so
we
presented
it
yesterday,
so
I
hope
to
have
a
bit
more
time
now
for
doing
some
other
things
maybe
help
with
open
Telemetry.
B
A
My
director
sheets
usually
beside
this
and
behind
this
room,
and
he
who
doesn't
like
me
taking
out
of
time
for
it
when
delivery,
but
okay,
but
now
that
there
are
no
European
teams
for
me,
I
think
I
would
have
time
for
some
of
these
things.
So
sorry
sorry
been
up
for
not
doing
that.
I
will
do
it
before
the
next
meeting
person.
I
I
swear
that
okay.
So
there
is
a
proper
right
word
right
on.
A
Yeah
I
I
was
just
confused
with
that.
It
was
had
that
meaning
or
just
ordered.
That
was
fancy.
So
great
I
will
do
that.
Sorry
for
the
documentation,
documentation,
yeah.
C
A
B
A
Think
it
helps
a
lot
of
the
people
so
that
that's
great
yeah
I
read
it
as
yours,
as
you
could
see,
iPhone
get
one
one,
a
small
nitpick
thing:
I,
don't
know
if
I
was
a
line
or
a
space
or
something
like
that
or
a
letter.
So
it
was
really
good.
I,
don't
know.
If,
finally,
you
remove
the
metric
stuff
or.
C
Yeah
they
they
didn't
want
that
in
there,
because
it's
so
out
of
spec,
okay,.
A
A
A
People
can
at
least
know
about
it.
C
A
I
think
it
can
be
useful,
so
yeah.
Let
me
yeah
another
another
thing
that
I
saw
in
the
place
where
documentation
is.
There
is
also
the
parent
document
where
your
Swift
examples
is
written.
It
includes
the
status
of
the
libraries
and
it
shows
tracing
beta
or
and
metrics
I
I,
don't
know
what's
alpha
or
something
like
that,
maybe
we
could
have
also
updated.
A
Tracer
should
be
or.
C
C
C
A
You
also
yeah,
but
I
know
that
people
is
using
it
on
production,
yeah.
C
A
Sounds
good
but
you
were
using
it
and
also
I.
Think
that
sir
look
it.
B
A
So,
and,
and
include
that
I
I
can
I
can
modify
the
readme
to
link
to
that
document
and
and
leave
a
gap.
So
we
can
add
your
metric
system
that.
B
A
At
least
someone
can
find
that
there,
even
when
we
say
that
that
it's
not
the
spec
an
updated
but
keep
that
code
there.
That
I
think
was
useful.
Yeah
yeah.
B
A
A
Also,
and
maybe
you
update
the
status
of
the
thing
right
but
can
I
put
that
for
you
yeah.
C
A
Yeah
we
we
had
here
the
in
the
last
meeting
into
the
pull
request
that
price
created
and
he
evolved
during
the
last
week
with
some
feedback
from
people
from
Telemetry
and
some
other
things
are
created.
So.
A
A
C
Yeah
I
was
just
the
links
they
didn't
like
the
links
they
were,
they
were
absolute
and
they
wanted
relatives.
So
that
was
the
main
thing.
B
A
Okay-
and
the
next
thing
we
had
from
last
week
was
the
protobab
format.
C
Yeah
I
talked
to
Bogdan,
who
works
in
the
protobuf,
Sig
and
I.
Think
I
I
sent
a
message
to
you
explaining
it,
but
I
can
explain
it
here.
So
what
happened
was?
Is
they
renamed
the
a
long
time
ago,
like
in
in
version
1.1.3
of
of
open,
Telemetry
Swift
when
we
updated
the
protobufs,
they
updated.
C
The
name
of
the
instrumentation
Library
info
object
to
instrumentation
scope,
but
they
added
a
new,
a
new
photobuff
index
for
the
old
name,
to
support
Json
thinking
that
Json
could
use
that
that
new
index
for
the
old
name,
so
that
Json
wouldn't
have
to
rename
everything
and
break
their
break
their
API,
their
their
exporters,
but
and
they
flagged
it
as
deprecated,
so
that
they
would
change
it
in
the
future.
C
But
for
some
reason
either
we
didn't
see
the
deprecation
notice
in
our
builds
or
they
didn't
show
up
at
all.
And
so
we
just
started
using
this
new
index
using
the
old
name
which
broke
us
for
old
versions
of
The
Collector.
C
If
we
had
updated
to
the
new
name,
it
would
have
used
the
old
index
and
our
everything
would
have
been
fine
and
in
the
most
recent
version,
we're
still
using
the
old
index
or
the
new
index
with
the
old
name,
but
they
remove
the
old
index
or
the
new
index
with
the
old
name,
and
now
it
is
broken
again.
So
that's
all
we
have
to
update
to
the
instrumentation
scope,
but
now
that
we
updated
to
the
instrument
station
scope
we're
using
the
original
index.
C
B
C
Yeah
yeah
I
fixed
the
that
that
what
was
it
the
object
that
was
being
used
for
testing
didn't
update
the
the
name
of
the
Json
indices,
so
I
fixed
that
and
that
got
the
build,
fixed
or
working
and
then
I
also
added
some
llvm
Cove
coverage
exceptions
for
the
generated
objects
that
generated
protobuf
stuff,
so
yeah.
A
I
saw
these
I
saw
that
it
was
approved
today
or
yesterday.
I
mean
I
have
seen
it
this
morning,
yeah,
so
I
just
thought
that
I
could
have
merged
it,
but
just
wanted
to
sure
to
confirm
with
you
today
that
it
was
so
we
can
merge.
Do
you
think?
Is
there
a
match
or
or
squash
and
merge,
commit
yeah.
B
Because
I
I
also
saw
that
build
was
failing.
Oh.
C
Yeah
go
ahead
if
you
scroll
down
to
my
second
to
last,
commit.
A
C
B
B
C
B
Soon
they
have
that
scope,
spans
and
other
places.
They
have
the
protocols,
they
have
instrumentation
scope.
C
Is
it
so
in
this
so
scope
spans
is
in
a
scope,
yeah,
scope,
spans
is
an
array
that's
in
there
and
that's
how
it's
represented
in
the
Json
Json.
B
Okay
yeah,
but
before
so
the
Prototype
didn't
change
any
of
that,
though,
but
still
or
the
product
of
actually
generated
Scopes
funds
instead
of
instrumentation
scope,
spans.
B
A
So
then,
then,
yes
yeah,
the
question
was
mainly
I
will
merge
it
now,
but
it
was
a
problem
with
your
company
price
and
The
Collector.
That
was
there.
Will
it
work
with
this
change?
Yes,
okay.
Okay,
then
yeah
that
that
was
my
biggest
lap
that
we
thought
that
it
may
break
so
yeah
great.
C
A
C
We're
going
back
to
the
original
index
for
that
that
object
in
in
the
the
Proto
buff,
so
it
will
work.
It
should
work
with
all
of
the
the
previous
versions
of
The
Collector.
Okay,.
B
C
B
C
I
guess
the
resolution
is:
is
that
they're
not
gonna?
Try
this
weird
re-indexing
of
old
names
for
supporting
Json?
What
they're
going
to
be
doing
in
the
future
is
just
using
Json
aliases
so
that
the
new
name
and
the
old
name
can
be
used
interchangeably
for
Json,
which
is
in
in
grpc
or
in
the
protobus
and
grpc.
It
just
uses
an
ID
and
like,
and
so
we
see
a
name
and
then
it
Maps
it
to
an
ID.
And
that's
where
the
issue
came
about.
C
A
C
A
You've
been
13
18
for
us
for
sending
and
avoiding
inducing
grpc
on
on
mobiles
yeah.
Okay,
great
so
then
I
can
question
mark.
So
so
what.
A
Have
a
yeah
in
the
project:
let
me
yeah!
Okay
and
I
can
go
directly
here.
When
we
go
to
the
export
tab.
We
have
this
hotel
exporter.
We
have
this
open,
Telemetry
Protocol.
No!
This
is
not
no.
This.
This
one
right
come
on.
A
A
It's
something
different:
it's
we
from
these
from
from
the
we
wanted
to
create
that
from
the
otlps
pan
object.
That
was
done
here
just
for
having
that
information
engagement,
but
it's
not
the
official
Json
format.
It
will
be
great
using
this
other
format.
A
I
think
when
someone
added
this
in
a
beer
long
ago
because
wanted
to
generate
Json
from
this
information-
and
it
was
not
available,
I
would
say,
but
it
was
probably
I-
don't
know
how
long
it
who
did
it
when
decoration
yeah,
it
was
created
on
one
year
and
a
half
ago
by
Yeah
by
this
person
who
wanted
yeah
I
think
he
wanted.
C
This
I
think
this
is
compatible
with
with
the
fact
you
know
well,
I
mean
that
was
basically
what
my
what
my
PR
fix
for
the
tests,
because
the
text
tests
take
the
the
output
from
the
grpc
format
and
then
translate
it.
You
know
it
gets.
You
know
translated
into
Json
and
then
translate
it
back
into
this
into
this
object.
So.
B
C
It
does
support
the
the
protobuf
format
it
just
does
not
directly
generated
from
it.
Oh.
B
Yeah,
so
if
there
is
some
update,
is
that
going
to
you
know
is.
A
C
I
guess
maybe
maybe
you
should
go,
look
at
the
go,
you
know
I
don't
know.
Actually
maybe
it
was
I
guess,
go
to
the
otlp
trace
exporter,
Json
exporter.
C
Think
it's
just
right
below
it's
right.
Oh
next,
one!
That's
the
that's
the
test,
the
the
SEC,
the
the
other
file
here.
A
A
C
A
Yeah,
that's
awesome,
yeah,
that's
okay!
So
maybe
this
can
get
up
outdated
because
we
are
not
generating
and
we
should
be
generating
automatically,
probably
from
the
product
yeah
or
something
like
that.
Yeah.
C
B
That's
something
that
yeah,
that
was
that's
a
future
project
as
well.
Whenever
there
is
a
product
of
update,
I,
think
there
is
a
compiler
that
updates
all
that
stuff
from
from
the
product
of
project
itself
yeah,
and
we
don't
have
you
know
that
addition
in
there
we
need
to
link.
B
No,
no,
no,
not
not
yeah.
So
this
is
where
you
we,
you
copy
the
product
of
files
right
yeah,
yeah
yeah,
but
but
this
is
generated
by
that
other
project.
B
A
A
B
I'll
add
that
I'll
I
had
started
it
like
six
months
back
or
something
and
then
I
got
it
off
track.
Yeah.
A
B
C
C
If
we
look
at
the
Swift
project
now
there
are
some.
There
are
some
deprecated
warnings.
B
C
A
Again,
yeah
that
it's
so
some
some
update,
yeah
deprecations,
yeah
yeah.
C
C
B
B
But
can
you
what
is
the
solution
for
this?
Should
we
yeah,
we
think
that's
an.
C
C
A
Yeah,
it
would
be
great
to
have
deprecation
of
notification
yeah
just
in
case
someone
just
notices
it
or
something
like
that
yeah,
because
they
saw
us
a
warning
on
xcode
when
you
are
building
and
that
will
flag
some
alarms
so
just
just
check
if
there
is
some
option
for
that.
Maybe
there
isn't,
but
if
you're,
updating
that
just
taking
a
look
shouldn't
be
in
much
time,
so
this
stock
file
or
something
like
this
okay.
A
So
what
about
releasing
a
new
version
with
this
protography
stuff
I,
think
that
can
be
useful
right,
yep.
A
B
A
Yeah
I
I
also
fixed
the
memory
leak
that
there
were
in
the
network
instrumentation.
It
was
quite
a
lot
of
strings.
They
were
just
strings
right.
B
C
A
Just
at
the
beginning,
I
mean
with
the
size
of
hubs:
now
that's
a
small
but
yeah,
okay,
so
yeah
and
about
the
active
context
just
to
update
you
be
not
yeah.
The
issue
that
Bryce
was
facing
was
that
he
was
creating
a
span
when
a
view
was
being
loaded.
Just
told
me
if
it's
wrong
what
I
said
because
I
tried
to.
A
If
you
have
the
same
opinion,
he
was
pretty
nice
band
with
a
view
was
loaded
and
sometimes
when
I
in
the
next
video,
we
did
a
lot
when
there
was
no
active
span.
He
created
a
new
one
and
would
use
that
as
the
parent
of
the
next
is
building
lot
that
checked
if
there
was
an
expansion.
So
in
its
beauty
love
he
checked.
If
there
was
an
active
Spanish.
A
So
the
thing
is
that
I
think
that,
in
the
view,
loading
the
system
uses
different
contexts
for
loading
things
and
those
views
that
are
related,
probably
found
themselves
in
the
same
context
and
some
other
views,
probably
other
windows
or
other
bay,
Pages
or
other
things
in
the
application,
like
I,
couldn't
find
that
active
expand
and
the
thing
was
that
they
were
actually
different
contexts,
so
they
couldn't
share
the
activist
plan.
The
activist
panel
is
not
perfect,
but
is
by
what
Apple
says
execution
context
or
something
like
that.
A
All
right,
I,
don't
know
exactly
what's
the
word,
because
they
have
changed
a
lot
in
the
recommendation,
but
the
thing
is
that
they
they
live
when
you
started
all
your
threads
that
you
create
from
there
on.
If,
even
if
you
have
a
lot
or
things
like
that,
will
inherit
your
context,
but
those
threads
that
you
generate
if
they
are
in
side
by
side
created
and
not
one
created,
the
other
will
have
different
contexts.
So
you
can
have
a
different
context
in
this
trade
and
each
other,
even
when
the
parent
was
the
same.
A
So
they
generate
the
context
from
the
parents,
but
don't
indirect
the
context
between
them
and
that's
what
I
think
was
happening
here.
So
if
you
created
a
context
when
the
app
just
starts,
that
context
will
be
the
apparent
of
all
the
other
context
in
the
app
so
every
which
build
it.
Log
will
find
that
but
cannot
communicate
with
between
between
them.
B
B
Right
so
so,
then,
then
the
span
that
is
out
of
context
does
it
have
another
root
span.
How
does
it
show?
Yeah
was.
A
A
A
So
that
was
what
price
was
finding,
so
maybe
for
that
use
case
we
have
been
talking
a
bit
at
the
beginning,
Maybe
happens
or
providing
another
context
provider
that
works
based
on
the
threat
and
using
something
like
thread.
Local
espan
could
work
for
that,
because
all
the
UI
is
done
on
the
main
thread,
so
I
think
now
you
can
put
local
values
in
into
the
thread
and
if
it's
the
main
thread,
you
know
that
it's
been
going
to
be
reused
during
your
application.
C
Yeah
I'm
not
really
yeah
I
get
yeah
I
guess
the
problem
is,
if
we
get
other
other
like
Network
requests
going
or
something
but
I,
don't
really
I.
Don't
really
I'm
not
worried
about
a
breakdown
of
exactly
which
view
controllers
are
being
loaded
where
I'm
just
kind
of
timing.
C
Like
a
general
like
a
view,
controller
is
like
your
view,
is
loading
and
I
don't
want
it
to
be
too,
like
it's
not
useful
to
know
every
single
view,
controller,
that's
being
loaded
in
Swift
UI,
because
it's
all
gibberish
right
like
it's
and
so
like
the
the
way
the
instrumentation
works
is
like.
Okay,
we
know
some
views.
Are
loading
I'm
going
to
look
through
them
for
some
context,
like
maybe
somebody
sets
a
navigation
name
for
a
navigation
title
for
one
of
them,
I'll!
C
Look
for
that,
grab
it
and
call
this
whole
thing
that
navigation
title
or
if,
if
there's
a,
you
know
an
API
to
set
the
name
of
this
context?
You
know
this
view
controller
context
and
I'll
grab
that
and
use
that,
but
knowing
each
and
every
individual
view
controller,
that's
getting
loaded,
I,
don't
care
about
that!
I
just
want
them
all
grouped
together,
so
the.
C
A
B
A
And,
and
for
Network
requests,
you
know
that
you
know
when
you
are
created
the
network
request,
but
you
have
to
map
that
to
the
response
by
using
a
we
have
a
dictionary
that
Maps
the
request
yeah
based
on
the
request,
ID
not
on
the
active
span,
because
the
response
comes
in
another
thread:
yeah
yeah
of
the
request.
Sorry,
it's
not
related
also
for
the
system,
so
you
we
have
a
dictionary
to
map
that
yeah.
It's
responded,
yeah.
A
Yeah,
they
know
that
yeah,
but
here
we
use
there
is
a
request,
ID
or
something
like
that
in
the
network
in
the
URL
session
information,
and
we
use
that
to
map
the
response
with
the
other
requests
that
we
have
created
before,
just
how
it's
done
in
the
neighborhood
instrumentation.
B
Cool,
so
do
you
did
you
have
to
use
a
different
like
you
know,
your
thread?
Local
I
mean
different
context.
Provider.
C
No,
no,
no,
no
I,
just
so
in
my
instrumentation
all
I
care
about
like
since
there
can
only
it's
one
thread:
the
UI
thread
once
one
view
controller
starts
loading
it
just
it.
It
puts
all
of
the
view
controllers
under
that
one
view:
controller
loading,
so
I,
don't
I,
don't
use
the
active
context
to
figure
out
if
there's
a
span
already
running
I,
just
save
it
in
a
you
know,
local
variable
for
for
the
instrumentation
okay.
A
A
From
any
other,
I
mean
from
any
any
threat
from
any
of
the
code.
If
it's
running
on
the
main
thread,
it
will
find
that
it's
on
the
local
storage
or
something
like
that.
A
Could
do
that
plus
that
everywhere
or
have
oh
okay?
You
also
can't
have
that
as
a
Singleton
somewhere,
where
you
can
read,
but
maybe,
depending
on
the
context,
you
could
use
that
on
the
main
I
don't
know
yeah.
C
It's
not
it's
I'm,
not
yeah.
It's
not
a
big
deal.
Yeah
I
I
still
am
setting
the
active
span.
So
that's
still
available.
It's
just
yeah,
it's
internal
to
the
instrumentation
I.
Just
don't
want
to
have
multiple
view.
Controller
spans
running.
At
the
same
time,.
B
A
C
Behavior,
but
I
mean
it
makes
sense
like
the
problem
is,
is
that
it's
really
hard
to
understand
what
Swift
UI
is
doing
under
the
hood,
because
you
have
like
your
view
definition,
but
then
it
creates,
like
four
different
view
controllers.
So
it's
like
okay.
A
No
one
understands
really
yeah.
A
Yeah
it's
difficult,
I
mean
I,
have
not
done
much
with
UI,
but
I
cannot
imagine
in
previous
work
when
I
was
doing
applications,
final
applications
trying
to
use
Swift
UI
and,
at
the
same
time
do
what
my
designers
wanted
me
to
do
with
the
UI
yeah
I
mean
I
thank
God
for
not
being
in
that
situation
now
because
is
totally
crazy.
Yeah,
okay,
okay
from
my
side,
I,
don't
have
more
topics
or
things
to
talk
about
I,
don't
know!
If
you
have
any
thing:
no
good.
A
Okay,
then
I
think
we
can
leave
it
here
today
has
been
I
think
it
has
been,
are
really
productive.
Meeting
today,
yeah.
A
Great
I
will
try
to
push
more
time
to
this
project
when
they
wake
up
my
director
who's
behind
me.
So.
C
A
B
C
A
So
if
you
want
to
vote,
you
know
that
it's
until
yeah
we
have
still
five
hours
or
more
or
less
I.
Think
for
voting
to
the
committee.