►
From YouTube: 2023-02-27 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
B
Do
a
workshop
with
Pavel
and
a
few
other
folks.
C
C
B
I
think
Philip
already
mentioned
that
he's
not
going
to
join
I,
have
a
cut
I,
think
at
half
so
but
I
think
we
should
get
through
that.
Probably
before
then
so
yeah,
let's
see
I,
don't
think
we
have
that
much
on
the
agenda
or
is
there
anything
missing?
B
Let's
see,
let's
maybe
give
people
two
more
minutes
to
join
or
something.
So
if
anybody
wants
to
add
something
to
the
agenda,
we
can
still
add.
D
B
Okay,
I
think
we
just
can
it
started
into
the
first
few
topics
and
then
then
see
whoever
else
is
joining
right.
So
I
just
saw
that
so
I
actually
wanted
to
quickly
get
this
blog
post
published,
but
I
just
see
that
we're
still,
it
still
needs
to
be
rebased
right.
So
yeah,
hey
Mary
good
morning,
I
guess
good.
B
So
yeah
I
think
we
have
to
follow
up
with
Sheen
I
think
his
real
name,
yeah,
I
I,
think
he's
based
in
in
APAC
somewhere.
So
probably
it's
light
for
him.
Maybe
I
can
follow
up
with
him.
My
am
morning
hours,
but
but
my
understanding
was
also
Patrice.
I.
Think
there's
Beyond
those
things,
nothing
missing
right
from
this
blog
post.
A
B
B
B
B
Let's
get
a
calendar
of
common
dates
across
popular
contributaries
and
recent
study
abandoned
to
community
six
somehow
has
interest,
since
every
company
and
culture
has
a
different
set
of
holidays,
Etc
I'm,
not
a
hundred
percent
sure
what
he
wants
to
accomplish
here,
but
I
guess
this
is
around
conflict
with
holidays
and
and
things
like
that,
so
yeah
I
I'm,
not
100
sure
if
this
can
even
be
solved
sufficiently,
but
maybe
it's
worthwhile
to
at
least
get
some.
B
On
the
other
hand,
I
mean
the
whole
calendar
is
nightmare,
so
I
gave
up
on
it
already
so,
but
yeah
I
think
maybe
he
joins
in
a
few
minutes
and
then
we
can
Circle
back
to
that.
If
not,
then
it's.
D
B
Awesome
any
comments
on
that.
Beyond
that
yeah
awesome
I
spend
a
little
bit
of
time
friendly
today.
I
had
a
few
minutes
to
do
something
myself
today,
so
I
I,
followed
up
on
this
best
practice.
Guidance
thingy
here
Philip
opened
a
few
weeks
back.
I
still
think.
That's
that's
something
we
should
be
tackling
so
I
I
made
a
suggestion
here
at
the
at
the
bottom.
How
how
this
could
look
like
and
I'm
curious
to
to
get
some
feedback
on
that.
So
just
as
a
reminder
what
this
is
about,
maybe
real,
quick.
B
Let
me
scroll
back
so
the
idea
was
like
hey.
We
have
a
lot
of
content
that
does
not
fit
the
current
architecture
of
our
navigation
right
I
mean
we
have
the
collector.
We
have
instrumentation,
so
it's
more
around
like
the
different
projects
that
we
have,
but
but
there's
like
cross-cutting
things
like
migration
guides.
General
guides
integration
with
things
that
exist,
maybe
already
and
and
then
even
things
like
hey
what
about
sampling?
What
about
managing
your
data
volume
I
think
there
has
been
a
few
more
around
collector.
B
A
few
more
around
I
think
sampling.
What
to
do?
What
not
to
do
I,
also
added
something
about
data
filtering
and
things
like
Apache
and
nginx,
and
then
other
instrumentations
right
really
hard
to
to
fit
into
the
current
architecture.
So
I
think
the
intent
from
from
Philippi
also
was
like
hey:
let's,
let's
collect
it
and
then
I
did
a
quick
trial
here
to
see
like
hey.
Maybe
we
introduce
a
section
called
guides
or
practices
or
I'm,
not
a
native
speaker,
so
so
I'm
open
to
to
suggestions
here
right
so
and
then
see
like
hey.
B
Can
we
fit
in
things
like
migrations,
Integrations,
some
non-language
instrumentations
and
then
things
like
yeah
managing
the
data
volume
what
to
do
about
data
privacy
and
whatnot?
So
that's
like
my
my
suggestion
and
then
beyond
that
everything.
That's
still
language
and
collector
specific
I
think
that
can
still
live
with
that
specific
area,
but
yeah
that
that
that's
like,
let's
say
my
my
line
of
thought
right
now.
A
I,
so
looking
at
your
first
couple
of
bullets,
I
I
agree
with
that.
So
whatever
we
can
Channel
intersections
that
are
already
existing
should
go
there
overall.
A
I,
like
the
proposal
in
terms
of
my
only
hesitation
coming
from
other
projects,
is
in
in
terms
of
the
use
of
the
word
guide
and,
and
maybe
not
in
the
sense
that
you
asked
the
question,
but
in
the
following
sense
that
if
we
label
certain
pages
guides
at
some
point,
some
somebody's
going
to
come
up
with
a
new
page
and
and
we're
going
to
have
to
scratch
our
heads
and
say:
is
this
a
guide
or
not?
Okay
and
yeah
I
found
that
it's
not
a
valid.
A
A
Pretty
much
didn't
organize
things
under
that
sort
of
a
categorization,
so
they
they
managed
to
fit
things
elsewhere.
So
your
first
few
bullets,
that's
what
you're
suggesting
so
any
language
specific
whatever
goes
under
the
languages
or
collector
Etc
note
that
we
already
have
a
migration
section
so.
B
Yeah
I
I
just
fit
fitted
it
into
them
right.
So
this
is
migration.
Open
tracing,
I,
yeah,
I,
I,
I
I
mean
yeah.
Let's
Maybe
see
how
it
looks
like
right
now
right
so
because
how
we
have
it
today
is
like
this
getting
started
concept,
and
then
this
is
more
like
aligned
a
little
bit
along
the
the
projects
demo,
including,
and
then
the
big
question
is
where,
where
do
you
put
all
those.
C
B
C
C
B
I
mean,
for
example,
kubernetes.
They
have
something
they
call
tasks,
but
this
is
also
very
open.
Then
again,
right
I
mean
this
could
be
like
everything
right,
tutorials
yeah,
so
they
they
have
restructured
this
entirely.
So
but.
B
I
could
I
could
live
with
something
like
recommended
practices
or
I,
don't
know
if
just
practice
this
works
or
whatever
it's
just
long
that
that's
my
only
issue
with
recommended
practices.
So
it's
just
like.
A
B
Yeah
so
so
here
recommended
practices
and
then
should
migration
still
go
below
it.
A
set
this
distance,
it's
just
something
I
was
thinking
about
moving
there,
so
also
to
make
the
existing
top
level
navigation
not
not
even
longer,
and
then
instead
having
things
like,
hey
I
also
have
my
issues
again
with
integration
and
instrumentation
right,
because
we
use
this
those
words
somewhere
else
already
with
a
different
meaning,
but
I
I
could
not
come
up
with
something
better.
D
B
There's
a
few
more
that
that
will
eventually
maybe
land
there
where
we
say
located,
there's
some
non-language
thing
under
the
hood
uses,
C
plus
plus,
or
go
but
but
allows
you
to
to
turn
on
open
Telemetry
natively
right
I
mean
this
is
this
is
what
what
is
this
pointing
towards
dent?
It's
something
like
kubernetes:
they.
They
have
a
good
support
for
that
yeah.
C
Oh
sorry,
well
I
was
gonna,
say
that's
why
I
know
for
us
at
honeycomb.
That's
why
we
put
everything
under
like
a
general,
send
data
umbrella,
because
we
had
the
same
discussion
going
like.
How
are
we
going
to
do
this?
So
we
just
said:
okay,
here's
the
different
ways:
how
to
send
data
whether
it
works
it
gets,
gets
the
point
across
and
I'm
not
sure,
if
that's
necessarily
something
that
would
work
for
open
Telemetry
either,
but
for
that
umbrella
term
is
what
I
am
sensing
from
this.
A
So
I
have
a
comment
and
a
question:
the
first
the
comment
in
terms
of
instrumentation.
If
we're
agreeing
that
practices
is
a
section
title
that
we
might
use.
So
if
you
go
back
to
the
website
well
under
integrate
under
sorry
instrumentation
I
meant
to
say
under
instrumentation,
there
could
be
a
section
at
the
top
called
practices
for
Best
Practices
that
relate
to
instrumentation.
So
we
could
have
practices
that
are
contextualized
in
sections
so
for
a
collector
Etc,
which
would
allow
us
to
not
stretch
out
the
left
nav
unnecessarily.
A
That
doesn't
prevent
us
from
having
a
top
level
practices
page.
That
would
then
redirect
to
section
specific
pages
or
subsection
specific
pages
so
that
I.
B
I'm
just
looking
at
the
collector,
because
we
will
get
to
that
eventually
I
mean
you
see
like
this-
is
growing
quickly
and
I
mean
you
called
it
out
as
well.
I
mean
there's
a
bunch
of
things
like
security
troubleshooting,
what
not
over
at
the
at
the
collector
Reaper
itself
and
if
we
add
all
of
that
I
mean
we
get
probably
like
10
points
more
so
so
it
starts
to
to
make
sense
to
to
structure
this
as
well.
B
So
I
like
this
idea
of
redirecting
that
you
feel
like
so
because
this
is
like
what
what
Philip
had
here
right
so
there's
language,
SDK,
specific
guides
and
then
like
pointing
back
to
like
hey.
You
could
also
find
this
here
my
blow
up
the
the
navigation
itself,
but
but
it
would
give
people,
let's
say
an
easier
way
to
be
because
one
person
goes
that
way
and
the
other
person
goes
that
way
and
then
hopefully
you
can
I'm
I'm,
not
an
expert
on
that.
So
I
rely
on
you
on
this
information
architecture.
B
How
to
yeah
make
this
good
so.
A
A
What's
nice
about
the
website,
even
if
we
make
a
bad
decision,
we
have
redirect
rules
that
can
allow
people
to
to
come
back
if
we
reorganize
content,
so
I
would
say
well,
first
of
all,
what
sort
of
timing
are
you
are
we
wanting
to
to
look
at
for
this
particular
issue
and,
let's
just
incrementally
bring
in
changes
and
and
yeah
get
some
feedback
see
how
it
works
so
and
and
then
readjust
as
as
necessary.
Yeah.
B
So
so
from
from
a
timeline
perspective,
I
think
and
then
that's
just
an
assumption.
I
have
to
double
check
on
that.
A
lot
of
that
context.
Content
already
existed,
it's
just
living
somewhere
else.
Right
I
mean
open
tracing
migration
is
already
part
of
the
website.
Yeah
Jagger
client
migration.
If
I
remember
correctly,
your
Aussie
had
something
mentioned
here
somewhere,
like
Jagger
migrating
from
Jager
Klein
to
open
Telemetry.
So
maybe
we
can
work
with
him
and
and
someone
else
to
to
see
if
we
can
make
make
a
copy
of
that
instructions
for
Apache
and
Engineers.
B
So
so
I
wrote
some
blog
posts
on
that.
We
probably
could
generalize
that
and-
and
put
it
here,
a
spell
leaves
us
with
this
integration
thing:
I
couldn't
live
without
them
at
the
beginning,
I
think
Rhys
mentioned
it
and
then
I
think
we
also
have
a
blog
post
on
sampling
and
whatnot.
So
we
can
maybe
even
get
something
for
the
the
data
volume
and
this
year
is
a
topic
I
wanted
to
to
get
into
anyway.
At
some
point
so
I
would
say
we
could
get
to
a
first
version
of
that
rather
quickly.
B
A
B
D
B
Yeah
yeah,
yeah
yeah,
so
so
I
was
for
for
a
long
time
just
circling
around
this
thing
where
to
put
the
Apache
and
the
engineic
stuff
right.
So
because,
let's
say
this,
this
is
my
engineering
team
that
has
worked
on
that.
B
So
so
I
want
to
to
get
them
some
some
promotion
for
that
on
on
the
website,
but
but
until
now,
I
just
did
not
find
a
good
place
because
technically
it's
a
C
plus
plus
contrib
thingy,
but
but
it's
a
weird
place
to
put
it
right,
I
mean
it
would
be
weird
to
to
have
it
under
C
plus
plus,
but
at
the
same
time
it
looks
weird
if
you
have
instrumentation
and
then
you
have
all
the
languages
and
then
suddenly
it's
Apache
and
engine
X,
so
yeah.
A
B
A
B
B
C
C
B
C
D
B
Now
I
mean
that
that
helps
a
lot
yeah
yeah
yeah,
but
but
I
think
that
that's,
maybe
even
something
we
can
codify
I
I,
find
it
a
hard
word
for
them,
but
but
maybe
even
put
something
like
that
into
our
contract
guidelines,
where
we
say
like
hey.
If
you
write
some
good
content
and
if
you're
not
sure
where
to
put
it
just
pick
a
place
and
then
we
can
help
you
to
to
make
it
happen
right
so
because
I
I
just
make
the
same
experience
myself.
B
E
A
I'd
like
to
say
that
in
the
past,
that's
kind
of
implicitly
what
has
been
happening
in
some
cases
where
content
has
been
contributed
and
in
a
section
that
eventually
ended
up
changing,
and
that
happened
with
the
demo,
for
example,
when
Philip
added
the
demo
and
here
and
there,
and
that
eventually
gave
enough
of
a
feel
for
hey.
Maybe
we
need
something
different
and
that's
how
the
ecosystem
section
showed
up,
but
it's
it's
hard,
it's
easier
to
do
that.
If
there's
actual
content
there.
B
Yeah
no
I
get
I
I
get
your
point,
yeah
yeah.
So
so
it's
easier
than
to
to
take
the
content.
We
have
already
put
it
there
and
move
it
around
yeah.
Okay,
that's
cool
yeah!
Thank
you,
yeah,
so
James
Patricia,
I'm,
not
sure
which
topic
we
should
take
next.
A
And
I'm
I'm
only
saying
this,
because
I've
had
to
clean
up
at
least
one
PR,
where
there
was
a
merge
done
and
it
broke
things
and
I
think
the
the
the
blog
post
that
we
talked
about
at
the
beginning,
I
think
that's
the
same
sort
of
problem.
A
Looking
well
I
what
I
wanted
to
say.
I
said:
I
spent
some
time
through
the
the
GitHub
options
to
try
and
see
how
to
twiddle
that,
so
that
we
can
potentially
remove
it,
but
I
I,
guess
I
want
to
say
I,
don't
know
how
relatively
important
it
is
to
other
topics.
Since
we
have.
A
Running
out
of
time
right,
several.
F
D
B
A
I've
done
some
digging
and
haven't
found.
Any
I
haven't
found
the
option
yet
because,
but
thanks
for
the
suggestion,
James
that
well.
F
D
Enforced
pretty
fire
workflow
right
so.
F
But
but
maybe
you
can
sorry
I
had
a
meeting
run
late
before
I
got
here,
yeah
just
so
quickly,
I,
don't
know
if
I
should
be
volunteering
myself
work
or
not,
I
haven't
confirmed
with
my
manager.
If
I
got
bandwidth,
you
know
that
whole
story,
but
yeah
so
I
mean
I've.
F
Seen
this
a
couple
times
now,
I
may
have
brought
this
up
in
a
prior
communication
meeting,
but
there's
a
lot
of
churn
going
on
because
everyone
has
different
holiday
calendars,
since
we
are
very,
like
you
know,
not
just
different
companies
but
different
cultures,
times
Etc
et
cetera
and
I've
seen
a
couple
times
now,
where,
like
people
have
shown
up
and
been
like,
oh
well,
some
key
people
the
need
to
run
this
meeting
for
a
Sig
group
aren't
here
because
their
company
has
this
holiday
off
and
my
company
doesn't
and
we're
like
or
something
so
yeah
I,
don't
know,
I
think
we've
talked
about
this
before.
F
As
far
as
like
you
know,
like
what
a
calendar
made
looked
like
for
these
days.
I
know:
we've
like
it's
been
handled
in
on
a
parasig
level,
I'm,
not
saying
we
would
need
to
enforce
anything,
but
maybe
just
like
make
some
way
of
proactively
letting
leaders
of
Sig
meetings
know
that
some
holidays
coming
up
and
therefore
your
audience
might
be
less
than
expected.
Upon
This,
Day
I.
F
C
F
Most
people
just
say
yes
for
all
right
and
that's
it
and
I.
Just
don't
look
at
it
because
it's
reoccurring.
So
this
is
like
another
event
that
I
don't
see
in
our
workflow
I.
B
Mean
the
thing
I
can
add:
I
wouldn't
even
know
as
a
maintainer
how
to
cancel
this
right.
If
I
now
would
know
that
I
don't
know
next
in
two
weeks
from
now,
Philip
and
I
are
out.
I
would
not
even
know
how
to
let
everybody
know
like
okay,
we
cancel
this
thing.
I
I
have
no
control
over
this
meeting.
I
think
that
that's
maybe
the
much
more.
F
B
Me
I
I,
get
your
point
and
I
agree
with
you.
I
have
this
issue
also
at
work
that
I
I
planned
a
meeting
or
I
think
it
was
January
16th
and
then
it
was
Martin
Luther
King's
day
and
nobody
showed
up
for
my
meetings,
so
I
I
think
the
there's
two
things
to
it.
So
the
one
is
a
sad.
Maybe
we
can
at
least
add
some
yeah
things
like
Christmas
or
winter
or
shutdown
break
or
a
highway.
B
You
want
to
call
those
two
weeks
around
around
the
end
of
December
early
January,
that's
yeah
their
holidays
right,
so
oh
yeah,
but
but
I
think
I
mean
there's,
maybe
a
few
others
where
you
say:
okay,
it's
very
certain
and
a
bunch
of
people
didn't
show
up,
but
I
think
what
would
be
much
more
helpful
is
and
then
I
don't
know
if
this
is
even
possible
if
a
maintainer
is
even
able
to
cancel
such
a
meeting
without
involving
a
third
party
right.
So.
F
Yeah
some
workflow
there
for
like
hey
it's
likely.
This
meeting
shouldn't
happen.
What's
the
workflow
look
like
so
people
aren't
just
constantly
going
like
wait.
What
do
we
do.
B
Why
should
they
cancel
their
meeting
right
so
but
I
think
at
the
end,
it
really
depends,
as
you
said
like
on
the
key
people,
that
they
at
least
coordinate
and
then
say
like
hey,
nathamine
or
Philip
in
our
case,
can
can
jump
to
this
meeting.
So
maybe
it
makes
sense
to
to
just
skip
it
or
we
we
talked
with
Patrice
and
Tad
and
say,
like
hey,
is
there
anything
you
want
to
discuss?
Do
you
want
to
run
this
meeting
and
if
not,
we
we
can
get
rid
of
it.
So.
F
D
F
B
No
but
at
least
they're
the
right
people
that
might
say
like
hey,
we
can
already
open
an
issue
on
the
community
GitHub
work,
you
check
the
maintainers
Hotel
maintainers
slack
or
something
like.
B
A
D
B
Understanding
was
to
to
figure
out
how
how
we,
as
many
generals,
can
cancel
the
comps
meeting
right.
So
it's
a
nice,
demeanor,
Philip,
probably
I,
guess
know
how
to
do
this
and.
B
I
I
mean
I
need
I.
Thank
you
for
calling
this
out.
I
need
to
jump
now.
Unfortunately,
it's
always
like
that
right,
the
meeting's
very
assumed
it
will
only
take
30
minutes.
They
suddenly
take
the
full
hour
and
vice
versa,
so
anyways
this
this
was
super
helpful.
Thank
you
very
much
and
then
let's
catch
up
on
slack
or
in
two
weeks
from
now
sounds
good
thanks.