►
From YouTube: 2021-09-01 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,
everybody,
if
you
could
please
add
your
names
to
the
document
and
if
you
have
agenda
items,
please
add
them
and
we
will
get
started
in
a
couple
minutes.
A
A
A
Yesterday,
with
that,
we
have
moved
all
of
the
components
that
are
not
otlp
receivers
and
exporters,
and
I
think
we
kept
a
couple
of
processors
in
the
in
the
court,
but
the
vast
majority
of
components
have
moved
to
the
contrib
repo
and
will
be
managed
there.
That
includes
all
of
the
prometheus
receivers
exporters
and
the
prometheus
remote
right
exporter.
B
There's
a
bug
mentioned
in
slack
this
week
and
I
was
hoping
it
would
get
discussed
and
I
was
going
to
put
it
on
the
agenda.
If
no
one
else
does.
B
Does
anyone
know
which
one
I'm
referring
to?
It
involves
man
values
and
a
regression
in
the
0
30
release
is
raised
on
slack
this
week,
yeah,
but
I'm
actually
debugging
the
same
issue,
so
I
thought
okay
well,
I'd
like
to
hear
about
it,
just
because
a
lolita
tagged
me
in
a
decade
on
this,
because
both
of
us
have
some
involvement
in
hotel
to
prometheus
conversion,
but
this
looks
more
like
a
change
in
the
code
may
have
produced
a
behavior
change
related
to
demand
values.
B
If
no
one
else
does
I,
I
can
leave
it
there,
but
we
could
also
yeah.
A
Anyone
else
know
anything
about
that.
One
emmanuel
was
here:
emmanuel's
been
working
with
the
the
reporter
of
that
issue
over
the
last
day,
trying
to
get
to
the
bottom
of
it.
It
looks
like
the
reporter
has
narrowed
it
down
to
they
suspect,
being
the
the
commit
that
introduced,
stale
markers,
which
is
sent
as
a
man
value
so
yeah.
A
It
does
seem
plausible
that
perhaps
the
handling
of
steel
markers,
which
we
we
know
from
the
other
issue
that
emanuel
is
working
on,
which
is
the
the
fact
that
steel
markers
were
being
emitted
for
all
series,
not
just
the
series
that
were
currently
being
scraped,
that
we
had
some
issues
with
how
we
were
handling
steel
markers.
A
So
I
think
that's
something
that
we
will
need
to
revisit.
He
has
apr
up
to
attempt
to
address
that.
That's
one
of
the
things
that's
on
my
plate
to
review
today,
and
hopefully
we
can
get
that
merged
quickly.
Now
that
we
are
past
the
move
of
components.
B
B
What
do
we
know
when
the
otl
hotel
collector
will
be
on
0.9?
I
suppose
that
was
what
I
assumed
was
a
blocker
first,
I
believe
it
is.
It
is
now
okay,
yeah
that
happened
a
couple
weeks
ago.
I
believe,
oh
fantastic.
So,
yes,
I
think.
As
of
the
0.33
release,
I
think
it
was
on
0.9
okay,
so
that
means
we
should
probably
get
our
acts
together
and
release
otlp
with
that
new
flag
available
for
future
iteration
on
the
collector.
A
B
B
Yeah
that
was
released
may
12th.
We
should.
We
should
take
a
look
at
releasing
a
new
version.
I
think
I
can
put
down
the
reminder
to
follow
up
on
that.
A
Okay,
and
if
there
are
no
other
issues,
I
guess
I
can
take
a
brief
moment
to
introduce.
We
have
eric
shea
and
hunic,
who
are
new
here
at
aws
and
who
will
be
working
with
us.
They've
just
joined
eric
is
a
full-time
engineer
has
joined
our
team
and
hunick
is
an
intern
who
will
be
working
with
us
for
the
next
few
months,
so
welcome
to
the
prometheus
working
group.
This
is
where
we
discuss
issues
related
to
prometheus
and
open
telemetry
interoperability
and
compatibility
and
yeah.