►
From YouTube: 2022-02-23 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
A
Given
how
many
people
we
we
have
something?
Finally,
there
we.
B
Actually
get
thoughts
together
as
well.
I
just
want
to
give
a
couple
updates
on
progress
for
the
prometheus
specification.
The.
A
C
B
A
I
have
one
other
thing,
because
that
is,
and
I'm
probably
not
getting
the
name
right.
Sorry
wish
nowhat
is
also
in
the
call.
Is
there
any
progress
on
on
planning
or
anything
regarding
the
promises,
remote
right
receiver,
which
azure
and
aws
wanted
to
tackle.
D
D
Probably
specifying
in
summer,
so
the
one
that
we
are
doing
right
now
is
asian
based
and
the
summer
is
what
we
are
planning
to
tackle.
The
the
premier
case,
server
based
direct
remote
right.
A
D
Yes,
I
think
there
is.
There
is
already
enough
test
cases
to
start
with
that.
We
will
have
to
actually
adhere
to.
You
know
when
we,
you
know,
start
doing
this,
but
if
you,
if
your
question
is
about,
if
we
need
any
help,
yeah
absolutely
absolutely.
A
Okay,
so
once
once
timing
and
and
head
count
and
everything
is
starting
to
solidify-
please
give
it
once
warning,
so
we
can
so
we
can
start
planning.
E
I
might
be
off,
but
I'm
also
new
to
attending
these
calls.
Is
this
the
remote
right
receiver
for
the
open,
telemetry
collector,
or
are
we
talking
about
something
else.
A
We
are
talking
about
testing
receivers
for
prometheus
remote
right
under
the
umbrella
of
prometheus
compliance
test
suite.
So
you
have
a
you,
have
an
end
point
that
is
receiving
stuff
metrics
over
prometheus,
remote,
right
and
testing
that
those
actually
arrive
correctly.
And
yes,
this
also
means
overlap
with
probably
at
least
from
clear,
because
you
need
some
basic
way
to
to
get
those
data
points
out
again.
But
that
is
what
what
we
talked
about.
I
think
it
was
summer
fall
of
last
year.
E
E
D
Yeah,
so
what
we
did
was
see
all
the
compatibility
was
actually
in
the
in
the
exporter.
We
won't
try
to
export
it
in
the
open,
telemetry
connector
and
we
wanted
to
move
all
those
compatibility
to
the
receiver,
because
previously
the
aws
remote
right
exporter
was
more
compliant,
but
actually
any
other
exporters
were
not
a
very
prometheus
remote
right
complaint.
So
we
wanted
to
move
all
those
compliance
to
the
receiver
so
that
it
will
be
compatible.
D
D
And
that
is
the
the
project
that
we
did
last
fall
to
to.
Actually,
you
know
move
the
compliance
test
into
the
receiver,
and
then
we
found
quite
a
bit
of
bugs
and
we
did
that.
E
Again,
dumb
question,
so
this
has
nothing
to
do
with
the
open,
telemetry
collector
right.