►
From YouTube: 2022-10-14 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
B
Not
really,
there
was
nobody
really
that
showed
up
yet.
So
it's
just
been
me.
B
I,
like
I
did
too,
but
it's
like
also
like
I,
don't
know
how
much
involved
with
people
you
could
be
included
in
this
I
actually
have
a
question
for
you
that
I.
A
B
Of
relates
to
this,
but
it's
like
this
Hotel
resource
Target
info
right,
yep,
there's
this
PR
that
Pablo
opened
up
on
this
one
and
one
of
the
things
that
I
was
kind
of
I
like
I've,
been
reviewing
this
for
like
almost
an
hour
now
as
I'm
thinking
about
it
is
it
creates
the
the
target
metric
or
like
the
target
info
metric
for
the
the
resource
down
here.
B
But
it
also
does
this
like
constant
attribute
or
labels
right
and
I
was
looking
at
the
specification
and
you
had
written
to
do
that
in
the
collector.
So
I
was
like
well
I.
Don't
think
we
should
be
doing
that
here
in
the
exporter,
because
every
measure
thing
gets
these
constant
labels,
but
then
I
was
thinking
well.
That
may
not
be
the
case
right
because,
oh
it
looks
like
you
commented
yeah.
You
did
the
same
thing.
B
You
said
the
same
thing
yeah,
so
this
is
but
the
problem
that
I'm
thinking
is
like
what
happens.
If
this
exporter
gets
handed
to
multiple
providers.
B
A
A
A
A
A
B
A
Yeah,
but
or
what
you
can
do
right,
if,
if
this
is
a
per
exporter,
config
is
you
just?
You
have
to
pick
one
to
keep
right,
so
it's
like
I
can
have
one
target
info
from
one
of
my
things,
hopefully,
which
is
describing
this
target
right.
The
thing
that's
producing
the
metrics
and
so
I
can
still
say:
oh
yeah,
what's
my
hotel
version?
What's
my
Go
version,
you
know
yeah
all
that
useful
information
once
but
then
I
can't
have
it
10
times
for
10
different
things
in
Prometheus.
B
Yeah,
okay
and
so
that's
the
other
thing
is
like
you
might
have
also
said
this
of
it's
like.
If
that's
going
to
be
the
case,
then
you
really
only
need
to
do
this
like
create
a
Target
info
metric
once
because
this
is
doing
this
every
single
time
that
a
collection
happens
and
that's
also
something
that
is
I
was
like.
Oh
that's,
gonna
be.
A
B
B
Okay,
that
being
said,
I
think
this
is.
We
could
probably
Aaron
had
these
nice,
like
triage
status,
things
done
that
I've
never
seen
before.
So
this
whole
thing
is
kind
of
new
to
me.
B
That's
a
good
point:
yeah
I
could
do
it.
I
could
definitely
do
it
that
way.
So
I
think
this
is
ready.
This
is
already
like
in
progress.
Actually
so
we'll
do
it
yeah,
no
I,
don't
know
how
to
how
do
they
change
it
one
at
a
time.
Oh
here
it
is
yeah.
B
Okay,
cool
figuring
it
out,
so
the
scope
attribute
stuff
I.
Also
added
that.
Thank
you
for
the
Prometheus.
Oh
wait.
Is
this
the
right
one
I
don't
know!
That
is
how
I
added
up
to
you
know.
I
think
this
is
different.
A
Oh
there's
talk
about
pulling
wait.
Wait
I
want
to
see
that
foreign.
A
B
B
I
think
this
is
supposed
to
be
a
metrics
specific,
but
I,
don't
I
I,
don't
see
it
being
just
a
metric
specific
in
the
long
run,
very
yeah
that
should
be
in
there.
B
B
This
is
in
progress,
add
back
the
open
census,
Bridge
code.
This
is
another
one
that
I
wanted
to
ask
you
about,
because
we
have
something
added
back
right.
Should
this
be
closed,
I.
A
A
I'm
trying
to
remember
how
this
was
supposed
to
work,
it
basically
would
be.
You
would
get
a
reader
back
that
returns
like
it's
a
periodic.
What
would
it
be?
It
would
be
like
a
periodic
Bridge
reader,
so
yeah.
You
would
use
that
instead
of
a
periodic
reader,
wherever
you
were
going
to
do
it
and
it
would
provide
metrics
from
both
hotel
and
from
open
census,
merge
together,
basically
to
the
exporter,
and
it
would
end
up
being
an
implementation
of.
B
And
I
talk
through
this
at
one
point:
okay,
but
it
would
have
to
live
in
this
main
SDK
right
because
there's
like
these
private
methods
to
this
reader
right
right.
B
B
B
A
A
I
think
that's
I,
don't
know
what
it
is,
but
if
I
had
a
guess,
I
would
say
that
it's
like
you
file
an
issue.
That's
like
move
metrics
to
GA
right
and
that's
in.
B
B
B
Do
we
need
exemplars
for
stable
release?
Are
they
stable
in
the
specification.
A
B
No
yeah,
we,
we
don't
I
noticed
in
Java.
There
are
they're
plumbed
throughout
the
entire
thing.
It's
a.
A
B
B
Do
you
kind
of
wonder
if
we
can
push
this
off
to
the
after
GA
phase,
but
I
also
don't
know
if
that's
something
that
we
would
need
to
change
the
API
to
support
it?
So
that's
kind
of
a
good
I,
don't
know
if,
like
worth
investigating
now,
I've.
B
A
Yeah,
it's
I,
I
guess
just
personally,
like
I,
haven't
been
telling
people
to
write,
instrumentation
or
use
it
very
much
because
I'm
like
well.
It's
all
still,
you
know
kind
of
Alfie
yeah,
but
if
all
it
is
is
like
the
SDK
might
change
or
something
and
they
can
start
writing
their
actual
instrumentation.
Then
I
feel
like
that's.
B
I
think
that's
fair,
I
still
kind
of
worry
about
this
like
structure
a
little
bit,
but
I
don't
think
it's
going
to
change
this
whole
like
distributed
sinking
provider.
That
kind
of
thing
I
know
that
was
kind
of
contentious,
but
it
was
at
this
point
I
think
that
ship
has
sailed
and
I.
Don't
really
think
it's
gonna
I
agree.
B
A
B
B
You
know
like
this
is:
is
yeah,
maybe
more
packages
than
it
needs,
but
like
it,
it's
not
like
it
doesn't
implement
the
API
that
needs
to
be
implemented
and
it
doesn't
fail.
So
yeah
I
think
that's
fair
excuse
me
I
was
thinking
of
opening
a
discussion
for
it,
but
would
you
think
an
issue
tracking
this,
or
what
do
you
think.
B
And
I
think
I
mean
yeah
I,
don't
know
like
the
exponential
histogram
I
think
is
one
of
the
big
ones,
but
like
no
that's
the
thing,
it's
like
it's
not
stable
in
the
specification,
but
I
know
that,
like
the
light
step,
SDK
also
added
it,
and
so
like
that's
like
the
one
thing
that
it's
not
compatible
with
or
not.
It's
not
feature
parity
with.
So
people
wanted
to
try
to
include
that
here,
but
yeah
I,
don't
know,
like
that's
that's
kind
of
my
been
my
reservation.
B
B
A
B
So
that
is
clear.
The
Milestones
then
yeah.
B
But
yeah
I
mean
so
the
thing
that's
the
other
thing
is
like:
do
we
couple
the
the
release
cycle
of
the
API
and
the
SDK
like?
That
would
be
another
thing
if
we
release
like
the
API
as
a
1.0
like
it
would
not
be
released
in
lockstep,
but
I,
don't
I,
don't
know
if
that's
necessarily
a
problem
I
mean
that's
the
whole
reason.
We
have
different
modules
right.
A
I,
personally,
don't
consider
that
a
problem
okay
and
to
for
something
like
light
step,
it
would
be
an
opportunity
for
them
to.
A
I
mean
the
SDK
in
terms
of
code.
It's
like
a
tiny
portion
of
what
users
should
be
using
like
yeah.
It's
not
actually
what
users
interact
with
that.
Much
so
like
if
I
was
light
stuff
I,
actually
are
you
light
stuff?
I,
don't
remember,
but
no
I
don't
know
if
it
matters.
No,
that's
what
that's
right!
No
sorry,
yeah
you're
small.
A
A
Don't
know
the
API
I
think
the
API
is
still
Alpha
right
or
go
only
has
pre-release
and
post
release
and
we
haven't
marked
anything
hi.
B
Three,
so
it's
the
same,
you
know
so
fees
are
32
32.,
but
so
like
it
would
essentially
I
can't
remember
our
exact
versioning
policy,
but
I
think
it
would
just
jump
to
be
like
at
the
one
by
12
or
something
it
would
jump
into
here.
Yeah.
Actually,
that's
a
good
question,
because
I
don't
like
the
release
process
is
also
like.
We
need
a
release
candidate
right,
like
did.
We
just
go
straight
to
a
stable
without
a
release.
Candidate.
A
B
B
Don't
think
GA
is
going
to
happen
for
the
metrics
SDK
before
kubecon,
because
no,
no,
definitely
not
I
yeah
I
misspoke,
but
I
do
I
do
think
that
getting
more
stable
API
for
kubecon
could
be
possible
like
if
it
already
is
pretty
stable.
B
I
feel
like
I,
don't
that's
the
thing
like
I,
don't
know
if
there
are
going
to
be
any
changes
like
we
implemented
it
with
an
SDK
at
this
point
right,
like
I,
feel
like
that's,
the
main
criteria
is
to
say
like
is
this
API
implementable
like
does
it
solve
the
problem
like
I?
Don't
think,
there's
any
like
major
functional
like
issues
we
found
with
it.
There's
like
not
performance
issues
like
with
our
structure,
API
yeah,
yeah,.
B
A
B
B
B
As
well,
we
didn't
release
it
so
yeah,
yeah,
okay
and
then
type
of
effects.
B
B
A
Okay,
yeah
better
stability
than
our
stable
metric,
spec
yeah.
B
Yeah,
that's
I
think
this
is
for
the
API
I'm
just
gonna
like
create
this
really
quick
yeah,
but
the
yeah,
like
that's
a
good
question.
A
I
I
would
actually
so
if
we
don't
I,
think
the
argument's
for
pushing
them
until
after
GA
would
be
if
we
wanted
to
get
GA
out
faster.
If
we
wanted
to
say
like
let's
target
GA
at
November
1st
or
something
and
let's
clean
up
everything,
we
can
clean
up
that,
we
think
is
going
to
be
breaking.
A
A
B
Yeah,
that's
a
good
question:
I
yeah,
I'm,
gonna,
add
I'm
gonna.
Add
that
to
the
agenda
for
next
week's
sake
meeting,
because
I
think
that's
important,
I,
I
kind
of
have
this
view
like
I'd,
rather
to
get
it
out
early
like
try
to
Target
November
1st,
but
I.
Also,
we've
been
seeing
a
lot
of
bug.
B
Reports
coming
in
and
I
kind
of
wonder
if
just
giving
a
little
bit
of
time
for
users
to
start
using
SDK
would
provide
more
confidence,
even
if
it
is
like
slowing
us
down
a
little
bit
but
yeah
I,
guess
I
guess.
My
answer
to
that
question
is
I.
Have
mixed
an
inconclusive
decisions
on
that,
so
yeah
I'll.
Add
it
to
the
agenda
for
next
week.
B
Yeah,
exactly
that's
that's
same
and
the
bridge
work
like
I
do
want
to
make
sure
that,
like
we
can
support
the
bridge,
but
also
like
does
that
mean
that
we're
gonna
have
to
have
like
something
supported,
for
you
know
an
extended
period
of
time,
because
we
wanted
to
shoot
in
something
right
now,
like
that's
also
another
question
I
wanted
to
ask,
but.
A
A
A
B
That
is
exactly
I
think
what
happened
with
the
metrics
specification
early
on
yeah.
They
were
yeah
yeah.
That
was,
that
was
a
funny
issue.
A
B
B
B
Yeah
all
right
I
would
definitely
want
to
Target
spec
compliance
for
the
Prometheus
exporter.
For
for
the
beta,
are
we
not
compliant
currently.
A
B
I
would
appreciate
it.
It
seems,
like
you,
have
a
way
better
grasp
on
that,
but
yeah
like
I.
Would
we
definitely
want
to?
Yes,
we
want
it
to
be
spec
compliant
because
I
think
that's
going
to
be
released
as
a
stable
thing.
B
Okay,
I
also
realized
that
this
is
a
30-minute
meeting,
we're
like
15
minutes
over
okay
cool
yeah.
Why
don't
we
go
with
that?
I'll
I'll!
Look
to
you
to
create
some
issues
for
the
Prometheus
stuff
and
we
can
I'll
keep
triaging
in
the
background
okay,
but
we
don't
need
to
be
on
the
call
all
right.
Dude
talk
to
you
later.