►
From YouTube: 2022-11-21 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
C
B
Yeah
so
people
add
the
points
in
the
agenda.
I
have
added
some
of
that
stuff,
which
we
can
discuss,
at
least
for
the
specs
changes.
D
B
So
the
first
one
is
basically
the
capturing
the
policy
regarding
non-exposure
of
generated
protobox
structure
in
the
end
user
API
so
I
mean
the
way
I
see
as
of
now
is
that
that
we
should
not
basically
release
at
least
we
should
not
be
releasing
the
genetic
protocol
photobomb
structures
either
as
a
package
for
other
languages,
but
for
C
plus
plus.
We
should
not
be
exposing
the
header
files
which
we
generate
for
protobuf
and
we
do
release
the
header
files.
As
of
now.
B
The
reason
why
we
release
these
header
files
is
because
the
we
do
also
install
the
recordable
headers,
and
so
there
was
a
couple
of
issues
which
was
a
couple
of
years,
which
was
raised
in
one
of
the
PRS.
We
removed
the
recordable
header,
but
in
another
PR
I
think
moment
has
raised
some
some
concerns
that
it
should
be
used.
B
It
should
be
available,
probably
for
the
exporters
to
be
able
to
I
mean
inherit
from
it
or
some
something
that
we
wanted
to
use
that,
and
then
we
brought
it
back,
but
inside
the
recordable
headers
we
are
also
including
the
headers.
B
So
probably
that
means
that
we
have
to
eventually
release
the
protocol
videos
also
so
yeah,
that's
something
probably
we
can
revisit
if
we
really
want
to
release
reportable
headers,
if
not
I,
think
we
can
probably
remove
it
and
around
with
all
the
protocol.
Windows,
probably
probably
I,
think
the
place.
This
issue
is
still
in
this
question:
let's
see
where
it
goes,
but
I
think
personally,
my
opinion
was
that
we
should
not
be
exposing
both.
B
The
other
one
is
specify
the
metric
reader
configurable
limits.
I
think
this
could
be
important.
As
of
now
we
don't
have.
We
don't
really
put
any
memory
constraints
in
terms
of
number
of
measurements
number
of
Matrix.
We
are
going
to
generate
number
of
Matrix,
which
we
are
going
to
store
in
our
internal
storage.
B
So
there
may
be
a
problem
that,
over
the
course
of
time,
if
the
collection
interval
is
very
long,
we
may
our
internal
memory
usage
can
keep
on
increasing,
based
on
better
based
on
the
temporarily,
whether
it's,
whether
whether
it's
a
delta
or
cumulative
based
on
that
I,
think
it's
possible
that
our
internal
storage
can
keep
on
increasing.
B
If
the
polling
interval
is
very
high,
you
know,
so
we
have
to
probably
test
those
scenarios
and
it
would
be
good
if
Patrick
data
can
add
some
constraints
in
terms
of
definitely
I
mean
how
many
time
series
data
given
instrumentation
Library
can
only
different
time
series
that
are
given
instrumentation
that
we
can
configure
and
for
for
a
given
instrument.
How
many
time
series
data
for
a
given
instrument
it
can
be
configured
default,
is
2000,
but
I
think
it
can
be
explosive
over
the
course
of
time.
B
If
you
don't
have
such
constraints,
so
that
would
be
important
to
really
have
a
very,
irrespective
of
this
PR
I
think
we
definitely
have
to
see.
How
can
we
put
some
constants
inside
our
it's
called
C
plus
plus
configurations
to
see
if
you
can
ensure
that
our
memory
does
not
keep
Sonic
exploring,
cannot
keeps
on
increasing
and
it
can
explode
over
the
course
of
a
few
days.
So
that's
something
we
have
to
definitely.
B
The
curve
one
is
make
sure
it
is
very
clear
that
we
are
not
building
blogging
API
yeah
this.
This
is
I,
think
we
are
clear.
I
mean
as
of
now
that
the
currently
logging
spec
the
current
logging
API
specs,
is
not
for
a
logging
API.
It
is
for
the
appenders
to
use
that
API
defined
API
to
use
through
appenders
for
the
existing
garbage
liabilities
of
probably
uploading
the
logs
from
open,
Tech,
Elementary
logs
to
say
logs
for
CG
logs
for
cxx
or
any
other
a
learning
library.
B
You
can
just
quickly
go
through
that
yeah,
this
one
so
I
think
I
from
it.
It
looked
like
that
we
are.
We
are
removing
the
existing
logging
API
and
we
are
just
adding
the
new
API
as
per
the
EPA
specs,
which
is
not
the
right
to
approach
so
yeah.
B
We
have
been
discussing
about
whether
we
should
use
internal
Lock,
Storage
or
not
so,
and
also
another
discussion
is
whether
we
should
we
should
keep
the
existing
API,
because
that
is
something
which
tells
you
might
actually
would
be
using
in
a
new
API
would
be
only
used
for
recordables,
so
yeah
I
think
something
moment
is
talking
about
that,
but
yeah,
that's
something.
Probably
we
have
to
take
care
of
in
our
implementation.
B
B
Okay,
we
don't
do
it
obviously,
so
this
request
was.
B
To
add
it
in
that
is
API
I.
Don't
think
this
should
get
added,
but
yeah
I
think
that
follow
that
follow
the
discretion,
because
I
instrumentation
library
is
not
the
right
place
to
to
plus
the
decrease
it
should
be
the
SDK
or
the
application,
the
application
code,
which
should
be
responsible
to
decide
when
to
do
their
real
mesh,
but
I
think
probably
let's,
let's
probably
follow
up
on
this.
If
something
has
to
be
done,.
B
Anything
else,
probably
in
the
specs,
otherwise
we
can
talk
on
the
existing
issues.
Just
let
me
know
the
information
you
can
always
talk
afterwards.
If
there's
anything
to
me
either.
B
Okay,
we
haven't
test,
I
mean
I,
haven't
tested
with
sentos,
but
I
think
it
should
work.
It
should
not
break
for
one
of
the
distribution
and
not
work
for
any
other
distribution
yeah.
Our
code
is
not
just
dependent
on
any
of
these
specific
distributions
unless
until
it's,
the
version
of
the
compiler.
E
B
B
B
B
D
B
Something
yeah
we
can
do
that.
The
way
we
do
it
for
TLS
I
think
we
can
do
the
simulator
in
this
yeah,
so
I
mean
I,
don't
know
much
about
what
mpls
is
so
I
cannot
really
comment,
but
yeah
yeah.
C
C
B
D
A
B
I
think
the
change
which
I
feel
is
basically,
so
we
have
our
own
wrapper
on
top
of
HTTP
right.
The
HTTP
client
Library,
which
we
use.
So
we
have
to
add
the
hooks
in
that
Library
so
that
it's
as
part
of
the
https
handshake
Whenever
there
is
a
request
coming
for
the
root
CA
certificate.
That
hook
should
be
able
to
provide
those
certificates.
B
B
It
does
not
I
mean
support
this;
it
will
support
SSL
by
default
without
without
doing
without
validating
the
certificates.
It
will
definitely
support
it.
Just
use
https,
it
will
support
it,
but
when
we,
if
we
want
to
validate
the
certificates
it
won't
it
cannot,
it
won't
support
validating
this.
It
will
fail
at
that
time
because
our
wrapper
HTTP
client
cannot
provide
those
certificates
for
it
to
for
it
to
validate
it.
B
B
No,
but
if
still
we
cannot,
it
cannot
work
because
we
have
to
provide
a
certificate
to
environment
variables,
and
then
we
have
to
ensure
that
our
HTTP
client
Library
should
be
able
to
load
those
certificates
provided
through
command
line
and
provide
those
to
the
coil
client.
So,
okay,
I
will
probably
let
me.
B
So
probably
we
have
to
add
I
mean
that's.
That's
probably
my
take.
We
have
to
add
in
another
session
State
here
for
the
SSL
handshake.
We
have
to
trap,
probably
the
the
session
State
should
be
set
whenever
the
request
is
coming
for
this
certificate,
whether
it's
client
or
server.
Based
on
that
we
have
to
set
the
system
State
and
then
there
should
be
a
hook
which
should
be
called
to
upload
to
load
that
certificate.
B
Like
this
all
connecting
we
are
providing,
we
are
not
using
it
anywhere,
but
I
think,
probably
somewhere
we
have
to
in
the
event
handler,
which
will
provide
a
hook
who
supports
it.
But
let
me
let
me
just
see
I
think
public.
D
D
B
B
B
B
B
D
B
B
B
B
B
B
Probably
it
is
something
I
think
I
am
reviewing
it,
as
of
now
feel
free
to
check
that
we
are
I,
think
that
that
PA
would
be
important
to
set
a
context
of
our
initial
set
of
apis,
which
we
are
going
to
use.
So
I
think
it's
important
here.
You
know
nothing
good.
If
we
all
can
review
it.
B
And
yeah,
so
that's
only
one
period
as
of
now
deadline
is
already
passed
by
just
just
want
to
add
some
deadline.
It
should
not
look
past
due
date.
Probably
15th
of
I
mean
just
just
extending
it
to
say.
15Th
of
December,
probably
I
feel
that
it
will
take
some
time
to
review
the
changes.
B
Matrix
I
think
you
know,
lots
of
things
are
in
place
which
we
have
to
start
working
I,
don't
see
anything
urgent
as
of
now
but
I
think
slowly
and
slowly
we
should
start
taking.
These
I'll
also
have
started.
D
B
Division
types
add:
support
for
exponential
Matrix
provide
Builder
to
expose
SDK,
internals
yeah,
adding
memory
exporter,
add
a
state
pointer,
obviousync
instruments.
We
need
supply
dependencies
for
both
getting
started.
Documentation,
handle
gaps,
recordable
interface
between
metrics
storage,
Explorer,
basic
education
does
not
do
Revolution
support
political
instrument
contacts.
B
B
Because
I
mean
none
of
the
other
languages
support
this
as
of
now
so
I
think
we
are
not
alone.
Even
though
everybody
is
real,
you
know
most
of
the
languages
being
GA.
They
don't
support
it
so
fast
that
things
should
be
okay
for
now,
but
yeah.
Apart
from
that
I
think
most
of
the
things
we
know
how
to
do
it.
B
B
E
B
So
I
mean
only
I
got
surprised
that
so
that
means
that,
with
the
latest
upsell
we
are
still
able
to
build
it
with
C
plus
11..
Is
that
what
you're
saying.
D
B
Fine,
but
the
only
I
mean
not
a
bigger
issue.
Only
thing
would
be
that
our
cmake
build
would
be
using
a
different
version
of
Excel,
and
our
bazel
would
be
using
a
different
version.
B
Welcome,
let's
see
I
think
it's
not
very
important,
I
think
it
should
be
okay
as
long
as
I
mean
I'm.
Okay
I
would
probably
prefer
if
we
are
using
something
which
is
coming
inside
the
sub
module,
so
I
think
it's
fine
I
mean
but
but
yeah
it's
your
take.
If
you
want,
if
you
want
to
make
it
consistent
in
both
feel
free
to
raise
a
PR
for
CMA
function,.
F
A
D
B
B
E
D
D
D
B
B
Okay,
thanks
Hassan
I
think
this
looks
good.
Let
me
just
review
this.
E
B
Your
tailway
sampling,
yeah,
I,
think
probably
Tom.
This
will
come
to
you.
You
need
not
review
it
as
of
now
I'm,
just
working
with
the
team
which
needs
that
if
they
feel
these
changes
are
good
enough,
then
probably
I
think
I'll
need
your
help
in
reviewing
it.
Okay,
I
mean,
as
of
now,
just
just
need
not
need
not
spend.
Time
on.
This
is.
C
B
B
C
B
B
Yes,
we,
oh
yeah,
we
do
support
I,
think
the
agent
when
you
with
the
agent,
you
said
which
agent
I
mean.
B
Yeah,
no
I,
don't
think
it's
supported
in
monitoring
agent,
but
it's
it's
definitely
supported
in
open
Telemetry
collector.
It
has
a
corporate
Elementary
collector
has
exhaustive
support
of
tail
based
sampling.
Even
it
supports
caching,
caching,
the
spans
from
all
the
relay
from
the
from
the
parent
to
the
all
the
child
spans
and
then
deciding
based
on
the.
If
any
of
these
fancy
scenario
of
any
of
this
pan
has
this
status
as
failed,
then
it
allows
you
to
to
drop
all
the
Sam
all
these
fans
coming
from
the
same
parent
or
something
like
this.
B
D
B
B
C
plus
plus
I
think
we
don't
have
a
full
Place
support
of
tail
based
sampling.
Obviously
yeah,
it's
the
it's
because
of
the
current
design.
We
don't.
We
don't
store
all
the
attributes
in
the
SDK.
So
all
the
attributes
that
directly
serialize
in
in
the
exporter,
so
that
that
something
which
is
necessary
but
yeah,
that's
okay,.
D
C
B
D
B
B
B
B
Yes,
we
already
waiting
for
this
PR
the
CLA
check.
Let
me
see,
if
he's
still
doing
it
for
things.
B
Okay,
yeah
all
right:
let's
wait
for
some
time
that
is
already
I.
Think
we
discussed
spin
lock
of
yeah
I
mean
feel
free
to
just
have
a
look
into
that.
B
B
Which
is
exporter
build?
This
is
again
also
for
CLA,
it's
kind
of
stuck.
Let's
wait
for
some
more
time,
otherwise,
I
think
we
can
add
a
picture.
Any
one
of
us
can
take
these
changes
in
order,
because
this
I'll
have
a
look
into
that
there
are.
There
are
comments
from
ovent
and
also
from
new
comment
from
Sergio,
so
welcome
to
this.
This
is
something
actually
we
have
to
implement
so
yeah
I.
Think
that's!
That's
all
we
have
in
this
and
going
back
to
this
agenda.
A
D
B
I
mean
I
think
it's
a
good
time
to
release
it.
We
have
already
done
the
cleanup
of
the
old
Matrix
implementation,
so
probably
I
think
it's
a
good
time.
If
one
of
us
can
take
responsibility
of
doing
a
new,
build
I
mean
I
mean
that's
somebody's
interested
just,
let
me
at
home
or
massage
or
anybody
who's
interested
to
have
a
new
brain
on.
If
you
want
me
to
do
it,
just
let
me
know:
okay.
B
D
B
Should
we
do
it,
but
I'm
not
sure
I
think
we
can
keep
it
1.7,
but
one
also
even
1.8.?
Oh,
if
you
think
the
duplicated
old
Matrix
as
the
kind
of
baking
changes,
probably
you
can
have
it.
1.8.2
I
mean
if
you
take
that
as
a
breaking
changes,
which
is
fine,
I,
think,
probably
it's
a
major
change.
We
are
removing
remove
an
existing
functionality.
A
Yeah
no
no
strong
opinion
both
works
for
me:
okay,
I
I,
don't
know
if
we
added
more
things
in
the
metrics
area
since
170.
B
We
did
add,
but
I
think
these
were
the
small
non-breaking
changes
to
cash.
First,
most
of
the
curves
related
to
fixing
the
crash
I,
don't
think
any
change
which
should
which
should
add,
let
us
add
the
major
version
or
something
I
mean
most
of
the
fixes
were
straightforward
without
breaking
the
SDK
and
the
API
interface.
D
B
Let's
say
I
think,
let's
plan
for
this
week,
I
think
any
day
is
fine.
We
we
don't
need
to
wait
or
probably,
if
you
want,
there
are
a
couple
of
PRS
which
I
think,
let's
wait
for
if
you
want
to
at
least
the
pr
which
was
raised
by
oment.
This
is
something
which
we
can
do
it
in
this
release.
These
will
not
go
which
are
waiting
for
this
for
the
CLA
sign
up.
So
at
least
we
can
really.
B
E
B
E
D
B
B
Yeah
and
in
continuation
to
that
I
think
probably
the
storm.
If
you
want
to
look
into
this.
C
F
C
B
B
F
C
A
E
E
So
the
question
is
why
this
is
an
issue
of
if
we
are
building
with
tests
for
tests.
E
B
This
is
something
which
which
has
dependency
on
Gene
Mock.
Then
probably
we
should
move
it
under
the
test
directory
I
mean
this
is
not
the
right
place
for
this
to
be
there
and
we
should
not.
We
don't
need
to
release
it.
Okay,
we
can
release
it
for
test,
but
we
don't
reduce
it
right
in
general
if
it
is
okay
anyway,
if
you
want
to
release
it
otherwise,
but
probably
I
think
if
it
is
something
which
is
only
for
testing
I
think
it's.
This
is
not
the
right
place
for
for
this.
B
B
E
F
D
E
B
Okay,
you
know,
if
not
anything
else,
probably
I,
think
thanks
for
joining
and
let's
meet
next
week,
November
30th
and
yeah
thanks
everyone
for
joining
every.