►
From YouTube: 2022-05-26 meeting
Description
OpenTelemetry Prometheus WG
B
B
A
Yeah
just
just
context:
it
came
up
last
last
week
to
continue,
and
you
know
I
saw
hendrick
there
doing
the
interviews
and
everything-
and
I
mentioned,
or
we
had
a
discussion
around
adoption
and
this
this
key
statement
was
around
you
know,
open
telemetry
is
awesome,
but
we
want
to
avoid
that.
We
become
the
next
ipv6
and
we
need
to
make
sure
that,
in
terms
of
adoption
that
there
is
a
clear
you
know
whatever
needs
to
be
done,
that
could
be.
You
know,
obviously,
the
user
research
better
understanding.
A
What
are
the
blockers,
what
you
know
the
or
whatever,
but
then
also
taking
it
further
like
you
know
what?
What?
What
can
we
do
to
to
increase
the
adoption?
Maybe
we
need
to
simplify
things
if
it's
messaging,
if
it's
whatever-
and
that
was
the
starting
point-
and
earlier
today
char
said
like
hey,
why
don't
you
just
join
the
media?
It's
like!
Oh,
I
actually,
you
know,
didn't
didn't
realize
and
that's
why
I
tried
that's
why
I.
B
A
A
D
A
B
A
B
B
E
C
E
E
B
B
B
E
A
E
B
A
A
I
think-
and
I
think
I
I
was
awesome-
I
I
owe
you
also
an
introduction,
because
you
you
were
kindly
explaining,
where
you're
coming
from
I
currently
own,
the
italy's
distributor
for
open
telemetry
in
our
service
team,
so
open
source
opportunity,
service
team
at
aws
and
yeah
I've
been
in
death
row
before
a
long
time.
Before
I
moved
into
the
product
role,
maybe
you
aprender,
since
you
mentioned
aprender,
wasn't
that,
like
I,
I
believe
it
wasn't
jj.
Also
sometime
at
the
brenda,
was
that
another?
A
B
Yeah
originally,
this
was
mirroring
the
comms
sig
and
every
other
week.
I
think
honestly,
there
might
be
the
easiest
thing
to
probably
be
to
match
up
to
45
to
match
the
comms,
because
that
has
expanded
as
well.
There
might
be
a
good
argument
to
turn
this
into
an
hour
and
change
the
date
to
change
like
what
day
it
falls
on
or
change
the
cadence.
D
D
B
E
B
B
E
D
B
I
think
let's
maybe
try
that
for
a
bit
and
if
char
has
like
really
strong
feelings
about
it,
then
she
can.
I
honestly
maybe
we
could
probably
like
we
could
probably
reschedule
comms
a
little
bit
too,
because
that's
a
pretty
light
meeting.
The
only
thing
that
I
the
only
comment
I
really
had
for
this
was
the
impression
I've
gotten
from
talking
to
people
that
were
at
kubecon
was
that
sort
of
the
big
things
were
identified
as
being
kind
of
pain.
Points
were
around
docs
and
like
onboarding
sort
of
new
user
experience.
B
E
E
E
Definitely
I
was
going
to
go
over
this
with
a
larger
group.
Chart
was
there
as
well,
and
so
we
we
had
a
discussion
like
we
did
a
roadmap
discussion
just
this
everywhere
else.
But
that's
sorry.
That's
was
tracked
in
this
dedicated
dock,
but
one
of
the
first
discussions
we
had
was
like
what
you
know.
We
shipped
lot
tracing
and
metrics.
What
let's
like,
take
a
look
back
at?
E
What's
working
well,
what's
not
working
well
in
the
community,
and
so
there
was
there's
a
lot
of
good
feedback
about
like
it's
easy,
the
easy
to
start
being
a
contributor
more
than
any
other
oss
project.
People
said
like
I
download
the
source
from
particular
repo,
and
it
tends
to
build
which,
like
honestly
in
my
experience
for
most
github
repos,
is
not
true,
where
I
spend
like
two
hours
fiddling
to
make
it
even
build
properly
and
they're,
like
hey
most
of
the
repos.
Have
things
tagged?
E
It's
a
good
first
issue
like
great
to
get
started
and
the
community
is
very
welcoming
kind
right.
You
join
sig
calls
people
are
nice,
they're,
very
welcoming
to
having
more
people,
and
that's
not
always
the
case
of
open
source
projects.
Then
we
asked
what
could
be
improved
more
maintainers
to
spread.
E
E
E
But
there
was
like
a
lot
of
a
lot
of
feedback
from
like
nick
and
amazon,
for
example,
about
like
hey,
open
slime.
Shoe
is
great
if
you're
fairly
technical
and
you
can
already
use
it,
but
for
a
lot
of
people
that
come
in
for
the
first
time
and
they're
overwhelmed.
They
need
more
opinions
on
like
basic
documentation
where
we're
like.
E
Yes,
it's
very
pluggable,
but
for
most
like
for
most
installs,
go
use
the
collector
and
then
use
the
language,
auto
instrumentation
agents
and
have
those
talk
to
the
collector
and
export
the
data
and
have
so
like,
like
more
sort
of
sort
of
very
basic
examples
and
opinions
about
how
to
use
things
and
how
to
get
started
with
it.
Have.
B
C
E
E
B
A
E
Opposed
to
being
like
here's
50
different
ways,
you
could
proceed.
It's
like
yeah,
but
here's
like
the
way
90
of
people
should
proceed.
Okay,
yeah
and
then
his
his
other
along
those
lines
was
also
just
making
like
like
these
are
technical
changes
now
but
like.
Why
aren't
more
things
configured
by
default
like?
Why
doesn't
the
collector
go
sniff
out
for
instrumentation
sources
and
just
instrument
them
instead
of
instead
of
having
to
be
configured
explicitly
to
do
so
yeah
that
one
is
getting
work
done
right
now,
yeah.
A
I
I
suppose,
on
a
high
level
the
what
I
heard
so
far.
The
documentation
is
really
great,
like
great
detail,
everything
there,
it's
more
like
navigation
like
if
you,
if
you
ask
yourself,
if
you
come
there
and
you
either
you're
like
contributing
I'm
doing
something,
I'm
you
know
part
of
the
sig,
and
I
want
to
know
where
to
go,
what
to
find
or
I'm
an
end
user.
I
just
want
to
know
how
do
I
deploy
the
collector
on
this
platform
or
whatever,
and
these
two
roles
you
know
that
can
be.
You
know.
A
Different
projects
have
different.
You
know
they
say
end
user
documentation,
developer
implementation
or
tagging
or
whatever
it
is
whatever
the
structure
is
and
if
we
can
guide
our
overall
open,
telemetry
audience
more
how
to
find
the
right
bits
for
for
them
as
a
contributor,
slash,
developer
or
as
an
end
user.
I
think
that
would
go
a
long
way.
That's
what
I
heard
in
terms
of
feedback.
B
So
we're
working
right
now
on
something
over
on
comms
about
trying
to
or
there's
a
general
com,
sig
goal
of
making
open,
telemetry
data,
io,
authoritative
about
open,
telemetry
yeah
and
we're
really
kind
of
starting
that
in
earnest.
Now
we
actually
just
had
a
big
pr
get
merged
that
takes
a
big
pass
on
all
the
conceptual
documentation
and
pulls
in
a
lot
of
sort
of
the
stuff
that
people
have
written
on
like
vendor-specific
sites.
Like
obviously
you
know,
amazon
has
really
good
docs
for
their
distribution.
Splunk
has
docs
for
hotel,
honeycomb
lightstep
new
relic.
B
E
B
Contact
with
whoever
is
your
owner
for
that
stuff,
so
that
I
can
like
pitch
them
on
this,
because
some
of
this
does
mean
that
I
will
like
docs.
You
know
the
the
com
sig
can
help
drive
this
like
we
are.
We
are
doing
the
work
to
make
these
docs
better,
but
a
lot,
but
there
needs
to
be
a
secondary
part
of
like
okay.
E
B
E
B
B
A
A
B
That
is
100.
The
the
ideal
here
is
that
everyone's
docs
teams
can
have
upstream
right
or
dedicated
writers
for
upstream.
So
some
of
that
is
like
I
said
since
you're
all
hearing
this.
If
that's
something
you
want
to
publicize
or
start
talking
about
like
there
is
an
open
issue
for
this
and
the
website
repo,
and
you
can
start
sending
people
to
like
the
comms
meetings
and
we
can
figure
out
what
you
all
need
in
terms
of
coordination
and
tracking
and
github
issues
and
stuff,
actually
with
contact
yeah
that
too
cool
beans.