►
From YouTube: Opening Remarks / Keynote: State of the Community - Morgan McLean & Alolita Sharma, OTel Gov Cmte.
Description
SAVE THE DATES!
ArgoCon – Register Now | September 19-21, 2022 | Mountain View, California - https://events.linuxfoundation.org/argocon/
KubeCon + CloudNativeCon North America | October 24-28 | Detroit, MI - https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
KubeCon + CloudNativeCon Europe 2023 | April 17-21 | Amsterdam, The Netherlands - https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
OpenTelemetry is a collection of tools, APIs, and SDKs. Use it to instrument, generate, collect, and export telemetry data (metrics, logs, and traces) to help you analyze your software’s performance and behavior. Go here to learn more: https://opentelemetry.io/
Opening Remarks / Keynote: State of the Community - Morgan McLean & Alolita Sharma, OTel Governance Committee
303+304 (JW Marriott Austin | 110 E 2nd St, Austin, TX 78701)
Speakers: Morgan McLean, Alolita Sharma
Welcome to the Otel Community Day! In this session, Alolita & Morgan will walk through the state of the community, discuss where we've been and give you a preview of where we're going in 2022 and beyond.
A
Hi
everyone.
Can
you
hear
me
cool,
awesome,
okay,
so
thank
you
for
joining
in
today,
I'm
alolita
sharma
and
again
we
have
all
met
virtually,
I
think,
more
or
less,
but
it's
so
nice
to
see
you
all
welcome
to
open
telemetry
day.
We
are
going
to
be
doing
a
community
day.
Today
and
again
we
have
many
of
our
maintainers
here
many
of
our
contributors.
Here
again
everybody
who
has
been
participating
on
the
project
as
well
as
all
our
observability
groupies.
A
A
I
was
previously
a
senior
manager
at
aws
working
on
open,
telemetry,
prometheus
and
grafana.
Very
you
know
again,
hi
aws
team
happy
to
have
you
here
and,
of
course,
introducing
morgan.
Also
morgan
is
the
director
of
pm
at
splunk,
he's
also
a
fellow
open,
telemetry,
gc
member
and
previously
a
pm
at
google
working
on
observability
tooling
and
has
worked
also
at
microsoft
in
the
past
developing
web
services.
A
B
Let's
review
how
we
got
here.
Metric
systems
have
been
around
a
long
time,
but
I'm
thinking
about
what
happened
around
10
years
ago,
looking
at
open
source
systems
prior
to
then
we
had
just
one
kind
of
metric
instrument,
I'll
call
it
the
number
instrument.
We
would
use
it
to
report
numbers
with
timestamps
and
then
we
would
plot
those
numbers
as
a
function
of
time.
The
result
is
numbers
in
a
line.
The
nice
thing
about
numbers.
Is
they
support?
Math?
B
A
B
A
A
We
began
work,
you
know,
shifting
into
instrumentation
and
metrics
2020
may
logs
was
added
as
a
new
signal,
which
is
pretty
significant.
So
now
you
know
this
is
back
in
the
past
two
years
ago
and
and,
as
you
know,
many
of
you
who
are
involved
in
the
project
logs
has
been
continuing
on,
as
the
project
has
kind
of
focused
in
on
tracing
and
metrics
tracing
landed
in
src
and
then
ga
last
year,
in
september,
2020
and
in
january
2021.
A
A
And
then
there
was
a
significant
amount
of
work
done,
which
is,
you
know,
been
ongoing
through
the
prometheus
work
group
on
the
project,
as
well
as
the
work
that
has
been
done
by
the
different
sigs
on
the
different
languages.
11
languages
are
supported
on
the
project
and
to
enhance
metrics
implementation
for
the
collector
agent,
as
well
as
the
apis
and
sdks
in
11
languages,
so
fast
forward
to
december
2021.
A
So
let
me
just
make
sure
that
you
can
see
it
so
september.
2021
fuji
tracing
was
finally
completed
as
ga
and
the
stanza
logging
agent,
which
is
kind
of
one
of
the
foundation
components
of
the
logging
work.
That's
happening
on
the
project
were
added
right,
so
big
milestones
december
2021,
the
logging
data
model
was
finally
and
the
protocol
for
phase
one
have
reached
ga.
So
that's
very
exciting
because
you
know,
as
a
project
completes
metrics
implementation
will
switch
over
to
supporting
logging
and
may
2022
in
at
kubecon
and
valencia.
A
As
you
know,
going
forward
into
2023
is
the
completion
of
logging
and
we
are
expecting
that
logging
releases
and
implementation
will
go
in
for
rcs
later
this
year
and
then
ga
is
targeted
for
the
first
half
of
2023,
so
that
kind
of
gives
you
a
glimpse
of
you
know
some
of
the
milestones
that
the
project
has
hit
continuously
and
again,
as
many
of
you
know,
milestones
are
also
dependent
on.
You
know.
A
A
A
As
you
can
see
in
the
last
you
know
part
there
are
five
rc's
in
progress
and
have
already
been
released
and
seven
are
in
progress.
So
we
are
anticipating
a
rolling
ga
for
the
different
languages
you
know
through
this
year
and
then
we
have
logs
as
the
final
signal
which
is
in
progress
right
now,
the
as
you
can
see,
the
protocol
has
already
been
stabilized
and
again.
Api
specification,
as
well
as
sdk
specification,
is
the
work
in
progress
again.
A
So,
what's
the
current
artifact
status,
this
is,
you
know
for
the
different
languages.
We
again,
as
I
said,
open
telemetry
supports
11
languages
and
apis
and
sdks
and
11
languages.
These
are
the
top
ones,
you
know
which
have
the
most
amount
of
activity,
and
then
there
are
others
which
are
not
on
this
list,
but
you
know
are
in
progress.
A
Also,
as
you
can
see,
the
collector,
which
is
used
as
an
standalone
agent,
is
in
ga
for
traces
beta
for
the
user
apis,
it's
in
rc,
the
user
api
is
stable
at
this
point,
so
you
should
be
able
to
you
know,
take
it
and
run
with
it
as
an
end
user.
There
are
some
improvements
and
enhancements
that
are
being
made
for
developer
apis
and
that's
you
know,
work
in
progress
java
is
an
rc
for
metrics.
Js
is
also
nrc.
A
Python
is
an
rc
and
as
of
the
late
as
of
this
week,
c,
plus
plus
as
well
as
dot
net,
have
already
hit
ga
and,
of
course,
as
you
can
see,
go
ruby
and
php
are
close,
be
close,
almost
close,
but
they're
not
at
rc
status.
There's
work
in
progress
again
for
any
of
these
languages.
You
know
if
you're
interested,
please
get
involved
and
help
and
then
comes
logs
right.
A
A
Okay,
so
switching
to
community
right,
so
I
mean
many
of
you
know
as
as
you've
all
been
involved
that
open
telemetry
has
seen
an
amazing
growth
in
the
last
three
years,
and
you
can
see
you
know
literally
more,
almost
a
thousand
seven
hundred
companies
participating
in
the
project.
It's
really
phenomenal
to
see
the
kind
of
growth
that
the
project
has
seen
open.
Telemetry
is
the
most
popular
project
on
in
observability
at
under
the
cncf
right
after
kubernetes.
A
It's
amazing,
with
the
kind
of
energy
and
the
collaboration
across
the
different
projects
and
teams
that
this
contribution
has
been
possible
so
far,
and
we
still
continue
to
see
it
growing
and
maintaining
momentum
as
we
go
into
logs,
which
is
in
one
sense
one
of
the
most
well
established
forms
of
monitoring,
as
you
know,
but
at
the
same
time
also
there's
an
enormous
amount
of
complexity
in
implementing
logs.
Well
just
wanted
to
do
a
call
out
most
of
the
world.
You
know
that
revolves
around
observability
is
involved
in
this
project.
A
Some
of
the
biggest
you
know,
vendors,
who
are
very
much
involved
in
building
out
observability
solutions
or
services
of
their
own,
are
involved
as
well,
as
you
know,
just
open
source
contributors
who
have
formed
the
fiber
of
the
project
as
maintainers
as
well
as
leaders
on
the
project.
Again
huge
thanks
to
our
contributors,
you
can
see.
Independent
is
a
very
interesting.
You
know
call
out
here.
There
are
a
lot
of
inter
independent
contributors
to
the
project.
A
As
you
can
see,
you
know,
many
of
these
companies
who
are
listed
here
and
organizations
are
very
involved
and-
and
we
continue
to
see
more
growth
on
on
you-
know,
end
users
actually
coming
in
and
joining
the
project
to
provide
requirements
and
being
able
to
actually
work
with.
You
know
voicing
some
of
the
requirements
that
they
have
and
you
you
know
configuration
management,
for
example,
is
a
big
area.
A
I
also
wanted
to
call
out
some
of
the
extraordinary
collaboration
and
interop
work
that
the
project
you
know
open,
telemetry,
has
done
and
has
been
involved
in
and
continues
to
be
involved
in
again
huge
thanks
to
all
the
contributors
from
these
projects
who
have
worked
very
closely
with
us.
Many
of
us
are
close
friends,
close
collaborators,
you
know
and
and
really
love
observability
and
open
source.
So,
as
you
can
see,
kubernetes
openmetrics,
prometheus
jaeger,
zipkin,
pixie,
cortex
thanos,
fluent
pit
fluently
stats.
The
prom
scale
are
some
of
the
big
projects.
A
Who've
been
involved
and
worked
closely
with
us.
We
continue
to
have
work
groups
in
these
areas
where
we
have
discussed
everything
from
protocols
to
what
makes
sense
from
an
observability
standpoint.
Apis
looking
at
compliance
tests
again,
we
worked
very
closely
with
richard
from
openmetrics
as
well
as
prometheus.
You
know
the
prometheus
project
to
drive
some
of
the
open,
the
prometheus
compliance
tests.
A
You
know,
which
were
announced
by
the
project
and
very
proud
to
see
the
collaboration
in
terms
of
compliance
tests
actually
being
part
of
open
source
projects
to
you
know
ensure
that
the
end
user
experience
is
really
first
class
and
there
is
full
compatibility
for
consumption
of
observability
data
across
these.
You
know,
platforms.
A
So,
what's
next
on
the
roadmap,
and
you
can
see
there's
lots
of
activity
which
is
happening
above
and
beyond
just
the
implementation
of
the
apis,
the
sdks
and
and
and
the
foundations,
if
you
will
of
supporting
you,
know
the
apis
and
sdks
and
the
collector
agents
of
in
the
languages
and
those
are
semantic
conventions.
As
many
of
you
know,
semantic
conventions
are
very
important
for
being
able
to
define
and
support,
correlation
and
insights
that
are
gathered
from
different
types
of
data
signals
and
so
that
there's
a
fair
bunch
of
work
happening
around
there.
A
So
get
this
having
this
kind
of
a
web
group
and
an
active
dialogue
really
helps
another
area
which
is
been
supported
and
and
was
added
to
the
project
last
year
is
client
telemetry,
and
this
is
a
very
important
area.
As
you
know,
many
of
us
come
from
the
server
infrastructure
world
where
server
telemetry
in
observability
is,
for
you
know,
quite
well
defined
and
supported,
but
client
telemetry
is
equally
important
for
those
of
us
who
have
networks
of
devices
or
iot
applications
or
web
browsers
or
programs.
You
know
that
are
running
on
browsers.
A
It's
it's
equally
important
to
understand
the
observability
and
observe
the
signals
for
system
performance
and
system
health
end
to
end
and
and
so
look
out,
for
you
know
the
work
that's
happening
in
the
client
telemetry
area,
which
will
then
again
intersect
as
a
stack
with
server
observability
to
actually
provide
a
full
stack
of.
You
know
really
system
performance
system,
health
for
those
networks
that
actually
you
know,
support
end-to-end,
not
only
services,
another
area,
a
set
of
areas
which
is
very
active
and
also
we
have
work
groups
for
these
are
client
instrumentation.
A
A
Another
area,
that's
a
another
language
that's
coming
in
is
javascript,
and
I
know
some
of
our
maintainers
will
be.
You
know
covering
that
later
today.
So
again,
you
know
we
are.
The
objective
of
the
project
is
to
make
instrumentation
as
seamless
as
possible,
and
and
again
we
invite
you
know
any
collaborators
who
are
interested
in
improving
instrumentation
to
work
with
us,
extending
observability
all
the
way
from
client,
apps
and
web
apps.
A
You
know
takings
fans,
metrics,
metadata
logs
and
making
that
available
easily
another
couple
of
work
groups
that
have
just
kicked
off
in
the
last
few
months.
One
is
agent
management,
and
this
really,
you
know
again,
goes
back
to.
How
do
you
make
agent
management
easy?
This
is
a
complex
area
because
you
not
only
have
local.
You
know
configurations
for
like
an
collector
agent,
for
example,
but
you
also
have
remote
configuration
right
for
many
large
scale.
A
Networks
that
end
users
have
remote
management
is
a
key
part
of
you
know
how
they
isolate
across
their
networks
and,
at
the
same
time,
are
able
to
interoperate
with
configurations
and
allowing
sdk's
agents,
and
the
collector
to
have
their
configuration
remotely
updated
is
a
big
big
is
a
big
area
of
work.
That's
ongoing,
there's
a
design
spec,
which
is
being
discussed
right
now
on
the
project,
especially
in
the
collector's
sig.
A
Again,
if
you're
interested
in
you
know
kind
of
even
tracking
the
instance
of
system
health
for
the
collector
agents
that
are
running
on
your
services
or
on
the
end
user
networks,
understanding
health
and
being
able
to
communicate
status
is
something
very
interesting
and-
and
you
know
again,
this
is
the
word
group.
That's
working
on
this.
A
Similarly
again-
and
this
is
amazing-
you
know
this
is
how
open
source
works.
We
just
kick-started
a
profiling
sig,
where
we
are
starting
to
look
at
how
we
can
actually
introduce
and
add
a
new
signal
that
will
bring
in
visibility
out
of
the
box
for
code
performance,
and
this
is
just
started
from
you
know-
discussions
with
the
larger
community
and
maintainers
at
kubecon
earlier
last
month,
and
there
were
a
bunch
of
discussions
before
that,
because
we've
been
working
with
pixi
and
other
projects
very
closely
on.
A
You
know
how
profiling
could
be
supported,
but
there's
a
new
sig
that
we
are
that
we
have
and
and
again
needless
to
say,
if
you're
looking
to
participate
in
any
of
these
areas,
there
is
a
calendar
that
you
know
for
the
project
that
you
can
just
sign
up
for
and
just
join
any
sig
or
work
group
that
you
want
to
that's
interesting
to
you.
You
can
attend
some
of
the
meetings.
While
there
are
specific
discussions
ongoing
there,
the
project
does
record
and
maintain.
A
You
know
very
good
notes
about
each
of
these
sig
areas,
so
you
can
catch
up
on
them
later.
However,
you
would
like
to
see
better
tagging
of
our
youtube
videos,
but
on
the
other
hand,
we
do
have
them
recorded
if
you
want
to
go
and
catch
up
so
just
wanted
to
call
out
some
of
the
major.
You
know
areas
that
we
are
working
on
and
and
of
course,
you
know
going
forward.
There'll
be
also
many
other
areas
which
I'm
sure
will
be.
A
Okay,
so
again
you
know
with
the
thousands
of
contributors
who
have
contributed
to
open
telemetry.
There
is
many.
There
are
many
ways
to
get
involved
and,
needless
to
say,
everyone
is
welcome.
I
really
have
found
the
project
to
be.
You
know
I've
been
involved
in
the
project
for
three
years
and
it's
really
an
amazing
project
to
be
involved
in
there's
just
so
much
activity
and
so
much
discussion
and
and
really
really
nice
people
that
you
know
we
collaborate
and
work
with.
A
So
so
again,
I
welcome
you
to
join
in
as
a
developer
again,
who
is
not
an
open
source
pro
but
is
getting
involved
in
open
source
from
their
company
or
from
your
organization.
Again,
it's
very
easy
to
join
in.
You
can
just
listen
in
lurk
on
the
sigs
get
involved.
Work
on
this
read
the
specification.
There's
a
lot
of
documentation
on
the
project.
A
A
We
have,
you
know
contributing
built
out
ci
cd
pipelines,
continuous
security
pipelines,
release
tooling,
again,
support
and
you
know
contribution
in
11
language,
spec
areas.
So,
needless
to
say,
there's
a
lot
to
be
done
right
and,
and
you
can
easily
get
involved
in
any
of
the
areas
if
you'd
like
to
write
features,
get
involved.
A
Welcome
you
to
do
so.
If
you
like
to
you,
know,
work
on
infrastructure,
ci
cd,
you
see,
a
continuous
security
is
an
area
you
can
get
involved
in
and
and
also
would
like
to
call
out
that
open
source
projects
of
this
size
and
magnitude
are
usually
not
single
dimensional.
It's
not
only
developers
who
are
working
on
these
projects.
We
have
really
an
extraordinary
number
and
and
wonderful
community
of
product
managers.
Community
managers
who
are
involved
in
the
project
again,
you
know
we
all
work
together.
A
Brainstorm
about
you
know
how
best
designs
can
be
built
and
for
the
different
components,
and
you
know
again
open
source,
iterates
and
and
polishes
and
improves
continuously
so
would
welcome
again.
You
know:
there's
lots
of
opportunity
to
create
awareness,
to
actually
educate
operators
and
end
user
developers
to
use
open,
telemetry
well
to
add
project
documentation
to
share
knowledge.
You
know
work
on
semantic
conventions.
If
that's
your
thing
run
an
open
telemetry
meet
up.
A
I
think
we
have
a
really
nice
community
across
the
world
of
folks
who
are
doing
online
podcasts
as
well
as
open
telemetry
meetups
in
person,
publish
blog
posts
and
demos
on
the
project
site.
You
can
contribute
it's
as
simple
as
doing
a
pr
and
also
welcoming
end
users.
You
know
to
again
join
in
provide
feedback.
You
know
your
feedback
matters,
a
lot
get
your
developers
involved
in
open,
telemetry,
provide
your
use
cases
and
requirements,
and
these
are
just
some
of
the
areas
you
can.
A
You
know
there's
a
lot
of
lot
of
energy
and
enthusiasm
around
these.
Last
but
not
least,
I'd
like
to
thank
all
of
our
contributors,
without
whom
we
wouldn't
have
such
an
awesome
project.
Our
maintainers
our
sponsors
and
hosts
again
very
thankful
to
cncf,
for
you
know,
actually
pulling
together
and
providing
us
the
support
for
the
for
doing
open
telemetry
community
day
today,
and
thanks
to
our
sponsors,
without
whom
we
wouldn't
be
able
to
pull
everybody
together
too.