►
From YouTube: 2021-09-14 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).
A
Hello,
I
think
we
can
start
in
another
minute
just
to
give
some
time
for
anyone
else
to
join
hello,
hey.
A
A
We
did
release
the
alpha
3
yesterday
and
there
were
a
lot
of
discussions
about
the
batch
api
from
the
tracing
world.
So
after,
like
benchmarking,
we
settled
down
to
using
it
and
for
metric
points,
which
is
the
individual
time
series.
We
invented
a
new
struct
iterator.
I
think
we
called
it
batch
metric
point.
There
might
be
like
some
revisions,
but
that's
the
current
design
and
all
the
exporters
are
modified.
With
this
approach.
A
The
performance
looks
good
now
seeing
some
noise.
Okay,
let
me
find
who
that
is.
A
Okay,
how
do
I
mute?
I
don't
know,
okay,
need
it
thanks,
yeah,
so
puff.
I
have
added
like
puff
text
as
well,
so
it
should
be
like
much
better
than
the
alpha
one
or
four
two
yeah
and
I'm
hoping
to
release
alpha
4
like
as
soon
as
this
week.
We
should
add
support
for
multiple
metric
readers,
because
right
now
we
only
support
one.
A
A
So
we
should
be
able
to
call
this
a
beta
release,
yeah
and
like
we'll,
get
more
disciplined
starting
with
beta,
because
we
were
not
very
organized
about
keeping
track
of
issues
because
it
was
just
alpha
so
next
week
onwards
we'll
create
issues
and
assign
milestones
to
it
and
reach
them
as
blocking
versus
not
blocking.
A
A
I
think
we
only
have
like
http,
client
and
asp.net
core,
so
we
have
opportunities
to
add
more
instrumentation
and
we
have
a
lot
of
need
for
tests.
I
think
I
did
like
couple
of
stress
tests
and
couple
of
multi-threading
tests
and
michael
helped
improve
it,
but
I
think
we
really
need
more
tests
to
cover
all
the
instruments.
B
A
Yeah,
so
we
basically
pretty
much
needed
for
instruments,
so
not
just
wage,
so
I'll
assign
you
this
issue
once
I
create
one
and
you
can
work
on
it
yeah.
It
should
be
very
similar
to
the
counter
one
but
yeah.
We
need
to
really
stress
it
and
do
it
from
multiple
threads
at
the
same
time
yeah,
and
we
also
need
test
for
prometheus.
It's.
I
just
realized
that
there
is
no
test
project
itself
for
prometheus,
so
god
removed
like
last
year
when
we
removed
the
prometheus
itself
and
when
we
restructed
it,
there
was
no
test.
A
So
as
of
now,
we
are
running
without
any
unit
tests,
but
it
should
be
fine
for
alpha,
but
next
week,
when
we
switch
gears
to
beta,
we
want
to
have
some
coverage
here.
So
if
anyone
wants
to
volunteer
for
that,
please
let
me
know
otherwise
I'll
take
it
myself,
yeah.
There
are
no
other
updates
here.
I
would
I
mean
if
there
are
any
questions
I
can
take
it
now.
Otherwise
we
can
meet
next
week.
B
For
the
alpha
four
here,
this
is
like
the
exporter
tweaks,
the
changing
it
to
use
like
the
the
batch
metric
point.
Reference
is
that.
A
Key
thing
I
want
is
the
multiple
reader
thing
and
there
are
like
already
work
in
progress
vr
for
further
tweaks
to
the
exporter
like,
for
example,
like
this
vr,
is
adding
more
attributes
to
the
exporter
to
determine
whether
it's
a
cool
or
push.
We
added
like
similar
thing
for
aggregation
terminality
yesterday,
so
these
are
like
what
I
planned
for
alpha
four
and
the
hope
is
after
alpha.
Four,
the
exporter
interface
should
be
like
fairly
stable.
There
shouldn't
be
like
any.
A
I
mean
we
might
still
provide
like
more
helper
methods,
but
conceptually
what
it
sees
from
a
memory
perspective.
What
is
the
thing
which
it
sees
would
be
stable
and
then,
like
everything
else,
is
now
after
that
it's
just
additional
features.
So
we
are
adding
views.
We
are
adding
like
x
employers.
Then
we
have
to
like
solve
some
issues
here,
but
we
will
come
back
to
it
after
we
reach
the
alpha
4.
C
A
Okay,
yeah,
here's
some
hint
for
you,
so
I
think
so.
This
is
a
prometheus
one.
If
we
go
back
in
time,
we
used
to
have
test
for
prometheus,
so
it
would
be
a
little
bit
tricky
to
find
because
we
went
back
and
forth
on
it
several
times.
I
it's
very
hard
like
there
were.
There
was
a
time
when
we
had
the
metric
tests
for
prometheus.
A
I
remember
like
adding
it
myself,
so
maybe
I
will
find
it
by
searching
for
matrix
trust
just
like
so
just
take
contact
like
we
had
like
matrix
in
our
repo
like
from
day
one
almost
like
day
one,
but
when
we
release
the
tracing
matrix
was
still
considered
experimental,
so
we
pretty
much
removed
it
from
the
main
branch
and
52
metric
so
in
and
then
we
brought
it
back
to
maine
again
like
a
couple
of
months
back
so
somewhere
in
that.
C
I'll
I'll
do
some
digging
I'll
I'll,
find
it
yeah
yeah.
It
should.
A
Be
there
should
be
like
something
like?
I
don't
know
whether
it
was
me
who
wrote
it,
but
someone
lta.
If
you
cannot
find
it
like
you
can
like
me,
I
can
do
some
digging
and
we
should
yeah
it.
A
Maybe
like
one
of
the
pr
which
has
the
yeah.
This
might
be
one
of
it
because
it
seems
to
be
having
a
lot
of
files
changed.
So,
okay,
I
won't
put
your
name,
but
if
you
are
working
on
it
just
like,
let
me
know
so
that
you
won't
have
any
duplicate
efforts.
A
Like
while
you're
here
like,
may
I
ask
you
like:
do
you
have
like
any
like
interest
in
adding
matrix
instrumentation
for
sql.
C
I
I
yeah
actually
yeah
I'll
I'll
I'll,
give
that
a
shot
I'll
give
that
a
shot
as
well
yeah.
A
You
can
take
a
look
at
the
http
and
spinner
code.
That's
where
we
already
have
the
matrix
one.
This
is,
it
should
be
model
like
I
think.
C
I've
tried
I'm
still
reading
through
that
metrics
code,
I'm
much
less
familiar
with
it
than
with
the
tracing
stuff,
so
that'll
be
good.
It'll,
be
a
good
way
to
see.
How
do
we
come
up
with
like
what
are
the
good
metrics
to
even
capture.
A
For
what
you
call
it's
bit
really
experimental.
The
reason
is
these
conventions
were
returned
like
long
back,
so
let
me
see
if
it
has
okay
that
doesn't
look
like
it
has
something
for
database.
A
C
A
But
since
instrumentations
are
anyway
not
stable,
we
can
always
keep
changing
it
and
these
semantic
inventions
four
metrics
are
like
really
old.
I
think
it
still
uses
the
old
instruments
we
got
rid
of
it
like
long
back,
so
it
still
uses
the
old
one.
So
this
is
like
in
general,
outdated,
but
it
wouldn't
hurt
us.
A
I
mean
it
wouldn't
hurt
if
we
just
add
like
one
instrumentation
for
sql
client,
just
to
get
the
duration
and
maybe
like
dimensions
like
whether
it
is
successful
or
failure,
or
maybe
the
name
of
the
database
itself
has
two
dimensions.
That
would
be
like
good
and
we
can
always
tweak
it.
So
if
we
just
get
the
framing
ready
like
when,
when
the
spec
eventually
evolves,
it
will
be
easy
for
the
future
folks
to
just
add
to
it
that
makes
sense,
yeah
again
no
pressure.
A
I
I
was
just
hoping
that,
like
the
more
instrumentations
we
have
the
easy
it
is
for
people
to
like
get
started
because
right
now,
the
only
way
you
are
going
to
see
any
matrix
is,
if
you
emit
it
yourself,
but
for
tracing
you
just
like
call
like
add
a
spinner
core
at
http
client.
You
already
see
almost
all
the
things
which
you
want
so
similarly,
if
you
have
a
good
story
for
metrics
by
the
time
we
release
1.2,
that
would
be
great,
but
it's
not
really
critical
for
one
point
to
release.
A
So
if
you
get
time,
go
for
it,
otherwise
it's
totally
fine
cool,
we'll,
try,
yeah
yeah,
nothing
else
to
be
discussed,
so
I
will
end
early
and
rejoined
next
week.
So
thank
you.