►
From YouTube: 2022-10-10 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
A
B
A
A
A
Right
so
in
the
Ultra
spec
we
released
the
October
release
with
version
1.14
fewer
than
usual
additions
to
it,
because
just
recently
we
released
1.13
some
highlights
are
histogram
packets,
Universe
uniformity.
For
me,
first
was
established.
A
The
end
bars
for
the
SDK,
config
were
extended
and
more
semantic
convention
additions
and
in
the
protospace,
the
exporter
spec,
as
part
of
the
generate
specification,
was
extended
to
define
the
usage
and
to
be
set
by
Hotel
sdks
so
that
those
are
uniformly
reported
and
then
for
Java.
We
have
a
release
with
a
prototype
log
events,
API
version
and
Java
instrumentation
release
will
follow.
A
For
go
more
SDK
bug
fixes
expected
this
week.
Do
we
have
any
update
for
the
for
a
potential
release
date
for
metrics?
There.
C
I,
don't
think
we
have
a
release
date
for
our
next
Milestone,
which
would
be
beta
for
metrics.
This
is
just
an
incremental
release,
addressing
some
of
the
issues
that
have
been
discovered
in
our
offer
released
by
early
users.
We
wanted
to
get
this
out
last
week,
but
didn't
quite
make
it.
So
we
expect
it'll
happen,
probably
tomorrow
or
Wednesday,.
A
All
right,
thank
you,
C
plus
plus
metrics
work
is
ongoing
and
40
percent
complete
and
erlang
has
an
experimental
locks.
Sdk
emerged
for
the
community
demo.
App
I
just
saw
that
some
Metric
support
is
being
added
and
the
end
user
working
group
has
some
survey
analysis
summary
to
share
link
from
the
document.
A
A
Otherwise,
let's
move
on
with
the
project
naming.
So
there
was
some
inconsistency
with
our
project
names,
saying
open,
Telemetry
for
C,
plus,
plus
or
open
Telemetry
in
C,
plus,
plus
or
open
Telemetry,
C,
plus,
plus
or
any
other
language,
and
there
seems
to
be
agreement
for
open,
Telemetry
and
trusty
language
name,
so
open
Telemetry,
Java,
open,
Telemetry,
JS
and
so
on
and
Riley
will
send
a
spec
PR
to
provide
an
official
suggestion
there
and
then
also
the
detox
will
be
updated
and
probably
some
some
headers.
In
the
mean
we
need
for
some
sdks.
A
And
on
the
topic
of
repository
tooling,
the
TC
discussed
that
we
should
suggest
setting
up
the
panda
button
or
repos
where
there
is
language
support
for
it.
Of
course,
that's
not
something
that
can
be
enforced
on
a
repository
level,
but
but
individual
maintenance
would
need
to
add
the
respective
workflows
to
their
repositories
if
they
haven't
done
so
yet
are
there
any
such
as
any
objections
to
that,
or
should
we
go
forward
and
and
request
people
to
add
it
to
their
reports?.
B
Hi
everyone-
hopefully
you
can
hear
me
I
just
wanted
to
pop
in
real
quick
and
let
you
all
become
aware
that
we've
done
some
survey
analysis
and
so,
if
you're
not
familiar,
if
you
want
to
go
to
the
next
slide,
real
quick
if
you're
not
familiar
the
end
user
working
group,
we
do
end
user
research,
but
we
also
do
advocacy
and
community
building,
and
so
really
what
this
like
next
three
minutes
is
focused
on
is
survey
that
we've
had
out
and
the
survey.
B
If
you
go
to
the
next
Slide,
the
survey
was
launched
at
kubecon
EU
we've
had
72
responses,
and
so
that's
not
nothing
but
more
responses
gives
more
confidence,
but
just
wanted
to
share
some
of
the
highlights
that
we
found
so
far
on
the
next
slide.
You
can
see
about
demographics,
and
so
the
majority
of
the
people
taking
this
survey
are
folks
who
produce
or
add
open
Telemetry
signals
on
behalf
of
their
respective
organizations
on
the
next
slide
it.
B
The
experience
level
is
pretty
much
leaning
towards
experienced
users
to
intermediate
users,
and
so
the
next
slide
talks
about
how
code
is
instrumented,
and
so
the
vast
majority
of
folks
are
doing
some
source
of
Auto
instrumentation
and
customer
instrumentation,
so
kind
of
that
hybrid
mode
and
then
the
last
demographic
question
we
have
are
open,
Telemetry
project,
compute
contributors.
So
fundamentally
most
of
the
folks
who
are
taking
the
survey
are
not
project
contributors
and
so
that's
kind
of
like
the
demographics
that
are
useful.
B
We
did
a
little
bit
of
analysis,
and
so
the
next
slide
talks
about
net
promoter
score
if
you're
not
familiar
with
net
promoter
score.
It's
a
sentiment.
Analysis
metric
that
measures
people's
likelihood
to
recommend
a
product,
Oh
I
didn't
put
a
link,
I'll
put
a
link
into
so
you
can
learn
more.
But
overall
our
project
net
promoter
score
is
55.2,
which
is
a
good
score,
but
I
did
want
to
highlight
to
all
of
the
maintainers
The
NPS.
B
It
really
does
vary
by
experience
level
and
so
for
our
new
and
beginner
personas
they're
having
a
measurably
different
and
less
positive
experience
with
a
project
overall
I.
Just
we
thought
that
was
the
thing,
but
now
we've
got
a
quantitative
proof
of
that,
and
so
it's
just
good
to
keep
in
mind.
B
There's
there's
lots
of
stuff
that
we
can
talk
about
in
the
survey,
but
not
so
much
time
this
morning,
and
so
just
we're
looking
at
Trends,
and
so
the
survey
was
really
designed
to
be
trendable
over
the
course
of
time,
and
so
every
quarter
we're
hoping
to
have
a
little
bit
of
information
about
Trends
and
the
more
people
that
take
it.
The
more
confidence
we
will
have
in
the
results.
B
The
next
slide
is
talking
about
component
usage,
so
we
see
a
lot
of
respondents
who
have
collectors
and
are
using
go
or
Java
in
their
systems,
and
so,
when
you
look
through
the
data,
there's
a
link
at
the
in
the
sick
meeting
notes
that
just
keep
that
in
mind
that
right
now
it
isn't
necessarily
the
most
comprehensive
folks
using
all
of
the
different
products,
but
with
your
help,
I
hope
that
will
improve
our
time
over
time.
B
The
next
graph
is
really
about
satisfaction,
so
we're
measuring
satisfaction
of
these
six
different
areas.
So
things
like
installation
configuration
operation
and
maintenance,
documentation,
troubleshooting
guidelines,
performance,
overhead
and
out
of
the
box
instrumentation,
and
so
this
graph
shows
kind
of
the
overall
summary
of
each
of
those
not
broken
down
by
component,
but
for
the
project
as
a
whole,
and
so
like.
The
key
takeaway
here
is
the
folks
who
are
taking
the
survey.
The
included
troubleshooting
guideline
guidance
has
less
satisfaction
comparatively
to
the
other
categories.
B
But
overall
we
just
want
to
keep
eyes
on
this
over
the
course
of
time
so
kind
of
a
cool
graph,
and
the
next
piece
is
qualitative
challenges.
So
we
have
a
free
form
text
field
in
the
survey
that
says
what's
holding
you
back
from
adopting
more
open
Telemetry,
and
so
this
is
not
like
something
I
selected.
This
is
my
interpretation
of
their
answers,
and
so
obviously
maturity
is
a
very
large
subsection.
Here.
Maturity
can
be
for
all
sorts
of
different
pieces.
B
We've
got
people
who
want
more
profiling,
people
that
want
more
vlogging
people
that
want
some
different
types
of
metrics
within
their
respective
language
areas
that
are
not
yet
released
as
stable,
but
that
seems
to
be
a
big
piece
followed
by
documentation
and
so
again,
not
necessarily
any
novel
insights
here,
but
good
things
to
keep
in
mind
as
we
scale
open,
Telemetry
and
really
focus
on
bringing
in
New
Year's,
new
users,
okay
and
last
piece
like
how
y'all
can
help
so
again,
more
responses,
more
confidence.
B
This
survey
we
advertised
it
on
like
Twitter
and
cncf
slack,
but
I
did
I,
have
thoughts
about
where
we
can
maybe
embed
this
in
some
of
the
documentation
and
if
you
would
like
to
engage,
please
reach
out
to
me
on
cncf
slack
or
if
you
want
to
help
with
anything
in
the
end
user
working
group,
our
home
channel
is
otel
user
research
and
I
will
be
quiet.
Now,
if
you
have
any
questions,
I'm
very
happy
to
answer
them.
Thank
you.
A
Thank
you
for
you're
working
for
running
us
through
this
in
in
that
speed,
it's
nice
to
see
that
the
documentation
seems
to
have
improved,
because
I
think
that
was
one
of
the
major
pain
points
that
we
that
we
saw
in
the
last
such
such
service.
So
something
is,
is
changing
for
the
better.
There.
C
Kind
of
outliers
on
the
component
usage:
do
you
think
that
that's
the
result
of
the
audience
that
we're
seeking
responses
from
or
just
the
way
the
chips
fell?
With
the
few
responses
we
did
get.
B
So
for
the
68
responses
that
we
did
get
I,
don't
think
that
is
particularly
different
than
what
I
see
in
my
vendor
day-to-day
job
I
see
those
as
the
majority
of
where
our
customers
are.
So
that
doesn't
surprise
me
personally.
As
for
my
understanding,
this
survey
has
been
hasn't
necessarily
hit
like
individual
Sig,
slack
channels
to
say:
hey
folks
in
the
PHP
cncf
Channel
go
take
our
survey
and
so
I.
B
A
And
it
also
doesn't
develop
from
from
General
language
popularity
by
those
I
think
tiobe
in
the
indexes
and
so
on,
and
also
gold
might
might
the
the
more
might
benefit
more
from
having
open
Telemetry,
because
there
are
fewer
out
of
the
box
agent
instrumentation
Solutions
available
so
could
indicate
that
this
is
a
somewhat
Fair
sample
that
was
taken
there.
B
A
majority
of
responses
came
from
kubecon
EU.
We
had
like
a
open,
Telemetry
project
meeting
and
it
was
standing
room
only.
Then
we
threw
the
QR
code
up
there
and
so
it's
possible
that
that,
out
of
all
of
the
Outreach
that
we've
been
trying
to
get
people
to
take
the
survey
that
resulted
in
the
most
responses,
and
so
it
could
be
possible
that
the
folks
were
physically
there
in
Valencia
may
have
slightly
different
technology
Stacks
than
the
whole
entire
world.
But
we
don't
actually
ask
any
questions
about
geography.
B
That
would
be
awesome.
I
would
appreciate
that,
and
also
this
is
the
first
survey
like
aspirationally
I
would
like
to
have
four
surveys
for
the
community
and
one
that
really
focuses
on
installation
and
configuration,
because
I've
heard
from
a
lot
of
maintainers
that
it's
that
they
believe
that
that
is
a
challenge,
but
for
this
General
survey,
if
we
can
just
get
it
promoted
or
potentially
I
thought
about,
maybe
embedding
it
in
some
of
the
readme's
but
I
feel
like
that.
Installation
configuration
that's
more
targeted
towards
your
Sig
and
individual
concerns.
B
You've
got
might
be
better
to
throw
in
read
news.
B
And
if
again,
if
you
have
any
questions,
please
feel
free
to
reach
out
to
me
or
the
folks
in
the
otel
user
research
Channel.
A
All
right,
thank
you.
Also,
your
research
results
will
go
into
finale,
Community,
repo
and
then
later
on
in
the
telemetry.io
website,
repo
right.
B
Yes,
they
I'm
still
waiting
for
my
PR
to
get
merged,
but
if
you
want
to
take
a
look
at
the
raw
data,
I've
sent
a
link
over
to
the
raw
data
with
the
person
identifiable
information
redacted,
and
so
you
can
check
out
what
folks
are
saying.
But
eventually
we
intend
to
some
of
these
graphs
are
like
from
Google,
and
some
of
them
are
from
Tableau
I'm
building
out
a
tableau,
automated
survey,
analysis,
workflow,
and
that
should
go
on
open
Telemetry.
B
I
o
for
folks
to
be
able
to
hear
from
others
I
think
it's
I,
don't
know
how
many
end
users
would
be
interested
in
this
data,
but
the
more
that
we
can
help
them,
because
we
all
really
believe
in
open
Telemetry
and
we're
like
this
is
totally
the
future.
But
the
more
we
can
get
end
users
to
say
that
to
other
end,
users
I
think,
will
help
with
project
adoption.
Overall.