►
From YouTube: 2021-10-28 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
B
B
B
We
don't
right
now
have
limits
on
like
setting
attributes,
which
we
I
mean
makes
sense
to
have
to
in
case
the
bug
happens,
and
you
know
start
adding
infinite
number
of
attributes,
and
probably
just
do
it
naively
for
now
and
maybe
can
optimize
in
the
future.
But.
B
No
we're
so
we
are
so
that's
where
I
did
we.
We
have
it
on
the
exporter,
but
we
don't
have
it
when
you're
setting
an
attribute
on
a
span
which
is
special
because
you
could
blow
up
a
system
by
if
you
have
a
bug
that
just
keeps
setting
attributes
forever.
B
A
B
Yeah,
that's
in
the
exporter,
so
you'd
have
to.
A
A
I
haven't
tested
it
just
do
the
time,
but
one
of
the
things
I
was
oh,
no,
that's
right.
It
wouldn't
work.
B
A
B
Systems
use
like
a
time
stamp
or
something
else
to
have
an
order,
and
originally
it
wasn't
supported.
C
B
Yeah,
you
have
to
use
random
change
your
systems,
but
they,
I
think,
aws
x-ray
is
one
probably
some
others.
I
guess
they
get
something
out
of
being
able
to
sort
them
by
that
by
an
order
instead
of
by
relationship,
but
not
sure
what
I'll
have
to
check
I'd
have
to
check
on
that.
B
B
B
B
B
Yeah,
they
probably
will
be
just
the
tracking
part
right
yeah
that
could
get
messy.
B
I
mean
we
yeah,
we
might
even
I
mean
say,
we'll
do
it
after,
but
I
think
I'm
it's
good
to
take
a
look
at
least
and
see
what
it
would
take
and
then
decide.
B
The
gzip
thing
is
just
is
a
someone's
working
on
a
pull
request
for
it
to
add
support
for.
B
There's
a
number
of
features
for
the
exporter
that
we
don't
have
like
retrying
and
back
off
and
throttling,
and
that
I
want
to
wait
until
I
rework
the
exporter
in
a
backwards
compatible
way.
But
in
a
way
that
will
make
this,
I
guess,
move
some
of
the
logic
right
now.
It's
all
tied
up
with
the
batch
processor
and.
B
B
B
A
You
get
schema
url
and
resource
logs
and
instrumentation
library.
Oh.
A
B
A
I'm
kind
of
waiting
to
see
what
greg
and
then
do
what
they
come
up
with
on
trying
to
track
that
cross
process
stuff.
I
did
very
briefly
so
I
guess
one
of
the
I
guess
yeah.
We
should
probably
talk
about
that.
A
A
I
guess
I
did
call
it
utility,
okay,
so
all
of
the
ecto
ones
that
they
have
are
task
related
and
the
task
things
use
a.
A
A
A
B
A
B
A
A
A
A
B
A
A
B
A
B
Might
even
make
sense
to
maybe
for
some
other
ones,
since
there's
not
going
to
integrate
open
telemetry
but
they've
integrated
telemetry.
It
might
be
worth
trying
to
open
an
issue
and
say:
hey,
I'm
using
telemetry,
and
I
want
to
relate
these
tasks
with
the
query
that
started
them
when
the
telemetry
event
triggers.
How
do
I,
how
do
we
do
that
and
get
them
to
add
something
into
ecto
itself
to
make
that
possible
or
in
the
telemetry
well
into
both?
I
guess
I
mean
it
would
be.
B
A
B
A
B
A
B
B
A
B
I
don't
think
so
without
doing
a
match.
There's
just
I
don't.
I
don't
think
you
can
do
it
because
there's
like
trace
date,
otherwise
I'd
say
you
could
construct
it.
If
you
know
the
two
ids
but
trace
state
is
not
gonna
be
available
and
you
can't
make
that
up
and
it's
not
stored
in,
like
I
said,
maybe.
A
C
Hi
yeah,
I'm
here
for
the
ebps
work
group,
is
that.
B
But
it's
also
did
you
get
the?
I
mean
it's
good
to
get
this
figured
out,
but
did
you
get
the
link
from
the
google
calendar
or
from
somewhere
else
because
they
changed
them.
C
Okay,
thanks,
oh
yeah,
I'll
drop
in
join
that
one.