►
From YouTube: 2023-02-07 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
D
Yeah
they
just
added
Zoom
onto
the
like
conference
rooms,
but
there's
no
way
to
change
your
name.
So
that's
the
name
of
this
conference
room
yeah
that.
B
D
Going
to
be
switching
to
remote
soon,
so
I'll
be
back
back
at
that
life
too.
Oh
nice,
yeah.
E
B
Yourself
to
the
attendees
list,
if
you
have
anything
else,
you
want
to
talk
about
on
the
agenda.
Please
add
it.
There
I've
added
four
topics,
just
from
current
PRS
and
leftovers,
so
yeah.
If
you
have
something
else
you
wanted
to
bring
up.
Please
do
so.
E
B
Cool
well
welcome
everyone,
let's
jump
into
it,
then
I
think
we
can
start
off
by
looking
at
this
PR
to
replace
this
kernel
function
here,
BPF
K
time
so
Eden
I,
don't
know.
If
you
want
to
talk
about
this,
it
looks
good
to
merge.
Just
this
outstanding
question.
B
Okay,
we
had
had
an
outstanding
topic
last
time.
I
think
we
can
say.
B
B
Was
it
like?
Yes,
something
of
course
you
can't
see
anything.
B
D
B
Okay,
actually,
let's
add
the
help
on
it
here.
B
Okay,
cool
next
up
was
the
offsets
for
the
results
for
the
Json.
So
this
looks
good
I
wanted
to
answer
a
question
on
this.
Just
offset
yeah
this
in
Eden
and
anyone
else
can
jump
in
here
as
well,
but
I
mean
these
choose
from
the
existing
version
just
because
these
are
offsets
on
the
field
name.
So
this
is
going
to
change
based
on
the
Go
version,
as
well
as
the
underlying
like
field
structures.
So
it
can
change
from
version
to
version
right.
E
F
E
The
reason
we
have
this
type,
because
otherwise,
if
version
of
go
is
not
changing
and
their
structure
is
also
not
changing.
It's
this
option.
Shouldn't
change
in
my
opinion,
is.
E
F
F
Just
like
I
wrote
it
in
the
description
in
the
pull
request.
It's
just.
F
General
to
file
that
I
ran
and
like
with
the
offset
of
the
tracker
tool.
So
just
because
there
is
a
new
version,
I
think
we
have
like
a
a
good
automated
way
to
to
basically
update
this
file
periodically
I
just
wanted
to
have
a
new
version.
E
B
Yeah
and
on
that
note,
I
also
created
an
issue
to
track
this.
Currently
this
is
done
manually
Mike
pointed
out
that
or
Damian
no,
it
is
Mike.
Okay
got
start
sorry,
GitHub
Haley
handles
I
was
pointing
out
that,
like
it
may
be
possible
to
do
this
at
runtime
as
well.
So
I
think
this
task
could
be
for
somebody
if
they
want
to
look
into
generating
these
as
startup
or
something
like
that.
Yeah
I
think.
D
That's
yeah
I
could
actually,
if
you
want
to
assign
that
to
me,
I
could
actually
take
that
okay
perfect,
since
it
was
my
idea,
I
guess.
B
Yeah
I
think
that's
a
that's
a
great
suggestion.
So
then
we
would
just
have
to
skip
this,
which
would
be
even
more
concise
as
well
so
I'll.
D
Start
out
looking
into
like
the
odd
automating,
the
update,
so
do
you
want?
Do
you
think
that,
like
a
GitHub
bot
that
does
this
periodically
would
work
or
have
that
triggered
on
like
a
go
release
or
I?
Guess
part
of
defining?
This
would
be
scoping
that
out
right.
B
F
E
B
Of
those
changes
so
like
that
might
be
too
complicated,
like
I
I,
feel
like
we
could
do
a
similar
time
frame
here
as
like,
and
a
lot
of
other
repos
that
I
managed
it's
like.
We
just
do
like
dependabots
on
like
Sunday
or
something
like
that.
I
don't
know.
If
there's
any
way,
you
can
build
the
automation
to
just
be
like.
If
there's
no
changes,
then
it
won't
create
a
PR,
and
if
there
are
changes,
just
create
a
PR.
You
know
once
a
week
or
something
like
that.
Okay,.
B
It
still
needs
human
review
yeah,
and
usually
these
are
it's
kind
of
like
the
depend
about
PR's
I'm,
guessing
where
it's
like
we're
pretty
relaxed
and
like
one
person
should
be
able
to
review
it
and
merge
it
like
I.
Don't
think
it
needs
to
be
like
a
full
consensus
on
that
one
given,
especially
since
the
Bots
can
be
running
it.
We
know
the
the
formula
they're
going
to
be
using
so
yeah.
B
Next,
up
on
the
agenda
was
the
asset
tracker
itself
code,
so
yeah.
This
is
going
to
be
something
that
Mike
is
going
to
need
for
this.
B
It's
gonna
be
hard
to
run
it.
So
there's
a
lot
of
suggestions
in
this
I
didn't
know.
If
anybody
wanted
to
touch
base.
F
Yeah,
it's
just
a
copy
paste
from
the
from
my
repository
to
this
one
like
it's
not
already
pretty
cold,
but
it
does
the
job.
Basically,
what's
this
opposite
tracker
thing
do
is
generate
these
Json
files
that
we
just
talked
about
it
does
for
like
it
has
a
main
function,
where
you
specify
all
the
relevant
structures
and
the
builds
that
you're
interested
in
tracking
and
basically
downloads
for
every
every
open
subscribers
that
you
specified
it
downloads
all
the
relevant
versions.
F
It
creates
this
dummy
go
program
that
embeds
this
Library
into
it,
and
then
there
is
this
thing
called
the
dwarf
symbols
which
is
like
debug
symbols.
So
it
looks
on
the
compiled
binary
and
basically
extract
what
is
the
current
offset
for
this
specific
library
for
this
specific
version,
and
it
does
it
for
every
version
and
it
does
something
pretty
similar
for
for
gold
standard
Library
as
well,
so
basically
just
a
Loops.
F
This
covers
on
the
relevant
measurements,
compile
dummy
application
with
this
version
and
observe
the
debug
symbols
and
generate
these
Json
files.
So
that's
like
the
general
overview
of
how
these
two
works.
There's
probably
a
lot
of
film
from
Improvement.
In
this
Tool,
but
like
they're,
just
like
the
first
step,
I,
don't
know
if
we
want
to
improve
this
code
in
this
point,
request
that
we
want
to
just
like.
Have
it
in
this
expository
and
type
start
to
discuss
it
on
another
podcast.
B
Yeah,
that's
a
that's
kind
of
my
question
as
well.
I
think
that,
like
Dinesh
asks
a
question
of
like
the
foul
path.
If
it
could
be
configurable
I
think
that's
a
great
thing.
President.
You
also
talk
about
like
configuration
of
Json
and
other,
like
improvements
here.
I
think
if
there's
like
I
I
would
love
it
if
it's
configurable,
but
I
also
think
this
could
get
merged
without
it
being
configurable
and
like
a
lot
of
these
details
just
so
that
we
could
iterate
on
it.
B
In
fact,
actually
this
looks
like
a
really
great
thing
to
just
build
a
bunch
of
issues
from
and
say,
like
you
know,
here's
a
really
small
thing
like
go:
make
this
file
path,
configurable
or
something
like
that,
because
then
it
could
be.
You
know
additional
PR's,
that's
my
perspective
on
it,
especially
since
Mike's
going
to
be
needing
something
like
this
for
this
next
task
to
try
to
get
this
merged
soon,
but
I'd
like
to
hear
other
people's
opinions
on
this
actually.
A
I
agree
with
that,
like
let's
merge
this
in
I
think
we
have
been
putting
it
in
on
all
the
smaller
things.
If
this
once
this
gets
much,
we
can
start
doing
some
smaller
peers,
and
we
can
also
get
familiar
with
the
code
which
kills
us
the
ability
to
iterate
as
well
right.
There
are
a
whole
bunch
of
things
we
can
improve
here,
like
the
Json
blob
is
too
big
like,
even
if
it
is
offset,
is
safe.
It
just
keeps
repeating,
like
yeah.
B
I
do
have
a
question,
though,
about
prizek
your
questions
about
tuning
further
in
cases
of
error
in
defer
statements
like
if
these
are
just
like
outright
bugs,
then
maybe
we
should
address
them
at
this
point.
B
So
maybe
I'll
ask
you
like
what
are
your
considered?
Should
we
merge
this
now
or
do
you
want
to
address
these
issues
before
this
gets
merged?.
B
All
right
that
sounds
good,
so,
if
that's
the
case,
would
you
both
go
and
give
this
an
approval
or,
if
you
find
it
like
I'm
guessing
you've
looked
through
this
whole
thing,
if
you
find
things
that
are
like,
we
probably
don't
want
to
merge
this
without
these
fixes
include
those
but
otherwise
for
the
open
issues
or
the
open
comments
that
you
have.
B
Could
you
create
issues
for
those
to
track
the
the
work
that
we
want
to
do
after
the
facts,
because
I
think
these
are
great
issues
to
split
up
and
help.
F
B
Okay
back
to
this
okay,
then
next
up
on
the
agenda
and
also
really
similar
to
that
conversation
we
were
just
having
is
this
still
needs
review?
This
instrument
implementation,
so
Dinesh
I,
know
that
you've
gone
through
this
I
haven't
read
their
through
your
reviews,
but
it
looks
like
there's
a
lot
of
things
that
have
been
addressed
as
well.
I
didn't
know
if
you've
had
more
time
to
take
a
look
at
it.
Yeah.
A
B
I
do
think
you
have
the
right
approach
as
well.
I
think
we
should
probably
try
to
take
the
same
approach
on
this
PR,
as
we
just
talked
about
with
the
the
donation
proposal
for
the
offset
generator,
I
I.
B
Think
that
there's
a
great
use-
and
maybe
just
trying
to
run
this
and
see
if
it
works
and
then
also
maybe
do
some
high
level
like
issues
I
I've
tried
to
go
through
this
like
three
times
now
and
like
there's
just
a
lot
of
code,
and
so
I
want
to
get
this
merged
because
it's
been
sitting
there
since
so
that's
we're
coming
up
on
a
month
next
week
so
like
I,
think
that's
something
that
we
just
try
to
prioritize
I
didn't
know.
If
anybody
else
has
any
opinions
on
that.
A
Yeah
I
think,
if
it
is,
let
me
run
I
think
I
was
running
it
in
the
wrong
manner.
So,
if
I'm,
able
to
run
in
a
basic
issues
or
address
I
can
give
an
approval,
but
I
think
it
might
need
an
approval
from
you
before
it
can
get
yeah.
B
And
I
think
I
think
what
I'll
do
as
well
is
yeah
I'll
try
to
review
it
again
the,
but
the
idea
is
that
I
think
that
I'll
try
to
capture
similar
to
what
you
all
have
done
for
the
other
PR
any
issues
that
I
think
we
can
fix
afterwards.
As
you
know,
comments
which
we
can
create
issues
from
because
again,
like
I,
think
this
is
something
that
we
could.
We
could
yeah
I,
don't
want
to
just
sit
here
for
the
next
month
either.
B
E
E
I
fixed
one
problem
that
Dinesh
mentioned,
so
the
second
parameter
should
be
a
directory,
not
a
file
and
so
I.
Am
it
a
message
that
if
someone
will
put
a
file
there,
I
will
have
it
a
mess
error
message
in
this
case,
but
anyway,
I
I
was
expecting
that
we
will
go
the
same
approach
as
with
this
ebpf.
So
we
will
merge
it
as
soon
as
possible
and
then,
as
you
said,
we
will
start
working
on
fixing
issues.
So
that
was
my
general
idea.
B
Yeah
I
agree:
let's,
let's
do
that.
Let's
take
that
I'll
try
to
prioritize
this
again
I'm
trying
to
get
this
metrics
SDK,
stuff
and
other
things
that
go.
It
seems
to
always
take
up
my
time,
but
I
would
I'll
try
to
prioritize
this
again
and
Dinesh
says
he's
gonna.
Take
a
look
at
it
too.
I
think
I
think
with
those
two
approvals
actually
I
don't
know
if
dinesha's
approval
would.
B
Yeah,
we
need
to
fix
that
somehow:
okay,
the
Aaron's.
B
As
well,
but
he
can,
he
can
take
a
look
at
this
as
well.
Man,
yeah
I,
there's
a
lot
of
work
there
to
do
we'll
get
it
all
worked
out.
It's
gonna
take
a
little
bit
of
time.
B
Okay,
cool,
so
we've
definitely
got
some
action
items
on
that
one.
That's
the
last
of
the
talks
I
had
for
the
agenda
for
today.
I
will
pause
here.
Let
anybody
else
jump
in
if
they
have
some
other
ideas
or
other
topics.
They
want
to
talk
about.
A
F
It
I'm
still
exploring
it
it's
it's
something
that
it's
not
very
stable
right
now,
so
they
don't
really
have
a
way
to
show
it
to
you,
but
hopefully
next
meeting
it
will
be
ready
or
maybe
before,
but
like
I'm
still,
not
sure
which
path
I'm
gonna
take
on
this.
So
not
really.
B
Okay,
cool
yeah
I
was
kind
of
interested
on
that
one
as
well,
but
I.
Imagine.
A
A
Should
we
donate
launcher
if
this
is
taking
longer,
because
last
week
you
said
you
wanted
to
finish
this
off.
F
Let
me
try
to
finish
it
by
the
end
of
this
week
and
if
I
see
it,
it
takes
longer,
I
will
just
open
a
couple
requested.
The
launcher.
Is
it
yeah.
A
B
Give
some
people
time
to
go
back
and
review
these
PRS
yeah.
That
sounds
good.
Okay.
Everyone
thanks
for
joining,
see
all
these
secrets
today
or
next
meeting.