►
From YouTube: OpenTracing Monthly Call - 2018-06-01
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
Join us for KubeCon + CloudNativeCon in San Diego November 18 - 21. Learn more at https://bit.ly/2XTN3ho. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
Well,
that's
the
first
time
we've
messed
that
up
all
right.
Moving
on
so
I
was
curious.
Jonathan
you
mentioned
unit
tests
and
I
was
wondering
if
you've
integrated
tracing
into
the
development
practice
at
all
at
Facebook.
Is
that
a
thing
people
think
about
when
they're
they're
writing
their
code
and
kind
of
integrating
it
into
how
they're
testing
and
developing,
or
is
it
still
just
something
that
gets
kind
of
layered
in?
And
it's
that
more
about
as
a
production
thing.
C
C
That
and
then
at
that
point,
then
they
sort
of
are
aware
of
the
tracing
libraries
regarding
the
tests,
so
it
I
guess
it
you
well
it
so
it's
all
built
on
top
of
the
canopy
paper,
and
so
it
can.
It
be
sort
of
had
this
notion
of
like
a
trace
pattern
and
so
effectively.
What
we're
trying
to
do
is
extend
that
out
to
say,
like
measuring,
trace,
quality
and
measuring
trace
breakages
by
expressing
patterns
that
say
we
expect
an
end-to-end
trace
to
have
these
particular
types,
these
particular
fields.
C
C
Ideally,
those
patterns
are
then
also
used
like
directly
for
the
metrics
that
you
care
about,
so
you
don't
need
to
write
them
twice.
You
can
just
simply
say:
I
want
a
pattern
which
is
going
to
pull
out
this
particular
field
from
you
know
the
end
systems
along
the
trace,
and
then,
if
that
field,
isn't
there,
that
pattern
will
just
fail
and
then
we'll
be
like
you
know
something
has
broken
in
this
trace.
C
B
There's
stage
company
that
that
I,
don't
think,
is
that
a
stealth
or
anything
but
they're
kind
of
doing
this,
but
with
a
technology
that
can't
intimated
and
development
work
close.
So
you
can
write
assertions
about
about
system
properties
that
are
only
visible
and
the
distributed
trace,
and
then
they
actually
enforced
those
in
bands.
B
It's
pretty
interesting,
I
think
if
you
have
like
really
good
hygiene
or
on
instrumentation
as
I,
mind
a
pretty
powerful
thing
to
be
able
to
do
versus
a
normal
integration
test,
for
everything
has
to
be
programmed
to
emit
things,
and
you
have
to
you
know,
reach
across
a
lot
of
boundaries
in
order
to
test
like
rather
simple
and
and
behaviors,
so
that
I
like
the
idea
of
it
all
and
it
does.
That
means
pretty
heavily
on
instrumentation.
B
B
B
In
you
know,
first
service
application
architecture:
you
could
get
open
trace
things
stood
up
without
making
any
code
changes.
I,
don't
think
that
should
be
particularly
difficult
and
doesn't
necessarily
require
writing
a
bunch
of
crazy
interposition
code.
It's
the
open,
tracing
expedition
already
exists,
it's
more
a
matter
of
discovering.
What's
in
the
process,
no
one
was
out
there
in
the
world
and
then
doing
the
binding
between
those
two
things.
B
Dynamically
I
don't
know
how
the
people
have
thought
very
hard
about
that,
but
I
think
it
would
give
some
of
the
benefits
of
both
worlds.
The
explicit
instrumentation
has
some
real
benefits
to.
It
was
maintainability
I
think,
but
it's
a
bummer
to
have
to
make
code
changes
in
order
to
get
a
basic
binding
set
up
it
in
the
in
the
mainland.
A
Yeah
I'm
curious
on
that
front.
I
see
Pavel's
on
the
call
and
I
know
Pavel
you've
done
a
lot
of
work
on
out
of
configuration
for
Java
spring
and
I
was
wondering
if
you
had
any
thoughts
on
on
generalizing,
that
out
of
configuration
to
just
open
tracing
Java
in
general
and
how
feasible
that
might
be
just
to
avoid
having
to
manually
thread
together.
All
of
the
the
packages.
A
No
because
that
seems
like
half
of
when
people
talk
about
agent,
it
does
seem.
Like
then
said
it's
part
of
it
is
just
being
able
to
take
the
existing
open
tracing
packages
and
get
get
them
installed
without
having
to
write
a
lot
of
code.
It's
not
it's.
Maybe
a
separate
problem
from
then
being
able
to
dynamically
insert
call
points
or
something
like
that:
you're,
not
dynamically,
inserting
the
call
points
you're,
simply
changing
which
packages
are
involved,
and
it
would
be
an
interesting
experiment
to
see
what
what
would
be
feasible
in
Java
on
that
front.
A
So
that's
one
approach
on
an
unrelated
note,
one
higher
level,
abstraction
I
think
we
could
benefit
from
and
maybe
even
consider
baking
into
some
of
the
API
packages.
Is
we
have
these
semantic
descriptions
of
certain
common
patterns
around
RPC
calls
database
calls
things
of
that
nature,
but
when
you
want
to
go
use
them,
you
have
to
sort
of
glue
together
a
bunch
of
individual
tags
or
logs
in
order
to
to
make
that
happen,
and
one
very
simple,
straightforward
form
of
sugar
would
be
something
that
allowed
you
to.
A
You
know
that
was
a
little
bit
more
of
a
guide
on
what
you
had
to
put
in
there
so,
rather
than
having
to
refer
to
a
spec
sheet
somewhere
about
what
all
the
fields
were
you
needed
to
add
in
order
to
record
an
HTTP
call.
If
there
was
just
a
function,
you
could
call
that
had
all
the
fields
required
fields
as
a
parameter
there,
just
to
make
it
clear
and
easier
to
people
rather
than
them
having
to
do
it
themselves.
A
E
Yeah,
that's
definitely
something
that
we
were
doing.
We
have
a
span,
a
pi/4
go
that
does
that
I
wrote
that
does
that
for
database
queries
and
cache
requests
and
external
and
incoming
service
calls
an
HTTP
request.
You
know,
because
we
are
looking
for
specific
tags
and
it's
really
helpful
to
be
able
to
formalize
those
for
our
users.
I
think
that
is.
E
E
We
have
a.
We
have
a
terrible
API
for
custom
SDK,
where
you
need
to
propagate
context
between
events
and
a
span
which
is
harder
than
propagating
expands
and
then
and
then
you
have
to
actually
be
very
careful
that
you
use
the
same
tags
in
the
start
and
end
event,
for
example,
for
in
certain
cases.
So
we
do
try
to
simplify
those.
We
do
duplicate
certain
repeated
values
that
have
to
show
up
in
both
the
fence.
A
E
Yeah
I
mean
there's
basically
an
open
tracing
mapping
from
open,
tracings,
hgp
tags
to
our
internal
tags.
In
my
ot
implementation
for
go,
for
example,
and
if
there
was
something
that
came
cooked
up
from
the
OT
team,
where
there's
a
several,
you
know,
standard
helper
functions
that
people
are
using.
We
would
just
map
it
to
internal
values
that
we
index
first.
E
Yeah,
it's
just
funny,
because
every
vendor
is
probably
indexing,
each
of
the
tags
differently
right
and
so,
like
some
people,
persons
requirements
are
different,
like
the
liver
number
of
required
tags
for
a
database.
Query
is
probably
vastly
different
across
the
different
vendors.
Who
would
be
doing
this.
A
Yeah,
this
came
up
in
the
trace
context,
working
group
attempting
to
to
find
you
know
what
is
the
commonality
if
we're
gonna
have
some
common
standard
definition
of
an
HTTP
request
and
it
does
sound
like
a
noble
thing,
but
it
was
also
instantly
clear
that
everyone
had
kind
of
a
slightly
different
opinion
about
what
was
important
and
what
was
the
correct
way
to
slice
it.
So
it
might
be
a
little
bit
tricky
to
come
up
with
a
universal
standard
for
that,
so
we
are
gonna,
take
a
shot
at
it.
A
All
right:
well,
it's
it's
nine
ten!
So
we
should
probably
move
on,
but
I
do
want
to
use
this
an
opportunity
to
promote
trace
identifiers,
so
we're
gonna
make
a
PR,
hopefully
next
week,
to
Java
to
add
those
so
people
who
have
a
Java
tracer,
keep
that
in
mind.
That'll
be
a
thing
coming
down
the
pipe
and
the
hope
is
by
exposing
getters
for
trace,
ID
and
span
ID
that
make
some
of
these
middleware
and
other
higher
level
abstractions
easier
for
people
to
write
easier
to
integrate
the
tracing
call
sites
into
secondary
systems
already
using.
A
A
So
now
that
that's
out
the
door
we'd
like
to
use
it
as
an
opportunity
to
kind
of
overhaul
the
documentation
on
the
website
and
because
that's
a
little
bit
slow
going,
we
thought
we
would
have
a
sort
of
hack
day
where
we
got
together.
People
who
work
on
the
various
languages,
some
copy
editors
and
people
who,
like
writing,
documentation,
hopefully
some
end
users
as
well
to
sort
of
sit
down
as
a
group
and
just
jam
out
as
much
of
the
docs
as
they
can
so
we're
doing.
A
Some
prep
work
there
to
get
the
new
site
set
up
with
enough
scaffolding
and
kind
of
bullet,
pointed
versions
of
the
different
kinds
of
Docs.
We
think
we
need
to
see
so
people
are
operating
from
a
blank
page,
but
what
I
would
like
to
ask
is
if
people
are
interested
in
this
that
they
they
sign
up
with
signup
form,
so
I'm
gonna
post,
that.
A
Post
that
into
the
the
chat
right
there
and
to
find
people
that
you
work
with
in
your
company
who
would
be
interested
in
contributing
to
the
docs,
so
there's
people
who
either
know
how
to
write
or
people
who
know
how
open
tracing
works
and
if
we
can
get
a
good
group
together,
we're
also
going
to
try
to
get
some
documentation
at
experts
from
the
floss
community
to
kind
of
guide
us
on
this,
and
this
is
coming
right
up.
It'll
be
the
week
after
next.
If
we
don't
get
it
all
done
in
the
first
session.
A
But
we
like
this
format,
we
may
have
a
second
one,
but
put
the
word
out.
Please
so
I'll
be
announcing
this
on
Twitter
and
making
a
blog
post
and
everything
else.
But
I
wanted
to
tell
you
all
first
and
though
she's
not
on
the
call
here.
I
want
to
do
a
shout
out
to
Julie
stickler
from
Red.
Hat
who's
been
a
total
champ
in
getting
this
together.
A
A
Something
I
just
am
in
the
process
of
setting
up
for
myself
and
could
probably
share
open
tracing
wide
is
just
some
code
to
identify
stale
issues.
I
decided,
stale
issues,
for
me
mean
anything
that
is,
is
active.
That
hasn't
received
a
response
from
someone
directly
associated
with
the
project,
either
someone
from
one
of
the
language,
maintainer
teams
or
another
core
member
for
seven
days.
A
So
anything
that's
gone
more
than
seven
days
without
a
response,
but
isn't
tagged
in
some
way
as
being
on
ice
is
stale
and
then
I
want
to
make
sure
that
gets
someone
assigned
to
it
and
some
attention.
So,
if
I
get
something
that
automatically
scrapes,
all
of
that
I'll
try
to
try
to
share
it
with
you
and
others
so
that
we
can
maybe
track
it
a
little
bit
better.
A
But
beyond
that,
it
would
be
great
I
feel
like
we
have
people
who
are
interested
in
responding
and
managing
peers
and
issues,
but
the
process
for
for
deciding
who
gets
assigned
to
what
I
feel
is
still
a
little
muddy.
I,
don't
know
if
you
have
any
thoughts
on
that
EURion
like
how
we
could
clean
that
that
part
of
the
process
up
I.
F
Think
in
my
view,
the
problem
is
not
like
assigning
someone
but
actually
come
into
consensus,
because
there
is
certain,
like
I,
think
they
do
longest
pr's
they're
controversial,
and
so
we
may,
we
may
need
so
like
we
used
to
do
this
on
this
call
right.
You
just
go
to
ghost
or
some
like,
like
important
issues,
they'd
be
in
Oakland.
So
maybe
we
need
some
some
time
dedicated
where
there's
a
like
a
group
of
people
where
we
can
just
and
at
high
speed,
discuss
and
make
a
decision
on
particular
person
and
just
render
it.
B
B
The
people
who
are
responsible
for
certain
repositories
are
supposed
to
respond
to
new
comments
on
issues
or
PRS
within
a
certain
amount
of
time
and
then
and
then
that
could
just
be
an
understanding
that
if
the
discussion
is
getting
kind
of
complicated
that
you're
supposed
to
resolve
that
you
know
important
like
this
or
something
that
happens
more
frequently
than
once
a
month
or
whatever.
Excite
I,
definitely
think
that
github
is
so
horrendous
place
to
resolve.
B
Like
really
thorny
issues
that
often
take
like
ten
minutes
intervening
where
you
have
all
the
participants
and
people
can
can
actually
have
a
dialogue
about
it.
So
I
like
the
idea
of
that,
but
it
seems
to
me
that
we
we
don't
have
and
for
certain
repositories.
We
don't
have
that
kind
of
there's
no
one
who's
responsible
for
just
responding
to
new
issues
and
PRS,
and
it
gets
done
sometimes.
B
But
it's
kind
of
ad
hoc,
like
it
almost
seems
like
that,
would
need
to
happen
first
and
that
you
need
to
get
to
a
sticking
point
before
you
escalate
or
whatever.
You
want
to
call
it
to
a
meeting
like
this.
Does
that
make
sense
like
I?
Don't
I
don't
know
if
other
people
feel
that
way,
but
but
some
repositories
I,
don't
think
they're
being
watched.
That
carefully,
necessarily
that's
probably
as
much
of
an
issue
to
me
as
as
being
able
to
discuss
things
in
the
forum
like
this.
B
I
mean
I,
guess
what
I'm
saying
is
we
if
we
defer
to
every
discussion
for
like
an
in-person
meeting,
then
it'll
become
a
scheduling
problem
and
you
know
progress
will
get
made.
But
but
if
we
don't
use
these
sorts
of
meetings
to
discuss
things
that
are
difficult
over
get
help,
then
they'll
still
get
stalled
because
we
just
can't
resolve
certain
issues
very
well.
B
If
it's
just
two
people
that
are
having
discussion,
they
can
have
a
meeting
and
then
summarize-
and
you
know
not
get
what
the-
what
the
notes
order
but
but
it'd
be
great
to
avoid
some
of
these
threads
that
I've
seen
at
Trevor,
Nelson
see
like
open
tracing
or
otherwise,
where
you
have
some
issue
and
there
are
hundreds
of
messages
and
then
no
one
can
ever
come
in
and
actually
follow
the
discussion.
That's
it
just
it's
not
an
effective
experience.
A
Well,
I
have
I
two
concrete
suggestions:
I
can
make
on
that
front
one
is
we
have
a
cross
language
working
group
meeting
every
week,
it's
usually
at
this
time,
but
we
can
start
varying
the
time
up
and
that's
mostly
been
focused
on
rolling
out
API
changes
that
have
already
been
approved
and
making
sure
they
go
in.
You
know
evenly
across
the
different
languages,
but
because
that
kind
of
work
is
calming
down
with
scopes
getting
completed
and
basically
all
the
languages.
A
We
could
be
using
that
time
to
resolving
some
of
these
issues.
I
think
the
only
thing
we
want
to
make
sure
we
do
there
is,
if
we're
going
to
discuss
one
of
these
issues
on
one
of
these
calls
that
we
promoted
ahead
of
time
so
just
to
make
sure
that
the
people
actually
care
about
that
are
actually
gonna
show
up
to
the
call,
because
it
doesn't
make
a
lot
of
sense
to
have
a
call
and
make
a
decision
and
then
have
someone
who
cares
be
like
I
object
and
they
weren't
there.
A
The
other
thing
I'll
say
when
there's
a
log
jam
in
the
past,
especially
around
API
changes,
something
that
I've
found
is
it
usually
means
the
English
language
has
ceased
to
be
specific
enough
and
a
lot
of
these
sort
of
long
tail.
Discussions
are
about
issues
that
maybe
they're
important.
Maybe
they
aren't
people
are
talking
past
each
other
and
when
we've
switched
from
English
to
to
code
and
tests,
that's
done
wonders
for
kind
of
clearing
up
a
lot
of
this.
A
We
really
saw
this
with
scopes,
where
it
just
seemed
impossible
to
come
to
conclusions
about
what
was
a
serious
issue
or
whether
this
API
was
gonna
work
in
this
scenario
or
that
scenario
and
just
switching
to
code.
Examples
and
tests
really
broke
the
logjam,
and
all
of
that.
So
that
would
be
my
other
suggestion
when
things
seem
to
be
getting
too
long.
Just
ask
people
to
to
actually
start
writing
code
to
explain
their
point
rather
than
continue
to
debate
it
in
English.
A
A
Great
well
looking
forward
to
seeing
some
of
you
at
monitor,
amma
next
week
and
for
the
rest
of
you.
Hopefully,
you
show
up
for
da
q.
Thon
I
am
gonna,
keep
keep
poking
everyone
on
that
front.
So
give
me
a
shout
out
if
you're
interested
in
organizing
an
in-person
meet
up,
we're
gonna
have
one
in
San
Francisco
another
one
in
Boston
and
another
one
in
Munich,
so
one
in
Portland
wants
to
organize
one
or
elsewhere.
Let
me
know,
and
yeah
I'll
see
you
all
on
the
Internet.
Is
there
chasing
meet
up
at.
A
You
know
I
asked
I
asked
on
slack,
and
people
wanted
to
do
that
and
I
haven't
gotten
much
response
I'm
happy
to
host
it.
I
think
the
way
we'd
probably
want
to
do
it
this
year
is
just
go
to
a
coffee
shop
or
something
nearby.
If
people
want
want
to
do
it,
but
if
you're
interested
yeah,
please
log
into
the
web,
monitor
I'm
slacking
and
make
a
post
there
I
feel
like
we
sort
of
got
away
by
just
bringing
a
bunch
of
food
in
and
taking
over
some
space
at
the
venue
last
year.
B
Mean
I
think
people
were
fine,
but
the
venue
I'm
positive
as
they
found
out
that
we
were
doing
that,
would
have
been
really
upset,
like
I
learned
afterwards
that
that
was
really
bad,
so
I
feel
a
little
bit
like
I.
Don't
know
it
doesn't
seem
super
superduper
or
moral
or
ethical
or
something
to
knowingly
and
last
time
I
ignorant
lee
did
that.
But
this
time
it
be
knowingly
senescent.
We
do
that.
I
actually
can't
be
there
for
family
reason.
B
I,
don't
know
maybe
Erica
when
the
New
Relic
people,
if
there's
some
space
in
Portland,
that's
like
close
to
that
University
that
could
post
if
I
check
last
year
and
like
the
public
spaces
are
not.
That
close
are
not
that
good
for
something.
So
that's
why
I
tend
to
think
that
coffee
shop
might
make
more
sense
than
anything
else.
B
G
A
Yeah
hard
I
can
tell
this
stuff
mostly
gets
organized
through
slack
on,
monitor
AMA,
but
I'm
totally
happy
to
have
one
again.
It
would
be
lovely
to
see
you
all
and
talk
shop
on
tracing.
So
you
know
it's
just
a
couple
of
us.
Yeah
there's
grab
breakfast
on:
let's,
let's
just
call
it
Tuesday,
Tuesday
or
Wednesday
for
the
same
for
Tuesday
and
see
if
that
works
great.