►
From YouTube: 2021-06-30 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
Hi
folks,
we
are
just
waiting
for
folks
to
turn.
A
All
right,
I
can,
let
me
share
the
doc.
You
can
folks
just
add
your
topics
here,
as
well
as
I'd
like
to
kind
of
go
through
a
couple
of
updates
on
my.
A
A
Anthony
I
added
your
name
on
the
prw
compliance
test
update.
Can
you
just
post
a
current
snapshot
whenever
you
can.
B
Sure
I'll
give
those
another
one
thanks,
don't
believe
anything
will
have
changed
since
last
week,
but
now
yeah.
A
A
Okay,
I
think
we
can
get
started.
I
don't
see
a
lot
of
topics
on
the
on
the
agenda
today,
so
maybe
we
can.
If
folks
have
questions
you
know
again,
please
bring
it
up,
but.
A
Again,
I
think
that
grace
there
was
I'll.
Maybe
I
should
just
go
through
the
open
prs.
First,
that's
something
that
we
have
been
tracking
in
the
collector
here.
So
if
you
have,
I
know
grace
your
pr
is
not
merged
yet
and
bogdan
said:
he'd
take
a
look
at
it
and
it's
already
been
reviewed,
so
it
should
be
merged
today,
hopefully,.
A
C
Yeah
so
there's
some
feedback.
I
still
need
to
address
I'll,
take
a
look
at
it
and
it's
like
a
problem
with
the
the
way
that
prometheus
sets
up
like
uses
one
of
the
endpoint
options
in
the
test.
So
I
need
to
check
with
tigran
how
we
want
to
go
about
that.
D
It
had
failing
tests
yeah,
but
look
back
into
this
okay,
yeah
yeah,
I'm
abroad,
yeah.
I'm
preparing
to
come
back
to
the
us.
A
No
worries
no
worries
again.
I
think
it's
all
work
in
progress,
so
I
think
there
are
just
some
tests
failing
also
in
there
again,
we've
got
to
fix
these
tests
because
they
failed
quite
randomly
also
all
right.
So,
okay
thanks.
So
I
think
when
we
wait
for
anthony's
update
on
the
compliance
tests
being
run,
I
think
there's
no,
not
much
change
because
of
just
you
know
the
last
pr
not
being
merged
yet
and
with
that.
A
I
think
it
should
complete
at
least
the
compliance
tests
all
passing,
but
that
said,
you
know
we
are
kind
of
also
looking
at
getting
the
collector
to
be
tracing
stable
and
doing
a
release
in
july.
For
that
there
are
clear
backlogs
at
this
point
that
we
are
tracking
on
the
collector
and
and
the
reason
I
bring
that
up
here
is
because
I've
also
kick-started
the
planning
for
the
metrics
work
that
needs
to
be
done
for
heading
towards
stable
and,
of
course,
prometheus's.
A
Stability
is
a
big
part
of
that
right.
So
the
prometheus
pipeline
stability-
and
there
are
a
couple
of
interesting
items
that
you
can
look
at
in
phase
two.
Let's
see
I
can
share
my
my
screen,
there's
a
couple
of
interesting
discussions
ongoing.
A
Let
me
just
share
my
screen
and
just
walk
through
it
and
again
would
like
love
to
get
your
feedback.
I'm
building
this
out
as
I
work
through
it.
So
again,
david
emmanuel
anthony
all
of
you
guys.
You
know
bro
grace
everybody.
Please
take
a
look
at
it.
There
are
a
couple
of
interesting
items,
as
you
can
see
here.
A
Definitely
the
interest
in
reducing
or
rewriting
the
prometheus
receiver,
so
that
it
is
focused
on
really
scraping
in
a
reliable
and
scalable
way
and
and
again
there
are
a
whole
bunch
of
issues
that
folks
have
filed
over
time.
We've
also
been
tracking
that
in
the
prometheus
work
group,
we
will,
I
you
know,
plan
to
go
through
that
in
care.
A
You
know
in
depth
and
make
sure
that
all
the
areas
are
captured
but
also
doing
a
design
dock
formal
design,
dock
walking
through
that,
with
everyone's
help,
building
that
out
and
then,
of
course,
implementing
a
new
receiver.
Similarly,
there's
also
a
discussion
about
separating
out
the
service
discovery.
A
You
know
as
an
general
component
for
the
collector,
so
I'd
like
to
get
you
know
again,
everyone's
thoughts
on
that
you
know
and
and
their
pros
and
cons
in
doing
that.
So
again,
this
is
moving
towards
you
know
what
does
the
collector
do
in
general
and
what
does
the
prometheus
pipeline
you
know
have
specifically
which
needs
to
be
stable
and
which
needs
to
be
fully
functional
for
all
the
use
cases?
A
Similarly,
you
know
the
removal
of
the
open
census
dependencies,
for
you
know
bugs
that
have
already
been
open,
or
you
know,
issues
that
need
to
be
addressed.
These
are
some
of
the
areas
that
I
just
wanted
to
call
out,
because
that
will
affect
the
way
that
you
know
we
are
actually
our
components
are
scraping
and
discovering
and
discovering,
scraping
and
and.
A
So
these
are
you
know,
items
in
the
second
part
of
the
roadmap
that
that
have
been
discussed
so
far
and
bogdan
and
tigran,
and
I
have
been
iterating
on
this
so
that
you
know
we
can
at
least
create
an
initial
list,
and
that
of
course
tune
this,
as
we
begin
work
towards
metrics
ga
also
other
items
that
need
to
be
done
before
that
we'll
cover
this
in
the
you
know,
briefly
in
the
collector's
sake
today,
also,
but
just
just
for
your
visibility
again
there
there
are
several
dependencies
that
will
need
to
be
done
for
the
collector
in
order
to
have
fully
functional
otlp
latest
version
compliant
implementations
for
the
collective
core.
A
Now
contrib
is
not
in
here
right
now
I
will
itemize
the
contrib
components
as
we
go
through
them
one
by
one.
This
is
just
the
framework
you
know.
A
I
just
started
pulling
this
together
earlier
this
week,
so
just
just
for
your
knowledge,
you
know
that,
as
you
see
other
components
that
need
to
be
done-
and
you
know
you
feel
that
it-
we
have
certain
areas
that
we've
already
targeted
in
our
prometheus
work
group
that
we
have
in
phase
2
and
that
will
align
with
these
milestones
that
we
are
trying
to
achieve
with
the
metrics
ga
roadmap.
A
Anthony
did
you
have
an
update,
no
change
right
next,
since
next
last
week,
no
change
yeah,
okay
cool,
so
we
thought
all
right.
Any
other
concerns
folks
have.
I
know
that
I
think
vishwa.
You
had
reported
some
instability
with
the
collective
build
right
now,
for
did
that.
E
Get
solved
no,
I
just
took
the
latest
bits.
E
Just
random
crashes
that
I
see
time
to
time
yeah
I
just
posted
some
stacks.
A
Yeah
thanks
thanks
for
doing
that
and
try
to.
I
think,
because
I
was
looking
at
your
issue
yesterday,
but
yeah
it's
just
random
you're
not
being
able
to
generate
the
exact
use.
E
Cases
yeah,
for
example,.
E
Like
until
now,
no
crashes
seems
to
be
some
data
pattern
looks.
A
A
Any
other
questions
I
think
there
was
also
another
item
about
redesigning
the
collector
metrics
processor
and
I
think
it's
not
a
directly
related.
You
know
to
prometheus
necessarily
but
rahan.
I
know
you
have
been
working
on
the
metrics
processors,
so
that's
something
that
also
will
get
refactored
in.
F
Yeah,
I
think
all
of
our
processors
will
be
combined
in
some
common
processors,
yeah.
A
F
Yeah,
I
am
playing
on
that
maybe
yeah
I
I'm
not
sure.
If
that's
related
to
our
prometheus
but
yeah,
we.
A
A
D
A
Julian
was
there
any
prometheus
related
talks
or
anything
that
you
guys
wanted
to
share?
I
know
richard
was
mentioning
that
you
did
a
pretty
cool
set
of
presentations
last
week.
A
That
was
the
monthly
presentations
you
do
right
and.
G
We
had
a
deaf
submit
yes,
but
what
I
want
to
say
is
that
we
will
be
releasing
this
week.
Bug
fix
release
for
the
httpsd
so
that
it
will
be
pointed
to
the
28.1.
So.
F
G
A
Wonderful,
that's
that's
a
good
bug
to
discover.
A
Do
you
know
when,
like
middle
of
the
week,
usually
right.
G
Well,
no
middle
of
the
week
is
the
major
races,
but
this
is
a
bug
fix
release
which
should
come
tomorrow
or
on
friday.
Maximum
okay.
A
A
Thank
you
for
that
anything
else.
Before
we
wrap
up,
I
think
everybody
is
pretty
much
deep
in
the
middle
of
doing
a
lot
of
work.
F
So
a
little
one
last
thing:
sorry
yeah.
A
F
Yeah
so
for
the
prometheus
receiver.
So,
according
to
the
status
like,
is
it
ready
for
like
using
in
production
like?
Is
it
in
ga
the
prometheus
receiver?
We
had
a
plan
to
rewrite
a
punch
of
stuff,
and
I
think
we
have
a
plan
to
make
it
like
kind
of
tag
it
as
a
stable,
if
not
like
in
some
way,
so
that,
like
we
can
use
it
in
production
system
also.
A
So
the
prometheus
receiver
is,
you
know
what
we
were
aiming
with.
The
first
phase
was
that
to
make
sure
that
the
remote
right
interface
and
and
it
meets
all
the
compliance
and
passes
all
the
compliance
tests
right
and
that
was
kind
of
our
objective,
with
all
the
fixes
that
we
have
made.
That
said,
it
is
not
going
to
be
marked
as
stable
right
now,
because
we
still
have
work
to
be
done.
We
will
definitely
communicate.
A
You
know
everything
that's
been
implemented
so
far,
but
it
will
still
be
available.
As
you
know,
it
won't
be
marked
stable,
it'll,
be
available
in
in
the
next
upcoming
release,
but
metrics
in
general,
all
the
components
will
not
be
marked
stable
until
metrics
is
done.
A
We'll
definitely
communicate,
you
know
what's
been
completed,
feature
completeness
as
well
as
the
clear
you
know:
the
prometheus,
remote
right
exporter
and
the
whole
pipeline
passing
the
compliance
tests
and
and
the
receiver
changes,
as
well
as
the
some
of
the
other
operator
and
additional
changes
that
we
have
been
making
in
order
for
deployments
to
support
deployments.
Okay,.
A
Exactly
so,
that's
definitely,
you
know
the
objective
and
you
know
as
as
initially
the
plan
is
by
next
month.
That
is
july
starts
tomorrow,
end
of
july
the
collector
will
do
a
release
which
will
have
tracing
components
stable
for
core,
but
metrics
will
stabilize
once
phase
one
and
phase
two
are
done.
A
I'm
talking
only
talking
about
the
collector,
the
the
sdk
will,
the
api
is
already
stable
and
and
the
sdk
is
being
in
development
right
now.
As
you
know,
riley
is
leading
that
effort,
and
that
will
land
in,
I
think
at
the
same
time,
targeted
foggest
as
as
the
collector
picks
up
steam.
Also.
E
Okay,
so
we
we
anticipate
the
collector
metric
site
to
become
stable
in
august.