►
From YouTube: 2023-03-09 meeting
Description
Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room
B
Hello,
yeah
I,
don't
I,
don't
have
anything
to
add
today
just
wanted
to
see
if
any
change
any
changes
were
happening.
A
A
Okay,
I,
don't
know
yeah
about
let's
meet
in
actions
just
to
go
fast
here,
I
think
Kevin.
Earls
is
a
week,
something
like
that.
I
think
he
mentioned
and
also
Bryce
was
not
was
we're
not
feeling
good
today,
so
he
told
me
he
was
not
joining.
So,
let's
go
quick
with
the
updates
from
last
week.
The
OTL
phttp
exporter
is
merge
in
the
main
in
the
main
branch.
So
you
can,
you
can
play
with
it
Stephen
if
you
want
okay.
A
Yeah,
it's
it's
not
like
proof,
wrote
a
lot
and
but
it
should
be
working
test
passes
and
the
example
also
works.
A
C
A
Synchronize,
when
you
went
the
tracers
and
or
I
think
it
should
work
more
or
less
well,
but
probably
it
needs
some
retouch
before
going
production
ready,
but
yeah
for
initial
test
and
I.
Think
you
can.
You
can
try
with
it
so
yeah.
B
I'll,
give
it
a
shot
and
and
that's
protobuf
and
that's
exporting
protobuf
format.
A
Yeah
yeah
I
mean
product
is
something
that
is
not
supported
by
that
also,
it
will
need
a
third
party,
okay,
so
yeah
and
yeah
that
that
that's
good
also.
D
A
Is
an
example
in
the
Pierre.
A
It
I
see
it
yeah.
A
I
would
say,
because
there
are
now
two
otlp
exporters
now
with
erpc
and
another
with
HTTP,
so
yeah
I
don't
know
if
it's
very
clear,
both
but
yeah
fair
enough.
They
did
that
with
me.
Adding
this
exporter
and
the
status
of
it
and
I
have
a
PR
for
the
readme.
So.
A
D
It
looks
exactly
the
same
inside
the
readme
foreign.
D
A
It's
like
there
are
yeah,
this
is
the
TLP
exported
and
the
HTTP
exporter,
and
it
should
be
using
I
mean
I
think
it
was
using
is
not
using
the
HTTP
one.
D
D
C
A
Really
so
yeah
that
that
was
a
long
trip
here,
because
it
I
think
it
it's
gonna
be
really
used
in
the
near
future,
because
one
of
the
topics
I
have
to
talk
later
talks
against
the
other
grpc
one
that
it's
habit
burden
to
to
maintain
so
yeah.
For
that
one,
that's
merch
next
topic,
the
spec
version
I
also
created
a
PR,
so
the
it
this
PR.
A
Basically,
it's
very
simple,
so
the
idea
is
having
a
new
field
in
the
open,
Telemetry
object
that
stores
the
version
and
that
version
is
updated
when
we
generate
the
semantic
convention
here.
So
whenever
we
create
a
different
semantic
convention
that
we
link,
it
will
update
automatically
here
directly.
So
we
don't
miss
that
I
also
had
a
problem,
so
I
wanted
to
update
the
semantic
conversion
convention.
Be
not
I
know
you
review
it
in
the
past
and
I
found
that
I
cannot
do
it
on
my
M1
Mac
now.
B
D
I
couldn't
yeah
I
think
the
problem
is
yeah
I've
come
across
this
problem
before
so.
So
what
has
happened
is
if
you,
if
the
image
was
built
with
the
previous
version
of
Docker,
build,
it
doesn't
work
on
M1,
so
the
previous
version,
meaning
the
older
Macs,
were
on
Intel
right,
okay,
the
Intel.
So
when
you
do
a
Docker
build,
it
would
use
the
default,
which
is
you
know,
the
the
chip
that
that
Max
is
on
so.
A
So
there
is
no
way
to
yeah
to.
D
The
there
is
a
way
there
is
a
way
you
have
to
use.
Docker
itself
has
now
added
a
something
called,
build
X,
so
build
X.
Does
architecture
independent
builds,
meaning
you
can
run
it
on?
Image
can
be
run
on.
You
know,
M1
M2,
you
know
Intel
and
so
on.
Right,
okay,.
D
D
Can
I
can
yeah?
Where
does
it
have
any
links
on?
You
know
who
this
who
maintains
the
SIM
card,
because
I
remember
there
was
one
image
that
I
was
following
up,
and
that
was
the
image
for,
or
maybe
it
was
just
that
was
for
the.
D
D
But
the
build
tools
are
for
the
the
the
hotel
buff,
the
protocol,
buff
compilation
for,
but.
D
A
We
are
a
bit,
I
mean
it's
not
that
we
need
to
be
out
updated,
but
we
are
a
bit
out
of
data,
probably.
D
C
C
A
A
D
A
D
C
A
Thought
that
it
would
be
great
to
update
that
and
I
couldn't
so.
A
The
diversion
thing
that
I
think
it
will
be
useful
because
I
think
that
the
aspect
says
that
we
should
send
that
in
a
header
when
we
send
in
the
otlp
payload
to
the
backend.
Probably
it's
TP
also
so
that
that's
something
we
should
update.
A
Okay,
next
topic
about
the
metric
for
right,
it
was,
is.
A
And
he's
not
today,
but
he's
probably
working
on
it,
because
he
he
had
an
API
for
about
two
weeks
now
so
probably
will
be
halfway
to
to
finish
it
and
yeah
and
the
URL
session
loading
time
yeah.
It
will
have
to
be
updated,
but
not
not
now
currently
and
that's
from
last
week.
A
A
Easy
that
said
that,
when
building
the
project
building.
C
A
A
Yeah
I,
I
couldn't
and
yesterday
also
another
developer
this
one
from
lightstep,
so
I
can
I
mean
when
you
have
reports
from
from
companies
that
work
fully
on
this
probably
I.
Also
had
this
I
miss
you,
the
the
thing
is
that
I
I
try
to
reproduce
locally,
but
I
couldn't
so
I.
A
Here
is
that
the.
A
Otlp
exporter,
have
you
linked
open,
TLP
or
TLP?
Yes,.
A
I
think
that
when
you
build
for
distribution
or
something
like
that,
depending
how
you
build
your
project,
vrpc
package
is
not
compatible
with
that
option
and
it
end
up
missing
things.
But
I,
don't
know.
If
that's
what
happens
here,
because
in
my
project
I
could
use
I
could
see
this
Library.
B
I
wonder
if
he
had
an
older
version
of
Swift
Neo
or
something
yeah.
A
And
and
erpc
also
I
I,
they
were,
it
happened
to
them.
It
I
tried
today
and
it
didn't
fail
for
me
this
way.
It
was
so
I
think
that
yeah,
this
Swift
package
manager
thing
for
versioning
and
transition
and
transitive
dependencies
is
a
real
nightmare.
Yeah.
A
Much
yeah
I
think
it's
I
mean
we
are
only
importing
one
library
from
Apple
that
is
erpc
yeah,
all
the
rest
just
come
transitively
and
they
I
mean
it's
it's
a
a
bit
of
a
nightmare
because
from
day
to
time
you
they
don't
let
you
fix
a
version.
They
said
you
shouldn't
fix
a
person.
Yes,
yes,
and
it
it
I,
don't
know
it
fails
from
time
to
time.
I
told
them
that
I
couldn't
reproduce
so
if
they
can
have
a
sample
project
or
something
like
that.
A
Last
time
we
also
had
some
problems
with
erpc
and
the
build
for
distribution
option
that
it
was
missing
some
neo-atomics,
something
like
that.
Yeah.
A
It's
yeah,
it's
like
like.
Do
you
never
know
what's
happening
and
the
only
thing
I
could
think
was
they
also
ping
me
on
honest
luck
yesterday,
the
only
thing
I
could
think
is
setting
your
dependencies
yourself.
The
transitive
dependence
is
as
if
it
were
yours,
try
to
set
diversity
on
there
and
try
to
make
it
work,
but
yeah
it's
it's
a
nightmare.
So
that's
why
I
think
that
the
faster
we
can
move
away
from
grpc
by
default.
A
B
The
choice
does
it
keep
the
connection
open.
Is
that
the
is
that
that
was
the
point
that
people
liked
about
it?
I.
A
Think
yeah
the
the
HTTP
one
currently
allows
to
set
your
own
URL
session,
so
you
can
configure
your
url
session.
However,
you
want
okay.
B
A
You
don't
provide
one,
it
will
create
an
ephemeral
one,
so
it
doesn't
catch
anything
and
that
stuff.
But
if
you
want
to
have
your
proper
control
and
settle
your
identity,
I
mean
all
your
headers,
all
your
system
whatever
or
it
allows
using
a
a
given
a
URL
session.
A
Yeah,
that's
right!
That's
right!
So
it
only
posts
things
using
that
session
so
that
whatever
you
want
there
I
I
think
that's
much
better
than
yeah
context.
I
like
for
for
a
mobile
I
mean.
D
D
You
cannot
see
things,
but
it's
at
the
same
time.
It's
binary
and
more
efficient
right.
It's
a
HTTP
is
all.
A
Yeah,
maybe
in
a
Herbert,
yeah
I,
don't
know
how
I
mean
efficiency
in
sending
data
but
processing.
It
is
much
much
more
expensive.
So
yeah.
B
C
A
So
yeah
I
don't
know
what
what
the
best
option,
but
I
I
am
yeah.
After
this
time,
I
started
to
think
that
maybe
we
should
even
have
separate
a
otlp
exporters,
one
for
HTTP
alone,
one
for
grpc,
so
we
can
really
use
one
or
the
other
if
it
has
some
problems.
B
I
I
can
sure
see
my
management
asking
me
to
put
both
in
and
have
a
switch,
so
people
can
choose.
I
can
I
can
picture
that
happening
too
so,
but.
A
Yeah,
we
want
more
choices,
but
you
could
link
both
libraries
right
if
you
want,
of
course,
so
yeah
having
just
different
names
for
for
that
and
the
classes.
D
C
D
A
Yet
maybe
we
cannot
separate
that
yeah
this
one
pandemic
protocol
I
I
choose
a
really
bad
name
for
it.
Sorry
so
yeah
the
trace,
https
exporter
this
one.
Now
it.
C
C
D
C
A
Yeah
sorry,
then
I
have
to
change
the
with
me.
I
really
missed
it.
I
would
say:
I
added
this
to
the
readme.
C
A
No,
it's
not
you
ingestion.
Sorry,
sorry.
We
have
another
Edition
exporter,
but
that's
yeah.
We
have
an
obligation
supporter,
but
that
doesn't
have
the
transport
code
or
something
like
that.
It
just
playing
Json
export
that
you
could
send
that.
But
I
don't
know
if
we
are
supporting
for
traces,
but
not
for
everything.
Yeah!
That's
right!.
D
So
what
is
the
advantage
in
doing
HTTP
with
protobufs,
because
a
Proto,
a
grpc
by
default,
also
is
https
right.
D
Sorry
grpc
also
uses
https.
So
what
is
the
advantage
in
doing
https
with
protobuf.
A
A
Instead
of
using
erpc
for
connection
to
the
back
to
to
the
to
the
back
and
it
uses
a
HTTP
intake,
so
you
can
connect
that
without
opening
grpc
for
the
collector
in
the
servers
and
something
like
that.
Okay.
D
So
because
there
is
no
real
gear
pieces
more
efficient,
because
I
thought
protobuf
will
so
because
protobuf
has
to
be
compiled.
It
is
a
binary
right,
so
you're
still
sending
a
binary
payload
over
http,
yeah,
yes,
so
and
which
is
what
grpc
also
does
so
because
grpc
under
the
covers
uses
https.
And
it
has.
You
know,
product
office
binary
and
you
know
it
uses
https
so
that
it
can
encrypt
it.
A
Yeah
we
are,
we
are
getting
about
in
the
same
way
that
erpc
does
it,
but
instead
of
getting
the
erpc
connection
and
the
channel
and
all
that
stuff.
A
Okay,
I
think
yeah.
There
is
a
way
to
to
get
the
yeah
the
the
Json
format
from
the
Proto.
B
A
That
we
we
have
here,
we
also.
A
And
that
yeah,
yes
as
a
human,
readable,
yeah,
yeah.
A
I
did
understand
what
he
meant
here.
Yeah
I,
don't
know.
B
Hey
Carlos,
we
know
this
one
yeah
yeah
this.
C
B
Is
this
is
the
XC
framework
sort
of
thing
and
any
older
framework
has
code
for
the
simulator
and
and
devices
in
there?
But
when
Apple
in
their
wisdom,
made
it
made
64-bit
arm
Max
the
M1
Max,
they
called
the
the
type
in
the
framework
is
arm
64,
exactly
the
same
as
it
is
for
the
phones,
but
it's
not
compatible
they're,
both
arm
processors
but
they're,
not
nearly
close
enough
to
be
identical
code.
B
So
basically,
you,
the
in
the
old
days,
you'd
end
up
trying
to
link
to
to
objects
into
a
into
a
fat
binary
in
your
framework.
So
they
came
up
with
this
XC
framework
thing
which
basically
just
added
another
layer
of
folders
to
separate
the
devices.
And
what
he's
missing
is
is
that
if
he
tells
it
not
to
use
the
M1,
it
builds,
but
it
can't
run
on
the
M1
because
there's
no
simulator
and
if
he
tells
it
to
run
the
simulator
on
the
M1.
B
A
B
I
build
a
framework
as
well
out
of
this
library,
but
you
have
to
build
an
XC
framework
or
or
to
solve
the
conflict
in
the
old
days
when,
when
M1
started
coming
out
and
we
all
had
still
had
Intel
Max,
what
we
do
is
just
say:
don't
build
for
M1
and
that
magically
solves
the
problem
because
it
doesn't
include
them.
A
Universal
binaries
yeah.
They
also
had
some
of
those
yeah.
B
So
you
have
to
just
switch
to
that
XC
framework
format
just
the
way
it's
exported
and
it
just
basically
packages
it
differently.
And
if
you
look
inside
the
sort
of
the
Manifest
file
of
that,
you
can
just
see
that
there's
a
there's
a
simulator
tree
and
a
device
tree
and
then
the
fact
that
there's
two
things
in
the
same
name
they're
in
different
they're
in
different
folders.
That's
really
the
only
major
change
to
taxi
framework
that
the
binaries
are
still
the
same.
A
Okay,
I'm
gonna
ask
something
here:
if
you
I
will,
if
you
want
to
add
something
to
this
thing,
I
will
add
something
about
the
building.
You.
B
Could
really
tag
me
in
it
here:
I'm
I'm,
so
I
haven't
been
I'm,
not
sure
entirely
sure
if
I've
got
that
set
up
so
that
I
can
make
comments,
but
yeah.
A
A
B
He's
and
and
the
other
thing
too,
if
you
get
far
enough
along
too
you
can
that
the
exit,
the
x86
64
Apple
simulator,
is
for
an
Intel
MacIntosh,
and
you
can
also
exclude
that
and
then
it
won't
work
on
an
Intel
Mac.
B
As
he
tries
to
build
an
old
school
framework
with
a
lipo
thing
in
there,
it's
not
going
to
work.
B
B
Yeah,
that
sounds
good
yeah,
that's
good,
and
if
he
comments
back,
I'll,
try
and
join
the
thread
and
see
if
we
can
help
them.
If
it's
yeah.
B
Kind
of
went
through
this
I,
don't
know.
Last
year
you
know
building
our
thing
and
just
dealing
with
making
this
work.
Our
customers
found
it
first,
unfortunately,
because
we
didn't
have
M1
Max
until
well.
After
other
people
did
and
our
customers
were
finding
it
up
the
hard
way.
A
Yeah,
that's
right:
yeah
I
built
it
for
a
project
that
is
used
on
testing
so
yeah
it.
It's
always
I'm
using
running
mainly
on
the
simulator
Yeah,
the
code.
So
yeah,
let's
see
with
the
NXT
framework
with
it,
but
I
had
not
thought
about
the
XC
framework
when
he
with
what
he
posted,
because
I
was
thinking.
He
was
ingesting
directly
the
the
code
and
that.
C
B
You,
you
know
I,
think
I,
think
that's
exactly
where,
where
he's
having
also
it's
always
it's
always
telling
when
someone
says
new,
M1
Mac,
that
means
like
they
just
got
one
and
now
all
their
stuff
and.
A
B
A
B
A
Yeah,
okay,
great
I,
don't
think
there
are
more
easiest
to
handle
and.
B
A
Yeah
yeah
I
will
I
would
want
that
that
other
topic.
D
B
The
same
armor,
okay,
I
won't
have
this
problem
because
it's
not
a
it
there
isn't
a
separate
simulator
build
for
M2
and
they've
said
M3
as
well
are
are,
are
essentially
armed
processors.
So
the
code
stays
the
same.
It's
just
a
higher
performance
versions
and.
B
B
That'll
be
another
version
again,
but
the
new
XE
format
was
designed
to
tolerate
as
many
versions
as
you
need.
There's
no
limits
or
types
not
like
the
old
days
where
there
was
one
simulator
and
one
release
object.
You
know
now
you
could
have
an
array
of
17
of
them
in
there
for
all
that
man.
A
Okay,
any
other
topic
that
you
you
can
have.
A
A
Okay,
then
I
think
we
can
end
it
here.
I
am
not
joining
this
week.
I
I
am
on
PTO
the
full
week.
Congratulations.
B
A
Will
be
two
weeks
for
me
for
the
next
meeting.
B
A
Yeah
I
mean
I
had
days
from
last
year
that
we're
going
to
be
dated
and
when
Martin,
oh.