►
From YouTube: 2022-08-17 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
A
B
B
A
Yeah
sure
so
the
first,
if
you
have
any
things
you
want
to
talk
about,
please
add
it
to
the
agenda.
I
have
two
things
that
I
just
added
just
for
General
visibility.
Maybe
I'll
talk
about
them
first,
some
solution.
Then
we
go
to
the
Android
topic.
A
So
yesterday,
I
requested
the
TC
DC
sponsor
to
please
start
joining
are
sick
I
think
we
need
some
help
with
a
few
things
in
the
specification
like
the
resources
sessions,
how
to
represent
sessions
and
potentially
other
other
things.
So
there's
a
new
process
which
includes
creating
a
project
tracking
issue
which
I
did
create
yesterday
and
hopefully
a
DC
member
will
be
assigned
to
us.
A
If
you
can
take
a
look
at
the
issue,
if
I,
if
you
have
any
things
anything
that
I
missed
in
in
there,
please
please
feel
free
to
add
edit.
The
issue,
and
the
other
thing
that
I
wanted
to
mention
is
that
we
have
the
the
logs
API
PR
in
the
specification
and
also
open
and
also
in
the
JavaScript
SDK,
there's
a
draft
PR
with
implementation
of
the
API.
A
This
will
be
this,
because
this
is
kind
of
the
foundation
of
you
know
a
lot
of
the
work
that
we're
doing
and
it
will
be
like
once
this
PR
is
merged
and
we
have
a
logs
SDK
will
be
able
to
start
implementing
some
of
the
events.
So
please
take
a
look
at
it.
B
Okay,
yeah:
we
can
talk
about
the
Android
SDK
and
thanks
Matias
for
joining
I
hope,
I'm,
taking
a
name
right
anywhere
else
from
the
Android
team.
Jason.
Are
you
as
well
from
the
same
team.
B
Yeah
so,
basically,
many
months
ago,
I
think
John
Watson.
He
used
to
join
this
Sig
and
he
at
one
point
indicated
that
you
know
Splunk.
You
know
they
are
open
to
contributing
the
Android
SDK
to
open
telemetry.
B
B
So
far,
so
even
if
we
actually
don't
have
folks,
you
know
we
have
been
making
a
good
progress
on
the
specification
with
respect
to
several
things,
client,
side
and
and
I
thought
it
would
be
good
to
have
some
representation
from
the
mobile
side,
because
you
know,
especially
there
are
a
couple
of
topics.
You
know
how
we
do
sessions,
How,
We,
Do,
Standalone
events,
the
different
semantic
conventions.
B
Well,
I
thought
it
might
be
good
to
you
know,
run
it
by
you
folks
as
well
every
once
in
a
while,
because
I
am
not
aware
of
anybody
else.
That's
working
on
mobile
application
instrumentation.
B
There
is
a
swift
Sig,
but
I
I
think
they
don't
focus
on
iOS,
it's
a
general
Swift
instrumentation.
B
So
among
the
many
things
I
think
one
agenda
was
to
see
few
folks
like
what
you
think
about
at
this
point.
Do
you
have
like
Cycles,
or
you
know,
bandwidths,
to
figure
out
a
way
to
contribute
the
Android
SDK
that
you
have
a
Splunk
to
the
open
Telemetry
project?
I
have
no
idea
what
it
involves.
D
Well,
I
think
any
of
us
could
sort
of
jump
in
on
this,
but
I'll
I'll
jump
in
and
take
a
stab
at
it,
and
you
can
tell
me
where
I
screw
up
so
yeah
I
think
we
are
hoping
to
have
some
Cycles
in
a
few
weeks
to
be
able
to
help
with
this
effort.
D
D
There's
no
open
Telemetry
specs,
so
it's
kind
of
the
Wild
West
as
to
what
we
implemented,
but
we
did
our
best
and
there
there
are
certain
aspects
of
the
implementation
that
are
kind
of
specific
to
Splunk
and
how
we
do
things
and
so
I
think
our
initial
thoughts
were
to
maybe
try
and
find
seams
around
that
custom.
These
Splunk
specific
behavior
and
carve
those
out
and
to
be
able
to
make
a
vendor
neutral
donation
of
the
SDK
I,
don't
know
what
else.
E
I
think
the
only
other
so
the
way
we
wanted
to
approach
this
was
santoshi
mentioned.
You
know,
someone
from
you
know.
Cisco
might
also
be
able
to
help
out
a
little
bit,
so
our
library
has
been
open
sourced
anyway.
We're
happy
to
have
anyone
have
a
look
at
it.
E
Give
us
feedback
where,
but
as
Jason
mentioned,
the
goal
is
to
kind
of
start
separating
out
the
Splunk
specific
and
maybe
sort
of
the
more
generic
Hotel
pieces
of
it
first,
and
we
were
thinking
of
doing
that
within
our
library
itself
in
the
sensor,
rather
than
creating
an
Hotel
project
and
then
sort
of
taking
away
from
it
because
then
just
maintaining
two.
At
the
same
time,
it's
just
going
to
be
a
bit
of
a
pain.
We
can
start.
E
E
B
Yeah,
at
least
in
the
beginning,
I,
don't
see
too
many
contributions
from
other
folks,
I.
Think
whatever
you
guys
have
in
mind
that
you
have
planned
that
only
you
will
be
contributing
from
others.
It
will
be
mostly
usage.
If
I,
you
know,
can
take
a
guess.
You
know
once
people
start
getting
familiar
only
after
that
I
think
they
will
want
to
you
know
onto
that,
so
it
will
be
a
while
so
from
open,
telemetries
perspective.
B
Are
there
any
like
how
anything
is
to
figure
out
like
how
to
create
a
report
or
anything?
Is
that
like
something
you
folks
can
take
care
of
like?
Are
there
any
formalities
with
the
TCR
somebody
that
you
need
to
do.
C
B
E
I
am
curious,
you
know
so
so
it's
great
that
we're
starting
on
web
JavaScript.
Are
we
also
thinking
about
web
Dart,
because
I
know
that
there
is?
There
is
a
team
that
has
been
wanting
to
contribute,
but
they're,
also
having
a
little
bit
of
trouble.
Getting
maintainers
I'm,
just
trying
to
figure
out
like
seems
like
there's
a
web
effort.
There's
a
mobile
effort.
B
Yeah,
so
this
sig
isn't
exactly
for
Quest
on
specific
languages.
B
The
started
off,
as
you
know,
whether
we
are
able
to
cover
all
the
use
cases
that
our
existing
products
have
and
notice
that
there
is
a
gap
and
that's
why
this
thing
was
formed
to
work
on
the
spec,
and
you
know
we.
So
that's
why
you
know
there
isn't
a
full
representation
from
from
all
angles,
and
it's
probably
okay.
That
way.
B
B
And
second
thing
was
matis
I.
Think
I
had
sent
you
a
link
to
the
events
API,
so
it's
specifically
to
create
Standalone
events
that
occur
outside
a
span.
B
There
is
yeah
go
ahead.
There
is
one
piece
there
where
we
wanted
your
specific
feedback,
which
is
the
in
the
semantic
convention
for
anything
mobile.
We
use
the
device
prefix
yeah
because
there
was
already
a
device
prefix,
and
you
know
there
was
some
confusion.
Whether
device
prefix
would
be
used
by
anything
other
devices
that
are
not
mobile,
that
are
not
even
client-side.
That
could
be
server
side
devices
and
tigrant
clarified
that
on
the
server-side
devices
they
are
going
to
use
HW
Hardware.
So
we
might
be
good.
B
So
just
wanted
to
get
an
odd
from
from
you
folks,
if
that's
okay
as.
C
B
Domain
for
all
the
mobile
events.
C
Yeah
I
only
started
reviewing
it
today
and
sorry.
I
didn't
really
have
time
before
to
take
a
look
at
that,
and
only
now
that
we
have
allocated
some
time
for
okay
for
the
contribution
I
actually
started.
Looking
at
it.
So
I
can't
really
answer
your
question,
but
I
remember
seeing
the
device
were
being
mentioned
only
in
the
context
of
mobile
devices
in
that
spec
before
so
I
suppose
it
makes
sense
to
keep
it
that
way.
Okay,
okay,.
B
Yeah,
okay,
yeah
I,
think
you
you
can
review
the
pr
and
and
comment
if
there
are
any
thoughts.
F
I
guess
probably
a
quick
update
on
the
web
sandbox.
It's
finally
made
some
progress.
The
script
to
merge
the
history
from
the
hotel,
JS
and
JS
API
repos
was
committed.
I
got
the
bot
token
in
there.
I
ran
the
the
script
to
bring
over
all
of
the
history.
The
pr
is
there
with
all
1800
files.
F
However,
one
of
the
commits
in
the
history
from
hotel
JS
came
from
the
GitHub
bot
who
can't
and
signed
the
CLA.
So
therefore,
the
pr
is
being
blocked
because
they
haven't
signed
the
CLA,
so
I
ping
Daniel
he's
going
to
bring
it
up.
The
TC
meeting,
which
is
tomorrow
so
hopefully
we'll
get
that
moving
to
see
how
we
go.
The
original
thing
was
maybe
I
just
added
out
of
the
existing
one,
but
the
problem
there
is
this
script
is
automated.
It
always
doesn't
get
merged,
so
we've
even
not
removed
it.
F
Next
time.
I
ran
the
script.
It
would
come
back
so
and
I
guess
once
we
add
the
Contra
repo
in
there
as
well
to
start
bringing
stuff
from
the
contrib
into
the
sandbox.
That
could
have
the
same
problem.
So
that's
where
that's
at
I'm
going
to
be
out
from
Friday
till
Tuesday,
so
I'm
probably
not
going
to
get
much
more
work
on
that
before
our
next
set
of
meetings.
G
I
guess
a
quick
update
on
some
of
the
supporting
protobuf
HTTP
in
the
browser,
so
I
made
a
made
some
progress
on
that
and
there's
basically
like
three
packages
that
need
to
be
browserified,
so
I'm
working
on
that
and
then
we
also
had
to
I
also
have
to
modify
how
we
send
xhr
data
to
support
buffers
so
I'm
hoping
to
have
a
PR
up
for
folks
to
look
at
in
the
next.
A
Okay,
great
does
anyone
else
have
anything
else
that
they
want
to
talk
about
today.
H
A
quick
question
I
think
Santosh
you'd
mentioned
something
about
the
Swift
Sig.
H
Have
we
actually
reached
out
to
them
to
confirm
they're,
not
working
on
iOS,
or
also
to
confirm
that
they're
not
just
working
on
Swift?
First,
getting
that
ready
getting
that
working
and
then
switching
their
focus
to
iOS
I'd.
Just
be
surprised
that
so
many
people
were
working
on
Swift
without
the
intention
of
doing
iOS,
instrumentation.
B
H
B
The
the
reason
for
you
know
that
thinking
was
that
at
one
point
in
the
last
few
months
there
was
another
entirely
new
project
from
somebody
in
eBay
for
iOS
specific,
like
they
had
their
own
implementation
of
yeah
I
was
and
when
I
asked
them.
What
was
the
reason
they
said
the
current
Swift
implementation
is
is
too
bulky.
It
has
a
lot
of
things
you
know
for
for
Linux
and
other
platforms
that
the
binary
for
iOS
you
know
becomes
too
big.