►
From YouTube: 2022-05-27 meeting
Description
Instrumentation: Messaging
A
C
B
C
A
C
C
C
A
E
C
A
C
Think
hold
on
you:
can
we
don't
have
a
drop
attributes
function?
We
have
a
set
which
you
could
use
to
make
an
attribute
blank
and
you
can
limit
the
number
of
attributes
and
you
can
truncate
attributes
so
that
they
don't
go
over
a
limit,
but
yeah
we
do.
We
don't
have
a
drop
function.
Yet
there's
a
lot
of
uses
for
a
drop
function.
We
should
probably
make
one
soon.
I
see
that
you.
C
Alpha
because,
okay,
the
the
issue
that
we
talked
about
on
the
sig
with
the
enums,
is
a
pretty
important
one
like
some
of
the
some
of
the
fields
that
you
might
want
to
use,
just
like
don't
like
they're,
not
actually
usable,
like
you,
couldn't
reference
them
in
a
function
correctly,
and
then
there's
some
also
just
some
defects
with
some
fields
that
they're
being
returned
and
data
types
that
don't
mean
anything
in
the
parser.
So
like
you
can't
actually
compare
anything
or
if
you
tried
to
set
a
data
type
it
like
wouldn't
work.
B
B
B
D
A
C
Production
use:
okay,
yeah
for
production
use
for
sure
it
sucks
to
add
things
to
the
other
processors
that
like
we
want
to
get
rid
of
but
like
at
the
same
time.
The
transform
processor
like
alpha
is
the
right
state
for
it,
but
for
like
a
large
customer
that
maybe
wants
some
stability.
Transform
is
like
probably
not
there
yet.
D
A
C
A
little
bit
but
yeah,
I
like
it's
my
primary
focus
right
now,
I'm
trying
to
focus
on
getting
the
thing
stable
and
not
so
much
on
the
on
like
adding
new
functions
myself
yet,
but
I
think
when
we
do
start
trying
to
replace
existing
processors,
we
should
have
like
large
overarching
issues
that
track
that,
but
I
haven't
created
any
of
them.
Yet
alex
was
asking
me
about
that
yesterday
and
I
was
like
we
want
to
like,
but
I
just
haven't.
I
haven't
made
it
that
far.
A
C
Especially
but
anyway,
it's
like
the
same
problem
with
the
logs
transformer
log
transform
processor.
It's
like
we
don't
want
to
rewrite
that
entire
thing
and
then
also
do
it
again
in
the
transform
processor
like
when
that
thing
emerges,
we'll
just
do
it
one
time
at
the
transform
processor,
I
think
that's
kind
of
how
it
is.
A
C
A
A
B
A
B
D
D
D
C
A
C
C
C
D
D
D
C
B
A
D
B
B
C
D
C
D
D
D
B
B
E
C
C
A
C
E
A
A
E
A
C
A
C
C
D
D
D
E
D
C
D
C
D
A
B
A
B
A
B
C
B
B
B
D
B
C
A
I
mean
windows
tests
are
running
now,
they're
fixed.
Finally,
but
we
still
have
all
of
this
issue,
but
fixed
so
yeah
I
fixed
like
pretty
much
most
of
them.
I
believe,
but
those
are
just
too
much
to
dig
and
do
so.
I
just
created
issues
for
them.
They
are
sticking
here.
Unfortunately,
when
those
tests
are
still
the
slowest.
How
yeah
is
that
to
you
guys.
B
A
C
D
C
No,
it
isn't
core,
it
isn't
core.
Maybe
it
got
moved
before
I
swear
it
wasn't
contrib,
because
that's
where
I've
got
notifications,
for
I
think
this
is
worth
talking
about
at
the
end
of
this
meeting,
because
it's
which
ones
it's
called
proposal
for
pipeline
branching
in
the
open,
telemetry
collector.