►
From YouTube: 2023-02-13 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
A
B
Put
your
names
on
the
on
the
attendees
list:
yeah
I
think
Patrice
put
a
few
things
there,
but
he
mentioned
that
he
might
join
later.
So,
let's
see.
A
A
B
B
Yeah,
maybe
taking
care
of
them
take,
takes
longer
than
two
minutes,
but
then
you
can
turn
later.
Phil
already
mentioned
that
he's
not
going
to
join
and
I
said.
Patrice
also
mentioned
to
me
that
he
will
join
later,
depending
on
how
long
we're
running
today,
this
meeting
might
miss
it
anyways,
but
then
I
can
follow
up
with
him.
A
A
B
Yeah,
that's
it
I
think
we
have
a
few
topics
getting
we
took
over
from
last
week,
so
the
one
thing
I
think
Philip
put
this
here
I
think
we
had
this
discussion
again
and
again
before
this
is
more
around.
Like
hey,
we
have
more
and
more
people
asking
for
more
advanced
or
more
detailed
guidance
like
hey.
B
What
should
I
do
with
instrumentation?
Where
should
I
start
some
things
on
like
yeah
migration
guides
I
think
we
have
one
already
for
open
tracing
or
a
started
one
etc,
etc.
So
he
started
here
a
long
list
of
things
even
also
The
Collector,
like
what
distribution
to
use
some
deployment
patterns,
I
think
we
have
a
little
bit
of
work
now
going
on
on
that
sampling
and
I
also
added
a
bunch
of
things,
I,
don't
know
if
there's
anything
to
discuss
or
to
end
it.
B
Yeah,
exactly
did
good.
Did
you
call
this
out?
The
one
thing
is
it's
a
kind
of
a
meta
issue,
so
if
you
say
like
hey,
I
think
that
we
should
have
a
best
practice
or
some
people
don't
like
the
term
best
practice,
but
but
but
some
some
guides
on
X
what
I
said
and
then
it
does
not
fit
in
the
current
current
doc
structure
right
because
right
now
it's
it's
sometimes
really
hard
to
to
put
something
here.
B
B
So
is
it
a
big
question
is:
is
where
to
put
this
so
so
we
we
started
to
to
collect
those
things
here
to
then
see
like
a
which
one
of
those
do
we
want
to
have
in
the
docs
in
B
what
what
might
be
a
good
structure,
because
maybe
it
makes
sense
to
maybe
it
makes
sense
to
to
have
some
kind
of
Arrested
different
structure
here
or
maybe
adding
here
something
like
tutorials
or
guides,
or
something
like
that.
B
But
one
thing
I
also
called
out
is,
for
example,
the
Kate's
IO.
They
have
restructured
their
documentation,
I
think
a
while
back
so
to
have
more
a
little
bit
like
that
sort
of
getting
started
Concepts
and
they
call
it
in
tasks
tutorials
and
something
like
that,
so
maybe
even
it
makes
sense
to
to
to
consider
re-architecturing
that
so
getting
some
important
like
what
could
be
part
of
that.
You
see
like
this
conversation
stalled
a
little
bit
a
month
ago.
B
So
if
you
have
any
good
ideas
on
that
that
that
could
be
helpful.
B
I
think
in
a
very
similar
matter,
we
we
have
this
issue
coming
up
again
and
again,
so
it
also
raised
some
kind
of
of
meta
issue
on
that
is
like
hey
what
what
to
do
with
with
the
vendors
page
and
the
so-called
adopters
page
and
what
else?
So,
if
you
look
here,
for
example,
just
to
to
fill
in
some
content,
if
we
go
here
in
the
ecosystem,
we
have
a
page
called
vendors
which
is
kind
of
a
list
of
just
companies.
B
B
How
can
we
do
this
page
here
better
and
at
the
same
time
I
mean
the
one
thing
are
all
those
vendors
which
is
great
I
mean
all
of
us
work
for
one
of
them
right,
but
but
on
the
other
hand,
I
mean
there's
also
this
thing
like
that
that
people
want
to
know
like
hey
who
is
integrating
with
open
Telemetry
and,
for
example,
I.
B
Don't
like
this
with
the
no
can
Telemetry
I
think
this
one
is
the
more
interesting
one
like
hey
what
projects
May
support
of
open,
Telemetry
right,
so
not
sure
if
you're
aware
of
that,
but
lots
of
container
run
times
or
even
Docker
build
aches,
or
something
like
that.
They
have
open
Telemetry
built
in
right.
So
so
it
would
would
be
really
cool
to
to
have
a
longer
list
of
this
as
well,
and
then,
lastly,
and
then
this
is
really
the
one
that
bucks
me
the
most
is
in
the
community.
B
We
have
this
list
of
adopters,
but
if
you
look
at
this
list
here,
there's
a
lot
of
vendors
here
as
well
and
not
all
of
them
are
like
hey.
We
do
dog
food
in
here
and
here's
a
blog
post
to
the
answer,
so
we
have
a
few
of
them
here
right.
B
So
there's
any
question
is:
who
of
damn
has
just
added
themselves
in
again
like
assuming.
This
is
a
vendors
list
right,
and
this
makes
it
really
hard
to
find
the
interesting
ones
like
missing
them
here
right
now,
eBay,
where
we
were
noted
that
they're
doing
something
like
or
there's
a
bunch
of
other
end
users
that
make
use
of
open
Telemetry
where
it
would
be
really
cool
to
sell.
B
Like
hey,
I,
don't
know
we
have
this
in
that
platform
and
we
make
use
of
open
Telemetry
and
this
in
that
way,
and-
and
that's
that's
how
this
is
cool
right
so
and
the
idea
here
is
to
to
brainstorm
a
little
bit
how
how
to
redo
that
right.
So
how
to
distinguish
between
adopters,
integrators
vendors
or
whatever
else
comes
to
mind.
If
this
makes
sense.
B
Exactly
even
those
terms
are
not
really
well
defined
right,
I
mean
what's
an
adopter.
Is
this
a
vendor
adopting
open
Telemetry,
or
is
it
an
end
user
adopting
it
so
so
being
a
little
bit
more
clear
around
that
and
having
some
guardrails
around
that
to
to
be
because
at
the
end,
I
think
it's
super
exciting
and
super
helpful
for
making
a
good
case
for
open
Telemetry
to
to
have
those,
and
in
that
regards
I
mean
everybody
knows
like
a
bunch
of
those
vendors
here
right
but
but
I
think
end.
B
Users
are
much
more
interested
in
like
hey.
Who
else
is
doing
open
Telemetry?
Is
it
ready
already
I
mean
if
big
company
a
b,
c
d
e
f
g
are
using
open,
Telemetry
I
probably
can
also
do
it
and
then
the
other
question,
like
hey
I'm,
using
some
of
those
tools
here.
Oh
awesome
I
can
use
open,
Telemetry
natively
right.
So
so
that's
that
that's
my
line
of
thinking
here
and
I
think
initially.
We
just
should
spend
some
time
on
discussing
how
to
do
this
best.
B
So
also
here
some
some
feedback
and
then
thoughts
are
very
welcome.
C
It
makes
sense
I
wonder
if,
like
along
the
same
vein,
so
like
really
feature
like
companies
that
are
using
open
Telemetry
having
like
a
case
study
section
because
I
mean
we
see,
it
I
think
it's
like
sprinkled
throughout
the
blog
but
bringing
it
bringing
it
in
to
like
one
central
location
where
people
can
be
like.
Oh
yeah,
this
company
uses
open,
Telemetry,
here's
the
blog
post
for
it
yeah.
B
B
Should
we
link
that
so
it
depends
a
little
bit
under
case
study.
I
guess
I
mean
if,
if
they're
talking
more
about
their
product
and
about
open
Telemetry,
but
you
know
I,
think
let's
discuss
this
on
the
ticket
right
I
mean
that's,
there's,
definitely
some
some
goodness
we
we
can
accomplish
here
by
by
pointing
to
case
studies
and
then
what
else
comes
to
mind
right.
So
yeah
sounds
good
yeah.
B
Exactly
that's
about
those
two
yeah
Patrice
is
not
here,
but
I'm,
not
sure.
If
you
saw
that
we
are
now
rolling
out
more
and
more
this
prettier
workflow.
So
if
you
raise
any
PRS
with
the
website
that
we
we
for
enforced
to
to
use
prettier
to
to
standardize
a
little
bit
under
markdowns
looks
and
Fields.
A
B
D
B
Yeah
I
said
Patrice
is
working
or
has
done
a
really
awesome
job
on
that
I
think
he
raised
like
I.
Don't
know
how
many
PR's
over
the
last
few
days
to
to
just
make
this
working
so
so
now,
if,
if
you,
if
you
raise
a
if
you
raise
a
PR,
remember
to
to
run
prettier
before
handing
it
in
that
that's
really
appreciated
or
at
the
end
I
mean
sometimes
it's
easier
to
to
do
it
later
on,
but
yeah
I
just
wanted
to
call
it
out.
B
Yeah,
exactly
that's
the
issue
we
we
ran
into
today,
I
think
that
that's
why
your
blog
post
was
published
later
in
than
I
assume,
because
it
it
failed
the
the
Netflix
fire
build.
Also
now
it's
just
happened
with
the
previews
as
well.
If
I
understand
it
correctly,
this
is
more
like
you
opened
your
PR
before
we
started
to
enforce
it
right.
So
it's
a
dead
slime.
C
Yeah
yeah
I
think
it's
a
great
idea
just
having
a
standardized
format
across
the
board.
Yeah.
B
Yeah
exactly
and
then
from
there
I
really
hope
that
that
we
can
also
apply
a
few
more
things
like
I.
Think
something
we
should
also
discuss
is
something
like
c-spell
right,
I
mean
we
have
it
somehow,
but
but
but
I
think
we
don't
enforce
it,
and
in
looking
at
a
few
PRS,
we
got
recently
from
typos.
A
few
of
them
are
mine,
so
it
looks.
B
It
looks
like
I'm,
also
not
doing
a
good
job
here,
so
just
like
hey
running
c-spell
on
a
PR
and
making
sure
that
there's
no
typos
or
something
like
that,
I
think
that
that
it
could
be
a
a
good
good
follow-up,
yeah
I.
C
Don't
know
I
don't
know,
does
it
does
it
also
check
like
capitalization,
because
I
I
know
I
got
some
comments
on
on
my
blog
blog
post,
because
I
I,
like
made
traces
metric
Vlogs
like
proper
nouns
and
people,
are
like?
No,
no,
that
should
be
a
lowercase.
So
is
there
like
a
check
as
well
to
just
enforce
that.
B
C
B
Little
bit,
we
all
also
tried
out
I,
think
barley
or
how
is
it
called?
So
it's
a
Splunk
as
I
have
a
user
of
that
I
saw
some
sort
of
them
using
that,
but
but
it's
a
very,
very
big
tool.
So
the
moment
you
throw
it
in
you
get
like
hundreds
and
thousands
of
of
Errors
reported
so
as
I
wanted
to
to
have
something
more
lightwide
and
and
there
we
could
do
something
like
that
right.
So
there
we
could
David
could
do
something
like
that
hey.
B
You
should
not
write
traces,
metrics
logs
uppercase,
but
to
be
honest,
I
I,
don't
see
an
issue
with
that
being
published
that
way,
and
then
someone
calling
it
out
and
if
it's
not
changed
I
mean
yeah.
It's
not
it's
not
the
worst
thing
in
the
world.
Right
I
mean
typos
in
a
documentation
a
little
bit
more
annoying.
D
C
So
I
was
like:
oh,
is
there
something
wrong
forever
and
then
and
then
the
last
the
last
couple
of
times
I've
been
like
submitting
and
not
just
open,
Telemetry
yeah
people
are
like.
No,
you
should
be.
You
know
capitalizing
that
but
I'm
like
observability
is
capital
O
for.
D
D
B
No
I
think
that
the
cool
thing
is,
if
you
use
npx
sorry,
it
should
be
installed
with
npm
installed.
I
mean
we
can
improve
on
that
right.
I
mean
there's
even
ways
to
run
prettier
before
you
push
a
PR
or
we
can
add
a
GitHub
workflow
that
it's
validating
that
I
I
did
some
experiments
on
that,
but
yeah
what
what
one
step
at
a
time
right
so
right
now,
if
you,
if
you
raise
a
PR
I,
don't
think
you
get
a
prettier
yet
tiered.
B
A
B
Good
yeah
yeah.
Lastly,
I
think
that
that
I
have
to
follow
up
with
this
Phil
and
and
Patrice
on
that
I
raised
this
issue
here,
with
the
go
Community
a
while
back,
they
still
need
to
merge
this
in
and
then
we
still
have
the
outstanding
conversation
with
them.
Maybe
to
bring
in
the
talks
like
everybody
else
on
the
website
makes
us
probably
move
faster.
B
This
is
a
good
example
of
not
make
making
yeah
making
that
change
in
in
over
a
month.
So
but
I
said
we
need
to
follow
up
on
that
yeah
any
any
more
opaque
issues
any
any
follow-ups
on
last
week.
Anything
anyone
wants
to
discuss.
C
You've
got
a
link
to
those
meta
issues
on
the
in
the
meeting
notes
right.
A
B
Oh
by
the
way
one
thing
I
wanted
to
quickly
mentioned,
we
had
a
plenty
of
blog
posts
once
again,
so
that
that
really
looks
good.
Look
like
it's
like
one,
two,
three
three
blog
posts
since
the
beginning
of
the
month,
three,
four
of
them
and
end
of
end
of
January
yeah.
We
still
don't
have
a
Cadence,
so
we
just
take
them
as
they
come
and
just
put
them
out.
So,
let's
see
if
this
continues
like
that
or
how
to
do
it
in
the
future.