►
From YouTube: Keynote: History of OpenTelemetry
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
Keynote: History of OpenTelemetry
Ted and Morgan will discuss the history and story behind OpenTelemetry, and what it means for the future of the project.
A
I
personally
have
a
special
place
in
my
heart
for
all
things:
observability
my
own
journey
in
cloud
native
began
with
the
open
tracing
project
where
I
worked
very
closely
with
ted
over
here
and
also
hung
out
with
morgan.
So
I'm
just
excited
to
see
all
the
momentum
that
has
happened
over
the
years
and
the
great
progress
we
have
made
till
date.
So
without
further
ado,
let's
get
started
and
learn
more
about
open
telemetry.
C
A
B
I'm
morgan
mclean.
I
work
at
google.
My
history
dates
back
to
our
cloud
trace,
product
and
later
open
census,
which
is
around
the
same
time
as
open
tracing
and,
and
you
know,
I've
been
involved
with
open
census
since
the
beginning,
and
certainly
with
the
merger
of
open
census
and
open
tracing
into
open,
telemetry
and
like
ted
if
you've
joined,
basically
any
call
for
any
of
the
open,
telemetry
sigs
you've
probably
seen
my
face
and
heard
my
voice,
and
so
it's
great
to
talk
about
it
today.
A
B
A
A
No,
you
know
this
really
brings
me
back
in
my
head
to
the
open
tracing
data.
Really
we
were
trying
to
talk
about.
How
do
you
understand
your
system,
which,
at
a
certain
level
of
complexity,
no
single
human
being
can,
and
so
what
would
be
really
helpful
is
to
understand
exactly
how
open
telemetry
is
different
from
open
tracing
as
well
as
open
sensors.
C
C
So
what
we
really
wanted
to
do
was
figure
out
a
way
that
we
could
share
all
of
this
instrumentation
and
be
able
to
have
that
instrumentation,
ideally
be
native
within
software
rather
than
plugins,
and
then
be
able
to
plug
in
any
kind
of
analysis
tool
on
the
back
end,
and
so
that
was
sort
of
the
direction
open
tracing
came
at
it.
You
want
to
talk
about
open
census,
morgan.
B
Specific
sdk
and
open
sense
census,
additionally
also
focused
on
metrics,
which
was
a
big
difference
from
open
tracing,
which
was,
as
its
name
suggests,
very
focused
on
tracing,
and
I
think
open
telemetry
brings
the
best
of
both
of
each
of
these
right.
You
have
in
in
open
telemetry.
You
have
apis
that
don't
include
the
implementation.
Much
like
open
tracing,
which
makes
it
really
easy
for
framework
maintainers
to
buy,
indicates
this
framework.
That
was
a
challenge
in
open
census.
B
It
was
a
drawback
you
had
to
bring
the
whole
implementation
with
you
and
open
telemetry
also
provides
the
full
sdk
as
a
separate
component
that
you
can
pull
down
much
like
what
opencensus
had,
and
it
also
includes
metrics,
and
so
really
it's
just
the
the
ultimate
marriage
of
both
projects
into
one
and
plus,
on
top
of
that
it
brings
a
vastly
larger
community
than
either
open
census
or
open
tracing
ever
had.
I
think
I
ran
the
numbers
a
few
months
ago.
B
The
last
few
months
we've
been
the
second
largest
or
second
most
active
cncf
project
in
terms
of
commits
and
committers,
which
is
huge
like
if
you
told
me
that,
like
last
year,
I
wouldn't
have
believed
you,
and
so
that's
that's.
Another
sort
of
non-technical
thing
that
the
project
brings
is
like
huge
support
from
the
industry
and
end
users,
which
is
fantastic.
B
B
A
B
But
I
I
think
it
speaks
to
the
hunger.
That's
existed
in
the
industry
for
this
solution,
and
I
mean
certainly
I
know
at
google
and
certainly
ted
for
yourself
at
lightstep
and
all
the
contributors
from
all
the
other
vendors
have
mentioned.
You
get
on
customer
calls
and,
and
they
see
the
value
immediately
and
that's
why
you
have.
I
think
so.
Many
end
users
like
like
shopify
and
others
and
mailchimp
and
and
postmates,
and
a
whole
group
making
their
own
contributions
and
putting
teams
on
this
because
they
see
the
value.
C
Yeah
and
that's
ultimately,
why
we
decided
to
merge
the
projects.
Normally,
it's
fine
to
have
like
a
bunch
of
separate
projects
in
the
same
space.
It's
no
big
deal
but
there's
something
about.
I
think
in
particular
the
distributed
tracing
aspect
of
it,
but
really
everyone
was
asking
for
there
to
be
one
standard
for
doing
this,
and
so
we
were
getting
a
lot
of
community
pressure
to
merge
the
projects
you
know
kind
of
from
the
get-go
people
were
like.
I
don't
really
want
to
pick
between
these
two
things.
Why?
C
Yeah,
but
it
was
like
totally
validating
because
when
we
merged
them,
so
we
actually
maybe
like
the
one
group
to
actually
reduce
the
number
of
potential
standards
out
there
by
going
from
two
to
one
and
when
we
did
that
that
was
what
made
everyone
get
involved,
because
that
was
ultimately
the
thing
people
were
looking
for
was
just
agreement
on
how
we
were
going
to
do
this.
Yes,.
A
Absolutely
I
think
you
have
truly
found
product
market
fit
and
in
this
case
it's
standard
market
fit.
Let's
maybe
we'll
call
it
that.
But
it's
I
think,
as
you
folks
said
right,
this
is
a
merger
and
then
some
because
your
community
has
grown
20x.
At
least
you
have
yes,
so
much
more
momentum,
and
that
tells
you
the
sum
is
greater
than
the
parts
and
that's
just
a
beautiful
beautiful
story.
A
I
I
think
one
thing
you
folks
have
been
saying:
one
thread
you
folks
have
been
talking
about
is
around
standards
and
how
there's
like
always
more
and
more
because
everyone,
I
think
to
quote
something
morgan
said
similar
but
different,
and
that's
sort
of
how
I
think,
n
plus
one.
Why
does
this
happen
so
much
in
standards.
C
Standards
are
hard
like
right,
it's
ultimately
about
organizing
people
and
finding
agreement
and
when
there's
less
people
around
it's
easier
to
find
agreement.
That's
just
one
of
the
things
about
you
know
having
a
diverse
coalition.
Is
you
have
to
do
the
work?
It's
real
work
to
actually
come
up
with
something
that
makes
everyone
happy
and
satisfied,
and
that's
always
going
to
be
slower
than
just
kind
of
going
off
on
your
own
and
you
know
taking
a
shot
at
it.
So
it's
it's.
C
B
That's
it
very
simple,
just
a
little
string
that
took
about
a
like,
we
had
sort
of
drafts
going
between
like
google
and
zipkin
for
a
while,
and
then
we
brought
it
into
the
w3c
or
actually
dynatrace
who
helped
us
bring
it
in
and
once
that
happened,
progress
did
slow,
not
in
a
bad
way,
but
just
because
yeah
everybody's
there,
like
you,
need
to
meet
everyone's
requirements
now
and
so
that
just
naturally
takes
a
lot
of
time.
It's
it's
good
like
it's
bad,
it's
good
about
it!
A
Yeah,
I
think,
you're
absolutely
right.
A
standard
is
just
different
because
it's
very
opinionated
and
very
specific
yeah
actually,
and
that
has
I
don't
think
the
difference
in
pace
is
by
any
means
a
bad
thing.
As
you
said,
you
added
time
to
your
roadmap,
but
now
you've
come
out
with
something
stronger,
that
people
really
love
and.
A
I
have
actually
had
my
own
brush
with
standards
lately
because
we're
working
on
an
inclusive
naming
initiative
for
all
of
not
just
the
ncf
but
leveraging
the
kubernetes
project's
work
and
removing
problematic
language
and
code
and
the
clear
knowledge,
a
clear
thing
we
were
told
you
have
to
work
with
standards,
because
there
are
aspects
of
software
that
have
to
be
determined
in
that
way
and
when
you
went
to
talk
to
them
it
was
like.
Oh
yeah.
A
very
fast
thing
will
be
like
probably
two
years,
because
it's
like
wait.
What.
A
A
Yep,
exactly
exactly
so
amazing
stuff,
I
think
myself,
I
and
the
audience
has
learned
a
lot
about
the
history
of
open
telemetry,
all
the
value
that
it's
brought.
I
think
now
we
would
like
to
learn
from
you
about.
Where
is
what
is
your
latest
update
from
open,
telemetry
to
end
users?
Potential
contributors
out
there.
B
Yeah,
so
I
can
speak
to
that
a
bit,
so
we
recently
had
an
announcement
that
the
tracing
specification
has
reached
release
candidate
status,
and
so
the
sdks
are
all
working
away
right
now
on
building
their
own
release,
candidates
for
tracing.
Obviously,
the
sdks
include
tracing
and
metrics
and
other
things,
but
the
tracing
part
of
each
of
these
sdks
once
they
hit
hit
release
candidate
status,
will
be
rc
and
we'll
have
the
intent
and-
and
I
think
we'll
need
this-
of
ensuring
there's
no
breaking
changes
between
that
release.
B
Candidate
and
the
final
ga
version
after
that.
We're
actually
in
parallel
to
that
we're
working
on
achieving
a
release.
Candidate
specification
for
metrics,
followed
by
then
the
sdks
achieving
release
candidate
status
for
tracing
and
metrics
together,
at
which
point
we'll
declare
the
project
to
be
release
candidate
status
following
that,
then
we'll
work
very
hard
towards
getting
to
ga.
That's
mostly
like
bug,
fixes
productionization
testing
documentation
and
so
we're
expecting
pretty
broad
adoption.
Once
the
project
hits
rc
for
both
tracing
and
metrics.
B
B
Yeah
you're
going
to
see
release
candidate
sdks
for
tracing
in
the
next
few
weeks.
Like
that,
that's
that's
well
underway!
That's
fast,
the
rc
release
of
the
tracing
spec.
I
think
it's
hopefully
probably
achievable
this
year,
we're
going
to
push
really
hard
towards
that.
The
rc
release
for
tracing
and
metrics,
both
in
the
sdks
is
possibly
achievable
this
year
again
we're
going
to
push
really
hard
to
try
and
get
that
we
we
may
or
may
not
we'll
see.
It's
debatable
right.
A
A
B
Yes,
exactly
so,
it
will
definitely
have
rc's
well
before
kubecon
eu
the
rcs.
I
expect
to
be
used
a
lot
of
places
in
production
like
I
I'm
curious
how
many
vendors
are
certified,
I'm
guessing
a
lot
of
them
will
but
ga,
hopefully
by
next
year,
but
to
be
blunt
for
most
users
that
probably
won't
matter,
because
I'm
expecting
pretty
broad
adoption
of
the
rc's
just
given
the
amount
of
contributions
we've
seen
from
end
users.
A
C
Yeah-
and
I
would
add
there-
there
is
actually
an
important
time
frame
right
now,
which
is
because
the
tracing
spec
is
now
frozen
and
we
have
not
yet
issued
a
release.
Candidate
now
is
the
time
to
really
dog
food
and
try
this
out
so
getting
involved
and
making
sure
that
it
feels
ergonomic
that
that
everything
is
working
properly,
that
we
don't
want
to
make
any
changes.
You
know
on
the
individual
language
levels.
This
is
the
time
to
be
doing
that
work,
so
I
would
encourage
anyone.
A
Amazing,
and
so
the
call
to
action
here
is,
go
check
out
the
open,
telemetry
libraries
for
various
languages
and
give
feedback,
because
the
rc
is
coming
soon
and
one
thing
I
think
would
be
helpful
just
for
you
know
first
time
attendees
as
well.
As
you
know,
some
end
users
and
contributors
is
to
really
understand
what
you
mean
when
you
say
rc
is
coming
it's
great.
I
think
that
would
help
them
feel
more
comfortable
going
forward
before
g8.
So
would
you
please
explain
that
one
of
you.
C
B
C
So
that's
the
part
we
really
really
want
to
nail
and
that's
to
my
mind,
like
the
heart
of
what
the
release
candidates
in
ga
is
about
is
saying
like
this
has
reached
a
stability
point
where
we
think
we're
just
going
to
leave
it
this
way-
and
we
might
add
things
to
it
later,
but
we're
not
going
to
break
this.
So
that's
why
it's
so
important
for
people
to
to
give
it
a
shot
right
now.
A
So
speaking
of
colos,
there's
a
lot
of
stuff
happening
right.
Uconn
is
so
full
of
energy
and
excitement
and
I'm
proud
to
say,
actually
compare
compared
to
our
first
first
rev
with
the
virtual
event.
This
time,
I
think
people
have
got
been
able
to
work
with
the
virtual
event
and
made
it
strategic
for
themselves
we're
having
polos
like
this
we're
doing,
inclusive
naming
meetings,
etc,
etc.
A
B
C
Yeah
stay
tuned,
we
do
have
after
this
we're
going
to
be
going
into
workshops
like
unconference
style
conversations,
and
so
that's
a
great
way
to
really
get
out
there
and
get
your
questions
answered,
because
we
have
a
lot
of
maintainers
and
community
members
here
and
I
love
unconferences.
That's
the
part,
I'm
most
excited
about
morgan
there
do
you
have
anything
beyond
that?
You
think
we
have
some
cool
talks.
B
Also
occurring
that
I
mean
it's
a
single
track,
so
if
you're,
if
you're
here
and
don't
change
the
channel,
I
said
you're
gonna
stick
around,
there's.
Definitely
a
few
talks
where
I
read
the
summary
and
they
look
pretty
interesting.
So
I'm
excited
to
listen
to
them
and
a
number
of
them
are,
by
actual
like
end
users
who
are
using
open,
telemetry
in
production,
and
so
you
can
understand
even
from
their
experience
in
the
beta,
how
things
have
gone,
pitfalls,
they've
ran
into
and
how
the
project
has
improved
and
evolved.
Since
then,.
A
A
I
always
say
her
last
name
wrong,
so
I'm
not
gonna,
try
but
constance
is
actually
co-chair
for
all
of
kubecon
this
time
around
and
she's
a
part
of
the
hotel
community
and
she's
going
to
do
her
keynote
as
a
co-chair
on
wednesday
november
18
at
1
51
pm
eastern
time,
and
so
you
can
listen
to
her
as
well
as
one
of
the
hard-working
collaborators
on
open
telemetry
with
all
that
said,
just
final
question
folks,
obviously,
we've
learned
a
lot.
We
know
about
the
history
of
open
telemetry
to
some
degree.
A
B
B
So
so
beyond
cubecon
this
year,
then
we're
active
on
getter,
like
I
said
that
might
be
moving
to
slack
eventually
there'll
be
an
announcement
about
that
when
it
happens
on
github
and
during
the
weekly
special
interest
group
meetings,
to
be
honest
like
if
you
really
want
to
get
involved
and
understand
the
pace
of
the
product
or
the
project.
Rather,
then,
the
weekly
sig
meetings
which
are
in
our
public
calendar
are
open
to
anyone.
I
really
recommend
joining
there's
great
discussions
that
happen
there
and
on
the
weekly
maintainers
meeting.
C
Yeah
yeah,
you
know
we
try
to
keep
all
of
the
actual
work
on
the
project
strictly
in
github.
Yes,
so
you
can
also
find
you
know,
publishing
issues
and
prs.
If
you
want
to
get
a
sense
of
where
the
project
is,
we
have
various
burn
down,
charts
and
projects
there,
but
please
do
come
to
the
calls.
I
think
people
can
be
maybe
a
little
shy
or
they're
like.
Oh
I'm
not
like
a
core
person,
but
but
we
really
welcome
participation
in
those
calls,
and
it's
it's
a
great
way
to
get
your
questions
answered.
B
A
So
those
are
two
options
and
then
for
long-term
engagement,
definitely
find
them
on
opentelemetry.io,
go
to
their
github
repos
and
show
up
to
the
meetings
you
don't
need
to
know
anything
to
show
up.
Everyone
can
contribute,
and
you
really
should
and
a
contribution
just
showing
up
you
did
it
check
so
highly,
encourage
you
all
to
participate
in
this
wonderful
community.
Thank
you!
So
much
ted
and
morgan
for
telling
us
about
the
awesome
project.