►
From YouTube: 2022-10-31 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
B
A
A
A
A
good
luck,
yeah,
it's
awesome,
I'm,
my
full
costume,
I'm,
a
it's,
a
very
bespoke
costume.
I
am
a
United
States
tennis
player
named
JJ
wolf.
He's
he's
got
a
very
interesting
look.
He
like
has
a
mullet
and
where's
the
gold
chains
and
has
more
sleeveless
tank
tops
and
super
short
shorts
and
it's
just
sort
of
a
spectacle.
So
a
very
big
costume.
C
A
D
B
D
D
B
All
right,
let's
get
started,
I'm
guessing
we'll
be
relatively
thin
on
updates,
just
because
a
lot
of
the
hotel
Community
was
at
kubecon
last
week.
So
starting
specification
we're
supposed
to
have
a
monthly
release
later
this
week,
I
assume
that's
the
November
release
that
might
be
the
October.
C
That's
correct
that
could
be
the
November
yeah,
so
yeah,
let's
see
how
it
goes.
B
All
right,
PHP,
Beta
release
is
still
coming
soon.
Question
the
agenda
so
we'll
get
down
to
that.
Once
we
wrap
up
with
the
the
updates,
no
updates
for
Java
Java
instrumentation
JS,
the
1.0
metrics
documentation
is
under
review
and
the
1.0
metrics
release
will
be
this
week
or
possibly
today,
it's
being
held
in
a
language
specific
packaging
concern.
Dan.
Do
you
want
to
speak
a
bit
more
to
this
yeah.
D
I
can
expand
on
that
a
little
bit.
The
question
really
boils
down
to
whether
we
release
the
API,
the
metrics
API
as
its
own
package
or
as
an
extension
of
the
existing
API
package,
which
currently
only
has
tracing
in
it.
D
D
You
have
to
pull
everything
in
there
is
that
the
the
maintainers
in
general
agree
that
the
developer
experience
of
a
single
package
is
better,
and
there
is
an
example
repository
showing
that
if
you
use
modern
tree
shaking
tools
like
roll
up
and
webpack
and
such
the
issue
is
fairly
effectively
mitigated,
not
a
hundred
percent,
maybe
but
like
90,
which
you
know
so
we
were
going
to
merge
them
into
a
single
package,
but
before
we
did
that,
we
decided
to
open
an
issue
and,
and
at
least
allow
for
dissenting
opinions
to
be
documented
and
if
they
have
evidence
why
it's
a
bad
idea.
D
B
D
Think
anyone
yeah
other
than
JavaScript
faces
the
the
issue
of
having
to
deploy
to
extremely
restricted
environments,
like
the
browser
right,
very,
very
regular
basis,
where
the
size
of
the
you
know
quote.
Binary
itself
is
actually
extremely
important
I.
This
may
be
important
for
things
like
iot
and
mobile
and
such
but
rarely
is,
are
any
environments
as
restricted
as
the
web
browser,
or
particularly
like
Edge,
compute,
nodes
and
stuff,
like
that
got.
C
So
I
mean
go,
isn't
as
restricted
for
I
think
a
lot
of
practical
reasons,
but
it
is
through
just
like
self-enforced
company
policies
and
we
we
do
take
that
idea
of
splitting
things
up
to
reduce
the
overhead
for
review
of
those
companies
that
don't
want
to
have
like
large
dependencies
as
seriously
as
we
can.
Obviously
there
is
a
minimum
size,
but
just
a
heads
up
like
we.
We
also
probably
are
going
to
release
like
the
metrics
API
as
a
separate,
what
we
call
module
and
go.
B
All
right
well,
then,
we'll
move
on
back
to
go,
looks
like
really
0.34
of
more
metrics.
Sdk
features
are
and
fixes
us
out,
40
or
45.
That's
45
complete
the
beta
metrics
SDK.
Progress
is
55,
complete
for
C
plus
plus
we
have
version.
1.7.0
has
been
released
with
the
metrics
API
and
sdkga
wow
fantastic,
so
people
can
go
use
that
and
The
Collector
.63.0
went
out.
B
It
says
no
updates
here
for
the
community
demo,
but
I
happen
to
know
that
the
community
demo
released
last
week,
which
was
also
very
exciting,
and
that
was
shown
off
at
the
open,
Telemetry
booth
at
kubecon
and
and
at
various
other
places
as
well
foreign
Bob.
Do
you
want
to
take
this
away
about
releasing
API
and
SDK
packages
separately.
A
Yeah,
this
is
the
last
thing
that
we
had
before
we
had
a
Beta
release.
I
want
to
get
other
maintainers
opinions
in
the
spec.
It
talks
a
lot
about
like
we
must
release
an
API
and
ended
SDK
package
separately.
That's
I,
don't
want
to
say
it's
Uncharted
Territory,
but
it's
not
like
common
path,
Common,
Ground
path
for
PHP
and
I.
Wonder
if
that
I'm
sure
that
is
set
for
an
explicit
reason,
but
I
wasn't
sure
what
it
was
so
I
figured
I'd
ask
the
community.
D
I
mean
the
reason
that
I
as
I
understand
it
is
that
if
you
have
some
some
module
like
a
database
driver
that
wants
to
add
first
party
support
for
open
Telemetry,
they
only
have
to
depend
on
the
API
package,
which
is
small
and
does
not
change
very
often,
and
the
underlying
SDK
can
be
updated
independently.
C
Yeah
Bob,
maybe
that's
a
question
to
you
like.
Maybe
are
you
understanding?
This
is
like
they
have
to
be
released
contemporaneously
or
they
have
to
be
released
as
like
different
packages,
because
I
think
that
the
different
packaging
structure
is
what
this
is
trying
to
talk
about,
not
necessarily
the
timeline
right.
Exactly.
D
Yeah,
the
timeline
of
releases
is
not
necessarily
coupled
in
JavaScript,
for
example,
we
have
the
tracing
API
that
we
released
like
two
years
ago
and
has
almost
had
not
been
updated
since
then,
but
the
SDK
has
been
updated.
You
know
multiple
times.
A
A
B
C
Yeah
just
kind
of
a
heads
up
to
other
maintainers.
There
is
a
question
of
behavior
around
when
attribute
features
are
or
I'm
sorry
attribute.
Filters
are
defined
with
async
instrument
counters,
it's
worth
taking
a
look,
it's
I
think
a
confusing
part
of
the
spec,
to
say
the
least,
but
it
doesn't
seem
like
any
implementations
actually
conform,
you
to
the
behavior
that
the
specification
was
anticipating
and
this
is
including
languages
that
are
stable.
C
So,
if
you're
about
to
go
stable,
you
might
want
to
take
a
look
at
this
just
to
double
check
that
your
conforming
to
the
behavior
that
is
expected
and
that,
if
not
it's
possible
to
fix
that
in
the
future
before
you
go
stable,
so
just
wanted
to
raise
that
as
an
issue.
C
Oh
I'm,
sorry
I'm,
not
really
I
mean
if
you
have
a
different
opinion,
I
guess:
yeah
yeah,
I
I
think
this
was
just
like
I,
like
the
ghost
signated
clarification
around,
like
the
expected
behavior
of
what
was
needed
from
the
metric
specification
and
I.
Think
Riley
and
Josh
have
answered
that
in
here.
Okay,
but
the
thing
was,
it
has
also
included
a
survey,
so
I
looked
at
like
Python,
and
then
it
was
confirmed.
I
think
that
both.net
and
maybe
Java
I,
can't
remember
if
Java
confirmed
it
don't
actually
conform
to
this
Behavior.
C
But
this
is
something
that
was
supposed
to
be
specified
or
I'm.
Sorry,
it
is
essentially
specified,
but
it's
nobody's
actually
implementing
this
Behavior,
so
just
kind
of
a
heads
up
that
bugs
probably
need
to
get
created
or
you
need
to
fix
it
before
you
do.
A
stable
release
is
the
point.
B
That
is
it
for
topics.
Is
there
anything
else
that
people
want
to
discuss.
D
Morgan,
do
you
want
to
give
a
short
update
on
the
community
meeting
that
we
had
or
do?
Would
you
rather
wait?
Are
you
going
to
prepare
something?
That's.
B
A
good
idea,
I
haven't
prepared
anything
but
I
think
that's
a
great
topic
for
today.
So
last
week,
as
most
people
know,
was
the
annual
kubernetes
kubecon
conference
in
North
America.
We
had
a
lot
of
community
community
members
arrive
as
well
as
end
users.
B
As
a
total
aside,
it
was
incredible
walking
with
show
floor
where
there's
you
know
the
corporate
booths
for
various
sponsors.
Certainly
in
previous
years,
most
of
the
boosts
were
focused
on
compute
and
storage.
It
seems
like
most
of
them
are
about
observability
now,
which
is
quite
incredible
and
open.
Telemetry
is
a
huge
part
of
that.
B
There
was
an
something
an
event
called
open,
some
tree
unplugged,
where,
where
we
had
maintainers
speak
to
community
members
and
and
and
had
some
breakouts
most
of
us
attended
at
least
half
of
that
and
then
later
in
the
afternoon
there
was
a
community
meeting
sort
of
the
official
one
was
unfortunately
timed
at
the
the
same
time
as
the
second
half
of
Hotel
unplugged,
where
we
had
about
75
people
show
up
and
we
discussed
the
project
road
map.
This
is
the
same:
dock
I
can
find
it.
B
B
We
had
a
similar
session
that
we
both
did
at
kubecon
and
then
discussed
on
this
meeting
a
few
weeks
after
where
we
did,
we
talked
about
like
the
major
projects
that
are
coming
up
in
open
Telemetry
and
earlier
this
year,
when
we
discussed
this,
some
new
ones
were
added
like
profiling,
which
now
has
a
large
set
of
new
people
working
on
it
as
well
as
we
discussed
the
the
work
that
at
the
time,
was
very
new
on
a
control,
plane
or
off-man
and
other
things
that
the
community
is
investing
in.
B
So
we
had
a
similar
discussion
here.
No
major
changes,
I
think
most
of
the
probably
the
power
benefit
of
of
the
session
was
to
sort
of
broadcast
to
people
who
are
attending
what
we
are
working
on.
B
That
being
said,
there
were
some
new
items
that
came
up
I'm,
gonna
I,
don't
have
the
photo
handy
to
present,
but
I'll
embed
it
into
the
dock.
Once
I
get
a
moment
for
some
additional
ideas
of
things
that
we
can
improve
on
open,
Telemetry
examples
included
eventually
waiting
into
the
area
of
showing
people
they're
building
semantics
around,
like
Cloud
cost,
and
there
were
various
others.
Unfortunately,
I
remember
them
off.
The
top
of
my
head.
B
I
will
take
the
action
to
integrate
these
new
items
into
the
dock
and
then,
secondly,
I
want
to
turn
the
dock
into
something,
probably
on
GitHub.
That's
like
a
I
hesitate
to
say
formal,
but
like
a
more
formal
project
roadmap.
Obviously
open
Telemetry
just
can't
have
like
a
super
formal
roadmap,
because
it's
not
like
we
all
work
at
one
company
and
someone's
our
boss
telling
us
what
to
do
things
get
developed
because
people
work
on
them,
but
still
it's
I,
think
very
valuable
to
have
something
a
bit
more
formal
and
GitHub.
B
That's
at
least
delineating
like
the
major
Investments
we
were
making
as
a
community.
This
does
not
preclude
other
Investments
being
made,
but
but
it
it
should.
You
know
in
some
cases
at
least
funnel
people's
effort
and
at
least
set
their
expectations
appropriately
around.
What's
going
to
be,
arriving
did
I
cover
that
Dan
yeah.
D
I
think
so
are
any
of
the
sort
of
topics
not
already
covered
by
a
Sega
or
a
working
group.
B
I
think
somewhere,
let
me
just
pull
up
a
photo
on
my
phone
I'm
just
hesitating
to
remember
what
the
new
topics
were.
The
existing
ones
are
all
are
already
covered.
Yeah.
D
B
Like
that
exactly
so
yeah
the
new
topics
work
one
one
idea,
and
again
none
of
these
are
sort
of
committed
or
formal,
yet
they're,
just
their
ideas.
One
was
building
semantics
and
and
doing
some
work
to
capture
Telemetry
from
CI
CD
systems.
I
think
I
want
to
be
really
excellent
and
possibly
very
straightforward.
That
would
be.
That
would
be
great.
Another
is
just
adding
more
kubernetes
metadata.
There's
some
specific
examples
of
of
metadata
that
we
could
add
one
that
comes
up.
B
A
lot
is
having
a
standard
Syntax
for
queries
made
to
back
ends.
I
think
this
one
is
a
bit
more,
maybe
contentious,
controversial,
just
because
I
think
there's
a
lot
of
there's
a
good
check
of
people
in
the
community
of
the
opinion
that,
like
this
is
valuable
that
maybe
shouldn't
be
a
no-tell
regardless
it
was
a
suggestion
and
the
thing
that
people
could
work
on,
perhaps
in
the
hotel,
Community,
perhaps
elsewhere
needs
to
be
discussed
further.
B
And
then
there
are
a
few
others,
like
a
Consolidated
symbol,
store
for
debugging
semantics
for
cloud,
spend
having
more
formal
user
extensibility
points
for
hotel
semantics,
so
I'll
get
those
noted
into
the
roadmap
Doc
in
the
next
few
weeks,
and
we
can
discuss
them
further.
I
think
this
is
probably
the
best
form
for
it
and
then
we'll
create
like
a
GitHub
markdown
file,
probably
on
the
community
repo.
B
B
One
other
cool
thing
of
note
for
all
the
maintainers
on
the
call,
because
we
ran
the
stats
from
cncf
Dev
stats
they're.
There
are
now
800
monthly,
active
contributors
to
open
Telemetry.
That's
like
people
active
in
our
GitHub
pushing
code
which
is
huge
like
it's
incredibly
exciting.
B
A
lot
of
people
here,
yeah
all
right,
that's
it.
If
no
one
else
has
any
other
topics,
then
I
think
we're
done.