►
From YouTube: 2022-06-09 meeting
Description
OpenTelemetry Prometheus WG
A
B
B
B
B
A
D
C
E
E
E
E
E
So
majority
was
medium,
I
would
say,
and
and
then
the
notion
of
experience
in
the
project,
so
we
have
most
of
the
attendees-
has
very
limited
experience
in
the
in
no-tell
and
then
what
we
see
the
interest
of
the
various
users
so
in
which
part
which
portion
of
the
product
they
were
interested
and
and
then
how
how
we
would
recommend
the
product
we
and
then
I
collected
you
a
few
feedback
from
users
and
I
had
an
interview
I
had.
I
wanted
to
do
interviews
with
a
few
users.
E
E
Now
it's
pretty
pretty
big.
I
need
to
process
it
to
optimize
a
bit
so
the
feedback.
I
can
we'll
see
it's
mainly
because
when
you
do
pure
asp
core
it
works
fine,
but
then
you
go
outside
of
traditional
sp
court.
You
start
to
have
issues
and
also
a
lot
of
issues
related
to
versioning
between
libraries.
That's,
that
was
the
main
feedback
that
was
shared
the
other
user.
I
tried
to
interview
him,
but
he
was
not
responsive.
So
I
took
some
notes.
E
It
was
related
to
php.
The
hp
is
not
the
the
strongest
support
that
we
we
have.
As
of
now.
To
be
honest,
so
he
clearly
said
that
he
wanted
to
have
authority.
He
tried
the
php,
it
was
a
disaster,
so
he
basically
said
he
stopped
and
they
say
he.
It
seems
that
either
library
is
not
mature
or
there's
something
so,
but
they
do
they
were
not
able
to
at
least
produce
anything
and
too
complicated
to
produce
anything.
E
I
had
a
positive
feedback
from
a
customer.
I
wanted
to
interview
him
and
get
his
feedback,
but
he
was
very
worried
about
the
anything
mentioning
the
company
name,
so
he
was
not
very
up
to
get
recorded,
but
he
basically
he
was
able
to
implement
it
and
they
use
it
for
a
few
projects.
So
that
was
a
pretty
interesting,
successful
project
to
share,
but
we
don't
have
the
recording,
but
most
of
the
people
that
was
in
the
room
during
that
meeting,
says
that
there's
not
enough
examples.
E
E
So
that's
that's
quite
kind
of
normal,
so
I
think
it's
more
about
helping
them
to
getting
boarded
on
board
it.
But
what
I
would
do
is
I
will
I
need.
I
don't
know
how
we
could
share
it
so
so
far.
I
want
to
share
this
one,
but
I
need
to
do
it
on
excel
sheets
and
reproduce
the
same
graphs,
because
I
don't
have
the
rights
on
this
to
change
the
survey
because
I
duplicate
it
and
there's
no
way
of
removing
one
one
part
of
the
statistics
hendrick.
B
E
B
A
E
B
B
B
E
E
C
I
will
not
be
there,
but
philip
will
be
there
from
honeycomb.
I
know
he's
very
interested
in
this
working
group.
Just
couldn't
do
both
this
and
comes.
I
can
certainly
ask
him
to
assist
you
if
you're,
he
might
say
he'll
probably
say:
yes,
I'm
dialing
him
from
online,
but
that
won't
do
us
any
good
with
end
user
interviews.
E
E
E
A
Yeah
I
mean
my
in
having
looked
at
this.
I
think
it's
pretty
interesting,
there's
something
that
I
think
was
sort
of
missing.
Just
based
again,
I'm
aggregating,
like
my
personal
conversations
by
hotel
in
my
own
head
and
then
comparing
it
to
this
and
there's
no
inconsistency
in
the
data
itself,
but
there's
sort
of
like
the
what
hotel
signals.
Are
you
interested
in
thing
versus
what
you're
doing
today?
A
A
What
we're
missing,
I
think,
in
my
opinion,
that
I'm
open
to
everyone
else.
You
know
your
take
on
this
is
like
some
sense
of
like
what
is
a
must
for
you
with
open
telemetry
versus
what
sort
of
nice
to
have,
and
what
I'm
hearing
today
is
that
people
are
adopting
open
telemetry
as
a
must
for
tracing,
because
it's
not
really
an
alternative,
and
then
they
like
the
vision
and
so
yeah
metrics
and
logs
are
kind
of
getting
there
and
there's
interest.
A
But
then
there's
a
lot
of
stumbling
blocks
on
just
getting
tracing
fully
deployed.
I
don't
mean,
like
you've,
got
a
couple
of
services
emitting
hotel
traces,
but
like
it's
actually
working,
including
through
all
of
your
brownfield
legacy
layer,
seven,
whatever
blah
blah
blah
stuff.
That's
like
dropping,
headers
and
like
that
is
not
a
solved
problem,
and
I
still
think
is
the.
A
If
you
took
the
sort
of
like
must
for
hotel
versus
then
would
be.
Nice
stuff
is
like
where
all
of
the
gaps
are
at
least
again
like.
This
is
maybe
bias
from
the
the
stance
that
I'm
coming
at
it.
Maybe
if
we
had
someone
from
splunk
on
the
call
with
more
vlogging
focus
that
wouldn't
be
the
case,
but
I
was
just
curious,
like
just
gut
check.
E
I
think
that
the
the
what
we
I
mean,
what
you
observe
this
is
what
we
also
see
people
are.
They
have
few
come
customers
who
has
invested
in
open
tracing,
right,
open
sensors
and
then
the
the
merging
to
open
telemetry,
but
they're
doing
it
very
slowly
because
the
because
it's
some
significant
work
from
their
end,
but
yeah
most
people
are
investing
in
tracing
through
open
telemetry.
As
of
now
one
thing
also
that
I
think
the
best
I
mean
we
suggested
that
idea,
and
I
think
that
would
be
great.
E
E
So
we
need
to
find
the
right
format
for
that
and
then
invite
if
we
do
a
week
a
vendor
a
week
per
vendor
and
oh
oh
month,
preventer,
where
every
vendor
brings
a
customer
and
we
try
to
keep
agnostic,
the
name
and
whatever
it
is.
To
avoid
any
I
mean
so
bad
sales
habits.
That
could
happen.
I
don't
know,
but
I
think
that
would
be
great
to
in
that
month.
We
can
basically
take
10
minutes
to
share
hey.
E
This
is
what
happened
during
in
the
community,
what
we've
been
released
and
then
we
give
the
the
stage
to
the
to
the
user.
He
starts
sharing
his
experience,
the
success,
the
frustrations
whatever
it
is,
and
then
we
can
basically
talk,
ask
questions
and
also,
if
they
are,
if
there
are
other
users,
they
would
be
able
to
also
probably
ask
their
own
questions,
saying
how
you
did
this,
maybe
by
just
listening
we
will
get
lots
of
valuable
facts
and
topics
for
us.
A
Right
yeah
and
I
I
think
that
that's
and
there's
been
a
number
of
times-
we've
talked
about
having
some
kind
of
rotation,
and
the
governing
committee
also
is
trying
to
schedule
that,
and
then
we
had
one
that
was
sort
of
set
to
go,
and
then
they
backed
out
for
kind
of
opaque
reasons.
I
I
wasn't
involved,
but
had
to
do
with
some
sort
of
like
psychological
safety,
something
something
which
I
found
a
little
alarming.
Honestly,
I
don't
know
what
the
issue
was,
but
anyway,
but
totally.
A
I
I
think
the
the
point
I'm
trying
to
make
with
the
survey
itself.
I
mean
I'm
I'll.
I
think
it'd
be
great.
To
do
this.
Henrik
and
no
one
is.
Everyone
seems
to
agree
that
we
want
to
have
that.
We
saw
the
beginning
of
the
conversation,
but
in
terms
of
the
survey
itself,
what
I
would
find
most
valuable
is
something
I
could
we
could
use
to
prioritize
our
work
and
I
guess
I
just
want
to
make
sure
we're
prioritizing
the
work.
That's
actually
blocking
the
thing
people
need
from
open
telemetry.
A
It's
just
that
open.
Telemetry
is
sort
of
this
candy
shop
of
possible
possibilities.
Right
now,
but
a
lot
of
them
are
not
urgently
needed.
I
think,
and
I'm
worried
that
we're
going
to
continue
to
like
dilute
the
focus,
the
project
towards
things
like
you
know
that
I'm,
I
think
are
great
like
I
like
it.
A
E
Think
we
should,
I
mean,
from
my
perspective,
I
think
it's
very
exciting-
to
have
extra
signals
extra
support
extra,
so
I
think
that
would
be
great
to
continue
that
direction
and
keep
the
innovation
and
the
ball
rolling.
So
I
think
that
we
should
continue
in
that
direction,
but
we
should
also
have
other
groups
that
will
be
there
to
make
make
the
end
user
experience
much
more
better,
so
collecting
those
feedback
and
making
sure
that
every
maintainers
of
every
libraries
make
the
right
work.
So
then
the
onboarding
will
be
faster
and
easier.
E
B
Sorry
listening
to
those
two
listening
to
what
goes,
if
you
said,
I
I
found
myself
wondering
if
perhaps
you
were
talking
past
each
other,
I
wasn't
sure
ben
it
sounded
like
you
were
looking
for
more
pointed
questions
to
help
with
prioritization
like
long-term
goals.
It
sounds
like
both
if
you
want
agree
and
want
the
same
things
want
adoption,
but
then
it
sounded
like
you
were
saying.
Maybe
this
is
giving
us
a
lot
of
broad
information,
but
not
sharp
enough
to
help
us
prioritize
is
that
is
that
an
accurate
depiction
of
what
you're
saying.
A
Yeah-
and
I
mean
I-
I
I'm
not
sure
if
we're
talking
past
each
other
or
not,
I
understand
what
henry's
saying
and
I
think
it's
also
valuable
to
determine
like
you
know
where
the
pain
points
are
for
adopting
any
aspect
of
hotel,
and
I
mean
this.
This
is,
can
be
a
yes
and
thing
right.
It's
not
like
I'm
not
suggesting
we
remove
anything
from
the
survey
it's
more
like.
A
I
would
just
like
to
understand
like
for
the
stuff
people
like
you
know,
what
is
the
one
thing
you
need
out
of
open
telemetry
and
what
is
your?
What
are
your
blockers
on?
Getting
that
one
thing
that
you
need
or
whatever
that
that's
just
some
signal
that
I'm
wanting.
I
think
looking
at
this.
That's
all
I'm
saying
so
it's
it's
a
it's!
It's
totally!
A
E
And
I
think
I
don't
know
how
many
people
will
assist
to
this
open.
We
should
try
to
share
this.
This
is
the
first
version
of
the
survey,
but
we
had
an
idea
to
get
different
survey
for
different
topics
so
survey
for
the
collector
survey.
Then
there
will
be
more
precise
answers
or
specific
topics
for
each
individual
libraries
that
is
part
of
the
project,
but
this
is
the
sort
of
the
start.
E
B
E
No
not
not
yet
we,
the
idea,
we
said
we
need
to
start
somewhere
and
because
kubecon
was
there,
we
said
we
need
to
start
with
the
first,
let's
say
the
the
injury,
the
entry
survey
and
then
maybe
specialize
different
survey
based
on
the
technology.
So
here
we
see
that
if
we
see
that
70
is
using
java,
then
we
can
have
a
dedicated
survey
for
java,
because
it's
it's
basically
there's
a
large
use
now
large
number
of
users
on
java.
So
we
could
have
specialized
questions.
B
F
A
Mean
I
I
was
giving
examples
of
the
sorts
of
things
that
I
think
we
all
probably
see
all
the
time
when
you
get
into
like
a
brownfield
environment.
This
is
rarely
the
case
that
the
whole
thing
is
is
you
know,
custom
written
code
in
any
framework,
there's
always
like
a
bunch
of
other
vendor
nonsense.
That's
in
there
and
stuff,
that's
not
very
friendly
to
hotel.
E
E
Where?
Was
it
something
about
professional
support
compared
to
vendor-specific
collectors,
and
also
people
has
maybe
issues
to
understand
the
concept,
but
I
think
if
we
keep
producing
content,
we
could
easily
resolve
those
those
problems
and
promote
that
content
so
and
examples.
I
think
that
you
never
yeah,
I
think,
without
with
a
minimal
effort,
we
could
at
least
resolve
couple
of
pain
that
we
that
has
been
shared
with
the
with
the
users.
E
B
E
C
A
Yeah,
it's
a
good
question.
I
mean
so
I
mean
I'm
looking
at
the
I'll
put
it
in
the
in
the
zoom
chat.
I
mean
there's
a
spreadsheet
for
this
I
mean
frankly,
I
didn't
know
this,
but
ted
I
mean
the
the
customer
but
ted
young,
who
I
think
is
on
pto
right
now,
but
he
had
suggested
someone
from
github
to
be
the
person
for
june,
so
good
that
we've
identified
that
person,
but
there's
no
specific
date.
B
A
The
interesting
question
because,
like
I
remember
that
this
topic
came
up
at
the
governance
committee
meeting
and
and
then
it's
also
come
up
here
and
I'm
not
really
sure
like
which
avenue
it's
from
the
only
concern,
I
would
have
it's
not
for
hotel's
sake,
but
just
I
think
some
of
these
people
would
prefer
like
a
non-recorded
session
or
for
the
reasons
that
we're
discussing
so
it's
it's.
Not
it's
not
clear
to
me
like
what
the
level
of
openness
is
on
the
audience.
B
Should
we
let
the
facilitator
run
with
it
then
and
say
like
look?
This
is
the
date.
This
is
the
customer
and
you
figure
out
with
them.
What
sort
of
audience
and
long-term
persistence
they're
comfortable
with
right,
I
get
the
best
and
then
maybe
after
we
have
a
few
instances,
we
can
try
to
generalize.