►
From YouTube: 2023-03-29 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
C
A
D
A
Yes,
we're
trying
yeah,
so
yesterday,
Jack
jackberg
was
on
the
TC
was
in
the
call
he's
been
trying
he's
trying
to
attend
these
these
meetings
and
we
talked
about
the
ephemeral
resources,
the
varying
resources,
so
he's
gonna
try
to
help
us
as
a
DC
member
with
a
few
things,
and
this
one
was
probably
the
first
one.
We
talked
about
related
to
that.
We're
probably
gonna
try
to
change
the
time
of
this
meeting
because
it
doesn't
work
for
Jack
and
it
doesn't
for
Josh
who's,
also
on
the
TC.
A
It
might
help
might
help
us.
So
Jack
was
going
to
talk
to
Josh
and
see
what
other
times
work
for
them
and
then
we'll
go
from
there,
but
most
likely
this.
This
Wednesday
meeting
time
will
change.
B
C
A
So
aside
from
that
update
for
me,
like
I've,
been
really
focusing
on
helping
the
log
SDK
PR
go,
you
know,
move
forward,
I
think
so
I
went
through.
You
know
another
review
and
went
through
the
whole
Spike
of
the
log
API
log
SDK.
A
A
But
if
you
you
know,
if
you
have
time
and
interest
in
in
this
part,
then
please
take
a
look
at
it
and
it
would
help
to
have
more
eyes
on
the
pr.
It's
it's
a
it's
a
bigger
PR,
so
it
would
I
would
appreciate
more
eyes
on
it,
but
I
think
we're
I
think
we're
very
close
to
to
approving
it.
At
least
from
my
perspective
from
my
side,
that's
been
my
focus.
A
D
B
B
E
I
I
Jason
I'm,
also
working
on
Android
and
so
I'm
interested.
Please.
Let
me
know
if
they're
you
know
how
can
I
start
contributing
or
what?
What
is
it
needed
right
now
so
yeah.
B
Cool
yeah,
so
we
you
know,
we
we
bootstrapped
this
project
like
a
couple
of
years
ago
and
is
kind
of
tailored
to
do
to
get
Splunk
ROM
up
and
going
quickly,
and
then
we've
been
over
the
last
several
months,
refactoring
it
into
kind
of
a
core
set
of
instrumentation
components
that
are
decoupled
from
anything,
that's
kind
of
vendor
specific,
and
so
that's
where
we're
at
now.
E
B
Well,
let's
see
where
I
mean
if
you
want
to
get
if
you
haven't
looked
at
our
Android
repo,
yet
it's
linked
from
the
community
issue
that
I
put
in
the
agenda
and
also
if
you,
if
you
have
a
repo,
that's
public
I,
would
love
to
see
that
as
well.
And
we
can
compare
notes.
B
C
I
guess:
how
closely
does
it
follow
the
existing
Java
stuff
like
or
is
it
it
conforms
to
the
output
but
doesn't
conform
to
the
general
spec
API?
Is
it
I
guess
where
my
question
is
going
like?
Is
this
but
more
associated
with
a
client
SDK
that
is
compatible
with
hotel
or
it's
just
on
top,
where
I'm
coming
from,
for
that
is
from
a
JavaScript
perspective,
Santos
who's,
not
on
the
call.
C
Today,
let's
talk
about
creating
a
minimal
JavaScript
version
of
just
the
bits
we
need
so
I'm
wondering
whether
these
two
could
then
form
you
know
a
modified
client
version
or
vision
of
what
hotel
might
look
like.
B
I
think
that's
pretty
well
aligned
yeah,
so
our
existing
solution
does
sit
on
top
of
open
Telemetry,
it's
kind
of
a
set.
It's
it's
two
things
it's
a
set
of
fluent
apis
for
configuring,
the
open,
Telemetry,
Java
SDK
for
Android
usages,
and
it's
also
a
couple
of
instrumentations
that
are
specific
to
mobile
things.
Okay,
but
yeah
I
mean
having
I
mean
we.
E
Cool
yeah
yeah,
actually
one
of
the
things
that
I
mentioned
last
week
was
that
in
Android
at
some
point,
we're
gonna
need
to
to
store
the
signal
data
send
it
later
and
and
it
the
guys
were
mentioning
that
it's
something
already
done
on
the
Splunk
SDK.
So
that
kind
of
thing
I
guess
is
the
is
that
the
standards
that
are
going
to
be
used.
E
B
There's
a
caveat
to
that,
though,
because
the
the
way
we're
doing
it
right
now
is
by
marshalling
ZIP
can
formatted
spans
after
they've,
been
after
they've
been
marshaled
to
like
a
string
to
a
byte
string?
That's
what
we're
that's,
what
we're
persisting
and
then
later
offloading,
and
that
probably
won't
that's,
probably
not
a
recommended
approach
going
forward
and
I
think
that
there's
been
some
talk
around
using
Arrow
there's
a
proposal
out
there
for
Arrow.
B
B
B
E
E
So
please
feel
free
to
reach
out
for
whenever
you
think,
whatever
you
think
I
could
help
with
the.
B
Yeah
the
TC
says:
it'll
take
some
somewhere
between
zero
and
and
two
weeks
for
them
to
respond
to
a
donation
request,
but
I
mean
we'll
just
we'll
see
it
might
be
faster.
It
might
be
slower.
B
A
A
Yeah
and
then
we
should,
we
should
I
guess
talk
about
maybe
forming
a
group
of
mobile,
Engineers
or
mobile
experts
and
where
we
can
talk
about
semantic
conventions
like
we
did
with
web.
B
A
C
A
C
Think
that
there's
still
the
open
issue
about
whether
we
still
keep
domain
and
name
I
think
that
tigran
raised
a
while
ago.
C
It
would
be
nice
to
collapse
that
back
to
just
a
name
and
then
potentially
we
could
use
that
and
say
you
know,
format
it
like
a
a
URL
and
therefore
potentially
have
versioning
on
it.
So
we
could
say,
like
Hotel,
colon,
slash
event,
name,
slash
version
that
way.
It
gets
us
away
from
the
schema
discussions
for
versioning.
A
C
It
was
already
defined
as
part
of
the
event
definition.
Okay,
quite
a
quite
a
while
ago.
Now
sorry,
this
has
been
catching.
A
C
I
haven't
updated
yet
in
terms
of
what
I,
what
the
shape
of
an
event
would
be
like.
It
should
be
in
the
notes
there
somewhere,
where
it's
just
building
on
top
of
the
existing
one,
which
is
your
event,
has
a
domain
and
a
name
and
I'm
saying
well.
We
also
have
a
data
for
the
specific
content
for
that
combination.
C
D
I
have
I
have
a
question
on
the
logs
SDK,
so
is
that
will
not
be
required
for
the
events
instrumentation
like,
for
example,
we
we
may
need
the
exporters
that
look
exporters.
A
Yes,
so
so
the
yeah,
so
there
will
be
events,
events
SDK
that
uses
that
uses
the
logs
SDK
behind
the
scenes.
D
A
How
is,
how
is
it
going
with
the
with
the
instrumentation
I
know
yes,
and
did
you
get
that?
Did
you
get
the
sandbox
working.
D
No
I'm,
just
gonna,
try
use
the
the
fix
you
mentioned.
I
haven't
I,
haven't
seen
it
yet.
A
A
B
A
For
me,
yeah,
it's
cool
sounds
like
short
meeting.
Then
thanks
everyone
and
talk
to
you
later.