►
From YouTube: 2022-08-12 meeting
Description
Instrumentation: Messaging
A
Yeah
I've
been
joining
for
the
last
five
or
six
weeks.
I
think.
A
A
B
B
B
A
A
A
B
B
B
B
B
B
Kafka
next
receiver
enhancement,
I'm
not
sure
if
it's
enhancement
or
not,
if
we
really
need
it,
let's
keep
the
discussion
and
priority
I'll
stay
p3.
It's
not
very
something
very
important.
I
don't
understand
what
what
was
gonna
be
like.
What's
the
raw
data,
how
that
will
be
translated
to
our
otp
model,
if
we
really
need
it
just
like
into
body
okay,
so
let's
keep
it.
That
is
not
very
urgent.
B
A
So
it
looks
to
me,
like
I
said
I
was
looking
at
this
one
earlier
a
little
bit.
I
it's
hard
to
tell
if,
if
data
is
even
getting
to
the
collector,
this
might
be
a
problem
with,
however,
their
with
their
sdk,
I'm
actually
the
one
that
commented
on
this.
B
B
Yeah
sounds
like
yeah:
it
can
be
instrumentation
stuff
related
to
aws
lambda,
so
we'll
probably
can
close
it
and
move
it.
Okay.
Can
I
assign
to
you
just
to
follow
up
on
this
one.
B
A
So
it
looks
like
they
just
want
a
native
way
like
an
azure
native
way
to
encrypt
the
connection.
A
A
A
B
B
B
Cool
update,
github.com
a
lesson
as
principal
to
the
better
version.
B
B
Okay,
it's
just
like
some
breaking
change
in
the
library
that
we
need
to
handle
assigned
dollar
could
tyler's
assigned,
and
I
don't
know
what's
the
it's
like
priority
just
needs
to
be
added
here.
It's
probably
high
because
it's
blocking
upgrades
of
the
dependencies
called
next
one
receiver
expert,
diverse
receiver,
metrics
incorrect
and
I
believe
I
saw
pull
requests
for
this
guy
already
yeah
and
that
was
look
good.
B
B
B
They
are
not
very
evolved,
e3
yeah
I'll,
follow
up
on
this
one
after
the
call
probably
will
check
if
that
is
important
enough
to
be
added
right
now,
I
can
wait
until
we
switch
to
open
telemetry
metrics.
B
B
This
is
something
interesting
we
it's
like.
We
we
run
into
this
issue
that
we,
our
configuration
interview
interface,
mostly
assumes
that
we
have
attributes
values
of
stream
string
type
only
like
it
used
to
be
the
case
most
of
the
cases
but
yeah
we
we
have
such
like
such
processors,
less
routine.
That
assume
that,
and
now
we
need
to
change
the
configuration
interface
likely.
B
Yeah
I'll
just
put
priority
here:
speed,
2
and
jurai
is
already
working
on
that
and.
B
B
I
I
just
sorry
for
for
phrases
like
this.
You
don't
you
you
don't
have
any
like
your
own
distribution
right.
You,
your
users,
use,
contribute
com,
contrib
builds
right,
complete
kind
of
country,
binaries.
B
Okay,
cool
yeah
just
want
to
make
sure
like,
because,
like
aws
had
the
sumo
logic
has
its
own.
You
know
destroyed
leaf
splunk
as
well,
so
that
they
just
unchecked
that
yeah,
because
filtration
is
very
popular
as
far
as
as
far
as
I
know
like
a
lot
of
users
and
yeah.
This
is
actually
what
I
I
supposed
to
work
on.
It's
like
a
bug
introduced
recently,
so
I'm
not
going
to
change
here.
B
B
A
So
it's
worth
mentioning:
that's
not
the
person
who
opened
the
the
ticket
yeah.
B
B
B
And
yeah
I'll
just
put
help
to
help
one
here.
So
it's
clear
that
might
be
not
a
good
first
issue,
but
well
that's
fine.
Priority
is
two,
I
believe
cool
and
everything
else
is
triashed.
Okay,
not
this
guy.
A
Oh
so
this
was
we
talked
about
this
last
week.
This
is
like
two
metrics
with
the
same
name.
Basically,
it's
like.
B
A
Something
like
a
user
error
yeah,
I
think
so.
I
didn't
we
talked
about
this
last
week,
though
I
think
we
already
triaged
this
one.
We.
B
A
B
B
A
Needed
is
just
when
we're
going
through
these
triage
meetings.
Sometimes
we
don't
have
all
the
context
or
expertise
needed
to
give
it
a
priority.
So
you
know
ping
the
code
owners
and
add
priority
needed,
and
then
they
can
prioritize
it.
Oh.
B
A
B
B
Oh
okay,
I
believe
we're
done
and
we
are
three
minutes
criminals
more,
but
I
think
we
should
be
good
to
close
it.
Okay,
now
right,
cool
cool!
Thank
you
folks,
for
helping
with
that.