►
From YouTube: Cloud Native Live: OpenTelemetry community demo
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
Foreign
Welcome
to
Cloud
native,
live
where
we
dive
into
the
code
behind
Cloud
native.
My
name
is
Taylor
dolezal
and
I'm
head
of
ecosystem
at
the
cncf,
where
I
get
to
work
closely
with
teams
as
they
navigate
their
Cloud
native
Journeys.
Now
every
week
we
bring
a
new
set
of
presenters
to
Showcase
how
to
work
with
Cloud
native
Technologies.
They
will
build
things,
they
will
break
things
and
they
will
answer
your
questions.
A
In
today's
session
we
have
Pierre
Tessier
from
honeycomb,
and
today
Pierre
will
be
presenting
the
open,
Telemetry
Community
demo
I'm
really
excited
to
see
all
the
things
that
come
out
of
the
open,
Telemetry
demo.
Today
myself.
Personally,
this
is
an
official
live
stream
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct,
please
don't
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
A
Basically,
please
be
respectful
to
all
of
your
fellow
participants
and
presenters
be
excellent
to
one
another
with
that
I'd
love
to
hand
it
over
to
Pierre
to
kick
off
today's
presentation
and
with
that
Pierre.
Please
take
it
away.
B
Awesome,
thank
you
very
much
Taylor.
My
name
is
Pierre
Pierre
teste
at
honeycombio.
I'm
I'm
really
excited
to
talk
about
this
topic
coming
here
today.
It's
it's
something!
That's
been
consuming
much
my
free
time
and
just
just
a
lot
of
thoughts
and
process
and
for
the
past
several
months,
but
it's
coming
for
which
it's
coming
to
Fortune,
really
nicely
I'm
going
to
talk
about
the
state
of
today.
So
early
October,
2022
I'm,
going
to
talk
about
where
we're
going
with
this
and
what's
happening
with
the
open
television
demo
itself.
B
If
you
have
not
heard
about
it
before
well,
what
is
this
state?
It's
it's!
It's
really,
a
Showcase
of
everything
open
Telemetry
has
to
offer
for
the
community
out
there
how
to
use
it
where
to
use
it
properly
different
combinations
of
usage.
You
could
get
out
of
it.
What
we
did
is
we
took
a
12
microservice
application
written
across
10
different
languages
and
we're
going
to
show
you
how
to
deploy
this
thing,
how
it's
instrumented,
it's
meant
to
be
rendered
and
forked.
B
If
you
will
there's
a
lot
of
vendors
that
are
part
of
the
open
television
Community.
That's
what
helps
keeps
it
going?
We
have
employers
that
are
grateful
to
provide
us
with
the
way
to
contribute
to
Over
The
Wider
Community
use.
Well.
These
vendors
also
want
to
show
off
what
they
can
do
with
open
Telemetry,
and
this
demo
is
meant
to
be
forked,
so
they
can
do
exactly
that.
B
We
do
have
our
own
GitHub
repo.
Of
course
we
do.
It's,
like
all.
The
demon
G6
go
ahead
and
check
it
out
and
we'll
check
on
that
a
little
bit
more
later,
but
I
want
to
showcase
what
this
thing
really
is.
It's
looks
like
this.
It's
like
I,
said:
it's
got
12
different
services
in
here,
a
couple:
different
storage
locations
as
well
uses
reddits,
which
we
don't
count
as
one
of
the
services
and
also
a
postgresdb
again,
not
counted
and
I'm.
B
Saying
actually
I
mean
it's
13
Services
I
keep
on
saying
12,
because
I
don't
count
the
load
generator
as
a
service
per
se,
but
it
is
in
this
case
here,
and
so,
if
you
look
at
all
the
boxes,
you'll
count
13
up
coming
up
here.
Internet
should
not
count
to
either
neither
does
load
it
generally.
B
If
you
want
to
get
to
your
12
but
and
we've
written
across
all
these
languages,
the
only
ones
that
kind
of
duplicated
front
end
payment
on
JavaScript,
but
it's
it's
fun
front,
end's,
actually
written
in
typescript
and
payment
is
written
in
JavaScript.
So,
although
it's
written
the
same
kind
of
output
compiled,
if
you
will
run
time
the
interpretive
language,
they
do
showcase
a
little
bit
of
this
syntax.
Differences
between
the
two
I
also
want
to
mentioned
front
end
also
instruments
the
web
browser.
B
So
if
you
came
in
here
as
a
front-end
developer,
like
man,
everybody
went
into
the
web
browser
I
got
you
covered.
We're
gonna
show
how
we
do
this
later
on
today,
and
then
we
move
on
to
the
other
languages
across
the
whole
gamut,
notably
missing
here
is
Swift.
B
We
do
one
day
want
to
add
a
swift
client
to
this
application,
to
make
it
even
better,
and
we're
also
going
to
be
looking
for
a
host
to
provide
this
application
for
people
to
use
without
having
to
install
them
as
well.
So
that's
coming
soon
plans
for
that
to
be
determined.
B
If
you
want
to
help
out
here,
I'll
get
more
info
on
how
you
can
reach
out
to
us
and
do
exactly
that
and
with
that
who
am
I
really
I
work
for
a
honeycomb
IO
I
I
run
the
solution
Architects
team
over
there.
That's
a
team
of
people
who
are
passionate
about
ensuring
that
other
customers
instrument
their
code,
get
up
and
running
mostly
with
open,
Telemetry
and
get
the
observability
they
need
for
their
applications.
Honeycomb
Mayo.
B
We
are
very
much
committed
to
supporting
open
Telemetry
and
we
support
all
the
various
endpoints
for
receive
traces,
metrics
and
logs
into
our
platform
allowed
to
provide
what
you
need
to
do
to
debug
your
applications.
So
they
go
sour
in
production
or
maybe
you
just
want
to
find
performance
improvements.
So
we
help
you
do
that
and
also
I'm
a
maintainer
on
the
open,
Telemetry
secret
itself.
I've
been
part
of
the
Sig
since
it
started
and
really
happy
to
be
part
of
that
through
the
contributions
that
we
do.
B
The
sick
was
formed
April
26
this
year
we
had
our
first
meeting
on
May
2nd
and
you
know
I
think
Carter
might
be
watching
right
now,
if
Carter
from
Microsoft
are
he's
been
instrumental,
really
kind
of
kicking
us
off
and
getting
going
and
helping
us
move
this
project
along
and
meeting
our
dates
and,
most
importantly,
here-
we're
going
to
hit
I'm
very
confident
we're
going
to
release
GA
at
the
end
of
this
month,
the
week
of
cloud
nativecon
cubecon.
B
B
Thanks
to
another
one
of
our
contributors,
Giuliano
who
took
the
Google
Google
Cloud
project,
it
was
known
as
microservices
demo
people
knew
at
his
hipster
shop
or
online
boutique.
He
took
that
kind
of
ripped
out
all
the
old
instrumentation,
all
the
other
stuff
and
got
us
the
first
cut
of
this
running
with
open
Telemetry.
So
we
could
use,
but
we
took
that
and
refined
it.
We
made
it
idiomatic
and
ultimately
we're
going
to
be
releasing
1.0
here
shortly.
B
B
It
wasn't
just
vendors,
it
was
people
and
and
other
developers
that
were
spitting
up
these
little
mini
hello,
world
applications
or
maybe
they're
using
some,
some
other
applications
or
some
other
microservices
things,
and
it
was
getting
kind
of
just
fragmented
out
there
and
they
were
doing
it
a
little
bit
differently.
B
Orbitometry
is
a
very
evolving
stack
of
Technologies
right.
It
spans
multiple
languages
and
they're
all
kind
of
evolving
at
their
own
pace,
and
sometimes
they
they
change.
How
you
should
do
things
and
all
these
demos
were
not
necessarily
keeping
up.
So
we
wanted
to
create
something
that
kept
up
at
the
latest
and
was
common
across
them
all
right,
and
we
wanted
to
make
sure
it
includes
every
single
language
that
open
telemachi
has
support
for
we're
one
short
right
now:
Swift,
we
will
get
there,
but
we
do
support
the
entire
ecosystem.
B
It's
got
to
be
using
the
latest
stuff.
Like
I
said
earlier,
it's
really
important.
We
do
that
and
I
think
the
biggest
Point
here
that
everybody
should
appreciate
it
needs
to
be
well
documented.
B
B
We
need
to
enable
the
community
with
this
demo
and
how
you
do
that
is
with
good,
strong
documentation
and
that's
really
one
of
our
big
goals
that
we're
going
to
do
when
we
release
eventually
a
couple
of
stats
and
I
really
carrying
this
with.
As
of
this
morning,
the
repo's
got
150
stars,
95,
forks
and
34
awesome
contributors.
B
We
just
cut
release
5-0
or
5.0
Alpha.
Yesterday,
I'm,
not
no,
it
says
Alpha
I,
don't
know,
maybe
we're
ready
to
drop
that
label
and
call
it
beta,
and
so
we
now
have
all
services
ready
and
kind
of
nearing
feature.
Freeze
here
you
could
use
it.
It
works.
I
may
show
you
the
small
little
caveats
of
deploying
this
thing
later
on
in
the
session.
It
works
across
a
whole
gamut.
B
So
definitely
don't
be
scared
that
Alpha
label
right
now,
if
you're
interested
and
after
you
see
all
this
they're
like
wow
I,
want
to
help
weaknesses,
we
meet
every
Monday
at
8
15
a.m.
Pacific
time
again,
the
repo
link
we
do
have
our
own
slack,
Channel,
otel
Community
demo,
is
a
slack
channel
in
case
you
haven't,
figured
it
out
yet
we're
looking
for
Swift
developers.
We
want
to
do
this.
B
We
don't
have
anybody
who
will
experience
in
this
and
we're
really
looking
for
perhaps
a
swift
developer
who
can
help
us
do
this
bill?
Does
a
small
app,
let's
get
it
in
the
App
Store
and
let's
allow
people
to
actually
play
with
this
and
we'll
have
them
point
to
a
hosted
version
of
the
demo
itself.
It'll,
be
great,
people
could
actually
use
their
phone
and
and
work
with
this
demo
and
see
the
code
how
it
all
works.
B
So,
if
you're
interested
you
write
Swift
code,
please
reach
out
to
us
we're
happy
to
help
them
and
provide
you
whatever
support
you
need
to
get
going
now
with
that,
what
did
we
do
in
the
code?
What
did
we
actually
instrument
so
first
off
when
we
did
this
instrumentation?
B
We
really
wanted
this
to
be
in
an
idiomatic
way
for
every
single
language,
and
that
was
really
important
for
us.
It's
just.
We
want
to
make
sure
that
when
people
look
at
the
code
inside
this
demo,
that's
the
right
way
to
do
it.
If
you
were
to
go
to
open
Telemetry
docs
and
you
were
to
go
to
copy
and
paste
code,
it
should
drop
right
into
what
we
have
inside
our
demo.
B
That's
the
idea
and
as
the
sdks
evolve,
as
they
perhaps
add,
additional
apis
and
functionalities
to
allow
you
to
tie
in
and
and
make
it
easier
to
use
we're
going
to
update
the
demo
code
to
stay
in
conjunction
with
whatever
is
available
in
the
rest
of
the
open
television
community,
and
this
will
be
the
proper
way
to
instrument
and
we're
going
to
keep
on
doing
that.
B
So
you
could
be
rest
assured
that
what
you
see
in
this
demo
will
be
hopefully
we'll
we'll
be
how
we
want
you
to
move
forward
with
it
and
how
to
use
open
television
to
best
advantage.
B
I
see
here
a
link,
somebody's
asking
for
that
link
and
chat
for
the
repo
I'm
gonna
post.
It
there
in
a
couple
minutes.
Just
give
me
a
couple
seconds
and
we're
going
to
run
through
more
stuff
and
I'll,
make
sure
I
get
you
all
the
links
when
we
get
going
for
the
repo
itself.
B
Sorry
here
here
we
go
so
when
did
we
do
in
cement
well
for
traces
all
languages
support
Trace,
so
they
all
have
tracing
support.
We
do
auto
instrumentation
we're
available,
so
Java
python
note
is
kind
of
a
weird
thing.
People
call
a
lot
of
information.
People,
don't
I,
don't
know
where
you
want
to
sit
on
that
world,
but
we
didn't
okay,
it's
pretty
easy
to
do
with
node
and
all
languages
also
have
manual
spans.
They
will
have
all
have
manual
spam
attributes.
B
Almost
all
languages
have
Spanish
Services
have
spam
events
actually
I.
Believe
all
services
do
do
spanned
events
somewhere
there,
maybe
Elixir
might
be
the
only
one.
We
don't
do
that
for
I'll
have
to
double
check,
and
we
also
include
spam
links,
and
we
only
did
this
for
one
spot,
notably
in
the
front
end,
but
we
want
to
introduce
a
concept
and
why
you
would
need
to
use
a
span
link
to
make
sure
people
understood
why
we
kind
of
did
that
for
metrics.
B
We're
going
to
have
javagon.net
with
our
GA
release
is
the
goal
we
have
a
stretch
goal
to
also
include
python,
though
we're
a
little
dependent
on
that
SDK
for
us
there
so,
like
I,
said
we're
keeping
up
with
what
the
sdks
are
doing
for
each
language
and
as
they
GA
their
support
for
metrics.
We're
going
to
go
ahead
and
add
that
in
as
well
for
all
these
metrics
we're
going
to
include
the
runtime
metrics
available
to
us
so
like
jvm,
you
get
Heap,
metrics,
threads
and
stuff
like
that.
Go
you
get
like
go
routines,
I.
B
Think
we're
also
going
to
include
on
the
HTTP
grpc
endpoints,
we'll
include
all
the
latency
distributions
for
every
one
of
them,
like
kind
of
your
typical
things
and
and
we're
going
to
get
this
dumped
into
a
Prometheus
another
cncf
technology,
so
it'll
go
into
Prometheus
and
then
we're
going
to
be
able
to
provide
you
with
a
grafana
dashboard
to
visualize
it
all
part
of
that
same
package.
Traces
are
going
to
end
up
going
to
a
jagger
that
gets
deployed
part
of
this
demo
as
well.
B
So
you
could
use
that,
but,
like
I
said,
because
we
made
this
very
vendor
Fork
friendly,
it's
easy
for
you
to
pipe
your
output
to
somewhere
else
I'm
at
honeycomb
I'm,
going
to
show
you
how
to
do
it
for
a
honeycomb,
but
look
it's
the
same
process.
You
want
to
dump
into
light
step
or
if
you
want
to
use
splunk's
way
of
doing
it
or
even
data
or
any
of
the
other
vendors.
It's
all
going
to
be
very
similar
in
how
you
get
the
data
out
to
them
from
this
demo.
B
Now
one
more
thing
we
wanted
to
add-
and
this
is
a
tricky
one-
it's
context
propagation,
it's
important
very
important
tracing
to
do
this,
so
all
the
trace
headers
will
propagate
properly
kind
of
already
do
it.
For
you
out
of
the
box,
some
languages
like
go,
you
gotta
explicitly
configure
it
but
baggage.
B
This
is
an
often
perhaps
often,
but
it
is
a
discussed
topic
and
even
when
we
were
discussing
it
in
in
our
Sig
meetings,
it
turns
out
that
a
lot
of
people,
perhaps
don't
use
baggage
the
way
it's
supposed
to
be
used
it.
If
you
don't
know
what
baggage
is,
baggage
is
a
way
for
you
to
pass
at
a
Telemetry
level,
additional
context,
additional
information
about
that
request.
B
Unfortunately,
some
people
perhaps
are
using
this
to
actually
pass
additional
parameters
to
the
request
itself
and
use
it
Downstream,
and
that's
not
the
right
use
of
baggage.
You
should
be
modifying
your
procedure
calls
instead
passing
that
exit
parameter
properly
when
you're
calling
the
various
Services
don't
attach
it
to
your
telemetry.
B
What
your
touch
and
baggage
should
be
context
to
affect
your
Telemetry
itself,
so
we
use
that
and
in
baggage
all
requests
coming
from
the
low
generator
will
be
marked
synthetic,
and
then
we
handled
this
later
on
in
the
front
end
to
understand
what
to
do
with
the
trace.
We
actually
break
the
trace
up
in
the
front
end.
If
it's
a
synthetic
Trace,
we
continue
that
baggage
down
to
to
alert
the
rest
of
the
downstream.
B
B
If
you
come
in
from
the
the
UI
the
browser
itself,
that
won't
be
an
issue,
you
won't
see
that
broken
up
stuff,
you
won't
see
the
synthetic
stuff
at
all,
and
maybe
don't
do
the
baggage
stuff,
so
proper
use
of
baggage
kind
of
want
to
encourage
people
to
don't
use
baggage.
To
do
things
that
you
should
be
doing
in
your
procedure.
Call
signatures
instead
use
baggage
to
influence
your
Telemetry
and
that's
what
we
want
to
do.
B
Also
all
metrics
will
include
Trace
exemplars,
where
appropriate,
so
you
could
use
those
in
any
platform
that
supports
them
with
that.
Let
me
check
real
quick
here.
If
there's
any
more
questions
here
in
the
chat,
I
see
Taylor.
Thank
you
for
dropping
in
the
link
to
the
repo
in
there.
B
This
is
all
Engineers
open,
Telemetry,
QA,
Engineers,
devops,
The,
Operators
developers,
platform,
Engineers
sres.
We
all
benefit
from
additional
Telemetry
in
our
production,
apps
and
open
Telemetry
is
made
to
do
that
so
that
you
could
send
it
to
whatever
tooling
you
have
to
understand.
What's
running
in
production,
doesn't
even
work.
So
one
use
case
I
like
to
use
often
with
open
television
when
it
comes
to
distributed
tracing
in
particular,
and
when
you
add
the
right
context,
is
you
can
find
those
really
gnarly
bugs?
B
You
know,
I
I
say
this
often,
but
things
like
maybe
iOS
version
14.1
using
the
French
language
pack
located
in
Germany
and
that,
for
whatever
reason,
has
a
problem
loading
the
resources,
because
last
week
somebody
made
a
change
to
the
resource,
loader
open
Tillman.
She
provides
you
the
context,
and
if
you
have
the
right
Tooling
in
place,
you
could
find
those
kinds
of
really
gnarly
bugs
in
your
applications.
B
So
moving
on,
let's,
let's
get
talking
about
deploying
the
actual
open
television
demo
itself
so
part
of
this.
We
wanted
to
make
it
really
really
easy
to
deploy.
It
is
a
microservices
application,
so
we
got
to
think
about
how
do
you
deploy
a
lot
of
things
together.
B
Have
two
choices
here:
when
it
comes
to
containerizing
stuff,
you
have
Docker
and
kubernetes.
We
provide
both
Avenues
there's
a
lot
of
services
in
here.
So,
if
you're
just
going
to
spin
this
up
in
Docker,
you
need
to
configure
Docker
to
have
at
least
eight
gigabytes
of
memory.
You
could
probably
get
away
with
six,
but
I
don't
recommend
it,
give
it
give
it
memory.
Okay,
your
money,
13
services,
it's
not
a
13
plus
redis,
plus
a
post
stress,
so
really
you're
running
15
containers,
plus
the
open
television
collector
16
containers.
B
To
make
this
thing
work.
You
know,
make
sure
you
have
the
memory
for
it.
It's
simple
get
clone
CD
into
the
folder
and
the
docker
compose
up.
If
you
do
not
pass
in
order
to
build,
this
could
take
up
to
up
and
above
20
minutes
to
build
if
you're
building
it
all
from
Source,
it
will
take
a
while
it's
working,
it's
just
going
to
turn
away
for
a
while.
Definitely
something
you
want
to
run
before
you
head
out
for
lunch
and
come
back.
B
We
provided
a
way
where
we
give
images,
we
publish
images,
so
you
can
build.
So
you
can
run
this
without
having
to
go
build
the
images
yourself
patches
and
you
know,
build
flag
and
you'll
get
the
latest
images
that
we
published
to
to
spin
up.
I
want
to
also
really
strongly
note
here.
This
is
Docker
space
compose,
not
Docker.
Dash
compose
Docker
made
a
change
in
how
compose
works
and
they're
effectively
deprecating
Docker
Dash
compose
compose
is
now
part
of
the
docker
binary
itself.
B
Docker
space
compose.
There
are
new
features,
part
of
this
that
we
take
advantage
of
inside
of
this
demo,
so
you
have
to
use
Docker
space
compose
otherwise
that
you
may
get
an
error.
B
Docs
matter
right,
I
said
earlier:
we're
going
to
well
document
everything.
There
are
documents
about
this
as
well.
Within
the
actual
repo
itself
under
kind
of
docs
holder,
you'll
see
a
deployment
for
Docker
there.
B
We're
gonna
do
this
in
a
little
bit
I'm
going
to
show
it
off
how
we're
going
to
do
it.
We're
also
going
to
do
this.
This
is
really
great.
You
need
some
3.0
I,
don't
know
what
version
of
kubernetes
you
need.
I'm,
sorry,
I,
don't
think
we
do
anything
special,
so
you
could
probably
go
way
back
in
kubernetes
days
and
it'll
still
work,
though
you
should
be
writing
the
supported
version
at
this
point.
B
Anyhow,
repo,
if
you
have
not
already
done
so
and
then
tell
them,
install
the
actual
demo
itself
and
its
default
settings
we'll
get
it
up
and
running
for
you
when
the
install
is
done.
It'll
give
you
a
couple
commands.
You
could
use
to
do
Cube
cuddle
proxy
to
port
forward
the
right
Port,
so
you
can
actually
access
the
demo.
B
Another
option
is
you
can
deploy
Ingress
routes
if
you
want
to
so
you
could
provide
a
way
for
you
to
access
that
demo
through
a
web
browser.
The
home
chart
does
have
several
configuration
options.
There
is
also
currently
as
of
right
now,
a
very
tiny
bug
in
the
home
chart
and
that
the
email
service
will
not
export
its
spans
by
default.
We're
aware
of
it.
B
We've
just
found
it
this
morning,
I'm
confident
team,
we'll
have
a
PR
we'll
have
that
fixed
shortly,
I'm
going
to
show
you
how
to
get
around
it
today,
but
I'm
going
to
guess
by
the
end
of
this
week,
it'll
be
it'll,
be
resolved
because
we're
pretty
fast
moving
on
this
whole
entire
world.
B
So
I've
done
a
lot
of
talking
a
lot
of
theory.
I
guess
I'm
done
with
my
slides.
This
is
not
for
me
to
talk
to
ebooks
live
I.
Just
want
me
to
show
you
how
to
do
this
stuff
and
how
to
run
it
in
code
and
take
a
look
at
it
before
I.
Do
that
if
there's
any
kind
of
wild
questions
or
anything
like
that,
please
drop
them
in
the
chat.
B
I'll
keep
an
eye
on
chat
here
moving
forward,
but
let's
go
ahead
and
dive
in
what
this
thing
actually
is
so
first
off
this
is
the
repo
for
it
right
here.
I,
it's
already
been
linked
from
a
kind
of
structure
perspective.
Our
readme
is
really
just
that
same
service
map
you've
seen
earlier
with
with
the
legend
and
links
to
again
documentation.
We're
really
all
about
the
docs.
B
Here
and
all
of
these
links
are
all
contained
within
this
docs
folder
up
here
inside
of
this
docs
folder
got
some
screenshots,
you
got
our
deployment
stuff,
we're
gonna,
have
feature
flags,
and
this
you
might
have
seen
the
feature
flag
service
running.
The
idea
here
is
we're
going
to
introduce
some
scenarios
where
they
can
break
now
by
default.
The
feature
flags
are
all
disabled.
B
You
have
to
actually
go
into
the
feature
flag,
UI
and
enable
them
yourself
or
perhaps
modify
a
fork
where
you
just
enable
it
in
your
fork,
foreign,
so
things
that
are
coming
out.
You
can
understand
them
right
now.
We
Define
two
feature
Flags,
although
just
one
of
them
actually
does
anything
we're
working
on
it.
We'll
get
more
we're
going
to
build
up
some
more
scenarios
in
here,
some
more
breaking
ways.
B
If
you
will,
if
anybody's
running,
wondering
we're
just
the
future
flag
service
has
written
by
Tristan
for
those
of
you
who
know
who
he
is
in
the
community
and
elixir
of
course,
because
that's
what
he's
wonderful
at
it's
a
pretty
simple
Phoenix
application
and
elixir,
and
it
just
serves
up
some
flags
and
writes
them
through
Ecto
I,
believe
it's
called
into
a
postgres
DB.
We're
gonna
actually
look
at
this
Eli
here
in
a
little
bit.
B
Other
parts
of
this,
of
course,
that
DACA
deployment
talk
about
the
kubernetes
deployment
and
and
I
like
to
talk
about
these
two
tables
right
here.
I'm
gonna,
start
off
with
the
trace
service
features.
First
off
I'm,
really
proud
of
this
table.
We've
actually
accomplished
all
of
our
goals
in
terms
of
tracing
coverage,
thus
far
because
we
don't
see
any
more
construction
signs
anywhere
on
this
table.
We
we
can't
do
certain
things
like
for
C,
plus,
plus
and
Russ.
B
There
are
no
instrumentation
libraries,
so
we
don't
do
those
so
and
we
just
didn't
do
manual
spans
in
this
go
service
down.
B
Go
service
up
there,
it's
kind
of
all
that
those
things
are
and
we'll
talk
about
where
the
RPC
context
propagation
doesn't
exist
for
you,
so
you
got
to
manually,
specify
and
go
in
C,
plus
plus,
again
and
again.
I
mentioned
where
we
do
the
span
links
as
well
as
baggage
stuff
and
I'll
show
you
how
that
all
that
works
later
on
for
metrics.
The
coverage
is
much
lower
right
now
we're
working
on
it
as
we
speak.
There
are
PR's
available
to
get
stuff
of
this
done.
B
I
am
actually
looking
at
this
table
and
maybe
not
quite
as
up
to
date.
So
we'll
make
sure
we
clean
this
up
here
moving
forward,
but
that
is
our
goals
to
to
make
all
the
construction
science
go
away,
either
replace
them
with
completed
or
we're
just
not
going
to
do
it
for
any
particular
reason.
B
With
that
I'm
going
to
drop
into
the
last
one
here
and
we're
going
to
do
this
for
any
manual
tags
as
well.
Part
of
this
is
you're
going
to
add
attributes
manual
attributes.
B
The
thing
about
distributive
tracing
is
that
you
get
good
value
with
automated
instrumentation
libraries
and
automatic
trace
and
instrumentation,
but
where
you
get
a
lot
of
value
where
you
go
over
that
Chasm
and
really
benefit
from
it
is
when
you
all
add
context
from
your
application,
which
only
you
know
as
the
developer
I
believe
there
is
an
Otep
right
now
that
should
say
all
of
your
own
contacts
should
be
prefixed
with
app
dot.
B
We
did
that
here
in
our
demo,
so
everyone
around
attributes
start
with
app
Dot
and,
although
it
may
seem
like
it's
app
dot
service
name
and
an
attribute
name,
that
is
not
of
this.
It's
app.context
of
what
this
thing
is
and
where
it
comes
from,
and
these
are
the
ones
that
ad
service
will
add.
These
are
the
ones
that
cart
service
lab.
So
you
see,
cart
adds
up
about
product
at
the
product.id
and
that's
kind
of
a
a
schema
that
works
well
with
many
organizations.
B
B
B
B
B
So
what
are
those
URLs
if
you
will
I've
got
them
all
bookmarked
underneath
my
thing
right
here,
but
you
know
what
we
documented
them
for
you
as
well
and
they're
all
available
right
here,
oh
I'm,
sorry
I
went
to
the
wrong
spot.
I
want
to
go
to
my
Docker
deployment.
A
B
B
Let's
go
look
at
what
it
is.
First
off
so
I'm
gonna
go
to
the
demo
app
I'm,
actually
going
to
create
a
new
tab
here
and
we're
going
to
go
to
the
demo
app-
and
this
is
it
right
here.
It's
if
you've
seen
online
boutique
from
Google
Google
Cloud
project
might
seem
a
little
familiar
and
I
want
to
say
this.
One
has
been
Rewritten
I
want
to
call
out
to
Oscar
Reyes,
who
rewrote
the
entire
front
end
and
xjs
gave
it
a
gorgeous
modern
touch
to
it.
B
It's
now
an
Spa
contributor
now
he's
part
of
our
team
he's
on
all
our
Sig
meetings,
really
phenomenal.
The
work
that
was
done
here
for
this
he's
also
done
other
stuff
for
us
to
do
integration
testing
but
I'm
particularly
really
proud
of
this
gorgeous.
Looking
guy
we
got
here,
you
can
see
the
open,
Telemetry
inspired
it's
you
know
products
if
you
will
I'm
going
to
go
ahead
and
just
click
on
one
of
these
I'm
going
to
add
a
chunk
load
of
these
I'm
Canadian.
B
So
let's
go
ahead
and
find
the
Canadian
currency
code.
I
got
super
cheap
Adam
to
cart.
You
can
see
them.
I'll
make
a
2400
purchase,
no
big
deal,
I'm
sure
there
will
be
okay
with
that,
but
we're
off
and
I've
generated
data
inside
of
my
environment
now
same
time.
We're
also
generated
through
a
load
generator.
So
I
didn't
need
to
do
all
that
stuff.
I
could
go
ahead
and
go
find
my
choices
if
I
wanted
to,
but
remember
I
said
we're
running
a
load
generator.
So
we
could
go.
A
B
Okay,
I
got
13
Services
going
on
here.
Here
are
all
the
various
Services.
You
want
to
look
at
I'm
just
going
to
pull
up
the
front
end
and
I'm
going
to
look
for
particularly
the
place
order.
Endpoint
place
order
hit
a
lot
of
services,
it's
probably
the
the
the
one
route
that
does
the
most
things
throughout
the
entire
thing.
So
go
ahead
and
find
traces
on
that,
and
you
can
see
here.
I've
got
49
spans,
56
fans
depending
on
them.
B
Some
of
them
will
place
more
products
in
there
than
others,
and
there
you
go.
I've
got
my
Trace,
it's
all
up
there
and
running
and
at
the
same
time,
I'm
also
setting
this
data
to
Honeycomb,
because
I
said
remember.
This
is
meant
to
be
vendored,
so
I'm
going
to
show
off
what
the
vendoring
looks
like
to
make
this
happen
in
the
honeycomb,
and
you
might
have
been
looking
right
here
and
you
might
have
seen
it
earlier
now
inside
of
every
repo
they're
I
encourage
if
you're
a
vendor
Fork.
B
This
thing
right
now
go
and
Fork
it
right
away.
Just
work
that
repo
go
inside
of
source
Hotel
collector.
There's
a
file
here
called
otel
config
extras
I'm,
going
to
give
this
file,
so
you
can
see
what
I've
done
to
it
differently
and
basically
it's
the
whole
file.
I've
disc
it,
okay,
I've
completely
replaced
the
whole
file.
The
idea
here
is
this
is
any
additional
configuration
you
need
to
send
this
to
Honeycomb.
B
Yes,
that
is
my
API
key
right
there.
That's
okay,
I'm
gonna,
delete
this
API
key
when
we're
done.
If
you
use
it,
it's
going
to
send
data
to
like
a
demo
team
that
we
have
in
honeycomb
it's
fine,
but
this
is
your
configuration.
B
So
if
you're
a
vendor,
you
know
add
in
whatever
it
is
that
you
need
to
do
to
send
your
data
into
it
or,
if
you're,
just
wanting
to
build
some
cool
stuff,
and
you
want
to
use
it
in
your
own
little
thing
go
ahead
and
configure
this
make
sure
you
add
your
exporters
into
the
pipelines
right
now.
B
We
only
have
a
metrics
and
traces
pipelines
to
find
and
you're
done
and
we'll
merge
that
with
the
the
prior
one
I
do
want
to
note
that
merging
configs
Maps
merge,
arrays
overwrite,
so
I
have
to
re-specify
the
entire
exporters.
All
the
options
in
exporters
here
here,
I'm,
not
respecting
Prometheus
I,
could
have
probably
should
have.
B
But
it's
it's
something
to
note
there
when
you
are
doing
these
config
merges
is
that
the
maps
will
merge,
but
the
array
elements
will
be
overwritten
and
that's
just
the
nature
of
merging
ammo,
and
you
also
see
several
outputs
here
by
console.
That's
a
load
generator
hitting
this
thing
all
the
time.
B
A
B
Me,
the
traces
there
Trace,
Dot
parent
ID,
does
not
exist.
That's
a
fancy
way
and
how
do
you
call
them
to
say?
Give
me
all
the
roots
I'm
going
to
group
this
by
route
or
and
run
that
query,
and
we
get
them
all
right
here.
I,
probably
only
care
about
these
checkout
ones,
so
I'm
just
going
to
filter
on
checkout
right
here
and
I
did
that,
because
these
are
usually
the
the
best
looking
traces
that
we
get
out
of
this
whole
platform,
and
you
can
see
it
right
here.
B
It's
called
all
the
different
services,
all
the
various
stuff
and
how
it
works
right.
We
get
spam
events
on
these
things.
This
one
here's
got
several
span.
Events
on
it,
for
example,
so
receive
get
quote,
request
processing
it.
You
see
this
man
events
right
there,
because
this
thing
came
from
the
front
end.
It's
also
got
a
Spam
link
to
it
span.
Link
is
really
just
going
to
give
me
back
a
low
generator
Trace
that
started
this
off.
B
So
you
kind
of
get
a
sense
of
what's
going
on
and
where
and
yeah
we've
got
all
the
data
flowing
into
honeycomb.
That's
pretty
cool,
it's
really
easy
to
get
going
with
that.
Now,
I'm
gonna,
stop
this
Docker
one
and
we're
gonna
do
the
same
thing
again
so
the
same
environment
but
in
kubernetes.
So
just
give
this
a
second.
This
is
the
cncf
live
stream.
We
love
coding,
one
beautiful
thing
about
coding
is:
sometimes
we've
got
to
wait
for
the
things
to
do
their
things
and
you
know,
is
ready.
My
Jeopardy
music.
B
B
This
is
my
Helm
configuration
some
of
you
who
are
familiar
with
Helm.
You
can
pass
in
value
files
when
you
install
a
component
instead
of
passing
in
set
in
like
a
bunch
of
names,
I'm
going
to
recommend
you
do
the
same
thing
for
rendering
of
this
the
helm
chart
today
does
not
allow
you
to
specify
image
names.
That
is
on
something
we're
going
to
do.
We're
also
going
to
allow
you
to
do
resource
limits,
so
vendors
can
get
really
fancy
with
perhaps
introducing
scenarios
where
you
know.
B
Maybe
you
want
to
add
a
new
feature
flag
and
you
want
to
have
a
pod
crash
so
on
on
a
memory
leak.
Well,
maybe
you
only
get
that
pod
25
megabytes,
so
we're
gonna.
Allow
you
to
do
all
these
things.
It
will
be
ready
for
GA
at
the
end
of
this
month,
not
quite
there
yet
again,
I
gotta
tell
this
thing.
My
open
television
configuration,
so
this
is
effectively
the
same
config
you've
seen
before,
but
it's
under
this
open
Telemetry
collector
config
block.
Instead
and
earlier
I
mentioned,
there
is
a
small
bug.
B
The
email
service
is
not
exporting
its
fans.
I
get
over
that
by
passing
in
this
little
component
to
the
helm,
chart
I'm
confident
by
the
end
of
the
week.
You
will
not
need
to
do
this
I'm
doing
it
myself,
because
I
need
to
get
this
out
there.
I
want
this
to
work
so
first
off
homeless,
I
should
say
nothing
here,
all
right,
so
install
open,
Telemetry
demo.
This
is
from
the
hotel,
no
I'm,
sorry
open
dash
Telemetry,
and
it's
this
slash.
B
Demo
values
I'm
in
the
right
folder,
so
I'm
just
going
to
call
that
file
already,
and
this
is
going
to
go
ahead
and
install
it
I'm
going
to
bring
this
up
a
little
bit,
because
when
it's
done
installing
it's
going
to
give
you
that
cool
little
graphic,
I,
don't
know
who
wrote
this
graphic,
but
I
wanted
thumbs
up.
That
is
a
really
hot
graphic
by
the
way
I'm
all
for
ASCII
art.
Coming
from
my
old
days
running,
a
BBS
ascare
was
huge
back
then.
B
So
it's
installed
it's
up
over
to
this
screen
here.
You
can
see
here
all
the
times
here.
The
ages
are
very
recent
anybody's
wondering
this
is
a
tool
called
canines.
It
is
a
CLI
based
UI
for
kubernetes.
If
you
have
not
heard
about
it
before
I
endorse
this
tool,
if
not
here,
to
tell
you
to
use
it
use
whatever
you're
most
comfortable
with
absolutely
I
love
canines,
it's
a
really
great
tool:
I'll
go
ahead
and
search
for
it.
B
B
As
you
all
know,
kubernetes
network
is
gnarly
as
in
nothing's
exposed.
Unless
you
explicitly
Celtic
exposed.
We
pop
a
bunch
of
services
in
here,
but
they're
all
cluster
IP
Services.
Nothing
is
done
to
be
exposed
externally.
If
you
intend
to
expose
anything
externally,
it's
up
to
you
to
then
write
your
own
load,
balanced
or
low,
bound
services
or
Ingress
routes
to
take
advantage
of
the
existing
service,
or
maybe
even
deploy
additional
Services
take
advantage
of
it.
You
would
do
this
above
and
beyond
the
standard
Helm
chart
for
vendors.
B
What
does
this
mean
to
you?
Well,
you
can
provide
instructions
to
deploy
these
things
on
your
own,
or
you
can
sub
chart
the
help
chart
and
deploy
them
on
your
own
up
to
you.
How
you
want
to
do
this
and
how
you
want
to
communicate
it
to
your
users,
but
that's
how
you
would
effectively
do
it
if
you
wanted
to
provide
a
way
for
them
to
get
additional
external
access.
B
We
do
give
you
simple
commands,
which
is
really
using
the
cube
color
Port
4
command
to
get
access
to
the
various
pieces
of
the
demo
UI.
Should
you
want
to
do
it
on
your
own
and
if
you're
deploying
this
to
maybe
a
mini,
Cube
or
you've,
got
your
own
eks
cluster
running
or
AKs
or
gke
or
whatever
you
got,
maybe
you're
doing
something
on
another
platform,
it's
it's!
It's
on
you
at
this
point,
mine's
running
in
EK,
apps
and
I
could
absolutely
run
these
commands,
but
these
are
blocking
commands
and
I've
got
canines.
B
So
I'm
just
going
to
come
here
on
K9s
and
say,
hey
front
end
shift.
F
yeah
I
want
port
8080,
that's
done!
That's
going
to
get
forwarded
for
me.
I
want
the
feature
flag,
UI
we're
going
to
show
off
that
UI
in
this
kind
of
here.
So
in
particular
the
feature
flag.
Ui
is
running
on
8081.
You
kind
of
see
it
right
there.
So
that's
the
one
I
want.
Let's
put
that
out
there,
I
can
expose
Jaeger
if
I
wanted
to
as
well.
B
Really
all
these
other
things.
If
you
want
to
explode
it's
up
to
you
at
that
point.
But
I
got
my
my
front
end
and
my
feature
flag
servers
exposed
for
me.
So
let's
go
ahead
and
check
them
out.
B
A
A
B
I'm
just
going
to
check,
let's
look
at
some
logs
on
this
feature:
Flags
I
know
why
it's
broken,
and
this
is
great
I'm.
So
happy
I
hit
that
error.
This
happens
we're
going
to
fix
it.
We
know
about
it.
We
got
to
do
something
about
it.
The
feature
flag
service
depends
on
postgraphs.
B
I
did
a
clean,
deploy
the
feature
flag
service
started
before
postgres
started
and
I'm
going
to
go
in
here
and
I'm,
going
to
see
a
bunch
of
SQL
errors
because
well,
yes,
postgres
doesn't
have
the
darn
database.
How
do
I
fix
this
I'm,
just
gonna
restart
the
Pod.
It's
that
simple,
so
I'm
going
to
delete
it.
Kubernetes
does
its
thing.
One
of
the
best
schedulers
in
the
world
restarts
the
Pod.
This
will
work.
I
will
need
to
remap
my
port
4.
B
A
B
Okay,
there
we
go.
It
took
a
second
there
for
for
the
release
of
Prior
fort.
So
let's
try
this
again.
Crush.
A
B
Right
two
feature
plates
product,
catalog
and
shipping.
This
one
here
is
implemented
this
one
here
not
yet
you
put
this
on
nothing's
gonna
happen.
What
what
happens
with
this
one?
Well,
really
it's
meant
for
a
very
specific
product
codes
and
like
oh
LJ
or
OJ,
something
product
code.
B
If
the
product
catalog
service
is
trying
to
get
that
product
code,
get
the
details
about
it,
it's
going
to
check
the
feature
flag
service.
First,
if
the
feature
flag,
this
feature
flag
comes
back,
is
enabled
the
product
catalog
server
is
going
to
spit
back
an
error.
Awesome
love
that
I'm
not
going
to
show
this
off
first
well.
Actually,
let's
flip
this
on
we'll
go
look
at
some
traces
here
in
a
second,
so
it's
on!
Oh,
my
goodness,
I
made
errors
happen.
I'm
gonna
come
to
Honeycomb
real
quickly.
B
None
of
these
here
will
show
error
equals
true,
at
least
not
recently,
because
error
equals
true
is
going
to
be
very
recent
and
they're
all
right
here.
These
are
the
ones
that
now
I
flipped
on
that
product
dialogue
flag.
So
when
this
is
going
out
to
go,
get
this
product
ID,
which
is
randomly
selected
from
a
group
of
like
10,
or
something
like
that,
the
feature
flag
service
will
return.
True,
we
Bubble
Up
the
errors,
all
the
way
up
the
pipe.
B
B
What's
happening,
I
I
believe
we
also
spit
out
an
event
here
as
well
to
say:
hey
we're
failing
on
this,
because
the
feature
flag
was
enabled
we
do
plan
on
introducing
another
feature
flag
which
is
going
to
actually
create
a
latency,
potentially
even
a
memory
leak,
and
the
Hope
here
is
that
we
will
allow
vendors
to
make
use
of
their
tools
to
really
discover
why
it
happened.
B
In
that
case,
there
it'll
be
a
unique
gnarly
little
situation,
where
it's
a
specific
user,
doing
a
specific
thing
and
causing
memory
to
leak
higher,
so
some
fun
ways
and
things
to
think
about
so
again
feature
flight
service
is
meant
to
for
you
to
enable
and
disable
different
kind
of
usage
and
demo
scenarios.
We
sometimes
call
them
hero
scenarios
within
the
actual
platform
itself,
now
I'm
going
to
show
off
some
code
of
how
we
made
this
all
work.
B
How
we
put
this
together,
I'm
not
going
to
show
off
code
for
every
single
service
for
every
single
thing,
I
kind
of
want
to
focus
more
on
the
not
so
popular
things.
The
things
I
want
people
to
really
focus
on
when
you're
running
this
application.
When
you're
using
it
yourself,
so
let
me
close
a
couple
of
these
I'm
gonna
actually
start
off
we're
going
to
go
into
the
front
end
service.
B
So
the
front
end
service
has
code
to
enable
telemetry.
Of
course
it
should
well.
I
actually
has
two
tracers
part
of
it.
It's
got
a
back-end
Tracer
which
is
used
by
the
front
end's
next
node
service
part
itself,
and
it's
got
a
front-end
Tracer
used
by
the
browser
I'm
going
to
show
off
the
front
end
Tracer.
First,
let's
see
a
question
here
about
I'm,
sorry
about
introducing
fault
injection
I'm,
not
clear
what
you
mean
by
that
David.
B
What
we're
trying
to
do
is
we're
trying
to
make
it
with
a
feature
flag.
So
the
feature
flag,
Returns
the
fault,
then
the
surface
itself
is
just
going
to
explode.
It's
just
going
to
turn
an
error.
It's
how
we
did
it
so
we're
kind
of
injecting
an
error
based
on
the
feature,
Flags
status
and
we're
doing
that
in
code.
B
So
this
here
is
instrumentation
for
the
front
end,
it's
a
little
wordier
than
node
back
then
some
of
that
has
to
do
because
we
gotta
do
some
course
URL
stuff
for
the
web
Auto
implementation.
We
need
to
kind
of
wrap
things
up
a
little
bit
more
manually.
You
don't
have
all
the
all
the
environment
variables
available
to
you
in
the
front
end,
so
you
got
to
specify
a
few
more
things.
When
you
do
this
from
a
back-end
perspective,
you
don't
need
to
specify
much
at
all.
B
In
fact,
this
here
is
not.
Actually.
This
is
the
instrumentation
for
the
back
end,
and
then
we
just
wrapped
it
up
with
something
called
back
and
Tracer
to
make
our
own
apis
easier
to
use.
But
this
is
what
how
you
bootstrap
the
back
end.
That's
it
there's
not
much
to
this
and
we'll
show
you
the
payment
service
very
similar
to
this
here.
B
How
you
do
it
is
when
you
start
up
a
service,
you
do
a
required
module,
so
node
is
not
an
agent
per
se,
but
required
module
makes
it
like
an
agent
David.
Your
question
about
chaos,
monkeys
and
you
know
the
tools
around
that
or
chaos
engineering.
We
thought
about
it.
We
did
it's
kind
of
a
big
task,
maybe
too
heavy-handed
for
what
we're
trying
to
do
and
we
wanted
to
not
have
to
introduce
other
dependencies
into
the
stack
if
possible.
B
So,
yes,
it
was
thought
about,
but
we
were
more
focused
on
kind
of
try
to
keep
a
little
bit
more
Nimble
than
having
to
introduce
additional
dependencies.
B
So
it's
kind
of
node.js
and
then
from
there
what
we
did
is
inside
the
middleware
is
where
we
did
a
lot
of
kind
of
magic.
If
you
will
and
I
want
to
discuss
this,
because
this
is
where
we
look
at
baggage,
so
baggage
is
actually
added
at
the
load,
generator
level.
B
It'll,
add
a
piece
of
baggage
and
all
the
locator
does
it
has
this
baggage
called
synthetic
request
and
it
could
have
a
value
of
true
okay,
and
here
you
have
to
use
true
string,
not
true
booming,
because
baggage
is
passed
in
as
an
HTTP
header.
It's
just
a
really
long
string,
so
everything
here
comes
down
back
to
a
spring
in
all
the
properties
and
everything
else.
B
B
So
this
is
effectively
a
next
JS
middleware
and
we're
going
to
look
to
see
if
it's
got
that
baggage.
If
it
does,
we
are
going
to
effectively
create
a
brand
new
Trace
we're
going
to
stop
the
existing
trade,
we're
going
to
create
I'm.
Sorry
we're
just
going
to
create
a
brand
new
span
with
no
prior
context
and
we're
going
to
put
this
one
into
context.
We're
going
to
make
this
one
active,
so
it
doesn't
have
a
parent
effectively
and
we're
going
to
link
it
to
the
prior
span.
B
Note
here
span
links
are
really
powerful
to
help.
You
do
these
things,
but
you
have
to
specify
the
spam
Link
at
span
creation
time.
This
is
part
of
this
back
across
all
languages.
I've
heard
people
ask.
Well
you
know,
I
I,
don't
know
the
link
until
after
my
experience
created.
Yes,
I
get
that,
but
you
have
to
specify
it
at
spam
creation
time
because
it
needs
to
be
mutable.
B
If
you
need
to
do
bi-directional
linking
and
then
you
would
have
to
create
an
additional
span
on
the
kind
of
the
one
that
you're
being
linked
to
initially
and
then
add
the
the
the
details,
the
context
from
that
one
there
it's
gonna,
be
a
little
more
manual
code
can
be
done.
I've
seen,
customers
do
this,
but
this
is
basically
what
you
want
to
do,
we're
going
to
add
an
attribute
Here
app.
B
That
said
that
the
request
equals
true,
because
we're
going
to
check
that
attribute
later
on
and
or
sorry
I
can
check
this.
Actually
we're
going
to
add
the
baggage
header
we're
going
to
keep
we're
going
to
push
a
baggage
with
the
baggage
continue,
because
we're
going
to
check
that
baggage
later
later
on
inside
the
payment
service.
B
B
These
are
the
kinds
of
things
you
should
be
using
baggage
for.
Please,
please,
please
do
not
use
baggage
to
actually
pass
context
to
a
downstream
service.
That's
not
what
it's
for
it's
or
I
should
say
application
context
or
Downstream
service.
You
want
to
pass
Telemetry
context
and
keep
it
to
that.
There
things
like
synthetic
requests.
B
So
that
was
kind
of
getting
up
and
running
with
node.js
the
front
end
I
wanted
to
really
discuss
that,
because
the
front
end
is
unique
in
that
it
has
two
different
tracers
one
for
the
browser
one
for
the
node.js
part.
The
payment
services
have
pure
node.js
only
service,
and
you
can
see
here.
This
is
kind
of
the
idiomatic
way
of
how
you
spin
up
and
how
you
add,
instrumentation,
open,
Telemetry
instrumentation
to
your
node
service.
B
This
will
instrument
most
well-known
Frameworks,
though
the
npm
world
for
open,
download
trees
growing
rapidly.
You
could
add
additional
instrumentations
to
here
as
well.
You'll
have
to
add
a
little
bit
of
code
to
do
that.
B
A
few
other
things
I
kind
of
really
want
to
to
touch
hard
on
here
and
really
make
sure
everybody
kind
of
got
was
I.
I
wanted
to
just
just
cover
a
little
bit
of
the
kind
of
the
known
things
about
ruby
in
particular,
Ruby's
different
abuse
doesn't
do
grpc
right,
Ruby's
different
than
that
area.
There
so
for
Ruby
in
particular,
we
need
to
pass
it
I'm.
Sorry
I
want
to
pull
up
the
doctor
proposed
for
this.
Instead,
we
need
to
pass
in
the
HTTP
port
to
export
the
traces.
B
So
if
you're
playing
with
this
you're
using
this
you're
saying,
why
did
that
happen?
That's
why
Ruby
just
doesn't
support
grpc
for
export
of
its
open
television
data
and
therefore
we
need
to
specify
it
that
way
there.
B
The
other
things
that
are
really
important,
I
want
to
make
sure
people
capture
we've
documented
them.
All
I
should
perhaps
show
some
of
that
documentation.
I
did
not
show
to
our
service
specific
documentation.
I
think
it
probably
makes
sense
here
as
well,
but
under
docs
we
have
Services
here,
every
service
will
be
documented
they're,
not
all
done
yet,
but
we're
getting
there.
For
example,
the
checkout
service
is
probably
the
the
most
busiest
of
all
services
we
go
through
how
to
initialize
the
tracing
provider.
How
to
do
it
right?
B
B
How
do
you
get
a
span?
How
do
you
add
attributes
what
about
spam
events,
all
that
is
shown
up
here?
B
They
will
all
be
documented
and,
as
you
continue
moving
forward
because
part
of
the
goals
of
this
project
is
to
be
well
documented,
you
will
see
us
put
them
in
here
and
if
we're
missing
something,
please
please
please
create
an
issue
we're
going
to
get
to
it
right
away,
I'm
going
to
end
it
there
we're
talking
quite
a
bit.
If
anybody
wants
to
ask
any
further
questions,
I'm
happy,
maybe
to
dive
down
and
show
you
how
we
show
you
how
we
did
that.
A
Awesome,
thank
you
so
much
Pierre.
If
you
do
have
questions,
please
feel
free
to
throw
them
in
the
chat
where
you're
at
whether
it's
YouTube
LinkedIn
or
you
know,
or
or
anywhere
else,
that
you're
that
you're
watching
this
I'm
sure
that
we
have
some
way
of
getting
your
feedback.
Please
please,
please
feel
free
to
ask
those
questions
and
we'll
get
those
answered.
I.
A
Think
one
one
question
that
I
have
is:
what
are
some
meaningful
ways
in
which
we
can
help
kind
of
contribute
back,
I'm,
sure,
obviously
being
a
demo.
The
biggest
thing
is
going
to
be
testing
it
and
actually
like
kind
of
poking
at
it,
and
really
taking
a
deeper
look
into
some
of
these
different
aspects.
But
is
there
anything
that
you
think
needs
a
little
bit
more
testing
or
or
really
that
you're
excited
to
see
about
this
project
really
coming
up.
B
I
would
love
for
people
to
try
this
in
more
scenarios
right
straight
up
right
now,
I
would
love
somebody
to
stand
this
up
and
host
it.
Let
me
know
how
the
browser
Parts
work,
because
cores
is
an
issue.
It
causes
a
thing.
I,
don't
think
we
well
tested
out
the
whole
course
aspect
and
I
know
once
this
thing
goes
on
a
web
browser
somewhere
else.
No,
the
Wild
Wild
web
world,
probably
gonna
break
so
we'd
love
to
have
feedback
on
that.
One
and
I
think
we
need
a
host.
B
B
A
I
really
like
all
of
the
languages
that
you
were
able
to
pick
and
Source
around
this
too,
like
seeing
rusts,
C,
plus
plus
Swift,
all
of
those
languages,
I've
I've
done
some
work
in
elixir
in
the
past
as
well,
so
really
fun
to
kind
of
see
all
those
different
contexts
come
together
to
give
you
that
visibility
that
you
just
normally
would
not
get
on
on
each
of
these
on
their
own
with
each
of
these
languages,
so
major
Credence
on
that
front,
that's
awesome.
Yeah.
B
Major
kudos
to
all
the
contributors
for
that
as
well.
You
know
we
could
not
have
done
this
without
people
in
the
community
who
knew
those
languages
were
familiar
with
how
to
instrument
them
and
just
walked
up
and
said
here.
You
go.
I
rewrote
this
service
for
you
in
that
language
and
implemented
the
Proto
and
they're
Off
to
the
Races.
So
it's
pretty
handy.
A
No
I
think
I
think
those
are
all
the
questions
that
we
have
today
so
with
that
would
like
to
wrap
and
and
give
you
a
little
bit
of
time
back
but
truly.
Thank
you
so
much
Pierre.
Do
you
have
any
parting
words
of
wisdom,
affirmations
or
any
fun
code
Snippets
to
share
with
us
before
you
go
I.
B
You
know
because
of
this
project,
I
learned
as
a
python
agent,
it's
interesting
when
you,
when
you're
running
I've,
been
part
of
the
open
television
for
a
long
time.
I
had
no
idea
python
had
an
agent,
although
I
think
the
agent
was
really
new
when
it
came
out,
but
it's
an
auto
instrument
or
thing,
and
it's
really
handy
to
use.
Please
use
it.
B
If
you
write
python
code,
it's
really
really
easy
to
use
and
we
encourage
you
to
to
try
it
out
and
we
also
use
it
for
our
our
load
generator
and
everything
else.
So
it's
kind
of
doing
those
weird
things
that
just
happened
to
me
because
of
this
whole
project.
A
B
Aggressive
well
awesome,
thank
you
so
much
to
cncf
for
hosting
this
live
stream.
Please
join
us
in
slack
if
you're
going
to
be
going
through
the
wonderful
conference
in
the
month.
If
we
are
going
to
have
an
open
television,
Community
Day
on
the
24th,
we're
going
to
be
really
pumping
it
up,
you'll
hear
stuff:
I'm
gonna,
I'm
gonna
slip
it
out.
Hopefully,
Austin
doesn't
get
mad
at
me,
but
it'll
be
called
the
hotel.
Unplugged
really
excited
about
this
and
I
hope
to
meet
you
all.
There
in
person
would
be
great.
A
A
Awesome.
Thank
you.
Everyone
for
joining
the
latest
episode
of
cloud
native
live.
We
enjoyed
all
of
the
interactions
and
questions
that
you
had
today
thanks
for
joining,
and
we
can't
wait
to
see
you
again
soon,
if
not,
if
not
online,
hopefully
at
one
of
the
upcoming
kubecons.
Thank
you
very
much.
Everybody
have
a
good
one.