►
From YouTube: 2021-04-07 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).
B
B
A
A
I
think
that
that
sounds
like
a
good
plan.
I
know
there's
not
too
much
changes
for
this
one
right.
We've
got
some
bunch
of
miscellaneous
metric
stuff
and
a
couple
bug
fixes.
No,
I
guess
like
I
was.
I
had
looked
at
the
up-to-date
release
notes
but
seems
like
a
good,
a
good
point.
There's
enough
stuff
that
thrift
exporter
bug,
that's
something
funk
needs.
B
A
Because
I
don't
know
why-
I
guess
the
only
thing
I
didn't
know
about
that
is
whether
I
should
continue
to
do
the
child
follow
or
the
the
child
link
or
whatever
it
is
there's
a
the
child
of,
but
I
decided
it
didn't
hurt
to
have
them
both
in
there
back
back
ends
that
understand
childhood
should
be
fine
and
ones
that
are
looking
for.
Paranoid
should
also
be
fine.
Hopefully,.
B
A
B
A
B
Collector
also
supports
eager
thrift
free
ingesting.
A
It
exporting
it
yeah,
I
think,
it'll
also
export
it
yeah,
although
in
for
splunk,
we
just
use
it
for
ingesting
it,
and
I
don't
honestly
remember
why
I
think
it's
because
the
old
splunk
smart
agent,
that
was
the
format
that
it
wanted,
and
so
people
don't
have
to
change
what
they're
expecting
like
their
configurations
and
their
ports
if
they
want
to
switch
over
to
the
collector
and
use
the
new
agent
or
something
right
whatever
something
like
that.
Yeah.
A
A
A
B
B
A
B
A
A
Yeah,
we'll
let
you
respond
to
jonathan's
you
just
because
you
have
more
grpc
experience
than
I
do
he
anyway,
he
keeps
on
trying
to
argue
it
on
the
splunk
on
the
sorry,
the
sleuth
repo
I'm
like
no
go.
Let's
go
talk
about
it
where
the
other
maintainers
can
actually
see
it
and
respond.
B
A
Yeah,
I
don't
know
why.
Well
I
mean
you
remember
seeing
the
way
they
do
all
their
maven
dependencies.
Is
they
only
they
like
explicitly
put
in
every
single
dependency
and
they
they
exclude
every
so
every
transit
dependency
for
every
dependency
that
they
put
in,
which
I
don't
understand
why
they
do
that,
but
yeah
instead.
A
B
Okay,
I'm
getting
another
review
of
that
baggage
thing
for
x-ray
yeah.
I
didn't
merge
it
because
I
thought
you
wanted
one
yeah
and
then
might
merge
that
and
release
it
or
might
not
know
see
what
will
says,
because
it's
one
like
I
it's
not
clear
whether
they
should
map
the
baggage
or
trace
date.
I
think
it's
supposed
to
be
baggage.
I
mean
our
spec
is
nowhere
near
thorough
enough
to
decide
like
what
the
use
case
is
for
these
key
value
pairs,
but
I
think
they're
for
apps,
not
some
like
x-ray
doesn't
use
them.
B
A
A
You
a
question
for
you:
we've
got
a
customer,
that's
trying
to
integrate
with
a
legacy
a
legacy,
tracing
solution
and
they
in
order
to
integrate
with
their
legacy
tracing
solution.
They
need
to
put
the
parent
span
id
on
the
response,
like
as
a
response
header
and
our
api
doesn't
expose
anything
like
there's.
No,
you
can't
get
parent
spam
out
of
our
api
at
all,
so
I've
been
trying
to
brainstorm
ideas
with
them
about
how
to
do
it.
My
initial
suggestion
was
that
they
could,
since
they
have
a
custom
propagator
to
manage
this.
You
know.
A
A
A
B
A
B
A
B
B
A
B
B
B
A
B
A
B
B
A
A
Well,
maybe
I
guess
if
they
don't
want
to
propagate
it
out,
but
they
don't
want
to
propagate
it
out,
although
I
don't
know,
there's
doesn't
seem
like
there's
a
huge
amount
of
harm
in
having
it
exactly
anyway,
like
I,
don't
even
think
it's
that
big
a
deal
to
ever
propagate
to
be
a
baggage,
but
anyway,
that's
a
really
that's
a
very
interesting
idea.
I
will
ponder
that
and
get
back
to
them
tomorrow
and
then
cool
thanks.
That's
a
great
idea.
Yeah.
B
B
A
B
A
B
I
respond
on
the
community
like
I,
if
it's
a
org
white
thing,
which
it
is,
I
think
like
doc,
each
docks
repo
has
the
docs
thing
and
it
is
the
plan.
I
guess
should
just
be
managed
by
the
org.
I
think.
But
if
yeah
I
mean,
I
think,
even
then,
if
we
want
to
merge
something
soon
so
that
the
docs
get
updated,
then
we
can
get.
A
A
We
definitely
need
to
get
those
docs
updated
yeah,
they
mean
the
other
option
would
be
the
tc.
Could
somebody
on
the
tc
could
own
the
token
and.