►
From YouTube: 2022-05-24 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
Let
me
share
my
screen.
He
asked
me
to
like
just
host
the
meeting
today.
A
Yeah,
I
guess
we
can
start
there's
no
specific
agenda
today
from
what
I
learned
from
cjo,
he
said,
like
1.3.0
version,
stable
version
is,
is
still
supposed
to
be
released
next
week
way.
Still
nothing
has
changed
in
the
plans
to
release
it
next
week
and
yeah
other
than
that.
I
think
if
anyone
has
anything
to
bring
up
would
be
a
good
time.
C
I
don't
personally
have
anything
in
particular
there's
a
couple
of
pr's
out
there.
I
have
one
people
have
a
chance
to
look
at
it.
I
think
michael
already
had
it
in
my
cast
this
one.
A
Do
you
guys
see
my
screen,
though
yeah?
Okay?
Okay?
So
this
is
the
one
right
exporting
tax
consistent.
This
is
the
one
you're
talking
about.
C
Yep
yep,
I
just
opened
that
up
or
took
it
out
of
draft
today
and
then
mike.
I
just
I
haven't
taken
a
super
deep
look
at
your
perf
improvement
one
yet,
but
I
will
I'll
do
that
after
this
meeting
I'll
take
a
closer
look.
D
Yeah,
that's
really
the
main
issue,
it's
saving
on
nanos
and
it's
got
some
api,
so
some
public
api
edition.
So
is
it
worth
it?
That's
the
question
we
need
to
answer.
A
D
A
D
A
D
D
C
Does
it
happen
on
every
activity
or
would
it
just
be
kind
of
like
entry
point
and
then,
like
external
call
type
of
things.
D
It
depends,
I
think,
the
way
I
don't
know
if
all
the
instrumentation
still
works
at
stake
this
way.
But
there's,
like
you,
know
the
built-in
extraction,
and
then
we
do
our
own
double
extraction
or
we
check
because
you
know
what
runtime
supports
doesn't
necessarily
cover.
You
know
if
people
have
a
composite,
propagator
and
they're
doing
like
b3
and
zipkin
and
stuff,
because
I
think
we
still
do
it
every
time,
but
I'm
not
100
sure.
C
C
Separately,
another
totally
tangential
thing
that
was
on
my
mind
today.
I
think.
B
C
Think
we're
maybe
wanting
to
do
something
with
a
logs
release
at
some
point,
and
I
was
just
noticing
another
wonkiness
in
regards
to
the
configuration
for
the
otlp
exporter,
where
the
batch
settings
are
activity
specific.
So
I
had
it
on
my
mind
to
do
something
about
that.
Just
saying
this
just
to
give
people
a
heads
up.
Do
you
all
know
what
I'm
talking
about
yeah?
If
you
don't
mind
bringing
it
up.
C
A
C
C
I
pulled
like
the
metric
reader
specific
options
out
of
the
otlp
expert
options,
they're
in
the
sdk
now-
and
I
was
thinking
about
doing
a
similar
thing
here
for
logs
just
so
that
we
don't
continue
to
piggyback
on
this
and
have
another
another
thing
that
depends
on
upon
it.
This
is
ultimately
something
I
think
that
we
had
discussed
deprecating
specifically
the
option
on
the
otlp
exporter
class
itself,.
D
D
C
C
A
A
Yeah
mothra:
do
you
want
to
ask
anything
about
the
in
memory
export
apr?
I
think
we've.
There
are
a
few
approvals
already.
B
A
Yeah,
I
think,
probably
he's
just
waiting
for
yeah
exactly
that,
like
he's
just
probably
giving
it
some
more
time
but
yeah.