►
From YouTube: 2021-05-14 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
C
B
C
It's
our
twice
annual
planning:
oh
no,
actually
yeah,
twice
annual
planning
right
now,
so
yeah
kind
of
the
same
deal.
B
B
No
it'd
be
it'd,
be
super
great
for
a
lot
of
reasons
like
the
mo.
A
lot
of
like
the
the
tracing
sdk
depends
on
the
metrics
api
at
the
moment
internally
as
an
implementation
detail,
but
this
has
made
sleuth
folks
uncomfortable
because
they
have
to
pull
it
in
as
a
dependency,
even
though
it's
still
alpha.
B
B
As
of
0.9.0
metrics
remark
stable
in
that
case
yeah.
They
can
easily.
B
D
B
B
They
didn't
get
rid
of
like
the
observers
here.
No,
they
were
just
the
the
requiring
things
to
be
named
observer.
So
there's
still
the
concept
of
observers.
I
think
it's.
It's
basically,
there's
no
reason
to
expose
that
as
a
type
like
it's
just
a
callback.
E
D
B
That
we
announced
last
week
last
week
called
splunk
observability
cloud,
and
this
is
basically
the
combination
of
signalfx
omniscient
that
synthetics
company
in
atlanta
we
acquired
another
company.
We
acquired
that
does
network
monitoring.
That
can't
remember
the
name
of,
and
I
think
there
was
a
fifth
company
as
well.
So
anyway,
it's
a
it's
a
new
product.
It's
not
the
classic
splunk
logging
product,
but
it
has
logging
as
a
part
of
it.
B
B
C
Kind
of
like
similar
to
a
la
I
mean
similar
to
elastic
they.
They
had
back-end,
I
mean
like
a
storage
system
and
then
they
they
went
into
or
they
added
atm
sort
of.
On
top
of
it.
E
C
C
I
did
not
that
the
bug
fixes
the
ones
just
the
ones
from
this
week,
yep.
E
C
C
That
was
a
good
bug
fix,
and
that
was
a
little
bug.
A
E
C
C
B
D
Yeah
yeah,
I
don't
think
I'm
gonna
prioritize
moving
to
that
new
instance,
but
it's
definitely
something
on
my
mind.
Yeah.
I
don't
know
how
difficult
that
is.
I
assume
we
need
to
set
up
new,
all
sorts
and
then
change
the
urls
in
our
build
scripts.
I
guess
it'd
be
all
three
of
them,
so
yeah.
We
can't
forget
to
open
them
to
java
contrib,
but
although.
D
D
D
E
D
B
D
D
C
Yeah
we've
been
having
problems
john,
where
we
merge
things
they're
green,
because
the
build
cache
thinks
it
doesn't
need
to
re-run
stuff,
and
then
we
later
find
out
that
it
should
have
re-run
stuff.
B
D
B
B
B
D
C
A
B
My
real
question
was
not
I
mean
why
it
was
doing
this,
but
in
the
java
repo
it
it
added
the
tag,
blocked
dependency
on
every
pr,
and
I
don't
know
why
it
would
have
done
that.
B
C
D
D
C
Yeah
did
we
tag
it
with
these
dependencies
back.
A
C
Rights
to
create
a
new
tag
anyway,
okay,
so
that's.
E
B
D
C
But
how
about
the
other
other.
D
C
Yeah
and
that
one
is
fine
because
that's
like,
but
like
a
lot
of
these
are
pretty
like
I
don't
know,
some
of
them
are
more
random.
D
C
Okay,
that
was
what
I
was
wondering
like
yeah
and
they
wouldn't
just
because
they're
running
they
wouldn't
have
access.
D
E
C
D
E
E
E
B
Well,
I
saw
it's
in
there.
It
is
now
in
their
roadmap,
but
it's
not
in
scheduled
at
any
time.
It's
like
future.
It's
in
the
future
bucket
of
the
roadmap.
B
C
I
was
gonna
tell
ya,
they
actually
implemented
some
cool
features.
Some
new
features
in
that
plug-in
recently
like
you,
can
now
update
the
pr
branch
from
in
there.
I
should
I
should
check
it.
B
D
B
B
D
B
Anyway,
you
should
you
should
just
pastor
your
your
github
friends,
oh
yeah,.
B
C
B
C
We
watch
the
can
we
watch
the
boiling
pot,
oh
whatever.
E
C
D
C
Well,
we
did
hide
here.
We
hijacked
the
yesterday's
meeting,
because
we
were
literally
the
only
people
there.
Oh.
C
C
I
don't
know
he
never
came
off
mute.
He
did
put
some
comments
in
chat.
D
D
D
C
I'm
guessing
maybe
I
mean,
could
it
have
been
for
not
overloading
and
not
the
server
and
not
getting
a
denial
of
service
like.
D
D
Is
not,
I
don't
think
it
might
be,
but
I
don't
I
don't
think
so
yeah
and
so
every
time
you
run
a
test.
It
starts
with
this
configuration
and
for
some
reason,
one
second,
that
seems
to
be
wasted
on
just
resolving
dependencies
every
time
I
don't
see
that
behavior
on
the
sticky
repo.
D
C
I'm
glad
we
talked
about
the
whole,
the
actions,
because
the
official
ones
that
will
make,
because
I
was
reluctant.
D
B
Hey
there's
two
pieces
of
observability
news
that
no
one's
mentioned
just
the
observability
world
lights
that
got
a
light
step,
got
acquired.
B
A
C
B
D
B
B
I
see
your
blah
blah
blah
blah
an
open
telemetry
this
that
any
other
thing
are
you
interested
in
doing
some
consulting
for
a
startup
or
for
a
vc
who's
interested
in
the
observability
space
and
wants
to
just
like
have
a
conversation
with
you,
and
I
was
like
okay
I'll
I'll
charge
600
for
an
hour
consulting
if
you
want
to
do
that,
and
I
okay,
but
okay
with
new
relic,
but
he
wanted
to
like
find
out
about
like
just
ask
questions
about.
Like
would.
B
C
My
ex-manager
is
in
that
doing
that,
I'm
not
sure.
What's
I'm
very
and
there's.
C
C
Like
why
there's
there's,
like
I
worked
before
microsoft
for
most
of
my
career,
I
worked
at
like
corporate
legal
matter
management
systems
and
like
there's
just
so
like
you
want
to
make
money
like
there's
so
many
business
like
neat,
there's
so
many
little
niches
out
there
that
don't
have
you
know
a
hundred
different
companies
competing
or
you
know,
and
and
a
hundred
different
open
source
products
and
cloud
vendors,
and
you
know,
like
there's
lots
of
little
niches
out
there,
like
that
you
can
go.
C
E
E
D
B
Oh,
I
had
a
along
those
same
lines.
Somebody
asked,
I
think
it
was
a
question
on
gitter,
which
I
tried
to
redirect.
I
haven't
answered
yet
about
wanting
basically
to
be
able
to
change
sampling
on
the
fly
like
without
having
to
go
restart,
and
I
realized
that
we
neither
have
supported
the
agent
for
configuring,
the
jaeger
remote
sampler.
B
D
Yeah,
when
nikita
is
done
with
the
extension
thing,
when
that's
merged
and
ready
to
go,
yeah
that'll
be
one
approach,
easy
pages.
I
mean
I'm
fine
with
just
deleting
z
pages.
I
haven't
put
any
maintenance
work
into
that
at
all.
Yeah
like
it
still
needs
a
lot
of
work
before
we
can
use
it
eager
I
mean
I
don't
see
any
reason
not
to
pull
jaeger
remote
sampler
in
it
presumably
doesn't
have
any
dependencies
outside
of
the
edgar
export
that
we
already
have.
It
should
be
the
same
profile,
I
think
so.
I
think
it
seems
harmless.
D
B
D
Which
you
could
like
they
aren't
dependent.
I
mean
we're
not
going
to
do
anything.
I
think
that
would
be
supported,
yeah
yeah,
but
I
guess
we
need
to
go
through
the
spec
first
to
give
it
an
environment
variable
right.
E
B
B
D
E
D
B
Yeah,
I
think
the
other
thing
I've
seen
was.
I
can't
get
baggage
to
work
with
the
agents
and
I
don't
know
I
don't
know
like
there's
no
reason
why.
Let
me
ask
the
question:
is
there
a
reason
why,
if
you're
using
the
baggage
api,
it
wouldn't
work
with
the
agent
like
if
I
wanted
to
go,
grab
the
grab,
baggage.current,
amend
it
and
then
set
current
again
and
put
it
in
scope
that
should
work
with
the
agent
right.
B
C
Yeah
right,
okay,
cool
one
thing
that
I
I
kind
of
I'm
curious.
Yes,.
D
D
B
B
Well,
I
mean:
if
user
wants
to
do
something
manual,
they
can
add
it
later
right,
I'm
just
thinking
from
they
want
to
do
automated
baggage.
Probably
you'd
expect
it
to
be
at
the
start.
Yeah
expand
processor
seems
like
it
should
be.
Good
enough.
I
mean
baggage
is
supposed
to
be
something
that
goes
throughout
the
life
cycle
of
the
trace
as
a
whole.
So
fan
start
seems
like
it
should
be.
Okay,.
D
B
How
much
logging
mdc
support
is
in
the
agent
at
the
moment.
B
B
E
C
Now
in
brave,
did
they
propagate
baggage
over
the
wire.
D
Yeah
but
as
as
a
header
per
like
each
key
value
appear
basically
became
an
http
header.
There
was
no
baggage
spec
or
anything
okay,
but
it
was
a
key
value
string
map
that
then
just
also
gets
added
to
the
outgoing
stuff.
B
C
B
A
B
C
E
D
A
B
A
D
Java
object
gets
property,
no
matter
what
so
that's
already
hotel
1.0,
so
that
we're
not
going
to
change,
and
so
what
we
can
offer
is
then
align
configuring,
a
subset
that
gets
injected
into
logs
automatically,
and
we
can't
really
offer
a
setting
to
control
the
remote
propagation
unless
we
make
a
big
change
to
the
spec
even
to
the
w3c,
probably
yeah.
I.
C
Until
then,
yeah
I'm
just
trying
to
think
for
how
to
solve
for,
like
we
have
I've
seen
this
request
of
stamping
like
a
tenant
id
or
something
onto
all
of
the
spams,
and
I
guess
yeah.
Maybe
I
shouldn't
be
so
worried
about
propagating
that
stuff
downstream.
D
B
C
Yeah
so
like
like
what
I
see
like
I've,
this
like
say
at
the
top
level
request
you
wanna,
like
you,
wanna,
apply
some
stamp
some
tag
on
to.
A
C
Downstream
spans
within
that
process,
so
baggage
seems
great
for
that
plus
a
span
processor,
but
then
you
have
the
downstream
over
the
wire
propagation,
which
I
would
which
I
I
guess
is
where
I'm
I
was
working
yeah.
D
C
Yeah
and
I'm
wondering
I
need
to
go
back
and
rethink
that
use
case
of
whether
why
I'm
worried
about
propagating
it
downstream,
like
maybe
that's
totally.
D
C
Yeah,
I
guess
even
then
like
how
would
you
like
a
sampler?
How
would
how
do
you
add
something
to
the
context,
because
the
sampler
can't
modify
the
context.
C
The
in
particular,
I
guess
that
the
primary
use
case
that
we
have
that
we
is
our
we
would
propagate
the
server
span
name
as
like
this
operation
name,
and
we
would
stamp
all
of
the
bands
with
that
operation
name.
D
B
C
D
C
E
C
But
in
the
java
agent
distro,
if.
C
C
D
Okay,
maybe
I'll
look
into
adding
a
spec
issue
to
discuss
the
idea
of
an
experimental
thing
to
populate
package
into
logs
because
we're
getting
a
lot
of
requests
for
it.
So
it
would
be
worth
having
an
experimental
knob
for
that
right
now,
probably
even
before
the
log
spec
and
see
if
other
people
agree.
B
B
I
don't
know
complaining
is
the
right
word.
He
was
trying
to
get
sleuth
instrumentation
to
interact
with
the
agent
instrumentation
and
share
probably
sharing
baggage
actually
between
the
two
and
I'm
like.
Why?
What
do
you?
Why,
like
don't
don't
have
the
agent
running
in
sleuth?
That's
a
bad
idea,
don't
don't
do
that
either
choose
one
choose
one
instrumentation
and
he
and
his
explanation
kind
of
confounded
me
and
he
said
he
uses
sleuth
only
in
production.
B
Which
I
thought
was
interesting
yeah.
I
never
heard
that
before
yeah,
and
I
also
said
I
don't
think
we're.
This
is
not
a
supported
use
case
like
you
might
get
lucky
and
things
might
work
occasionally,
but
we're
not
gonna
like
nobody's
interested
in
supporting
this
case
anyway,
I
thought
it
was
very
strange
that
they
turned
on
the
agent
locally.
Only
get
more
information.
C
A
C
Was
that
the
person
the
that
was
had
the
inline
span,
the
inline
zipkin
trace.
B
D
B
D
D
C
D
B
D
D
D
B
So
martian
now
makes
it
so
you
can
configure.
You
can
use
the
batch
spam
processor
if
you're
willing
to
use
the
metrics
the
alpha
metrics
api
yeah.
B
E
B
D
B
D
D
D
D
B
Those
depending
unless
you
want
to
merge
those
depend
about
pr's
you're,
welcome
to
either
way
that
doesn't
matter
to
me.
Okay,
cool
all
right,
see
you
all
later
have
a
good
night
good
afternoon.
C
C
D
D
D
I
don't
think
I
ever
do.
Okay,
I'm
not
sure
what
the
what's.
D
D
C
For
it
looks
like
it
could
take,
set
an.
E
C
For
two
hours
that
way
and
if,
if
there's
more
problems,
then
I
will
hit
the
button
and
I'll,
let
you
all
know
so
you
can
check
it
in
another
two
hours
after.