►
From YouTube: 2022-07-01 meeting
Description
Instrumentation: Messaging
A
Sweet,
I
was
that
was
abstinent
last
week.
A
Normally
it'll
be
dimitri
or
dan,
but
I
actually
I'm
pretty
sure
dan's
working
today.
I
expect
him
to
come
to
this
dimitri's
kind
of
been
he's
been
pulled
off
of
open
telemetry
for
like
a
couple
weeks,
so
he's
not
working
open,
telemetry
full-time
right
now,
until
like
the
end
of
july,
or
something
like
that
he's
still,
I
think
he
still
comes
to
these
meetings.
Yeah.
B
A
So
we'll
just
start
going
through
these
until
we
find
some
that
don't
have
priority
labels,
so
this
looks
like
a
good
one
to
start
with,
we're
do
we'll
do
contrib
today,
instead
of
core,
because
more
happens
in
contrib
right
now.
Okay,
pablo
open
this
one.
A
C
A
When
there
was
an
issue
like
during
a
release
that
we
were
doing
when
someone
found
like
a
a
memory
leak
and
prometheus,
that
we
had
like
a
dependency
on
so
like
the
collector
was
about
to
get
a
memory
leak,
something
like
that.
But
then
it
turned
out
it
wasn't.
Memory
like
it
was
stopping.
It
was
blocking
a
release.
I
think
they
might
have
put
a
p0
on
that
one,
but
I
don't
know
okay
I'll
put
the
p2
on
this
one
and
move
on.
A
I
know
dan's
working
on
this.
One
I'll
probably
leave
this
one
until
he
joins
this
meeting
if
he
doesn't
join
the
meeting
all
I'll
add
one
later,
but
this
is
something
for
our
new.
A
A
A
A
B
A
That
it
might
be
this,
this
dollar
sign
he
might
have
to
put
two
dollar
signs
yeah
in
there
even
saying
that.
A
Man
there
was
another
component.
There
was
something
with
the
config.
I
thought.
Maybe
I
think
prometheus
had
to
do
this,
where
dollar
signs
like
registered
as
a
dollar
sign,
because
dollar
sign
was
like
already
a
key
character
or
something
like
that.
But
then
I
thought
they
got
rid
of
that.
So
then
you
could
just
use
a
single
dollar
sign,
so
I
don't
actually
know
so.
I'm
just
going
to
reach
out
to
the
code
owner
and
say:
hey,
please
triage
this
code
owner.
A
Yeah
we
have
so
many
different
components
in
contrib
and
like
there's,
no
way
to
associate
there's
no
good
way
to
associate
issues
with
code
owners
and
like
unless
you're
like
a
member
unless
you're
an
approver
or
above
the
code.
Owner's
file
like
you
can
see.
It's
like
yelling
at
us
like,
doesn't
even
know
how
to
ping
these
people
so
like
yeah,.
B
I
know
it
can
be
hard
to
get.
I
mean
the
code
owners
and
I
it
doesn't
ping
me
either
since
I'm
not
yeah.
B
A
I
know
that
I
think
that
alex
said
that
he
was
gonna
go
through
and
clean
up
some
of
our
labels
as
well
like
we
have
some
situations
where
it's
like
transform,
processor
right,
it's
the
component
and
the
type
and
the
same
thing,
but
then
there's
situations
where
it's
like
kafka
and
it's
an
exporter
where
it's
like
split,
because
there's
also
a
kafka
receiver
so
like
instead
of
having
two
labels,
they
just
had
coffee,
but
I
think
we
want
to
make
it
all
just
uniform
and
just
ping
the
exact
component,
but
we
haven't
gone
through
and
cleaned
that
up
yet.
B
A
B
B
Handle
it
yet
that
was
added
within
the
last
year,
maybe
even.
B
B
A
A
C
C
A
Yeah,
I'm
not
actually
I've
not
actually
seen
anything
added
that
label
recently
and
it
already
got
data
metrics
on
it.
So
we'll
just
look
at
that.
Okay,
it
looks
like
pablo,
did
a
little
bit
of
triaging,
so
we'll
leave
that
and
then
we
ping
them
and
so
triaged
moving
on.
A
These
are
all
dan's
flicky
tests,
and
then
they
put
these
that
normally
do
help
wanted
on
these
and
normally
a
good
first
issue.
A
C
A
I
think
for
vendor
specific
components,
we've
actually
added
to
our
template
for
new
components.
That,
like
please,
tell
us
if
you
are
so
that,
like
you,
could
be
the
person
for
it.
We've
had
some.
B
A
In
the
past,
where
components
that
were
very
vendor-specific
were
proposed
by
non-vendor
community
members,
which
can
be
super
useful
right.
If
you
need
to
solve
some
issue-
and
you
know
the
community's
all
for
it,
but
like
it,
gets
hard
to
maintain
it
because.
A
A
B
B
I'm
not
as
familiar,
but
it
is
this
a
crashing
bug,
or
is
this
just
just
fail
to
process
this
particular?
I.
A
Then
the
logs
aren't
as
in
depth
as
I
think
we
need
them,
but
I
think
that
it.
A
Yeah,
I'm
hoping
that
during
processing,
I
think
the
collector
it
looks
like
to
me
like
the
collector,
is
still
starting
up,
and
then
it
gets
itself
into
a
weird
situation.
Maybe
either
way
we
need
to
reach
out
to
some
people
so
build
two
processor.
A
A
It's
easier
to
get
to
p1s
for
for
contrib
individual
components,
especially
if
it's
like,
if
you
have
to
do
something
to
get
yourself
into
that
spot,
we
prioritize
it
a
little
lower
like.
A
Like
started
up
the
processor
and
like
instantly
clash,
the
collector
like
that
would
be
bad
or
like
for,
like
one
of
the
other
things
that
we
ask,
people
to
do
is
if
they
open
an
issue,
and
they
can't
put
labels
on
for
themselves
is
to
like
suggest
a
priority
so
like
there
are
some
situations
like
for
issues
that
I've
opened
for
components
that
I
own.
That
are
things
that
I
want
to
work
on
before.
A
C
A
It
might
be,
it
looks
like
someone
put
a
p1
on
the
flaky
test,
which
I
don't
know
if
I
agree
with,
but
maybe
maybe
for
certain
situations
since
there's
two
here,
I
can
I'll
go
back
and
add
the
I'll
make
this
one
a
p1
yeah.
I
suppose
it
depends
how
flaky.
A
A
B
B
B
Okay,
so
this
is
just
or
instead
of
and
yeah,
this
is
an
enhancement
yeah,
it's
not
a
bug,
I
would
say
it's.
I
mean
they're
asking
to
change
the
d
here.
It's
not
even
a
feature.
B
B
A
Maybe
I'm
pretty
sure
if
you're
over
here,
just
search
for
files
go
to
file,
you
can
do
it
in
here.
A
A
A
C
B
A
I
think
this
one's
been
in
here
for
a
while,
though,
so
I'm
kind
of
surprised
this
hasn't
come
up
before
like
this
has
been
in
here
for
quite
a
quite
a
bit.
So
this
is
a.
This
is
an
interesting
one.
I
don't
know
why
this
one's
not
working.
A
A
A
I'm
not
sure,
but
that's
all
we
can
do
for
that
looks
like
pablo's,
already
got
a
lot
of
research
going
on
that
one.
So
it's
good
enough
for
now.
A
C
A
B
B
That's
the
idea,
yeah
to
become
more
involved
with
collector
right
evan
here
is
also
from
dynatrace,
and
dynatrace
in
general
would
like
to
be
more
involved
with
the
collector.
B
A
Yeah
we've
tried
to
do
better
recently,
with,
especially
with
the
like
help
wanted.
Labels
like
it
is
getting
a
little
longer
to
get
things
triaged
because,
like
we
have
to
paint
the
code
owners
and
then
hopefully,
they
show
up.
B
A
They
don't
show
up
and
you
can't
really
ask
for
help
until
the
thing
is
more
triage
and
like
we
can't,
can
triage
the
individual
components
but
yeah,
that's
the
only
tricky
part
is
if
we
don't
know
how
one
is
needed
immediately
like
we
need
the
code
owners
to
reach
out
to
us
again
on
the
issue,
because
they
can't
add
the
label
themselves,
maybe
there's
a
bot,
we
could
add
that
would
make
it
easier
to
add
labels
for
other
people.
I
don't
know,
but.
A
That
would
be
a
problem
in
core
yeah
yeah
I'll,
throw
a
p2
on
this
one,
if
the
maybe
jurassic
and
go
deeper
in
it,
but
yeah
that
is
interesting
like
this
would
be
a
metric,
that's
being
reported
from
well.
Actually
I
don't
know
that
for
sure
this
could
be
something
that
the
health
check
extension
is
maintaining.
If
this
is
something
that
the
health
check
is
extension
is
maintaining,
and
it's
not
one
of
the
metrics
that
the
collector
core
reports,
which
I
assume
is
how
this
extension
is
working.
A
B
A
The
number
today
I
think
we
left
some
gaps
from
the
previous
week.
I
try
to
go
in
here,
sometimes
and
fill
out
things.
We
are
actively
looking
for
triagers
so
like
if
you
want
to
get
more
involved
with
the
collector.
That
could
be
a
good
place
to
start
reviews.