►
From YouTube: 2023-02-02 meeting
Description
Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room
D
C
Am
can
you
hear
me
good
I
had
I
had
one
question,
the
the
export
or
the
hotel
export
open,
otlp
exporter
defaults
to
speaking
communicating
in
grpc
correct.
Yes,.
B
The
yeah,
the
current
border
just
supports
erpc
by
by
default
yeah.
We
still
don't
support
directly
Json
with
with
with.
C
Http
yeah,
so
we
do,
is
there
we
don't
have.
Okay
is,
do
we
plan?
Is
that
plan
to
come
at
some
point
or.
B
He
is
more
or
less
I
mean
the
disappear.
Who
was
based
on
that,
but
the
author
I
mean
received
some
feedback.
No,
he
didn't
added
all
the
things
that
were
needed.
Okay,
so
yeah.
It
was
like
a
simple
thing:
he
that
God
was
missing
tests,
for
example,
okay,
and
he
had
not
provided
him
and
also
yeah
I.
Don't
know
there
are
also
some
more
feedback
that
I
don't
know
if
he
addressed
okay.
C
B
C
B
Kevin
I
think
took
a
look
also
in
that
area.
Right.
E
Right
so
I
yeah,
I've,
been
obviously
haven't
been
around
for
I've,
been
tied
up
with
some
other
things
for
the
last
couple
weeks.
So
I'm
going
to
try
to
look
at
that
again.
In
fact,
I
just
started
looking
at
it
this
afternoon,
so
I
think
that
originally
was
submitted
in
November,
and
then
people
ask
for
a
couple
of
things.
E
One
was
yeah
tests,
like
you
mentioned,
and
also
it
was
to
do
the
posts
and
background,
and
the
original
author
has
never
replied
so
I'm
going
to
try
to
pick
that
up
mostly
I,
don't
know
if
I'll
be
able
to
do
anything
tomorrow,
but
mostly
next
week,
I
should
be
able
to
work
on
it.
Excellent.
C
Excellent
yeah
one
of
the
here
at
Cisco,
one
of
the
one
of
the
projects
going
The
Collector
they
built
is
HTTP
and
yeah
and
we
were
having
communication
difficulties.
Obviously,
and-
and
so
this
was
sort
of
the
well
who's
gonna
go
first,
are
they
going
to
support
grpc
or
are
we
going
to
support,
as
is
always
the
case,
but
that's
good
to
know,
I'm
glad,
I'm
glad
it's
a
possibility
at
some
point.
Okay,
thank
you.
B
Yeah
yeah,
let
me
share
the
document.
I,
don't
know
if
you
have
any
topic
to
add
it
yeah
also.
The
document
has
changed,
I,
don't
know
if
yeah
I
was
trying
to
change
it
to
be
owned
by
okay,
I,
don't
know
if
you
have
access
now
to
it.
Do
you.
B
I
I
yeah.
They
asked
for
a
change
in
the
documents,
so
they
were
owned
by
the.
Let
me
share
it
in
the
slack
Channel
I
can
say
also
here
at
the
URL.
If
you
want
to
add
something
there,
some
topic
or
something
like
that,
I
will
have
to
also
change
that
in
the
in
the
slack
channel.
So
because
I
we
have
yeah.
D
A
B
I
have
to
change
it
in
the
yeah
I
think
I.
Have
it
yeah,
yeah
so
yeah
that
that's
the
the
document
that
we
have
for
yeah,
yeah,
Kevin,
I,
didn't
know
your
company,
your
current
company,
so
I
didn't
add
any
I.
E
I
actually
am
not
working
right
now,
so
I
was
at
Red
Hat
and
so
there's
been
a
little
December.
Okay,
yeah
taking.
B
B
C
Have
I
have
yes,
I'm
using
well
1.3.1,
okay,
working,
fine.
B
Okay,
we
are
releasing
a
new
version
that
we
have
some
breaking
changes
in
code
source
code,
breaking
changes,
because
in
the
to
like
one
month
ago
or
three
weeks
ago,
we
were
talking
with
one
of
the
users
that
said
that
I
don't
know
this
is
looking.
No.
This
is
not
looking
very
good
but
yeah.
The
plan
was
that,
depending.
B
That
you
in
this
initi
in
italicized,
the
the
library
you
could
end
up
having
to
insta
two
instances
of
the
open
Telemetry
object,
one
through
open
Telemetry
SDK
instance,
and
the
other
through
open,
Telemetry
dot
instance.
That
should
be
more
or
less
the
same,
but
the
it
could
end
up
being
messed
up.
So
also
it
was
not
very
clear.
The
I
mean
it
was
not
the
official
way
of
using
it
using
open,
Telemetry
SDK
from
clients
who
has
not
the
desired
thing,
at
least
by
default.
B
So
we
we
have
changed
that
and
there
is
yeah,
so
they
open
Telemetry
SDK
instance
is
not
anymore.
You
can
access
the
same
functionality
through
open
telemetry
dot
instance
so
like
instead
of
from
Pennsylvania
SDK
instance.
Now
you
have
to
access
like
this,
and
maybe,
if
you
are
using
something
in
I
mean
you
should
initialize
it
in
the
way
that
you
send
the
documents
so
with
the
Tracer
provider
and
that
stuff,
instead
of
calling
it
that
somehow
initialize
easily.
B
But
we
have
also
updated
the
examples
and
the
code
and
the
documentation
is
missing
for
the
update
and
that's
why
we.
So
we
are
going
to
release
version
1.4.
As
we
talked
last
week,
I
have
a
pre-release
version,
so
if
you
ping
the
number
you
can
download
that
the
examples
and
the
code
is
working
but
the
documentation
at
open,
Telemetry
IO
a
web
page
is
not
updated.
B
So
I
am
waiting
for
that
documentation
to
release
it
officially
and
Bryce
was
gonna
change
that,
but
he
told
told
me
before
that
he
was
with
a
vehicle
and
he
he
was
not
going
to
join
this
meeting,
but
I
will
tell
him
to
please
update
documentation
because
in
the
documentation
in
some
places
it
still
talks
about
open
Telemetry
SDK
instance,
and
this
object
is
not
anymore.
B
So
yeah
that's
a
source,
a
small
Source
called
Breaking
Chains.
You
can
see
the
the
commit
that
change
that
how
it
was
changed
in
the
examples,
so
you
should
use
that
way
of
initializing.
That
is
the
same.
That
was
more
documented.
So
if
you
use
the
documentation
for
starting
it
should
be
good
for
you
yep.
Not.
You
will
get
some
error
that
using
the
the
differences
with
the
previous
commit
that
you
can
see
from
the
release
note.
B
Let
me
I
understand
that
in
the
yeah
I
mean
the
release
is
here
in
Period
release
mode
because
we
are
missing
the
documentation,
but
in
this
call
me
the
manual
that
must
be
updated
with
small
things,
but
in
the
commit
where
things
are
changed,
you
can
see
the
differences
that
needs
to
be
the
change
that
must
be
done
in
the
in
the
sample.
In
the
examples,
for
example,
instead
of
initializing
like
this,
you
have
to
initialize
with
just
open
telemetry.
B
B
It
adds
a
bit
more
code,
but
basically
it
does
the
same,
but
in
a
clean
way,
because
if
you
added
the
Tracer
like
this,
you
could
end
up
with
different
instances
or
the
network.
Instrumentation
could
be
referring
to
another
Tracer.
That
was
not
the
one
being
used
and
it
was,
it
could
end
up
being
been
missed.
B
So
we
had
to
change
that,
but
we
are
changing
the
number
at
least
a
minute,
not
the
the
other,
the
big
one,
because
yeah
it
will
be
the
first
change
for
something
that
is
just
a
simple
code.
But
for
the
rest
it
should
work
the
same
or
maybe
even
a
bit
better,
because
you.
B
Yeah
so
yeah
I
will,
whenever
the
documentation
is
updated,
I
will
release
it.
But
if
you
want
to
test
with
a
new
version,
you
can
already
use
that
number
yeah
in
the
your
dependencies
because
they're
the
version
exists,
but
it's
not
announced
as
the
latest
release.
B
So
you
have
to
manually
add
it
to
to
check
that
I
already
changed.
My
the
I
I
use
this
library
for
other
users
for
for
a
project.
I
do
add
data
log
and
I
change
my
code
also
for
this,
and
it
took
me
some
minutes
to
to
change,
but
it.
B
Yeah,
it
is
there,
so
it
should
be
nice,
so
release
waiting
for
the
commentation.
E
B
Oops,
okay,
okay
and
we
have
been-
and
that's
the
only
topics
we
have
from
meeting
actions.
We
have
been
talking
about
the
otlp
exporter
and.
B
There
is,
as
I
said,
there
is
a
PR
in
earlier
stages.
Let's
say
bigger.
B
Missing
but
I
mean
did
you
have?
Currently,
you
have
two
options,
basically,
depending
on
what
you
want
to
export.
If
you
want
to
use
the
collector,
you
can
also
configure
the
RPC
on
on
the
mobile
phone
temporarily.
If
you
want
to
test
that
everything
is
working
on
your
side.
There
is
an
example.
There
is
a
no
TLP
example
with
erpc
yeah.
B
Yeah
and
I
think
that
also
the
manual
explains
how
to
use
that
with
with
erpc
and
creating
the
channels
and
that
stuff
in
the
manual
I
think
that
price
brought
about
it.
That's
the
approach
that
he's
using
in
his
product.
So
is
it's
totally
functional,
but
yeah.
B
There
is
also,
if
you
are
just
using
a
sponge
I
think
there
is
a
there
is
ideation
serializer
for
spans.
That's
compatible
with
otlp
I
think
so.
B
This
had
otlp
Json
exporter
class
already
that
only
supports
the
spans,
but
those
spans
are
compatible
with
otlp
I
would
say
so
that
will
be
another
option,
but
you
will
have
to
handle
all
the
all
the
URL
session
yeah
send
that
the
exporter,
that's
in
the
in
the
pr
already
handles
the
connections
with
the
backend
or
tries
to
do
it
automatically,
but
it
has
some.
You
know
some
feedback
from
users
that.
D
C
That
happen
at
all
is
that
a
is
that
a
I'm
just
I'm,
just
I
I,
don't
think
I.
Don't
think
we'll
need
that.
But
does
anyone.
B
B
Ahead
I
think
I
mean
you
should
probably
code
something,
but
lots
of
the
things
are
already
solved
so
yeah.
C
B
C
Cisco,
we
have
there's
a
whole
bunch
of
different
groups,
it's
a
big
company,
doing
variant,
open,
Telemetry
things
and
they
keep
coming
up
with
all
sorts
of
weird
collectors
and
we've
I've
I'm
building
the
iOS
side
of
things,
and
they
it's
one
of
the
few
things
that's
actually
working
already.
So
I
start
so
they
all
say:
hey,
send
me
data
and
they
they
came
up
the
other
day
when
I
started,
sending
grp.
C
Who
knows
you
never
just
trying
to
be
ready.
B
I,
don't
think
we
have
any
use
here
that
uses
that
approach.
For
that
also,
the
problem
with
using
protoba
on
on
on
Swift
is
that
you
don't
have
a
you,
have
to
add
a
protoba,
a
serializer.
Yes,
so
that's
that
that's
another
dependency.
While
you
have
Json
already
in
the
system,
so
yeah,
that's,
probably
the
the
biggest.
Please
do
that.
B
Here
at
data
also,
they
they
some.
We
have
some
users
that
use
protobuf
over
over
HTTP
for
some
of
our
Solutions,
but
for
iOS
I
only
use
Json
over
it
I.
D
A
B
Okay,
so
I
don't
have
anymore
topics
from
my
side.
Do
you
have
any
topic
Kevin?
You
said
you
were
planning
to
review
this
PR.
E
Or
write
your
ears
aren't
I'm
planning
to
pick
that
pick
up
on
that
again
tomorrow,
beginning
of
next
week-
and
you
know,
take
care
of
some
of
the
stuff
that
he
didn't
do
that
the
original
submitter
didn't
do
so
write
some
tests
and.
C
B
B
E
B
B
B
B
Expect
many
users
of
that
and
having
an
example
that
shows
how
to
call
that
easily
I
think
it's
the
the
best
help
for
our
users.
D
B
D
B
Commented
code
that
works
on
one
side
or
the
other,
or
just
a
Boolean
that
change
the
way
it
works
because,
probably
is
the
same
configuration
same
Docker
file
same
everything
is
using
different
approach.
It
will
be
great
also
probably
to
test
and
to
code.
The
the
thing
is
whether
on
top
of
something
that
more
or
less
works,
yeah.
B
Okay,
so
any
other
topic,
any
other
problem
adapt.
B
Okay,
I
think
that
they
were
going
to
we
we
added
with
version
1.3.
We
added
support
for
launch
I,
don't
know
if
you
are
into
logs
spaces.
B
I
think
that
they
were
going
to,
they
said
that
they
were
going
to
approve
officially
the
spec
for
logs.
That
I
think
that
we
are
currently
covering
I
suspect
that
I
think
that
I,
we
probably
rise
will
will
take
care
of
that.
Just
to
validate
that
we
are
covering.
Everything
is.
F
There
is
there
some
semantics
test
that
we
have
to
go
through
to
make
sure
that
our
implementation
is
compliant
with
our
the
hotel,
spec.
F
Isn't
that
in
that
semantic
convention
directories
there's
some
scripts
right
for.
B
We
have
a
semantic
conventions
file
that
we
update
from
time
to
time.
Do
you
remember
that
I
don't
know
where.
F
B
That
that
generates
our.
B
We
have
yeah,
we
have
somewhere,
we
have
a
I,
don't
know
exactly
what
it
is.
No.
B
It
it
generates
the
the
semantic
convention
from
the
from
the
spec
yeah
with
this
stuff,
but
and
generates
from
aversion
that
you
should
put
here.
B
B
B
B
D
D
B
B
Yeah,
maybe
yeah,
we
should
check
if
we
are
still
valid
or
they
are
just
new
things.
Yeah
do
you
want
to
take
a
look.
F
D
B
Those
files,
okay,
let
me
check
the
code.
Those
files
are
then
used,
they
are
sweet.
Files
are
not
compiled
inside
the
project
but
probably
have
to
be
copied
to
their
respective
places.
Probably
yes
and
then.
F
So
so
what
does
that
cement?
Yeah
I
see
that
it's
there
is
a
semantic
attributes
that
Swift
under
open
Telemetry.
B
B
Okay,
yeah,
let.
B
B
D
F
A
B
Added
someone
some
some
extra
attribute
and
the
other
I
don't
know.
Maybe
you
said
that
it's
very
general.
F
Oh,
no,
it's
under
it's
under
Trace
right,
so
yes,
I
would
think
it
should
be
under
you
know,
because
there
will
be
a
symmetric
attribute
for
each
of
them
right.
Foreign.
B
D
F
Oh
sorry,
we
I
didn't
so
so
semantic
attributes.
Dot
Swift
is
is
probably
from
a
time
when
Matrix
was
not
ga
November,
2021,
yeah
I,
don't
know
probably
yeah
yeah,
because
I
think
metric
was
not.
Metrics
was
not
yet
till
like
beginning
of
2022.
E
B
Now
we
had
somewhere
diversion
yeah,
we,
we
must
I,
think
there
is
a
place
where
we
have
to
say
which
version
we
are
using
in
the
headers,
which
was
that.
B
And
we
have
not
that
person
anywhere.
So
do
you
know
what.
D
B
B
So
maybe
we
could
use
the
expect
to
create
a
file
or
use
that
file
from
this
project
attributes
or
something
like
that,
but
that
will
mean
modifying
this
somehow
to
read
the
to
export
this
file.
This
number.
B
From
here
to
export
to
some
file
Maybe,
so
maybe
something
like
I,
don't
know
just.
B
F
B
Yes
yeah,
so
maybe
we
can
use
that
now
this
and
just
write
another
file.
We
include
in
the
project.
What
do
you
think.
F
B
Forward
and
also
send
our
version
when
we
send.tlp
in
the
headers
I'm
saying
in
the
version
that
we
are
using
but
I
think
that's
missing,
also
correct.
Okay,.
B
B
Yeah,
so
the
thing
is
that
they
speak
is
updated
from
time
to
time,
adding
new
tags
and
changing
some,
usually
adding,
so
they
make
some
Breaking
Chains
like
yes,
we
will
be
uncompatible
if
they,
but
they
are
not.
Usually
they
don't
break
the
tax,
so
we
will
be
uncompatible
with
the
collector
and
things
like
that
we
could
be
uncompatible,
but
the
thing
is
that
they
usually
add
more
things
and
we
just
update
from
day
to
time.
So
yeah,
probably
we
know
this
is
gonna.
B
Take
a
look
at
this,
so
we
at
the
same
time
we
update
the
person.
We
can
update
the
spec
also
and
be
a
bit
more
up
to
date,
so
yeah,
and
also
we
can
report
that
version
somehow
in
some
place
that
currently
we
don't.
B
Okay,
any
other
topic
that
you
have
in
mind.