►
From YouTube: 2022-07-07 meeting
Description
OpenTelemetry Prometheus WG
A
B
D
I'm
from
brazil
I'm
in
a
very
close
time
zone.
I
guess
it's
2pm
here.
C
A
Nice
all
right,
so
I've
got
two
folks
in
the
east
coast
time
zone.
Well,
let's
go
ahead
and
get
started.
I'm
going
to
drop
the
link
to
the
meeting
notes
into
the
zoom
chat.
If
you
don't
have
them
handy,
if
I
can
click
the
right
buttons.
I've
got
a
couple
things
on
the
agenda
here,
but
I
want
to
take
the
next
two
minutes
for
you
all
to
review
the
agenda
and
add
any
items
that
you
want
to
specifically
chat
about
and
then
we'll
go
ahead
and
get
started.
A
Okay,
welcome
to
the
the
week
all
right.
The
first
agenda
we
have
up
here
is
pro
end
user
discussion
group
and
chat
channels
on
slack
for
those
of
you
who
are
not
aware,
this
is
the
end
user
discussion
group
is
aimed
to
be
a
vendor
agnostic
place
for
end
users
to
discuss
their
adoption
of
open,
telemetry
and
kind
of
discover
best
practices
together.
There's
a
few
reasons
that
we
are
doing
this,
but
recently
I've
talked
to
a
lot
of
end
users
who
really
want
that
space
and
that
form
to
come
together.
A
So
we're
gonna
do
that
so
the
first
one
is
july.
14Th
I've
been
chatting
with
various
product
managers
at
different
organizations
to
promote
this.
A
But
I
because
it's
a
google
me-
I
don't
know
how
many
people
are
gonna
show
up,
but
I
think
we
should
do
some
promotion
and
I'm
thinking
at
a
minimum,
throw
it
in
the
cncf
slack
open,
telemetry
channel,
but
I'm
curious
about,
if
other
folks
have
thoughts
on
how
to
promote
the
existence
of
that
discussion
group
and
also
this
separate
effort
to
provide
a
private
slack
channel
for
end
users
to
again
discuss
whatever
it
is.
They
want,
but
out
of
a
little
bit
of
the
public
eye
and
reese
and
rin
are
moderating
that
slack
channel.
A
A
Okay,
so
besides
throwing
it
in
these
open,
telemetry
channel
any
other
ideas
for
promoting
either
of
these
two
resources.
A
And
will
you
add
that
to
your
agenda,
michael,
I
think
is
here.
A
Okay,
cool
I'll,
give
you
that
action
item
I'm
gonna
reach
out
to
taylor,
I'm
not
exactly
sure
how
to
say
his
last
name,
but
he
runs
the
cncf
end
user
group
as
a
whole.
It's
like
a
program
and
it's
incredibly
different
than
what
we're
trying
to
do
and
see
if
he
has
any
suggestions
and
then
reese
do
you
want
to
be
the
person
that
adds
it
to
the
open,
telemetry
channel
and
does
a
little
bit
of
promotion?
We
can
do
some
this
week
and
then
probably
next
week
also.
C
Yeah
sounds
good:
okay!
C
A
So
I
guess
my
suggestion
would
be
hey.
Have
you
seen
this
because
we
threw
it
on
the
open,
telemetry
blog
last
week?
I
believe-
and
so
maybe
just
like
re-amplifying-
that
the
blog
is
there,
because
the
blog
has
all
the
information
which
I
think
just
a
quick
how
to
catch
somebody's
attention
and
be
like.
Please
read
this
thing:
hey
the
first
end
user
discussion
group
is
next
week.
Learn
more
here.
Put
it
on
your
calendars.
Don't
forget,
come
hang
out
with
us.
Otherwise
it's
going
to
be
a
very
lonely
discussion
group.
A
And
I
I
think
I
put
this
in
the
channel
and
by
the
channel
I
mean
the
end
user
research
channel
that
I
picked
lean.coffee
as
a
facilitation
tool
for
the
discussion
group.
We'll
try
it
out
and
see
if
it
works,
because
I've
led
a
lot
of
these
groups
in
real
life,
but
never
virtually.
A
Okay,
cool
second
item
up
here,
bring
your
own
customer.
First
interview
mini
retro
drossie.
I
can't
remember
if
you
were
in
attendance
last
thursday
you
were.
I
was.
A
Sweet
all
right,
reese
rin.
Sorry,
maybe
you
don't
have
a
ton
of
contacts.
But
last
week
we
ran
our
first
community-led
customer
interview
and
end
user
interview,
but
we
call
it
customer
because
we
need
a
better
name
naming
scheme.
But
vendors
are
like
finding
folks
and
funneling
them
into
this
program,
and
so
we
had
our
very
first
one
last
week
and
jurassic.
I
don't
know
if
you
have
anything
that
you
want
to
say
from
like
a
mini
retro
and
planning
perspective
on
attending.
D
On
top
of
that
discussion
I
mean
I
did,
I
just
take
notes,
and
there
were
a
lot
of
things
that
were
very
interesting
and
I
think
if
we
had
like
one
more
hour,
we
would
be
talking
for
one
more
hour
because
we
had
a
lot
to
discuss
from
from.
You
know
the
very
basics
of
what
is
in
the
scope
of
the
project
stages
of
the
different
signals
and
so
on
down
to
very
technical
details
about
the
collector.
D
So
I
think
because
the
project
itself
is
huge,
open
country
is
huge,
there
is,
there
is
a
lot
to
discuss
and
people
do
have
a
lot
of
questions
and
I'm
joining
this
call
here
today,
because
you
know,
customers
and
people
from
the
community
have
been
requesting
time
with
me
to
talk
about
open,
telemetry
and
their
end
users,
and
I
found
out
about
this
work
group
here
and
I
thought
users
would
be
here
as
well,
but
I
think
in
all
of
those
conversations
that
I'm
that
I'm
having
with
those
folks,
it
is
the
same
pattern
right.
D
A
And
so
we've
had
end
users
show
up
to
this
group
before
and
it
hasn't
quite
felt
right
yet
because
a
lot
of
this
is
the
logistical
planning
of
how
do
we
get
this
information,
this
user
research
back
into
the
community?
How
do
we
facilitate
all
of
those
moving
pieces,
but
certainly
we
had
an
end
user
show
up
last
time
and
they're
like
I
want.
I
have
a
need
and
they
shared
it
with
us
and
we
were
like
thank
you.
A
We're
not
exactly
sure
what
to
do
with
that
feedback,
and
so
I'm
hoping
that
maybe
the
discussion
groups
are
a
little
bit
better
of
a
place
for
them
to
like
chat
out
amongst
themselves.
But
I
I
do
think
you
you
mentioned.
It
always
starts
out
with
a
discussion
about
the
scope
of
the
project
there
may
be
and
where
we,
this
working
group
works
closely
with
the
comms
sig
as
well.
A
There
may
be
opportunity
to
if
you,
if
you're,
seeing
this
as
a
pattern,
could
we
throw
it
in
a
dock
and
say,
go
to
the
dock
first
and
then
come
back
to
me
to
try
to
like
yeah.
That
might
be
a
good,
a
good
first
step,
because
if
it's
a
pattern,
you're
seeing
people
you
you
within
the
project
have
a
lot
of
different
roles,
and
so
I
think
it's
a
good
call
out
on.
If
you
are
seeing
this
probably
other
maintainers
and
deeply
involved.
Technical
folks
are
seeing
similar
things.
A
A
Yeah,
when
they're
talking
about
scope
of
the
project,
is
there
like?
What
does
the
scope
of
the
project
mean?
In
that
context,.
D
So
we
don't,
I
guess
I
guess
it
all
actually
starts
very
specific,
with
very
specific
items,
very
specific
concerns,
and
then
we
go
back
and
check
whether
they
understand
what
the
project
is.
But
people
use
open,
telemetry
to
mean
anything
they
want
from
the
client
libraries
to
the
specification
to
the
collector
for
a
lot
of
people.
Open
telemetry
is
all
of
them.
D
We
just
don't
know
what
they're
talking
about
and
then
we
go
back
and
say
you
know
open
telemetry
is
all
of
that,
and
and
that's
why,
then
we
talk
about
the
scope
and
so
on.
So
perhaps
it
doesn't
really
start
with
the
with
the
scope.
It
really
starts
in
making
sure
that
we
are
talking
the
same
language,
so
I
guess
working
on
the
terminology
we
did
at
the
right
would
be
the
the
beginning
of
the
conversation.
Typically
now
some
users
are
very
technical
and
they're.
D
Very,
I
don't
know
they
they've
made
contributions
to
the
project
and
they're
well
aware
of
all
the
facets
of
the
project,
so
they,
but
those
are
the
minority
most
of
the
people
they
come
because
they
heard
about
open,
telemetry,
somewhere
and
and
then
open
times
becomes
what
they've
seen
in
that
specific
context.
D
But
you
know
you
mentioned
that
we
should
be
having
a
document
somewhere
or
something
that
people
can
refer
to
before.
Talking
to
us,
I'm.
D
With
that
I
mean
I
was
of
that
of
the
same
opinion
before,
and
I
think
we
had
a
discussion
about
that
on
the
governing
board
on
how
to
best
create
this
avenue
for
end
users
to
talk
to
us
and
someone
made
a
a
proposal
to
have
a
call
every
week,
every
couple
of
weeks
like
in
an
office
hour
office
hours
and
then
someone-
and
I
think
I
agreed
with
that
said-
wouldn't
it
be
better
to
have
just
an
open
channel
in
on
slack
like
a
channel
or
a
place
like
that
where
people
could
then
just
join
and
ask
questions,
and
I
think,
while
I
I
still
think
that
we
should
have
that
slack
channel.
D
I
found
out
that
people
talk
more
when
we
talk
live
with
or
online
with
them.
You
know
when
I,
when
I,
when
I
face
call
they
would
just
I
don't
know
it's
a
time
that
would
where
you
have
their
attention
and
they
their
thoughts
are
progressing
as
well
and
they
make
questions,
and
so
I
think
it's
worth
having
a
talk
like
that
with
end
users
or
when
no
office
hours.
A
You
up
a
little
bit
on
different
conversations
that
we've
had
around
similar
topics,
but
I
guess
the
tldr
is.
A
We
want
to
try
to
lighten
the
load
of
the
various
contributors
to
open
telemetry
and
something
like
office
hours
doesn't
help
with
that.
But
a
user-led
discussion
group,
hopefully
doesn't
need
our
maintainers
to
come
in
and
and
help
moderate
that
I
want
to
experience
experiment
over
the
summer
and
see
if
that
still
holds
true
and
if
there's
value
for
end
users
that
can
work
with
each
other
instead
of
grabbing,
because
our
maintainers
are
very
limited
and
very
busy.
A
So
that's
kind
of
the
the
piece
there
so
far,
so
maybe
that
discussion
group
can
be
a
little
bit
of
that
and
definitely
project
contributors
are
very
welcome
to
attend
those
as
well.
If
they
want
to
hear
from
end
users
get
that
experience
get
that
face
to
face,
but
there's
no
expectation
that
they
show
up
and
that
this
is
a
you
know,
a
burden
on
the
folks
in
the
community,
so
we'll
see
how
it
goes.
Okay,
so
changes
for
next
time.
A
I
think
one
of
the
pieces
of
feedback
is
audience
identification
and
so
the
the
work
I
think
is
going
to
be
reach
out
to
the
end
user
who's
going
to
come
to
the
interview
and
say:
hey:
what's
your
project
stack
where
an
open
telemetry
are
you
like
deploying
or
interested
in,
and
then
we
can
select?
A
We
can
optionally
invite
maybe
maintainers
of
those
particular
projects
or
components
to
come
so
that
they've
got
that
direct
piece,
because
our
our
first
interviewee
was
not
totally
comfortable
talking
about
the
collector,
because
that
wasn't
something
that
they
personally
did,
and
so
is
there
a
way
that
we
can
help
like
identify
the
audience
ahead
of
time
and
also
send
out
a
audience
invite
to
the
technical
committee,
because
the
technical
committee
are
going
to
be
the
ones
that
are
going
to
act
on
that
feedback
more
directly
and
so
audience
identification.
A
A
A
It's
not
intended
to
be
a
rigid
structure,
but
here's
the
high
level
of
what
we
want
to
talk
about
and
then
be
able
to
have
some
flexibility
to
flow
where
the
end
user
wants
to
take
us
in
the
conversation,
because
we
can't
necessarily
know
that
from
the
start,
but
our
end
user
said
that
they
would
have
appreciated
that
yeah.
So
those
are
the
only
two
changes.
I've
identified
at
this
point
for
running
one
of
these.
A
I
suppose
I
should
have
all
of
the
right
documents
up:
oh
they're,
further
down
in
the
notes,
I
think
for
people
who
maybe
possibly
scheduled,
but
nothing
has
been
scheduled
to
my
knowledge.
So
unless
anyone
has
an
idea
about
bringing
someone
in
probably
the
second
to
last
or
last
week
of
july,
we'll
probably
try
to
work
with
looks
like
morgan
had
an
idea
potentially.
So
we
need
to
follow
up
with
morgan
to
see
if
that
person's,
actually
getting
scheduled
for
this
month.
A
Okay:
okay,
any
other
conversation
I
feel
like
I'm
talking.
C
A
Okay,
oh
I'm
gonna
send
a
couple
of
links
in
here:
yeah
there's
our
blog
post.
Thank
you
but
okay.
So
this
is
the
process
doc,
and
this
is
the
discussion
template.
You
guys
can
read
that
at
your
leisure
and
if
you
have
particular
questions,
we'll
just
move
it
into
the
hotel
end
user
research,
slack
channel-
and
so
also,
if
you
have
suggestions
for
names
because
bring
your
own
customer
sounds
kind
of
weird.
A
So
we
also
try
to
bring
your
own
hotel,
end
user
and
that's
like
so
many
words
and
you
can't
make
an
acronym.
So
we
need
to
find
like
the
right
branding
for
this
effort.
But
fundamentally
it's
that
high
fidelity
feedback
from
an
end
user
versus
a
survey
which
you
know
you.
You
can't
really
necessarily
dig
into
it.
A
Okay,
moving
right
around
discuss
ideas
to
help
end
users,
understand
the
state
of
the
open,
telemetry
project
and
sub
projects.
This
is
a
pet
peeve
of
mine
and
a
lot
of
end
users
that
I've
talked
about
and
so
open
telemetry
community
day
was
last
a
couple
weeks
ago.
A
I
guess
and
they
threw
up
a
simplified
table
of
the
statuses
of
open
telemetry,
and
some
of
you
know
some
of
those
weren't
necessarily
accurate
to
my
version
of
accuracy,
and
it
made
me
think
if,
as
a
community
we're
having
a
trouble
to
communicate
with
each
other
about
the
status,
how
do
end
users
figure
this
out?
And
this
is
a
big
challenge
for
them,
and
so
I
attended
the
maintainers
meeting
last
week
just
to
see
what
was
up
and
I
had
an
idea,
but
I
wanted
to
chat
through
it.
A
A
I
know
it
doesn't
say
like
all
of
the
sub
categories,
but
I
feel
like
if
we
could
propose
definitions
for
a
release
candidate
for
beta,
because
right
now
I've
done
it
it's
so
many
months
but
like
trying
to
dig
through
all
the
docs
and
come
up
with
my
own
schema,
but
I
think
we
can
standardize
it
because
all
of
the
sub
projects
kind
of
have
a
different
definition
of
beta.
Some
of
them
are
like,
oh
yeah.
You
can
totally
use
this
and
some
of
them
are
like.
Oh,
please,
don't
use
it.
A
I
think
if
there
was
a
standard
set
of
words
that
we
used
to
explain
status,
then
that's
step
one
and
then
step
two
is
we
could
have
that
that
grid
that's
somewhere,
so
folks
don't
have
to
dig
through
documentation
or
that
amazing,
yet
totally
overwhelming
status
chart
of
inside
one
of
the,
I
think,
maybe
community
repo.
That
is
also
not
updated
too
often,
but
if
it
was
easy
we
could
bring
it
to
the
maintainers
meeting
and
ask
the
maintainers
who
are
there?
Is
this
still
true
this
week?
That
was
my
idea.
D
I
guess
the
complication
is
that
for
some
projects
like
the
collector,
there
isn't
one
single
stages
that
you
can
use.
Some
parts
of
it
are
stable.
There
are
many
consumers
of
the
collector,
so
there
are
distribution
builders
that
depend
on
the
collector
apis.
There
are
users
who
are
using
collector
distributions.
D
There
are
people
who
are
maintaining,
so
they
need
to
check
what
are
the
metrics
that
the
collector
is
is
creating
and
so
on
so
forth,
and
not
only
that,
but
even
you
know,
each
component
in
the
collector
has
its
own
status.
D
D
D
A
That's
a
good
call
out,
I
think
the
collector
is
awesome
and
amazing
and
very
complicated
and
it's
kind
of
in
a
leak
of
its
own.
I
guess
I
was
thinking
this
is
fundamentally
around
data
signal
stability
across
the
language
sdks.
A
Maybe
I
should
mock
up
something
instead
of
trying
to
explain
a
concept
and
then
you'd
be
like
this
is
just
misleading,
because
what
I
don't
want
to
do
is
further
mislead
folks,
but
I
want
to
make
it
easy
for
them
to
make
a
determination.
Is
it
should
I
try
it
out
now,
or
should
I
wait
and
how
do
they
make
that
determination.
D
Yeah,
I'm
sure
you
thought
about
that,
but
even
for
those
libraries
you
would
have
three
states
at
least
one
for
each
signal,
because.
B
D
We
we
say
that
they
will
go
sdk
just
to
say
just
change
mission,
one
the
go
sdk
for
or
the
tracing
the
traces
api
for
the
go
sdk
is
ready
does
not
mean
that
the
logs
api
is
ready
for
the
same
sdk
or
even
the
metrics
or
even
within
the
metrics.
I
mean
most
of
the
parts
of
the
metrics
are
ready.
But
then,
if
you
want
to
use
histograms,
you
should
stay
away
from
the
go
sdk.
You
know
so.
D
A
A
Yeah,
yes,
I
agree,
and
so
how
do
we?
I
think,
there's
like
small
caveats
that
we
can
say
like
metrics
of
stable
caveat,
except
for
exemplars
and
histograms
in
some
of
these
things,
there's
just
something
that's
more
friendly
than
that
crazy
large
chart
out
there.
So
I'm
I
will
muck
up
my
concept
and
share
it
out
with
folks
to
see.
Would
this
be
better
or
is
it?
Is
it
too
misleading?
A
And
I
guess
my
piece
is
for
those
folks
who
are
new
to
the
project
and
they
don't
want
to
dig
through
all
of
the
documentation
and
they
don't
want
to,
or
they
don't
have
time
to
they're
just
trying
to
like
start
it
get
started.
Is
there
a
medium
that
we
can
provide
them?
That
provides
a
little
bit
more
confidence
in
current
things,.
D
Yeah,
just
just
for
the
record,
and
I
guess
off
their
record
what
I
typically
tell
users
when
I'm
on
those
calls
that
I
mentioned
is,
is
my
feeling
or
around
the
the
stability
of
the
components
right.
So
when
they
ask
me
what
should
I
use
for
metrics,
I
just
tell
them.
You
just
use
the
client,
the
promiscuous
client,
because
sdk
is
not
ready
for
that.
D
Yet
for
traces,
sure
you
can
use
open,
client
sdk
and
for
the
collector
the
answer
is
typically,
it
depends
which
components
which
features
do
you
want
to
use
and
how
critical
it
is.
D
How
critical
is
it
for
your
pipeline
for
your
telemetry
pipeline
and
I
guess
that's
the
kind
of
answer
that
people
are
looking
for,
not
not
a
table
with
caveats.
It's
just
you
know.
Should
I
use
this
or
should
I
not
use
this
right
now
for
my
greenfield
project
and
should
I
use
this
for
my
critical
high
availability
applications
and
running
production
right
now?
D
D
A
Does
anyone
else
have
anything
they
want
to
share
on
like
ideas
to
help
end
users
understand
the
state
and
of
the
projects.
A
A
I
was
on
an
analyst
call
yesterday
talking
all
about
open
telemetry,
and
so
that
came
from
like
my
pages
of
notes
down
here,
but
I
thought
it
was
actually
really
interesting,
and
so
they
say
that
since
hotel
is
so
vendor-led
there's
a
high
degree
of
excitement,
but
vendors
have
identified
as
the
right
solution,
but
there's
not
a
not
a
broad-based
install
base
yet-
and
I
think
that's
generally
true-
and
so
did
someone
have
something
to
add.
D
It
is
so
true
that
even
companies
that
are
not
contributing
to
open
telemetry
are
trying
to
right.
The
wagon
are
trying
to
be
connected
to
the
project
on
their
marketing
materials,
so
it
is
true
to
some
level.
I
was
just
trying
to
understand.
D
You
know
in
which
context
was
it
said,
because
at
least
from
what
I
see,
most
users
are
just
at
the
beginning
of
their
open
telemetry
journey,
some
vendors
that
were
skeptical
at
first,
they
are
now
jumping
jumping
with
you
know,
full
force
in
the
project
and
more
vendors
are
doing
that
every
day.
You
know,
I've
just
noticed
that
one
other
another
vendor
is
is
now
also
investing
a
lot.
We're
planning
to
invest
a
lot
in
open
telemetry
in
the
next
few
months.
D
D
What
are
we
are
delivering
on
that
or
not
it's
it's
up
to
discussion,
but
that's
the
promise.
A
Absolutely
and
that's
the
most
common
thing
that
we've
heard
from
new
relic
customers
is
that
vendor
agnosticity
value
is
the
primary
driver
for
them
to
move
towards
open
telemetry,
but
also
a
close
second
is
around
tool
consolidation,
and
so
how
can
they
provide?
A
A
As
a
community
right,
that's
the
other,
the
challenging
piece,
and
so
since
we
are
here
to
help
bring
some
of
the
voice
of
the
end
users,
I
don't
know:
have
you
guys
seen
this
adopters
file?
I've
threw
a
link
in
there
and
does
it
make
sense
for
us
to
encourage
folks
to
sign
up.
Do
you
think
this?
This
matters
and
people
go
here
and
they're
like?
Oh,
because
a
lot
of
this
is
the
back
end
vendors
themselves,
but
care.com,
oh
care.com,
they
use
open
telemetry.
That's
awesome.
A
C
I'm
going
to
say
yes
because
there's
like
this
thing
called
social
proof
where
people
like
to
see.
Oh,
who
else
has
like
done
something,
so
I
think
this
is
actually
probably
gonna
be
really
effective
as
long
as
it's
accurate
and
you
know,
people
know
about
it
because
yeah
I
didn't
know
this
existed.
D
Yeah,
I
can
share
our
experience
with
jaeger
so
for
for
the
eager
project,
we
have
a
an
adopters
file
as
well
and
what
we
used
to
do
at
the
very
beginning,
not
only
at
the
very
beginning,
but
what
we
used
to
do
is
on
prs
from
new
users.
We
would
ask
them,
or
even
one
bug
reports
we
would
ask
them,
you
know.
D
Are
you
using
production,
which
company
are
you,
and
can
you
add
yourself
to
the
doctors
file
and
most
of
the
time
will
just
gladly
add
themselves
to
the
file,
and
you
would
find
good
users
there,
like
users
from
big
companies
from
workload
that
we
haven't
imagined
before,
of
course
not
as
not
as
big
as
uber.
D
One
of
the
you
know
the
starters
of
the
project,
but
still
that
is
a
very
good
resource
for
kubecon
as
well.
So
we
would
reach
out
to
users
with
nice
use
cases
and
ask
them
you
know.
Would
you
want
to
make
it
talk
about
your
your
situation
about
your
usage
of
the
project
and
some
of
them
have
so
I
think
an
adulterous
file
is
a
good
idea
and
perhaps
complementing
that
we
could
be
having
a
list
of
talks
from
end
users
at
conferences.
D
So
you
can
say:
oh,
this
is
how
shopify,
I
think,
shopify
delivered
a
talk
a
couple
of
years
ago
at
cubecon,
so
this
is
how
shopify
did
or
is
doing
now.
One
of
the
challenges
of
the
adopters
md
file
is
that
it
gets
outdated,
really
fast
and
it
gets
not
relevant
anymore
really
fast,
so
users
from
a
couple
of
years
ago
might
not
be
using
anymore
and
then,
when
we
refer
to
them,
they
just
say:
oh,
no,
I've
just
used
an
id
proof
of
concept
and
that's
it
or
the.
A
D
A
That's
an
interesting
experience.
Thank
you
so
much
for
sharing.
I
think
we're
not
we're
not
to
that
state.
Yet
so,
let's
encourage
them.
I
I
don't
know
who
owns
this
file.
I
came
across
it
kind
of
randomly,
and
so
I
really
totally
love
the
idea
of
reaching
out
to
folks
on
that
list
for
to
share
their
experience
about
at
conferences
and
stuff,
because
I
think
that
goes
to
the
vendors
have
identified
it,
but
we
don't.
A
We
don't
want
to
be
the
source
of
all
the
hype
right
if
we
can
get
those
reference
stories
out
there,
that's
gonna
be
really
great
for
folks,
and
that
gives
us
potentially
a
list
of
leads
plus,
maybe
even
a
bring
your
own
customer,
a
list
of
leads
as
well.
So
that's
great,
I
think
the
answer
is
yes.
D
I
think
we
should
not
open
appear
on
their
behalf,
because
we
most
of
most
of
the
times
we
we
cannot
verify
that
that
information
is
true,
so
we
don't
want
a
maintainer
on
our
side,
claiming
that
acme
corp
is
using
open
telemetry.
We
want.
D
Not
tied
to
the
project
stating
that.
A
Okay,
that
is
an
excellent
point,
but
it's
not
open
prs
on
their
behalf,
we'll
just
encourage
folks
to
do
it,
and
I
will
I'll
also
send
this
out
to
all
the
various
product
managers.
Most
of
them
are
like
they
show
up
in
the
open
telemetry
project
in
different
areas,
but
not
all
of
them
are
super
active,
and
so
I
will
ask
them
to
encourage
folks
to
add
themselves
to
the
adopters
file
just
to
make
them
aware,
as
I'm
asking
them
to
do,
that
for
the
discussion
groups
and
slack
channel
as
well.
A
Is
there
anything
else
related?
I
also
really
like
the
idea
of
a
curated
list
of
customer
stories,
like
some
of
those
recordings
in
a
centralized
place
that
people
can
more
easily
access.
That
should
be
something
relatively
easy
to
put
together
easy.
I
say
that
probably
not,
but
not
too
bad
to
put
together.
A
How
do
we
get
end
users
to
identify
as
the
right
solution
instead
of
vendors,
trying
to
like
celebrate
so
much.
A
A
I
wonder
what
that
would
look
like,
because
that
information,
I
guess,
is
sort
of
visible.
If
you,
you
know,
go
into
contrib
and
you
like
get
farther
down
into
it
in
some
of
the
the
areas
of
the
project.
But
it's
not
in
a
centralized
location
and
neither
is
instrumentation
to
be
fair.
I
think
it
is
super
easy
to
find
out
if
there's
even
a
package
or
library
available.
A
A
Todd
you
have
a
you,
you
mentioned
wordpress.
E
Yeah,
so
I
mean
there's
multiple
levels
that
open
telemetry
could
be
integrated
within
wordpress.
You
know,
be
it
a
theme
or
a
plugin
or
within
the
actual
wordpress
core
itself
to
some
level
or
even
automatic,
which
is
behind
wordpress.
They
could
be
using
open
telemetry.
So,
to
address
this
point,
I
I
wouldn't
say
that
we
should
set
up
a
pr
for
them.
E
They
should
sort
of
do
it
on
them
for
themselves,
but
there's,
I
guess
my
sub
question
is
a
meta
question
is
what
is
the
beyond
the
vision
of
having
interoperability
with
you
know
your
metrics
across
different
vendors,
like
what
is
the
angle
for
end
users
to
be
able
to
integrate
like?
E
Is
it
for
all
of
the
different
languages
to
have
auto
instrumentation,
because
right
now
it
seems
to
be
manual
across
a
variety
of
languages,
and
so
that's
also
a
major
hurdle
for
end
users
to
even
adopt
open
telemetry
to
begin
with
a
it's
manual
and
b,
it's
it's
not
stable.
Yet.
D
I
guess
there
are
different
levels,
so
there
is
the
instrumentation
side
that
I
mentioned
and
then
on
the
collector's
side
we
have
so
many
integrations
with
so
many
things
and
one
thing
that
that
charm
mentioned
no
sorry
it
was
ryan.
I
think
that
what,
if
should
we
document
or
should
we
mentioned?
D
Should
we
mention
people
who
are
interoperability
with
us
in
some
way,
and
there
is
a
there
was
an
issue
open
with
the
collector
a
couple
of
days
ago
asking.
How
do
I
configure
the
collector
with
cloud
foundry
and
it's
still
open,
you
know
and
that's
one
of
those
cases.
So
if
we
work
with
cloud
foundry,
should
we
document
it
somewhere?
If
we
work
in
kubernetes,
how
should
we
document
it?
When
we
have
an
operator,
the
collector
can
run
without
the
operator
in
the
in
kubernetes,
I'm
sure
it
can
run
on
cloud
foundry
as
well.
D
But
how
do
we
do
that?
And
it's
not
just
claiming
it's,
I
think,
also
showing
people
how
to
do
that,
and
that
implies
creating
documentation
on
our
side.
For
that-
and
I
guess
the
main
I
don't
know
on
my
mind-
I
guess.
D
D
So
with
all
that
said,
I'm
not
quite
sure
how
that
list
would
look
like,
because
we
have
really.
I
guess
we
are
close
to
100
components
on
the
collector
and
we
certainly
do
not
want
to
list
all
of
them
on
a
document
somewhere
saying.
B
B
A
I
think
this
is
maybe
a
good
question
to
take
to
tag
observability
as
I
go
to
those
incredibly
inconsistently.
Does
anyone
hear
a
regular
attendant
attendee
of
that.
A
Okay,
I
think
what
I'm
I
think,
alito's
pretty
regular
attendance
and
maybe
paul
bruce-
is
a
pretty
regular
attendant
attendee,
I'm
gonna,
throw
it
at
them
to
just
like
start.
The
conversation,
because
I
know
interop
is
a
big.
It's
a
major
value
prop
of
cncf
projects
as
a
whole,
but
I
I
know
that
they've
been
talking
a
lot
about.
I
mean
the
observe
k8's
effort
and
that
that's
primarily
a
big
interrupt
project.
A
D
Certainly
want
to
call
out
like
we
are
compatible
with
promises
on
different
sides,
so
we
can
read
prometheus
metrics
and
we
can
write
to
permission
servers.
What
are
future
issues
remote
right,
compatible
endpoints,
so
we
sh.
We
certainly
do
want
to
say
that
we
want
to
say
that
you
know
if
you
want,
if
you
want
to
use
the
open
cloud
sdk
and
api
to
instrument
your
application
for
and
expose
those
as
prometheus
endpoints,
you
can
do
that
as
well.
So
that's
something
we
we
should
be
talking,
but
I'm
not
sure
where
to
stop.
A
A
Awesome:
okay:
is
there
anything
else
on
the
this
topic,
I
see
reece
you've
added
one
last
point.
C
Yeah,
I
guess,
if
we're
done
with
the
previous
topic,
I
was
just
thinking
you
know,
thinking
about
the
quality
of
discussion.
Maybe
we
might
want
to
id
like
a
few
stronger
end
users
to
join
the
discussion.
So
it's
not
just
like
I
mean
I
don't
know
who's
going
to
come
right,
but
if
it
ends
up
being
like
a
lot
of
more
inexperienced
users,
they
might
kind
of.
C
I
think
there
was
a
suggestion
about
having
like
maybe
a
couple
of
maintainers
two
who
might
be
interested
in
joining,
but
you
know
I
don't
want
to
set
that
and
have
that
be
the
tone
or
not
the
tone,
but
like
have
that
expectation,
oh
someone
from
the
project
is
always
going
to
be
here.
C
So
if
we
can,
I
don't
know,
maybe
each
try
and
like
have
one
stronger
end
user
committed
to
coming
to
the
first
one.
At
least
I
don't
know
if
that
would
make
sense.
A
I
think
it
would
certainly
help-
and
I
think
since
reecey
and
I
have
talked
to
a
lot
of
end
users
who
are
like
please
do
this
and
we've
done
it
be
like
okay
now
you
gotta
show
up,
and
those
folks
are
generally
more
on
the
advanced
use
cases
anyway.
A
Yeah,
I
would
say:
let's,
let's
see
what
we
can
do
so
we've
got
one
week,
wow
it's
next
week.
Wow.
I
don't
know
yes,
it's
like
end
of
summer
already,
so
if
you
just
want
to
reach
out
to
folks
on
slack
and
just
you're
gonna,
throw
something
in
the
overall
open
telemetry,
and
we
can
also
point
that
point
people
to
it
and
I
can
slack
with
a
couple
of
customers
that
I
think
may
be
interested
in
well
as
well.
D
I
have
a
couple
of
people
like
startups
and
companies
that
are
trying
to
organize
and
end
users,
open
source
trading,
end
users
meeting,
and
I
guess
that's
the
main
reason
why
I'm
joining
this
one
here
today
is.
I
found
this
one
because
of
that,
and
so
I
could
try
to
lure
them
to
joining
those
calls.
A
Yeah,
I
I
would
encourage
you
to
do
that
or
if
they
have
ideas
about
how
to
make
it
better,
they
are
totally
welcome
to
come
either
in
the
slack
channel
or
in
these
meetings
and
discuss
how
to
do
that.
My
my
goal
really
was
just
how,
instead
of
trying
to
connect
new
relic
customers
to
new
relic
customers,
I
was
like,
let's
build
a
vendor
agnostic
place,
because
I'm
not
saying
that
new
relic
necessarily
does
this
the
best
way
right.
A
So
how
do
we?
How
do
we
get
to
that
vendor
agnostic
space?
That
again,
is
one
of
the
primary
value
drivers
for
end
users
to
adopt
open,
telemetry
right,
okay,
suggested
action
item
I
like
it,
how
about
everyone
tries
to
find
a
end
user
to
commit
to
join?
The
first
discussion
is
to
happen
next
week
july.
14Th.
A
A
July
28th,
so
I
don't
think
anyone's
necessarily
committed,
but
we've
got
a
bunch
of
question
marks
for
somebody
in
august
and
then
I
committed
somebody
in
september
so
potentially
some
somewhere
near
the
end
dish
of
august.
What
we're
trying
to
do
is
one
of
these
discussion
groups
per
month,
so
I
I'll
reach
out
to
morgan
if
the
person
for
july
isn't
gonna
if
it's
not
finalized
yet
I'll,
throw
that
in
the
end
user
discussion
group.
Whatever
is
the
outcome
of
that,
but
there's
too
many
question
marks
for
august.
D
Okay,
so
I
have
someone,
but
that
person
is
on
pto
between
july
18th
to
29th,
so
that
person
would
be
available
either
before
that,
supposedly
or
after
july.
29Th
and.
A
D
A
D
Yeah
yeah
yeah
so
yeah.
So
if
you
can
figure
out
a
date
in
in
august
or
just
keep
in
mind
that
I
do
have
someone
that
would
be
willing
to
be
interviewed
or
okay
yeah
yeah.
So
to
be
honest,.
A
Okay,
I'll
reach
out
to
so
ben
is
the
person
who
has
a
bunch
of
question
marks
in
august
I'll
see
if
that
person
is
committed
in
august.
So
I'll
just
reach
out
to
the
next
two
months
and
say:
are
they
committed
if
they're
not
committed,
then
what
do
we
need
to
do
to
get
folks
to
commit
so
that
we
don't
just
kind
of
like
run
this
last
minute,
yep.
A
Awesome
all
right
folks,
thanks
so
much.
I
thought
this
was
a
great
conversation.
Have
a
really
nice
weekend
see
you
in
the
community.