►
From YouTube: CNCF Open Telemetry Community Meeting 2019-12-11
Description
Join us for Kubernetes Forums Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
CNCF Open Telemetry Community Meeting 2019-12-11
A
A
B
And
you
know,
like
normally,
food
poisoning
lasts
for
a
day
or
something
and
I
was
out
from
last
Wednesday
afternoon
like
late
afternoon.
Until
this
morning,
oh
yeah,
it
was
terrible,
I
and
then
I
got
an
ear
infection
at
the
same
time,
which
was
just
like
the
cherry
on
top
of
the
yeah
so
yeah
anyway,.
D
F
B
C
B
B
A
lot
of
us
just
spent
some
time
together
at
Q
Khan,
which
was
pretty
exciting.
So
there
will
be
less
to
discuss
at
this
meeting
than
usual.
That's
okay!
We
have
the
agenda
shared
in
the
calendar,
invite
so
they
used
that
to
join.
There's
a
link
to
the
agenda
there
and
the
first
item
on
the
agenda
is
Ted.
B
C
Absolutely
so
you
know
we're
continuously
evolving
and
growing
this
project.
We
evolved
our
RFC
specification
process
over
the
summer,
but
we
haven't
really
had
like
a
big
community
check-in
about
the
general
sort
of
project
structure.
So
you
know
the
way
we're
kind
of
set
up
is:
there's
a
governance
committee
that
creates
a
charter
for
a
technical
committee
which
helps
manage
a
bunch
of
SIG's
special
interest
groups
in
each
special
interest.
C
Group
has
a
set
of
membership,
tiers
and
contribution
requirements
needed
to
to
reach
each
tier,
and
so
it
would
be
great
to
just
get
some
feedback
from
the
community
about
how
that
process
has
been
going
and
how
we
could
improve
it,
and
it
could
really
just
be
general
purpose
feedback
as
well.
If
there's
just
something
about
the
project.
C
Really,
oh
I
see
this
thing
and
I
wish
it
was
better
and
you
prefer
to
submit
that
feedback
through
an
anonymous
form,
we're
providing
a
forum
for
that
feedback
as
well,
so
the
people
who
will
be
reading
this
feedback
will
be
the
Governance
Committee.
You
can
optionally
include
your
name
and
email
if
you'd
like
to
have
a
follow
up
conversation.
That
is
also
fine
to
include
anonymous
feedback,
so
it
can
really
be
about
anything
but
we're
primarily
interested
in
the
the
structure
of
the
project
and
ways.
Our
structure
or
a
process
could
be
approved.
E
H
C
F
C
That
seems
tight,
but
I
really
would
like
us
to
be
shipping
a
point
three
release
of
the
spec
and
to
have
that
contained
what
I
think
are
sort
of
the
the
last
issues
modulo
that
kind
of
named
name
tracer
resource
stuff,
but
that
seems
like
that'll
land
well,
but
obviously,
if
we're
releasing
that
spec
at
the
end
of
next
week,
I
wouldn't
expect
people
to
be
implementing
that
over
Christmas
break.
Why.
E
B
C
I
mean
but
I
would
say,
like
keep
shipping
versions.
Don't
worry
about
the
version
number
as
far
as
like
improving
the
the
spec
I
would
like
this
point
three
release
to
ideally
be
the
last
major
changes
and
I.
Don't
even
know
that
the
changes
the
changes
actually
are
like
getting
narrowed
down,
so
I,
don't
think
it'll
be
too
invasive
when
we
do
it,
but
my
hope
is
in
general,
in
q1,
starting
in
January,
we'll
be
able
to
start
pivoting
more
towards
production
izing.
C
D
F
Don't
right
now
have
a
schedule
for
beta
in
GA
and
I
know
we
we've
talked
about
having
a
g8
release
in
March,
but
one
thing
I
think
we
haven't
really
described
is
the
tests
that
we
want
in
place
before
we
call
our
releases
GA
and
I
think
this
is
having
to
focus
on
in
January.
So
as
as
we
have
the
final
version
of
the
spec,
and
we
know
about
what
every
client
needs
to
implement.
C
Maybe
like
beginning
of
January,
we
can
have
a
sort
of
some
kind
of
like
kickoff
meeting
to
specifically
brainstorm
around
like
well.
What
is
the
checklist
that
we
want
to
go
through
to
make
sure
like
what
are
the
specific
things
that
we're
looking
for
to
say
like
this
is
a
ga
release
like
what
do
we
want
to
test?
What
tests
do
we
want
to
have
in
place.
B
C
C
B
B
E
I
was
curious
if
we
should
do
this
in
this
meeting
and
if,
yes,
probably
you
are
the
best
person
or
say
hey,
who
wrote
the
I
mean
I
saw
the
the
write-up
is
weird.
But
if
let's
see,
let's
rephrase
the
question,
if
anyone
has
any
question
about
what
happened
cook
on
four
people
that
were
not
there
and
they
don't
know
what
we
need.
B
B
B
So
yes,
Sergey
summarized
the
key
notes:
the
talks
that
we
had
as
part
of
the
community
and
also
the
community
meetups
that
we
held
and
finally
the
observability
summit,
which
tied
it
organized
I,
did
end
other
settings
and
organized
and
yeah
it's
a
very
thorough
write-up.
Speaking
for
myself,
having
done
to
the
talks,
there
I
think
it
was
a
big
success
and
yeah
I
was
really
excited
just
to
see
how
large
the
communities
grown
and
how
often
open
telemetry
is
being
referenced
in
talks
and
like
other
projects
and
things
that
we
didn't
even
set
up.
F
B
It
was,
it
was
amazing,
like
especially
the
observe
observability
summit,
seeing
how
people
are
already
using
open,
telemetry
or
other
things
that
I
think
a
lot
of
us
have
worked
on
like
trace
context
in
ways
that
we
hadn't
originally
imagined
or
ways
that
we
hadn't
really
heard
about
it.
Toby
we
went
to
the
talks,
so
super
successful,
very
excited
for
the
next
cube
con
in
Amsterdam,
because
we
will,
with
any
luck,
be
going
beta,
then
so
yeah
so
yeah.
Looking
forward
to
that
also.
G
B
G
I
just
wanted
to
highlight
your
attention
if
you
want
to
be
a
mentor
of
like
some
students,
I'm
not
sure
all
the
details
about
this,
but
my
sincere
co-sponsor
five
projects,
connection
mentors
from
CN
CF
projects
to
students
who
wants
to
get
some
experience.
So
you
can
either
take
one
of
those
projects
and
like
put
your
name
as
a
mentor
and
totally
find,
is
any
additions
or
put
on
more
projects.
B
B
B
B
D
Our
focus
recently
was
primarily
on
two
areas:
number
one
is
improving
stability
and
making
sure
the
collector
is
ready
for
production.
Use.
Number
two
is
reviewing
and
accepting
new
components
from
other
contributors
with
AWS
exporter,
Asia
exporter,
on
stability
track,
we've
recently
added
metric
testing
to
the
collector
test
bed,
in
addition
to
testing
that
don't
really
exist
and
we
plan
to
add
more
more
than
20
s
or
protocols
supported
by
collector,
add
more
of
those
automated
tests
to
the
continuous
integration
builds.
D
Another
important
update
on
the
collector
is
regarding
the
stability
of
exporting
interfaces
now
code
base,
so
we
were
planning
to
announce
the
public
interfaces
consumable
by
third-party
dependencies
are
stable.
However,
this
announcement
needs
to
wait
till
we
declare
the
open
telemetry
protocol
as
final
and
the
truth
either
specification
seek,
since
we
plan
to
make
use
of
the
protocol
schema
in
the
internals
of
the
codebase,
so
I
just
want
to
make
sure
that
that
all
of
the
contributors
who
develop
components
for
them.
We
are
aware
that
these
interfaces
they
depend
on.
D
D
A
B
E
So
Tigran
couple
of
things
here,
even
though
we
may
add
new
allegations
or
new
things
that
will
be
backwards
compatible
right.
So
in
terms
of
in
terms
of
the
protocol
being
finalized,
we
we
haven't
made
any
commitment
that
will
not
add
new
features
or
new
things,
but
what
we'll
do
we'll
do
it
in
a
backwards
compatible
way,
so
I
think
from
that
regard.
I
would
expect
that
the
protocol
to
be
very
very
soon
yeah
I.
C
Tigran
I
haven't
looked
at
it
recently,
but
does
the
protocol
currently
contain
a
place
to
put
resources
great
yeah?
It
does
okay,
just
double-checking
that
that's
not
a
thing
or
so
we're.
Not
it's
cool,
yeah
I,
don't
anticipate
I
personally,
don't
see
any
spec
changes
on
the
horizon,
except
for
maybe
some
final
cleanup
with
metrics
I,
don't
see
anyone
I've
talked
to
proposing
something
that
would
really
change
the
protocol.
The.
D
A
B
B
G
A
G
G
Next
year
for
stabilization
efforts,
we
probably
will
have
a
lot
of
rearrangements
I
mean
maybe
I'm
not
sure
how,
because
small
are
to
make
sure
that
all
open
geometric
answer
works
nicely
his
dotnet
concepts.
So
maybe
we
can
move
songs
us
down
to
the
dotnet
itself
and
that
will
require
some
changes,
but
those
are
good
changes
and
I
think
we
can
accommodate
them
by
I
can
at
least
plant
them
by
March.
C
C
I've
been
trying
to
add
sort
of
triage
parties
to
the
calendar.
I
haven't
come
down
as
SF
this
week
and
kind
of
you
know
through
a
truck
for
my
schedule,
but
like
next
week,
I'm
happy
to
add
more
I
will
say
the
suspect
meetings.
We
always
seem
to
have
enough
stuff
happening
that
we
we
use
that
whole
spec
meeting
for
other
purposes,
so
it
hasn't
been
feasible
to
have
it
double
D
yeah
that
can
be
AI
right.
E
I
C
B
B
Protocol,
specs,
birch,
I,
think,
okay,
glad
to
hear
about
the
metrics
metrics
SDK
next
is
JavaScript
also
filled
in
so
they
completed
getting
started,
go
ahead,
okay
started
guide,
they
have
the
collector
exporter
and
my
sequel
and
brightest
plugins
Wow
and
a
few
more
bugs
I
thought
v3
is
released,
but
some
features
and
move
to
be
for
including
metrics
aggregation
from
UK's
exporter.
Ok,
move
an
additional
maintain,
excellent
and
some
there's
some
work.
That's
blocked
on
specs,
that's
Chris,
because
I
know
you're
on
the
Colin
you're
on
Python.
F
F
C
It's
so
there
is
a
dollar
installer
we've
been
helping
ported
over
based
on
the
data
dog
flavor,
but
because
that
had
a
different
license.
The
Apache
one
and
yadda-yadda
we've
just
been
waiting
for
their
lawyers
of
data
dog
to
be
satisfied
that
everybody's
happy
and
we're
dotting
the
is
and
crossing
the
t's.
B
Okay,
I'll
sign
it
francis
c++,
a
big
focus
is
currently
on.
Metrics
would
like
to
do
like
review
of
the
metrics
api
is
currently
under
development.
I,
don't
know
who
wrote
that.
But
if
you
want
to
speak
up
or
add
your
name,
there
I'm
sure
you
can
review
the
spec
changes.
Oh
no
you're
asking
sorry
I
think
they're,
asking
for
a
review
of
the
metrics
API
by
someone
else.
C
Know
I've
been
directly
involved
with
the
rest
group,
but
I
do
know
that.
That's
that
is
now
a
real
thing.
They
have
ported
over
an
implementation
based
on
from
what
I
understand.
I'm
sorry,
if
I'm
getting
this
wrong,
but
based
on
pre-existing
rest
project
meeting
up
with
basically
the
go
API
so
looking
at
what
was
made
and
go
and
making
a
REST
API
somewhat
based
on
the
go
flavor
of
open
telemetry.
B
C
As
always,
just
a
you
know,
a
general
request
if
people
are
interested
in
you
know,
as
things
are
moving
forward,
we
we
still
need
like
basic
content
on
the
website,
so
interested
in
writing
whether
it's
like
the
overview
content
or
something
specific
at
the
language
you
work
in
the
definitely
anything
is
better
than
nothing
and
there's
a
lot
of
nothing
on
the
website
right
now.
So
please
help
and
we're.
C
J
Actually
I
do
have
one
we
were
talking.
We
talked
about
this
offline
but
moving
the
community
meetings
to
not
be
in
the
same
week
as
the
public
governance
meeting
and
so
there'd
be
two
weeks
off.
So
that
way,
then
there's
two
sets
of
opportunities
for
the
community
to
actually
reach
people
a
wider
set
of
people,
instead
of
it
being
Wednesday
Thursday
morning.
Sure.