►
From YouTube: 2022-08-25 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
A
C
A
B
A
A
A
A
B
A
A
A
A
A
But
yeah
I
will
so
actually,
I
think,
every
I
think
the
majority
there's
like
one
other
thing
that
that
does
need
to
get
moved
off
and
that's
the
collector
for
hotel
web
telemetry,
but
that
is
going
to
require
like
service
desk
and
stuff,
so
that
can
be
put
off
to
the
future.
But
I
think
that
the
biggest
things
is
getting
you
in
the
maintainer's
role
in
github
and
then
getting
you
into
netlify
and
that
should
be
analytics.
A
A
D
C
D
B
A
I
guess
I
will
oh
and
then
so
right.
The
other
thing
just
for
youtube's
notes
like
now
like
patrice,
like
they're,
like
maybe
the
three
of
you,
should
just
like
a
group
dm
or
something
or
a
private
channel
or
whatever
you
want,
but
they
should
be
your
primary
points
of
contact
now,
for
the
sake.
Okay,.
A
C
So
I
think
today,
at
least
from
my
point
of
view,
the
objective
was
to
get
buy-in
for
such
a
table
the
existence
of
such
a
table,
regardless
of
how
we
eventually
make
sure
it
is
up
to
date,
and
so
I
saw
two
things.
One
is
getting
buy-in
from
you
austin,
because
you
had
concerns
about
what
such
a
status
table
might
look,
what
sort
of
image
it
might
project.
Overall,
I
don't
know
if
you
agree.
My
feeling
right
now
is
that
I
think
this
is
very
useful
and
gives
a
good
overview.
A
A
D
My
chief
concern
is
that,
as
implemented,
there's
multiple
places
where
the
words
like
stable,
experimental,
alpha
and
stuff
contained-
and
I
would
just
like,
since
the
language
sig
maintainers
like
they
seem
to
do
a
pretty
decent
job
of
doing
updates.
I
would
like
for
them
not
to
have
to
update
multiple
places,
and
so
there's
there
might
be
a
technical
solution
to
this
and
then
surface
it
in
multiple
places
or
like.
D
Maybe
it's
just
like
it's
just
anchor
links
like
everywhere,
and
they
just
all
point
to
that
singular
spot
and,
like
maybe
you
got
to
click
a
link
in
another
place
or
something
but
like
I
like
the
table
being
there.
I
think
it
would
also
be
good
in
the
status
page
itself.
This
page
gets
a
lot
of
views
so
like
it's
a
good
place
to
put
that
kind
of
information
but
yeah,
I
don't.
A
The
more
excuse
me,
the
two
things
I
think
in
my
mind,
is
one
the
technical
solution
to
actually
like
to
building
a
reusable
component
that
we
can
put
on
like
multiple
pages
and
then
a
single
data
source
for
those,
so
that
this
entire
table
is
data
driven.
You
know
from
like
a
single
yaml
file
or
whatever,
or
god
forbid,
some
sort
of
build
time.
A
C
A
C
Like
to
say,
it
may
not
be
that
much
effort.
If,
if
we
can
agree
that
this
table
is
useful,
I
would
suggest
let's
put
it
in,
as
is
like
plain
text,
and
then
I
can
work
on
automation.
So,
for
example,
the
specification
statuses
are
updated
by
pulling
them
out
of
the
specification
so
that
nobody
has
to
update
a
yaml
file
once
the
spec
is
updated
it
just
it
just
happens.
A
A
A
C
A
C
A
A
C
B
C
B
C
A
C
A
C
To
well,
maybe
if
I
can
provide
some
context,
severin
raised
the
issue,
but
he's
not
the
first.
There
are
other
cncf
projects
that
are
that
are
and
have
have
and
are
facing
this.
So
it's
something
we
need
to
implement
more
broadly
anyways
and
as
a
first
step.
What
I
wanted
to
bring
to
the
attention
of
all
of
you
is
that,
after
speaking
to
chris
from
cncf,
he
was
saying:
let's
go
with
what
cntf.io
has,
which
is
essentially
I'm
going
to
modify
the
text
a
bit.
C
B
A
A
B
I
I
mean
I
have
spent
way
too
much
time
in
my
life
to
to
think
about
gdpr,
and
I
always
get
a
headache.
I
think
it's
not
perfect
yet,
but
none
of
us
is
really
let's
say,
a
legal
expert
on
making
a
final
call
and
saying
hey
this.
This
is
this
is
correct
and
this
is
not
correct.
So
probably
some
someone
from
cncf
or
linux
foundation
needs
to
to
to
go
deep
into
that
and
tell
us
at
some
point
this.
A
A
C
B
B
A
That's
it,
I
think,
browser
language
in
the
path.
So
there's
nothing.
That's
like
this
is
coming
from
a
particular
user.
I
don't
know,
if
that's,
I
would
also
say,
since
it's
performance
monitoring,
it's
probably
considered
functional
rather
than
for
ad
purposes
and
I'm
pretty
sure
there's
that
whole
like
functional
telemetry
loophole
anyway,.
A
B
B
How
do
people
put
the
author
name?
People
did
not
put
the
images
into
into
the
blog,
but
but
had
them
still
on
their
website
and
then
patrice
you
mentioned
like
hey.
We
could
package
them
up
in
a
certain
way
and
there
was
some
things
that
were
cross
posting
and
there
were
some
things
that
came
up
and
I
was
thinking
like
yeah.
Maybe
we
we
should
at
least
give
some
more
guidelines,
maybe
in
the
in
the
blog
template
or
something
saying
like
hey.
A
B
B
A
I
mean,
and
another
way
like
you
know,
let's
take
a
virtuous
example
right,
like
there's
light
step,
did
a
bunch
of
work
in
the
to
create
these
launchers
right.
It's
like
a
wrapper
that
has
like
a
config
layer
and
it's
stuff
that
isn't
in
upstream
and
like
over
honeycomb
they're
working
on
you
know
they
took
parts
of
what
we
did,
because
we
open
sourced
it
and
put
it
into
like
their
go
distro
and
I
believe,
we're
trying
to
actually
upstream
it,
but
like.
A
A
So
what?
If,
if
we
turn
around
and
say
like
oh
well,
this
is
just
like
a
little
command
line
tool.
This
is
just
like
some
little
add-on
to
the
collector,
we're
going
to
open
source
and
we're
going
to
write
a
blog
for
our
site
and
all
it
refers
to
is
just
the
open
source,
collector
tool.
You
know
it's
not
that's
something
that
would
probably
be
really
good
to
put
on
the
hotel
side
as
well,
because
that's
something
that
otel
users
would
find
useful.
A
A
Then
you've
made
a
lot
of
work
for
yourself
to
figure
out
like
where
is
the
line,
and
you
also
like,
let's
pretend
that
hotel
remains
like
this
very
important
part
of
the
ecosystem
going
forward
like
you
have
to
deal
with
people,
mommy
daddy
and
you
about.
Well,
you
did
this
for
x
company,
but
why
not
us
right.
D
Then
there's
also,
I
would
posit
that
a
very
healthy
for
the
ecosystem.
Kind
of
blog
post
would
just
be
like
a
survey
of
all
of
the
stuff
that
vendors
have
built
to
support
their
support
of
hotel
and,
like
not
only
is
this
like
a
great
open
standard,
but
like
for
the
majority
of
people
who
do
like
pick
a
vendor
for
certain
things.
Look
at
how
awesome
the
support
is
across
the
entire
ecosystem,
not
just
on
github
right.
A
So
originally
I
thought
I
here's
kind
of
my
here's
where
my
thinking
is
today,
because
when
I
originally
when
originally
moved
the
blog
over,
I
made,
I
said
something
like
it's:
okay,
to
cross
post
stuff
that
some
it's
okay
to
cross
post.
You
just
can't
have
like
a
active
cta
for
your
product
or
service,
even
if
it
is
about
a
commercial
thing
right.
A
But
it
can
talk
about
like
it
needs
to
be
original
content
like
any
content
for
the
open
source.
Blog
needs
to
be
original
content
for
the
open,
telemetry
blog,
with
the
exception
of
stuff
that
is
cross-posted
to
other
cncf
blogs
right.
So
if
we
want
to
make
an
announcement
post
about
metrics
ga
and
go
and
that's
gonna,
you
know
or
general
rc,
is
it
for
metrics
everywhere
or
logs
ga,
whatever
right
some
big
project
feature
that
also
should
be
blogged
about
on,
like
cncf.io
or
or
whatevs,
or
something
about
kubernetes
right
like
it's
like?
A
Oh,
this
would
go
in
the
kubernetes
blog
and
also
on
the
hotel
blog.
That's
fine!
If
it's
simply
repost,
if
it's
one
blog,
it's
going
to
appear
on
multiple
sites
in
the
same
ecosystem
or
if
it's
a
blog
that
originates
on
hotel,
io
and
then
is
reposted
with
some
changes
to
other
sites
like
two
vendor
sites
so
like.
If
there's
a
let's
say
we
hit
our
metrics
one
or
we
hit.
You
know
at
some
point.
The
future
was
like.
Oh
here's,
the
fun
right.
A
Here's
like
the
retrospective
of
like
the
past
five
years
of
hotel
and
it's
gonna
go
on.
It's
gonna
have
like
thank
yous
like
hey
microsoft.
You
helped
with
this
amazon.
You
helped
with
this
it's
kind
of
coordinated
to
go
out
to
all
these
different
vendor
blogs.
That's
fine!
As
long
as
the
source
as
long
as
the
main.
As
long
as
it's
like
hey
this
lives
in
the
hotel
site,
it
can
be
republished
on
other
things.
A
Because
that's
reasonable,
in
my
mind,
like
you,
can
talk
about
like
I
mean
a
good
example.
This
is
like
hey,
there's
like
stuff
in
the
a
dot.
You
know
collector
right,
that's
probably
not
going
to
be
turned
upstream,
but
there's
a
lot
of
amazon
users
that
might
be
reading
the
blog
and
they're
like
how
does
open
sound
help
me
with
like
ecs
or
with
the
specific
amazon
service.
That
is
only
in
the
where
the
plug
receivers
only
in
adot
like
it
would
be
useful
to
have
that
blog
on
the
hotel
site.
A
A
A
A
splunk
builds
a
distro
of
the
java
agent
that
includes
proprietary
extensions
to
otlp,
to
send
in
logging
information
about
profiling
and
that
data
only
works
in
splunk
it's
collected
through
the
opens
it's
collected
through
I
mean
it's
still
open
source
code,
but
the
data
is
not
used
like
it's
not,
but
it's
not
otlp
right
or
it
isn't
it's
otlp,
but
it
doesn't
make
sense
to
anyone
else,
so
it
gets
dropped.
That
to
me
seems
like
okay.
B
That
that's
what
it
comes
down
to
right
because
let's
say
I
said,
I
mean
emerson,
google
cloud
and
then
whatever
makes
it
complicated,
but
if
it
says
yet.
If
if
now
stick
with
the
splunk
example,
they
say
like
hey,
we
have
this
splunk
distro
and
you
can
do
this
special
special
stuff
here,
but
the
special
stuff
I
can
also
consume
with
jagger
or
with
whatever
back-end
I
use.
Then
awesome.
B
I
could
also
probably
live
with
that,
but
I
think
that
the
really
important
point
is
that
I,
as
a
as
an
end
user
or
reader
of
the
blog,
should
be
able
to
reproduce
that
without
going
back
to
the
person,
writing
a
blog
post
and
saying,
like
hey
here's
a
few
thousand
dollars
so
that
I
can
even
try
this
out.
Yeah.
A
A
A
A
D
I
took
a
pass
through
and
just
the
ones
that
were
like,
obviously,
either
out
of
date
or
like
just
not
applicable
anymore
or
just
like
this
was
completed
and
we
forgot
to
close
the
issue,
but
yeah,
there's
probably
like
a
whole
other
pass
of
like
well.
This
is
technically
a
problem,
but
it's
clearly
not
been
a
priority.
B
C
B
I
I
mean
if
we
I
I
raise
this
ticket,
so
if
we,
if
we
can
can
at
least
continue
this
discussion
a
little
bit
on
the
issue
I
I
raised,
then
I
can
in
a
second
step,
sit
down
and-
and
I
said,
codify
this
a
little
bit
and
I
think
we
also
need
to
to
look
like
hey.
Should
we
have
a
separate
markdown
file
for
that
or
do
we
want
to,
for
example,
put
it
into
this
block
template?
B
There
is
already
a
few
rules
there
that
we
say
like
it
is
especially
the
the
the
non-content
related
stuff,
like
put
an
example
image
there
and
say:
okay,
this.
This
is
how
you
should
ideally
do
it
yeah,
but
I
said
maybe
we
can
discuss
this
on
the
ticket
a
little
bit
more
and
then
I
can
see
if
I
can
can
come
up
with
something.
A
D
Yeah,
just
is
a
high
level
thing.
So,
as
you
are
probably
all
aware
of
kubecon
north
america,
there
is
no
open
telemetry
project
day
and
there's
no
like
open,
telemetry,
focused
event,
there's
a
thing
called
open
observability
day
that
appears
to
be
driven
by
some
logging
vendors
and
it's
like
logs,
focused
and
evidently
nobody
who
works
on
hotel
like
knew
about
this
thing
until
like
a
week
before
the
cfp
closed,
so
suffice
to
say
not
not
the
best
of
outcomes.
Some
of
the.
D
We're
sending
people
to
kubecon
like
lead
generation
right
and
we're
like
hey.
So
like
the
kubecon
eu,
there
was
this
thing
called
open,
telemetry
project
day
and
like
we
had
some
people
like
some
of
our
engineers,
just
like
go
to
like
part
of
the
community
and
like
talk
with
people
and
like
it
was,
it
was
cool,
and
then
there
was
the
open
telemetry
community
day
that
that
austin,
you
helped
run
at
in
in
texas.
That
was
also
pretty
good
like
it
was.
D
I
felt
it
was
highly
valuable
and
so
we're
like
hey
what,
if
like,
if
honeycomb
put
the
bill
for
it,
but
it
wasn't
a
honeycomb
event.
It's
just
vendor
neutral
and,
like
maybe
some
other
vendors
could
pitch
in
or
something
like
that.
There
was
a
like
just
independent,
open,
telemetry
event
happens
to
be
during
kubecon
when
a
lot
of
people
who
work
on
hotel
and
who
use
hotel
are
also
going
to
be
there.
A
D
D
A
I
mean
is
that
someone
that's
involved
in
the
comments
someone's
involved
in
like
the
discussion
here
like
I
will
some
point
of
privilege
yeah.
We
should
like
when
we
actually
set
it
up
like,
let's
put
it
on
the
blog
and
let's
like
talk
about
it
through
comms
and
stuff.
I
don't
know
how
much
we're
gonna
be
able
to
get
other
vendors
involved
just
because
we're
talking
about
like
super
short
timelines
here,
but
there's
yeah.
You
know.
A
D
B
D
Yeah
they
tend
to
do
like
you
know
vendor
parties,
and
so
this
would
like
not
be
a
party
and
not
a
vendor
thing
really
yeah.
It's
just
like
happens
to
be
a
vendor
like
paying
for
some,
because,
like
here's,
a
massive
missed
opportunity
by
the
cncf
to
like
get
people
from
their
second
largest
project
together,
yeah,
so.
D
It's
under
neutral
and
but
then
the
trench
coat
is
actually
like
honeycomb
underneath
it
I
think,
austin
said
that,
like
he
could
get
lightstep
to
like
pay
for
some
of
it
as
well
and
like
maybe
like
maybe
someone
a
spawn
can
do
something
to,
but
there's
also
some
like
shitty
logistics,
where,
like
they,
someone
from
the
cncf
sent
us
a
bullet
pointed
list
of
like
you
cannot
do
this.
You
cannot
do
this.
D
You
can't
do
this
and
they're
like,
and
we
were
like
reserve
the
right
to
like
blacklist
you
for
all
kinds
of
different
reasons
and
stuff.
It's
like
they're,
like
very,
very
protective
of
their
brand
and
what
they're
calling
their
community
and
it's
I
don't
know
it's
sad
because,
like
the
the
place
where
hotel
fits
in
is
a
vendor
sponsored
thing
that
is
not
about
open
telemetry.
C
D
No
idea
I
mean,
I
think,
like
this
is
also
an
example
of
the
kinds
of
things
that
like
why
austin
wants
to
spend
more
time
on
the
the
community
side
and
have
that
more
because,
like
there's,
no
one
working
on
hotel
who's,
like
the
point
person
to
talk
with
cncf
people
about
this
kind
of
stuff
and
like
people
and
like
the
government's
sake
from
what
I
could
tell
they're
like
super
on
board
with
having
somebody
do
that
kind
of
stuff
but
they're
all
like.
But
I
don't
have
the
time
for
it.
D
Yeah
but
okay,
so
there
might
be
some
more
things
to
share
in
two
weeks,
but
I
would
I
would
expect
we
would
do
something
with
the
open,
telemetry
blog
to
just
announce
it,
and
it
would
be
like
anything
like.
I
wouldn't
want
the
honeycomb
name
anywhere
on
the
blog
at
all,
not
even
at
the
event
frankly,
but
details.