►
From YouTube: 2021-11-03 meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
C
Okay,
all
right,
I
think,
there's
also
like
a
bunch
of
other
seas
that,
like
there's
a
client,
instrumentation
scene
that
started
last
week.
It's
like
at
8
30.
B
A
Well,
I
guess
we'll
get
started,
no
point
in
waiting
if
we're
not
sure
they're
coming.
A
Yeah
bart
says
he's
about
to
join,
so
the
first
thing
that
I
want
to
talk
about
is
just
the
the
metrics
api
work.
This
is
going
pretty
well
particularly
legendicus,
who
is
in
india,
so
doesn't
join
these
meetings,
but
he's
been
doing
a
ton
of
work
and
we've
been
moving
right
along
with
the
api.
We
only
have
a
few
to
do
tasks
and
they're
fairly
small.
A
I
opened
a
draft
pr
because
it
only
updates
the
api
and
I
need
to
update
the
sdk
also,
but
I
didn't
have
time
to
do
that
before
the
meeting
today,
so
I
opened
it
as
a
draft
just
so
that
people
would
have
something
to
look
at,
but
that's
where
we're
at
for
the
api
in
terms
of
the
sdk
I
started.
A
A
Oh
okay,
yeah
in
terms
of
the
sdk
I
started
creating
some
issues
for
the
sdk
updates.
A
A
A
A
A
A
That's
the
the
metric
reader
interface
handles
what
on
the
trace
side,
I
guess
we
would
call
the
the
span
processor,
but
it
handles
collecting
all
the
metrics
from
the
sdk
and
sending
them
to
an
exporter,
and
I
think
that
this
is
going
to
be
sort
of
a
big
piece
of
work,
although
I'm
not
entirely
sure
it
may
be
similar
enough
to
what
we
already
have.
A
A
That
does
the
metrics
collection,
but
I
would
definitely
appreciate
help
breaking
up
some
of
these
issues.
I
just
created
them
this
morning,
so
I
don't
really
have
that
much
to
say
about
them.
None
of
them
are
assigned
or
anything
like
that.
A
A
But
that's
really
all
I
have
today.
I
didn't
have
anything
other
than
metrics
on
the
agenda.
Is
there
any
any
questions
anyone
has
or
anything
that
they
would
like
to
to
bring
up.
B
A
So,
okay,
I
mean
I
I
commented
on
this
earlier.
Obviously,
ideally,
these
would
be
metrics
I
assume
right
is,
is
what
you're
you're
looking
for.
B
I
think
so
yeah,
maybe
events
or
I
mean
logs
or
logs.
Okay,
the
ram
zig
is
going
to
the
direction
that
everything
will
be
long.
That's
what
most
people
want,
but
that's
under
discussion
still,
but
then.
A
Yeah,
I
guess
that
kind
of
falls
into
the
category
of
event
where
you
could
kind
of
describe
it
using
a
log
or
a
metric,
or
maybe
a
log,
that's
tied
to
a
metric.
I
guess
or
something
like
that,.
A
Yeah,
I
mean
it's
up
to
you.
That's
sort
of
what
the
contributory
bow
is
for
is
to
be
able
to
have
these
sorts
of
experiments.
A
If
you
make
it
clear
in
the
readme
that
that
it's
experimental
and
unstable
and
sort
of
describe
the
the
caveats
involved,
I
don't
see
a
problem
with
it.
You
know
when,
when
metrics
becomes
available,
which
should
be
fairly
soon,
you
can
move
this
over
to
use
metrics
or
if
you'd,
rather,
you
can
just
wait
and
implement
it.
Then,
in
terms
of
logs,
I
can't
I
have
no
idea
when
logs
will
be
available
in
js.
A
Stable
for
the
spec
yeah,
okay,
do
you
know
which
languages
they're
prototyping.
A
Yeah,
I
I
know
very
little
about
logs
too,
so
I
I
can't
obviously
promise
any
timelines,
because
I'm
not
not
that
up
to
date
on
the
logging
spec
it
may
be
further,
along
than
I
thought.
I
also
don't
have
any
idea
how
much
work
it
will
be
to
implement
it.
A
A
Okay,
so
then,
if
that's
the
case,
it'll
be
up
to
you
now,
if
you
don't
want
to
take
ownership
of
the
package,
then
I
think
we
we
would
maybe
have
more
of
an
issue
with
it,
because
then
it
would
have
to
be
up
to
someone
else
to
maintain
it.
We'd
have
to
find
an
owner.
That
would
be.
B
A
D
B
A
B
B
And
if
you
like
enable
but
for
example,
for
document
load,
if
you
re-enable,
if
you
re-enable
it,
then
you
get
double
the
spend
for
what
we
currently
just
in
the
config
set,
enabled
or
enabled
false
at
the
start.
So
the
auto
registration
will
enable
it
the
first
time
for
all
web
things,
but
I
think
it's
only
a
problem
for
like
document
load
like
a
problem
problem.
It
happens
for
all
web
instrumentations.
B
B
B
B
A
B
E
But
this
this
is
the
different
issue,
then
the
pull
request
that
is
here-
and
this
is
about
the
new.
B
E
E
But
I'm
wondering
if
you
want
really
to
implement
the
matrix
you
might
have
to
look
because
the
metrics
I
mean
we
kind
of
have
metrics
right.
They
might
change,
but
maybe
not
so
much
so
unless
you
need
really
like
the
most
basic
metrics,
I
think
you
should
be
able
to
to
do
something
still
so
like.
I
know
if
you
depends
what
kind
of
metrics
do
you
need,
but
if
you
need
like
a
very
typical
one,
I
I
think
you
could
already
start
experimenting
with
this.
One.
B
B
E
B
A
A
The
api
is
is
moving
along
well
with
the
sdk.
So
far
nobody
has
started
to
work
on
like
I
said.
I
only
created
those
issues
this
morning,
so
please
take
a
look
at
them
if
any
of
them
look
like
something
you'd
like
to
handle.
Please
just
comment
on
them
or
assign
yourself.
If
you
have
permission
to
do
that,
if
you
don't
add
a
comment,
and
I
will
assign
you
and
right
now,
metrics
is
is,
is
my
priority
at
least.
A
Obviously
none
of
you
work
for
me,
but
metrics
is
my
priority,
so
I
would
appreciate
it
if
if
people
could
help
out
with
that,
when
they
have
time,
if
we
don't
have
anything
else,
then
I
guess
I'll
give
you
guys.
E
A
Oh
okay,
I'm
I'm
sorry
to
hear
that.
Will
you
be
still
working
on
open,
telemetry.
E
I
mean
not
really
I
mean
so
definitely
step
down
from
the
maintainer,
so
you
won't
have
time
for
for
that.
But
as
an
improvement,
you
know
occasionally
yeah.
A
C
A
Definitely
still
keep
your
approver
status.
I
think
that's
the
same
thing
we
did
when
when
mayor
stepped
down
as
maintainer,
we
left
him
as
an
approver
for
a
long
time
and
yeah,
we'll
we'll
see
how
it
goes,
we're
sorry
to
lose.
You,
though,.
A
Yeah,
well,
I
guess
good
luck
to
you
on
whatever
it
is
that
that
you're
you're
moving
on
to
you,
said
you're
leaving
lightsab
to
do
something
else.
Yes,
okay!
Well
best
of
luck
to
you
and
you
know.
Hopefully
you
can
still
stick
around
a
little
bit.
You've
been
really
valuable
to
us,
so
we
appreciate.
D
A
Well,
thank
you
everybody
for
your
time
and
we
will
talk
to
you
next
week.