►
From YouTube: 2022-10-05 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
B
C
B
D
All
right
I
have
a
fairly
short
agenda
today.
So
if
everybody
has
anything
to
add,
go
ahead
and
add
it
at
the
bottom
but
I
guess
we
can
just
get
started
here.
The
metrics
GA
is
no
change
from
last
week.
D
The
TC
review
is
scheduled,
I
think
Carlos
is
going
to
do
it
for
us.
He
reached
out
just
to
ask
where
he
can
find
like
the
the
various
SDK
packages
and
stuff,
like
that.
I
believe
he's
going
to
start
on
that
review
this
week.
So
yeah
no
change
really
there,
the
after
GA
work.
We
have
still
the
same
items
from
from
last
week:
I
just
organized
them
a
little
bit
here,
Mark
I
know
you
were
working
on
the
Prometheus
exporter.
D
Do
you
have
anything
any
update
here
or
no.
D
And
that's
just
for
the
resource
support
right
right.
C
Yeah
it's
the
resource
support
as
this
target
info
metric,
which
is
supposed
to
be
there
on
export.
D
D
I,
don't
really
have
any
update
from
the
API
merge.
I
didn't
have
a
lot
of
time
to
work
on
that
this
week
the
the
issue
migration
I
think
is
going
to
take
a
while,
just
because
there
is
no
real
stale
bot
and
I
don't
want
to
move
over
super
old,
stale
API
issues,
but
the
the
technical
work
is
basically
done.
It's
a
part
of
the
learning
monorepo.
Now
it's
building
and
running
with
the
rest
of
the
SDK
packages
and
everything
should
work
there.
D
Anybody
have
any
questions
on
on.
What's
going
on
with
the
API
merge
before
we
move
on.
D
D
I
hope
to
finish
that
today
and
I
will
look
into
I
believe
we're
also
having
the
same
problem
with
the
fetch
plugin,
probably
because
the
same
person
wrote
both
of
those
they're
probably
similarly
implemented
so
yeah,
no
real
update
there
other
than
expect
that
PR
to
come
soon.
D
D
Instead
of
using
the
monotonic
clock,
we
would
potentially
run
into
some
scenarios
where
you
could
get
spans
that
don't
make
sense
if
you
have
like
an
ntp
sync
or
something
like
that
during
a
span.
D
But
the
there's
more
discussion
in
the
issue,
but
I
think
some
of
those
problems
are
a
combination
of
not
as
bad
as
we
think
and
not
as
as
fixed
by
using
the
monotonic
clock,
as
we
think,
because
browsers
in
particular,
don't
give
accurate
timings
anyways
in
order
to
prevent
against
fingerprinting
attacks,
and
things
like
that.
D
I
would
encourage
people
to.
Please
read
the
issue
and
and
give
an
opinion
there.
If
you
can
personally
I'm
I'm
leaning
towards
just
using
the
date
interface
for
time,
unless
there's
a
good
reason
that
we
shouldn't.
B
C
So
the
demo
application
seek
is
looking
for
developers
to
add
metrics
to
a
JS
service,
so
there's
actually
two
Services.
So
basically
the
demo
app
for
everybody
that
doesn't
know
is
like
open,
telemetry
demo,
based
on
the
Hipster
shop
example
from
Google,
which
yeah
has
basically
multiple
micro
services
and
they
are
instrumented
with
Hotel
and
they
are
planning
to
release
a
1.0
sometime
around
kubecon
and
yeah.
As
I
already
said,
they
are
looking
for
people
to
add
metrics.
C
So
if
anybody
has
some
cycles
and
wants
to
pick
that
up,
that
would
be
great.
If
not,
then
maybe
I
will
get
around
to
doing
doing
it
as
well,
but
I
think
it
would
be
great
to
Showcase
the
metrics
SDK
as
well
there
as
other
language.
Sdks
are
yeah,
they
are
starting
to
be
more
represented.
C
Go
has
edit
this
and
I.
Think
Carter
mentioned
that
there's
some
other
languages
also
in
the
pipeline.
D
B
C
Yeah,
the
link
there
is
for
the
payment
service,
I,
think
yeah
yeah.
B
C
Not
on
the
road
also
as
far
as
I
know,.
D
Okay,
I
added
this
next
item,
I
wanted
to
ask:
if
there's
anyone
working
on
the
logs
and
events,
SDK
and
exporter
components,
we
had
the
API
emerged
a
couple
weeks
ago
three
weeks
ago,
I
think
now
at
this
point,
but
it's
not
really
usable
without
SDK
components
and
before
I
started
working
on
that
I
wanted
to
know.
If
there's
anybody
that
is
currently
already
working
on
that
or
planning
on
working
on
that
I.
B
Think
Martin
was
he's
actually
out
last
weekend
this
week,
so
he'll
he
should
be
back
next
week,
he's
also
not
full-time
on
Hotel
anymore
as
well,
so
but
I
think
he
had
as
part
of
the
events
API.
He
also
started
something
with
logs
so
with
Santosh.
Isn't
here
T2
you
remember
where
that
was
at
all,
maybe
in
his
own
personal
Ripple,
yeah.
D
Okay,
do
you
have
any
idea
when
he'll
be
back,
he.
B
D
D
Something
in
the
chat
here-
oh
that's,
the
marriage
ranges
yeah
logs
API,
so
the
logs
API
Branch
I,
believe,
is
the
one
that
oh
SDK
I
see.
So
it
looks
like
he
is
working
on
that.
Do
not
merge
all
right.
Thank
you
for
the
update
all
right
in
a
similar
vein.
The
Proto
released
zero.19.0
also
about
three
weeks
ago.
D
I
was
going
to
work
on
that
this
afternoon.
Actually,
but
before
I
did
that
I
wanted
to
make
sure
that
nobody
else
had
started
on
that
or
was
planning
on
working
that
or
on
that
or
anything
along
those
lines
should
be
a
relatively
straightforward
change.
I
think:
okay,
I
guess
just
look
for
that
PR.
Hopefully
this
afternoon.
E
Yeah
I
was
just
going
to
mention
I
think
we
had
this
issue
with
some
of
the
instrumentation
packages
before
and
then
I
think
we
added
a
handful
of
new
packages
to
the
node
instrumentation.
All
I
noticed
that
Mongoose
and
data
loader
seemed
to
it
seemed
like
you
need
to
have
at
least
a
Dev
dependency
on
the
underlying
libraries
in
order
for
the
types
to
compile,
not
sure.
If
anybody
else
has
noticed
this.
D
Yeah
they're
affected
a
few
packages
in
the
past.
I
think
Rano
did
a
lot
of
work.
Vendoring
types
into
the
contrib.
A
Yeah
for
those
buckets
I
just
confirmed
that
the
that
at
least
has
it
I
did
review
it,
but
somehow
missed
that
aspects
in
the
review
Matthew.
What
do
you
think,
maybe
or
anyone
else
thinks
of
removing
the
generic
or
generic
season
from
the
instrumentation
all
together,
because
that
seems
to
be
the
you
know.
A
We
make
the
instrumentation
generic
over
the
the
underlying
package
and
thus
basically
create
a
dependency
most
of
the
time
and
basically
removing
the
dependency
was
mainly
removing
that
mainly
basically
removing
it
from
the
types
from
all
of
the
public
interfaces,
which
kind
of
solves
the
issue.
But
one
of
the
public
interfaces
is
almost
always.
You
know
the
init
function
that
that
is
generic
over
the
package,
that's
being
imported,
and
you
know
I
at
this
time.
I
know
to
avoid
this
adding
the
type
there,
but
it's
actually
a
really
really
on
it's.
It's
like.
A
It's
easy
to
miss
when
definitely
when
you,
especially
when
you're
the
new
developer,
you
you
don't
know
that
that
you
should
avoid
the
types
from
the
public
interfaces,
so
I
would
basically
to
fix
it
all
once
and
for
all
fix
it
in
the
instrumentation
package
itself
and
remove
the
generic
function
or
generic
aspect
of
init
function.
A
D
A
D
Yeah
I
mean
I
I
think
that
having
having
a
generic
with
the
types
was
well
intentioned
and
at
the
time
I
mean
when
we
did
that
it
was,
and
almost
three
years
ago
now
and
typescript
didn't
do
as
much
library
checking
and
stuff
like
that,
so
it
didn't
come
up,
but
as
the
typescript
compiler
gets
more
and
more
intelligent,
I
think
it's
it's
going
to
be
a
problem
forever
now
and
like
turning
off
those
Library
checks
is
not
something.
People
want
to
do.
D
I
think
that
just
removing
that
type
is
probably
probably
the
only
way
to
solve
this
long
term
unless
typescript
adds
some
some
new
features
specifically
around
this
type
of
like
optional
typing,
but
that
seems
unlikely
to
me
and
certainly
not
coming
anytime
soon.
D
That
was
the
last
agenda
item.
We've
only
spent
about
15
minutes.
Anyone
have
anything
that
they
want
to
bring
up
before
we
move
on
to
bug
triage.
B
Okay,
I.
D
Don't
see
active
context,
not
added
to
Telemetry
I
know
that
Florida
has
been
discussing
with
this
user.
I
actually
already
went
through
this.
They
are
trying
to
set
like
attributes
in
context,
and
then
they
expect
them
to
be
on
spans.
This
is
just
them
misunderstanding
how
the
the
SDK
actually
works
at
this
point,
I'm
going
to
say
that
this
is
a
question,
since
it
is
not
a
bug.
D
B
D
That's
it
for
the
main,
repo
and
I
believe
we
got
through
Mo
yeah.
We
got
through
all
of
the
contrib
ones
last
week
it
does
not
look
like
we
have
any
new
ones
right
now,
so.
D
We
have
40
minutes
left
last
chance.
Anyone
want
to
bring
anything
up.
D
Okay,
I
like
a
short
meeting
as
much
as
anyone
else.
So
thanks
everybody
for
your
time
and
I'll
talk
to
you
next
week.