►
From YouTube: 2022-09-09 meeting
Description
Instrumentation: Messaging
B
C
I
haven't
been
to
one
of
these
in
about
a
month,
so
if
someone
else
would
wouldn't
mind
sharing,
maybe
we
can
get
started
since
it's
already
three
minutes
in.
A
Okay,
I
can
share
so
I'm
a
triager
in
the
contrib
repo.
Now
so
I've
been
going
through
the
the
issue
backlog.
I
think
I've
made
it
pretty
far.
I've
been
trying
to
keep
up
with
current
issues.
B
A
Okay,
zoom
does
not
seem
happy
right
now.
In
fact,
I
can't
get
out
of
the
screen
share.
A
Okay,
so
I've
gotten
pretty
much
all
of
the
issues
for
the
past
two
weeks,
triaged.
If
we
want,
we
can
start
a
bit
further
back
and
see
if
we
can
potentially
close
some
issues,
we
could
review
a
couple
of
the
issues.
I've
tried
to
make
sure
I've
got
it
right.
A
I
think
I'm
mostly
relying
on
input
here
in
the
past
two
months
that
I've
been
here.
We've
mostly
just
been
keeping
up
with
recent
issues,
but
since
I've
gotten
those
triaged
already,
we
might
want
to
take
it.
C
I'd
say:
let's
just
start
further
back.
I
guess.
B
A
Yep,
we
might
want
to
consider
an
actual
like
triage
label
just
to
make
that
a
little
bit
more
explicit
in
the
future,
but
up
until
now,
it
mostly
relies
on
simply
having
the
appropriate
labels,
whether
it's
a
priority
or
maybe
a
question
or
new
component
labels.
If
those
are
appropriate.
A
Makes
sense,
I
will
yeah
note
that
down
I'll
look
at
adding
that
and
then
see
what
issues
I
can
add
it
to
hopefully
give
us
a
better
view.
Sure,
okay.
A
It
would
also
be
worth
it
to
discuss
it
with
tyler,
in
fact,
maybe
I'll
open
an
issue
on
that,
just
to
make
sure
everyone
can
offer
some
input,
but
he's
mostly
been
kind
of
leading
the
triage
effort
during
the
past
two
months
anyway.
B
Because
you
could,
you
could
at
least
trim
your
query
by
saying
I
guess,
which
I
think
basically
want
and
not
a
priority
tag.
Maybe,
but
I
don't
know
it
may
not
be
worth
writing
that
query
right
now,.
C
B
A
A
A
B
A
As
for
any
other
labels,
it's
really
hard
to
say
that
it
it's
not.
I
don't
know
that
it's
necessarily,
I
guess
it
could
be
a
bug.
Would
we
want
to
throw
a
bug
out
label
on
this.
A
Okay
make
sense
moving
on,
I
just
start
down
the
list
here.
A
I'm
looking
at
a
few
of
these
and
I
wasn't
able
to
determine
a
priority.
I
will
close
that
for
now.
B
B
B
C
B
A
This
one
is
specifically
an
issue
with
what
was
this.
I
think
this
was
exporting
to
honeycomb,
I'm
not
clear
that
this
is
a
a
collector
issue,
especially
a
collector
contribution,
considering
they're
exporting
with
the
otlp
exporter,
but
I
haven't
heard
from
them,
so
I
haven't
applied
any
additional
labels.
It's
kind
of
just
waiting
for
feedback.
B
Okay,
how
do
we
handle
like
vendor-specific
issues
or
didn't
need.
A
Okay,
this
one's
also
a
little
confusing.
This
deals
with
the
logging
exporter,
which
is
a
core
package,
so
I'm
not
100
sure
why
this
is
in
contrib
and
I'm
not
sure
what
to
label
it
as
as
a
result.
C
Yeah,
I
think
I
think
the
the
initial
reporter
also
had
the
same
question
as
to
why
this
got
moved
to
the
contributor.
B
C
C
A
Okay,
and
so
that
ends
us.
B
A
A
A
So
what
we
had
discussed,
I
think,
would
make
sense
around
not
having
a
or
around
just
having
a
triage
label.
So,
just
once
once
an
issue
is
considered
triaged,
it's
yeah!
I
guess
that
covers
it
too.
It's
been
triaged
somebody's
looked
at
it.
A
Oh
yes,
I
wanted
them
to
so
this
is
they're
having
a
permission
denied
error
when
trying
to,
I
think,
let's
do
some
file
scraping
and
was
it
exporting
to.
If
I
was
one
exporting
to
a
file-
and
it's
not
clear
to
me
that
it's
an
exporter
issue,
it
seems
like
it's
probably
a
configuration
issue
on
their
end,
but
I
needed
them
to
look
into
it.
I
have
not
heard
back.
Is
it
sufficient
to
put
a
question
label
on
these
when
we're
not
sure
about
them?
B
Do
we
have
a
status
of
waiting
for
response
or
something
like
that
it'd
be
nice
to
be
able
to
have
something?
That's
like
okay!
It's
on
you!
Now,
until
you
get
back
to
us,
we're
not
gonna.
Do
anything
right.
C
I
thought
there
was
like,
like
requests
for
information
type
or
more
info
needed.
Let's.
A
B
A
Yeah
we
do,
but
I
believe
when
these
issues
are
opened,
it's
because
it
can't
be
automatically
merged
that
there
needs
to.
B
C
Right,
this
is
probably
like
a
prometheus
label
either
prometheus
receiver.
I
don't
know
exactly
which
components.
A
B
A
A
B
C
Looks
like
someone
replied
with
like
a
workaround
or
basically
describing
what's
happening
here.
I
don't
know
if
this
is
a
bug.
C
Okay,
maybe
just
pick
the
author
and
see
if.
A
I
mean
I'd
be
fine
with
that.
What
do
you
is
that
is
that
proper
etiquette.
B
I
mean
I
think
it
is,
but
I
tend
to
want
to
be
like,
with
this
volume
of
issues
kind
of
like
to
close
them
fairly
aggressively.
Still
it's
nice
to
have
a
stailbot
to
do
it.
If
we
had
a
snail
bot
or
whatever
we
could
just
say
you
know
let
stailbot
do
it.
Unless
they
respond,
you
know
without
a
stale
bot,
then
you
have
to
be
more
aggressive
about
it.
So
I
don't
know
yeah.
That's
that
that's
the
kind
of
comment
you
want
to
make
and
they
may
come
back
and
go
wait.
B
I'm
not
done
great.
Just
pay
attention.
A
You
know
I
think
we
should
be.
We
should
be
aggressive
about
making
sure
that
the
issues
are,
they
were
getting
responses
and
that
there's
some
kind
of
movement,
even
if
it's
slow.
B
A
A
It
sounds
like
it's
a
question
we're
just
gonna
have
to
so
dan
or
alex.
If
you
want
to
get
back
to
him,
you
can't
otherwise
we
can.
One
of
you
guys
can
feel
free
to
close
it.
I
guess.