►
From YouTube: 2021-11-24 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).
B
A
Today
it's
gonna
be
probably
reasonably
low
audience
because
of
the
holiday
week.
So
all
right,
let's
bring
up
our
list
again,
I
think
mustafin
did
you
want
us
to
give
a
quick
update
on
the
tests
and
then
we
can
also
have
purosh
giving
an
update.
Can
we
quickly
do
that
for
brian
and
vishwa.
C
Yeah
sure
so,
regarding
the
test
implementations,
we've
been
filing
prs
on
collector
contrib
to
implement
those
tests,
and
most
of
them
have
been
reviewed
internally
in
our
open
audio
repository,
and
we
have
filed
prs
for
those
upstream
and
the
ones
that
are
pending
will,
probably
once
they
are
reviewed,
they
they
will
be
filed
upstream,
and
hopefully
you
can
get
reviews
on
them.
C
I
think
vishwa
and
david
rashford
have
been
helping
out
with
the
reviews
for
the
pr's
that
I've
been
fighting
and
most
of
them
are
good
to
go.
I
have
one
thing
that
I
wanted
to
bring
up
and
it
was
regarding
the
open,
metrics
test
cases
I'll
just
share
my
screen
quickly.
A
A
C
Okay,
so
this
was
a
pr
that
adds
the
open,
metrics
test
cases
that
we
we
are
using
for
the
prometheus
receiver
and
david
had
a
good
like
some
good
feedback
on
it.
So
what
we
saw
what
I
did
in
this
pr
was
basically,
so
let
me
just
show
you
metric,
so
this
is
the
open
metrics
tests
and
the
this
is
like
all
the
data
test
data
that
they
have
so
for
each
test.
C
There
are
some
sort
of
metrics
available,
so
we
basically
cloned
this
test
data
into
our
prometheus
receiver,
test
test
files
and
then
read
the
metrics
data
from
these
files.
Just
so,
we
don't
have
to
make
http
requests
to
get
up
to
get
the
tell
data
from
the
openmetrics
repository,
but
the
thing
that
the
but
the
problem
with
that
is
now
we
need
somewhere
to
sync
the
test
files
from
with
the
open
metrics
repository,
and
this
is
something
that
david
brought
up
like
do.
C
C
So
I
would
appreciate
feedback
on
if
that's
something
you
want
to
do.
A
Report,
what
what
do
you
mean
by
that
the
hotel
so.
D
When
you,
sir
yeah,
when
you
sub
module,
it
will
just
pull
the
files
as
a
part
of
the
action,
get
up
action
and
then
you
will
run
the
test.
So
basically
it's
like
a
sub.
D
A
I
mean
that's
one
idea:
the
other
idea
is
to
actually
have
another
repo
or
use
the
prometheus
for
group
people
to
just
execute
the
tests
and
kind
of
do
a
snapshot
of
the
open,
metrics
tests
or
point
to
them
and
execute
them
in
the
work
group.
Repo.
E
A
On
the
open,
telemetry
side
we
can
say
I
mean
we
can
take
responsibility
for
keeping
it
in
sync
for
sure,
because
it's
just
easier
regarding
you
know
given
access
and
and
roles
and
setup
and
stuff
right,
I
mean
if
we
run
it
on
the
open,
metrics
reapers,
then
I'm
not
sure
whether
we
have
adequate
access
or
you
know
what
the
process
is
there,
because
I
think
again-
and
maybe
you
know
brian-
you
can
give
us
some
advice
there,
that
is
that
even
doable
or
would
you
advise
us
to
run
it
on
a
hotel
repo
and
you
know,
execute
the
open
metrics
tests.
A
Who
would
be
the
right
person
on
the
project?
To
ask?
A
No
agree
that
a
great
agreed,
but
it's
it's
just
that
which
domain
do
we
run
it
and
we'll
we'll
figure
it
out
and
you
know,
but
there
are
need.
I
think
there
are
two
options:
the
third
option
being
in
a
third-party
repo
like
we
could
run
it
on
aws's,
reapers
or
anywhere
else
right.
So
but
I'd
love
to
have
it
either
on
hotel
or
open
metrics.
Whatever
works.
A
C
Agreed,
okay,
yeah
I'll
investigate
this.
For
then,
maybe
file
up
an
issue
file,
an
issue
to
address
this.
If
there's
any
action
items
like
regarding
keeping
those
tests
in
sync.
E
Yeah
sure
so
my
screen
is
visible.
E
E
And
apart
from
that,
these
tests
consist
to
validate
the
honor
time
stamp
currently
for
honor
timestamp.
We
have
a
issue
for
the
counter
metric
that
the
counter
metric
start
time
is
not
consistent
with
the
start
time
of
histogram
and
summary
matrix.
So
basically,
there
is
an
issue
with
the
start.
Timestamp
of
the
counter
matrix
of
this
issue.
E
6405
was
filed
on
the
on
the
collector
contributor
after
that
worked
on
the
metric
and
label
renaming
to
validate
the
whether
the
matrix
are
renamed
as
per
the
configuration
and
also
the
labels.
So
this
test
was
also
filed
is
under
review
on
the
open,
only
wrapper
right
now
and
after
that
there
are
test
cases
to
validate
and
type
metrics.
E
So
this
one
is
also
under
review,
and
apart
from
that,
there
is
one
test
which
is
to
validate
the
non-numerical
values,
whether
they
like
to
validate
the
pass-through
of
non-numerical
values
through
from
this
receiver.
So
there
I
there
is
one
question
that
I
want
you
to
ask
so
like
for
normal
lens
and
infinity
values.
E
What
is
a
valid
test
data,
or
a
use
case
for
prometheus
receiver
to
receive
a
normal
land
or
infinity
values?
So
current
assumption
is
that
a
normal
land
can
be
received
for
a
gauge
metric
or
in
some
quantized
values,
so
just
wanted
to
understand.
If
is
there,
any
additional
use
case
like
for
counters
current
assumption
is
that
it
cannot
be
set
to
nand
because
it
cannot
be
incremented
like.
If
you
have
nan
then
be
increment
by
one,
then
it
would
remain
then.
E
E
Counter
could
have
unmanned
for
prometheus.
B
B
E
B
Same
sort
of
answer
like
in
principle,
all
the
counters
can
get
the
positive
infinity.
I
guess,
if
you
overflow,
or
something
but
yeah
gauge
and
untyped
or
unknown,
would
be
the
only
place.
I
guess
would
make
sense
for
that,
and
I
guess
you
could
also
get
it
for
once
again
upon
hours
of
summaries.
B
F
Hello,
everybody
we
need
to
move
over
to
the
other
due
to
the
other
zoom.
This
is
an
account
that
is
going
to
be
terminated,
we're
moving
to
a
new
system
where
each
site
gets
its
own
meetings.
Here,
I
will
provide
a
link.
F
A
Okay,
I
mean
given
okay,
let's
let's
do
that
because
it's
just
we
are
in
the
midst
of
the
discussion,
so.