►
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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.
What Is the CNCF TAG Observability and How You Can Join Our Effort! - Bartłomiej Płotka, Red Hat; Alolita Sharma, Amazon; Richard Hartmann, Grafana Labs; Matthew Young, Everquote
The Technical Advisory Groups (TAGs, formerly SIGs) were created by the CNCF to help provide technical guidance and expertise across projects pertaining to a specific domain. One of the domains that are continuously demanded and show great innovation within the cloud-native ecosystem is Observability. In this talk, the TAG Observability co-chairs and team lead will introduce the activities we do with TAG members and the community. You will learn what has been done so far and how you can join us in our efforts to improve the observability ecosystem around us. We are looking for a diversity of skills and backgrounds, so we can give out more supporting materials and best practices for end-users and contributors around monitoring and observability. The audience will learn what TAG Observability is responsible for, how to contribute and where to find us. Hopefully, this talk will inspire your to join our Observability community!
A
So
if
you
can
do
it,
it
doesn't
matter
so
welcome
everyone,
we're
bartek
and
richie.
As
you
probably
know,
as
per
usual,
we
are
trying
to
optimize
these
for
or
questions
which
also
means
that
if
someone
can
go
on
slack
and
check
online,
if
there's
any
questions
in
the
tag
observability
channel
for
everyone
who
is
following
online,
please
ask
questions
in
the
tag
observability
channel
and
I
presume
someone
up
here
is
going
to
volunteer
to
just
read
them
out.
Okay,
ian
is
volunteering
perfect,
so
housekeeping
aside.
B
A
Hello
person,
please
thank
you
yeah,
so
welcome
to
the
tech
observability
thing.
What
is
tag
technical
advisory
group
renamed
from
you
as
well?
No
behind
you,
the
person
behind
you
person,
hello,
no
yeah,
includes
the
nose.
Thank
you.
No
I'm
not
taking
off
the
mask.
I'm
a
decent
person,
I'm
keeping
the
mask
on
anyway.
A
Your
mask,
this
is
highly
highly
unfair
to
everyone
else.
It's
like
peeing
into
the
pool,
it's
simply
unfair.
You
you
legally
agreed
to
wear
a
mask.
I
hate
this
thing.
Just
do
it
so
anyway,
as
there
is
huge
confusion
about
about
all
of
the
structure
of
cncf,
let's
walk
through
this
quickly
and
with
my
governing
board
head
on.
We
created
this
really
really
pretty
slide
it's,
but
it
gives
you
a
good
overview.
So
you
have
the
governing
board,
which
has
a
few
subcommittees.
A
There
is
a
what's
a
budget
subcommittee
introduced,
so
that's
that's
the
governing
board,
which
basically
sets
the
the
whole
structure
of
of
cnc
under
the
governing
board.
You
have
the
technical
oversight
committee,
which
I'm
also
part
of
under
those
you
have
the
tags
and
the
technical
oversight
committee
basically
is
about
the
life
cycle
of
the
projects.
A
A
Recently,
we
named
from
special
interest
groups,
which
used
to
be
called
zig,
yeah
security,
observability
blah
blah
blah,
and
then
you
have
the
end
user
community,
which
also
has
their
sigs
with
a
still
name
overlap
of
the
kubernetes
six,
which
is
why
the
cnc
f6
got
renamed
two
tags.
And
yes,
this
is
all
confusing,
and
this
is
really
really
ugly
but
like
this
should
at
least
give
you
the
the
overview
and
from
the
amount
of
people
who
took
pictures
of
this.
I
guess
this
is
good
content
anyway.
A
A
A
A
Okay,
so
like
from
the
initial
control
theory
from
like
coming
from
math
and
like
having
mathematical
models
of
industrial
control
processes,
observability
is
defined
as
being
able
to
determine
the
internal
state
of
a
system
simply
by
looking
at
its
inputs
and
its
outputs.
There's
some
some
discussion
on
end
of
on.
A
There's
questions.
There's
many
other
things
we
see
more
and
more
that
we
have
overlapped,
that
we
have
new
people
coming
into
the
observability
space,
to
define
this
wider
and
wider
and
wider
and
wider
to
basically
give
you
more
insight
into
your
complete
system,
because
if
you
already
have
certain
things
about
like
your
performance,
metrics
or
your
api
contracts-
and
you
already
know
that
this
thing
is
in
this
and
that
state
you
can
use
this
as
part
of
your
whole
observability
story.
B
Thank
you
reggie.
So
now
comes
the
difficult
part
right,
so
we
know
theory,
but
are
there
any?
You
know,
projects
that
help
us
to
fulfill?
You
know
those
those
those
rules
around
finding
those
unknowns
and
known
unknowns
and
known
unknown
unknowns
right.
So
how
to
find
those
we
have.
This
you
know,
landscape
is,
is
very
very
complex,
as
you
can
see
like
this
kind
of
there
are
memes
about
that.
So
it's
kind
of
clear,
but
there
is
some.
B
You
know
rule
to
this
madness,
and
this
is
why
we
try
to
aggregate
those
projects
into
groups
of
things
that
you
know
have
in
common.
So
we
have
this
observability
group
that
you
can.
You
can
zoom
in.
There
are
lots
of
projects
that
are
kind
of
members
of
direct
members
of
the
cncf
in
either
sandbox,
incubated
or
or
graduated,
or
there
are
kind
of
projects
related
in
the
open
source
that
are
somewhat.
You
know
connected
to
the
observability
and
kind
of.
B
Hopefully
I
mean
I'm
pretty
sure
you,
you
know
prometheus
already,
because
that's
kind
of
a
default
monitoring
tool
for
for
communities,
but
there
are
more
right,
as
richard
mentioned,
that
their
signals
are
growing
growing
growing.
There
are
more
types
of
the
information
categories
of
information
that
we
can
present
and
use
in
in
various
ways,
so
there
are
more
tools
than
just
from
to
use
to
kind
of
leverage.
B
Those
and
with
with
the
stack
we
try
to
ensure
you
know
all
of
those
there
is
some
kind
of
map
towards
you
know
how
to
use
those
and
which
you
should
use
based
on
your
use
cases.
So,
let's
focus
on
the
cncf
projects
now
right
so
in
the
strict
kind
of
cncf
landscape
around
you
know,
sandbox
incubating
and
graduating
projects.
We
have
a
few
of
those
graduated
prometheus
jagger
and
fluency,
so
religious
representative
from
metrics
logging
and
tracing
so
kind
of
already.
B
You
know
those
pillars,
the
basic
pillars
that
we
discuss,
but,
of
course
we
have
other
projects
that
represents.
Maybe
you
know
extensions
that
morse
some
some
kind
of
solutions
around
that
that
really
it's
not
easy
to
make
sure
they
cooperate
with
each
other,
all
those
standards
and
and
apis
and
and
technologies.
B
But
we
try
our
best
to
make
sure
you
know
those
teams
talk
to
each
other
and
there
is
like
a
common
pattern
and-
and-
and
you
know
way
of
using
those
together
in
this
in
the
stack
right
so
now
with
those
projects.
Let's,
let's
see
what
we
can
do
with
those.
So
at
the
end,
project
is
one
thing,
but
what
tack
is
responsible
for
what?
What?
What
is
our
kind
of
future
future
steps?
So
we
want
more
content
right.
So,
as
you
can
see,
the
space
is
very
complex.
B
We
know
the
basics
like
prometheus,
but
what's
next,
how
to
how
to
really
have
this
observability
story,
concretely
figure
it
out
and
to
to
do
that
we
need
to
have
more
educational
content
and
kind
of
sort
of.
I
would
call
it
an
index
of
you
know
how
to
start
with
observability
in
the
cloud
native
space.
So
we
need,
you,
know
more
help
and
and
feedback
and
kind
of
more
hands
to
to
really
create
those
videos,
blog
posts,
tutorials
and
and
demos
right.
B
So
there
are
lots
of
good
content
that
we
we.
You
know
someone
did
over
time
in
this
in
the
space,
but
you
know
it's
hard
to
find
those,
so
we
have
to
make
sure
you
know
it's
really
easy
to
consume.
Furthermore,
we
want
to
focus
on
white
papers.
We
already
have
one
which
is
really
99
done,
and
it's
just
really
missing,
like
last
touches,
which
already
explains
this
landscape
in
in
details,
those
signals
how
to
potentially
use
them.
B
What
are
the
kind
of
you
know,
tricks
and
tips
and
and
and
kind
of
where
to
start
so
you
can
you
could
I'll
tell
you
where
you
can
find
it
already,
but
we
need
more
of
those
right
and
we
need
more
more
hands
to
help
with
it
and
by
the
way,
the
white
purple
that
is
already
was
created
was
jointly
created
by.
I
know
at
least
like
dozen
people
right,
so
it
wasn't
like
one
person
responsible
for
that,
because
that's
not
the
point.
B
Our
point
is
to
build
community
and
make
sure
we
can
work
together
so
of
course,
part
of
the
best
best
best
practices,
demos
and
yeah-
really
getting
more
end
users
right.
So
I
think
we
touched
that
on
our
meeting
on
monday
here
in
kubecon,
but
essentially
we
really
want
to
make
sure
that
the
questions
and
the
direction
of
the
topic
is
influenced
by
the
end
user.
B
So
someone
that
doesn't
directly
sell
observability,
because
then
there
might
be
bias
right
and-
and
there
might
be
other
you
know
they
might
not
see
the
problem
that
end
users
are
are
seeing
right.
So,
especially
if
you're
end
user-
or
you
know-
maybe
end
users
interesting
in
observability,
just
direct
them
to
attack
observability,
please
that
would
be
very,
very
helpful.
B
So
this
is
where
you
can
really
find
us.
We
have
meetings
which
are
fortnightly,
tuesday
evenings
evenings,
of
course,
european
time,
and
we
have
repository
github
responsory,
which
is
kind
of
the
center
of
what
we
do.
We
put
issues
there
for
you
know
anything
that
we
want
to
do
in
future.
Maybe
you
want
to
assign.
Maybe
you
want
to
assign
yourself
and
help
with
that.
That
would
be
amazing.
Maybe
you
have
ideas
to
propose.
Do
that
do
do
it
there?
The
white
paper
you
can
find
in
this
repository
as
well.
B
A
A
D
Sorry,
it's
not
saying
that
I'm
watching
this
live
channel,
okay,
cool,
but
I
do
have
a
question,
though
sure
so
in
both
of
your
opinions.
Obviously,
we
have
the
state
of
visibility
where
we
are
at
the
moment,
but
kind
of
looking
one
two
five
years
in
the
future.
What
do
each
of
you
think
is
going
to
be
the
next
best
addition
to
the
observability
tool
belt
that
we
we're
not
using
today
that
we
may
be
using
in
three
or
five
years
time.
A
A
A
So
what
I
personally
expect
is
is
more
distillation
of
all
those
signals
back
again
into
metrics,
because
those
are
the
cheapest
way
and
the
most
efficient
and
the
most
effective
way
to
to
work
with
insane
amounts
of
data
and
allow
you
to
just
get
more
insight
into
your
system
with
with
less
cost.
The
other
thing
is
integration,
integration,
integration,
those
are
all
tools.
They
are
not
ready
solutions.
B
Yeah
and
from
my
side
I
think
for
the
future.
We
definitely,
I
would
say
we
see
more
of
you
know,
correlations
side
of
the
story,
which
means
that
you
might
have
one
signal
but
how
to
cooperate
with
other
signals
right,
and
it
is
especially
important
because
people
will
realize-
or
I
mean
hopefully,
they
realize
right
now
that
you
cannot
solve
all
the
use
cases
with
like
fully
tracing
and
only
tracing
and
then
deriving
metrics
and
all
of
this
because
of
the
cost
reasons
right.
B
So
you
really
have
to
look
on
diversifying
your
your
observability
to
make
sure
you
really
kind
of
be.
You
are
pragmatic
in
what
you
do,
and
maybe
you
use
more
expensive
signals
like
you
know,
even
logging
or
or
tracing
or
even
like,
even
even
more
gradual
event.
Observability
you
you
do
that
only
ad
hoc
only
for
you
know
like
dynamically,
enable
that
or
disable
that.
So
I
would
see
all
those
solutions
to
work
better
together,
and
I
hope
for
that
as
well.
D
A
E
E
C
A
People
who
are
not
aware
of
this
so
like
with
my
cortex
is,
is
a
healthy
project.
Yes,
grafana
labs
decided
to
fork
away
from
it
and
maintain
its
own
thing,
and
I
like
many
properties
about
about
mimir.
Personally
speaking,
I
even
considered
not
joining
prometheus
in
2015-2016
because
it
was
apache
2
and
not
a
gpl,
and
personally
I
prefer
reciprocal
licenses
over
over
non-reciprocal
ones.
A
A
B
So
I
think
you
mean
the
cows
tooling,
for
example,
right,
and
I
think
there
is
a
revelation
in
this
space
because
I
think
they
propose
to
create
a
tag.
I
don't
know
if
you
remember
if
they
actually
did
it,
but
I'm
pretty
sure
I
mean
I
think
it
will.
It
makes
sense
to
kind
of
separate
this
kind
of
cows.
Monkey
solutions
to
be
a
separate,
very
you
know,
focused
group.
That
really
focuses
on
that.
Of
course
everything
is
really
connected
to
observing
those.
You
know
the
scowls.
B
This
is
like
plant
cows
and
really
learn
from
that,
but
in
the
same
time,
in
the
same
way,
security
is
really
connected
to
observability.
So
we
should
have
a
ways
to
cooperate
between
those
groups,
but
at
the
end
it
makes
so
much
sense
to
group
them.
So
I
think
that
that's
the
solution
for
now,
so
we
can
essentially
hopefully
contribute
the
content
we
put
in
white
paper
there
or
maybe
lack
of
it.
B
A
You
can
easily
argue
that
chaos
testing
is
just
a
way
to
introduce
more
input,
more
signals
for
observability,
which
isn't
the
definition.
I
would
choose
myself
like
initially,
but
it
is
a
valid
and
logically
consistent
definition
of
what
what
chaos
testing
is
and
that's
where
this
thing
is
coming
on.
This
is
all
related
to
making
the
code
work
and
it's
just
how
you
look
at
it
and
how
you
approach
it.
A
The
the
commercial
or
enterprise
term
is
shift
left
shift
right
when
you
like,
before
you
even
run
the
code
after
you.
Sorry
before
you
write
the
code
after
you
write
the
code,
and
this
is
like
just
a
shift
draft
shift
right
thing
from
from
that
perspective,
but
it's
basically
all
the
same
general
intention.
A
Basically
ask
them
what
they
need.
The
white
paper
is
one
of
those
one
of
those
initially.
The
other
thing
is
I
myself.
I
have
a
pretty
old
talk
about
like
intro
to
observability,
and
I've
been
given
this
again
and
again
and
again
also
in
the
context
of
of
tag
observability,
because
the
thing
is
the
fundamentals:
don't
change
just
the
audience
changes,
but
several
people
in
this
working
group
on
monday,
because
again
we
had
this
other
meeting
for
tag
observability
on
monday
weren't,
even
aware
this
existed.
A
So,
oh
contrib!
Oh,
oh
sorry,
sorry,
sorry,
I
I
got
it
completely.
The
other
way
around
sorry
show
up
voice
your
problems,
work
with
others
on
solving
those
problems.
When
you
have
solved
your
problems,
maybe
write
a
blog
post
or
something
like
teach
others
about
how
you
did
it
case.
Studies
are
one
of
those
types
of
of
talks
which
are
super
well
received
at
coupon
as
well,
where
end
users
just
walk
through
how
they
actually
achieve
their
goals.
A
And
again
the
thing
is
the
fundamentals,
don't
change
and
bluntly
speaking,
your
case
study
from
next
year
when
you
submit
it.
Hopefully
it
will
be,
or
this
year
will
be
largely
the
same
as
the
thing
which
someone
else
did
two
years
ago.
That's
not
the
point.
The
point
is
it's
new
and
the
audience
changes
and
but
the
main
thing
is
show
up
to
the
calls
get
involved.
E
Try
to
alert
on
that.
But
it's
always
you
know
a
bit
reactive,
yes,
and
we
end
up
with
a
lot
of
data
without
tracing
and
so
on.
So
we
end
up
with
the
big
cost
of
of
that.
So
what
is
the
I
don't
know?
Maybe
it's
naive.
But
what
is
the
good
way
to?
I
don't
know,
choose
what
is
valuable
for
for
us
to
to
observe
right,
maybe
not
from
business
point
of
view,
because
it's
always
you
know
a
bit
related
with
what
the
company
is
doing
but
from
technical
point
of
view,.
B
So,
first
of
all,
I
would
like
to
say
that
it's
not
always
reactive,
like
you,
can
totally
build
automation
that
really
reacts
to
metrics
and
logs,
like
one
of
the
one
of
kind
of
a
very
useful
example
that
you
can
do
right
now
is
to
you
know,
use
horizontal,
auto,
scaler
or
vertical
apple
scalers
and
hook
that
into
promoters
metrics
that
will,
for
example,
your
application
will
tell
that
you
know
the
cpu
is
too
high
and
you
have
to
scale
it.
So
that's
you
know
another.
B
D
D
D
A
I
mean
when
you,
when
you
look
back
and
this
this
is
a
kind
of
I
think
it
comes
from
ibm
and
I
think
it
comes
from
like
the
70s
or
so
so
again.
None
of
what
we're
doing
is
new
it's.
It
is
not
new.
It's
just
like
more
modern
technology,
different
different
api
interfaces,
http
replacing
tcp
blah
blah
blah
blah
blah,
but
it
is
not
fundamentally
new
and
like
for
literally
50
years
in
computer
science.
A
The
running
wisdom
was
that
you
should
invest
roughly
15
to
20
of
your
resources
into
the
monitoring
of
the
actual
software
and
oh
like
if
you,
if
you
read
the
actual
literature
and
the
actual
research
over
the
years
over
the
decades.
This
number
didn't
really
change
so
like
this
is
kind
of
the
sweet
spot
where,
where
we
as
humanity
landed
on
as
as
the
overhead
or
the
cost
of
doing
business,
which
might
also
be
a
good
way
to
to
tell
your
manager
hey.
D
A
G
I
guess
I
guess
it
depends.
You
know
there
are
different
companies
and
some
companies
are
high
and
some
companies
are
used
to
know
maybe
rely
not
on
the
observability
signals.
Maybe
they
rely
just
on
the
calls.
Someone
will
call
say:
oh
it's
down,
yeah,
it's
everything
about
knowledge
and
where,
like
you
said,
other
end
users
and
ourselves
community,
we
educate
our
companies
to
educate
our
users
and
situation
changes.
Of
course
I
saw
on
the
conference.
Observability
is
very
popular
topic
here,
a
lot
of
different
solutions.
G
A
C
H
I
I
re,
I
was
reviewing
the
the
white
paper
and
I
really
like
it
as
a
resource,
so
I'm
looking
forward
to
when
it's
released
and
like
I
can
refer
to
it
when
someone
asks
me
an
observability
I
wouldn't
like
for
now.
I
think
I
understand
better.
What
do
you
want
to
do,
but
again,
short
term?
Do
you
have
already
some
other
outputs
like
in
the
pipeline,
or
is
there
something
that
you're
already
working
on
that
there
will
be
some
output
off.
A
A
So
people
see
it
again
or
though
this
audience
sees
it
for
the
first
time,
because
again
the
content,
like
the
underlying
things,
don't
change,
it's
the
audience
which
changes
like
this,
this
thing
from
from
going
from
logs
to
metrics
and
having
metrics.
If
you
go
back
to
to
the
internet
20
years
ago,
they
made
the
same
move.
A
If
you
go
to
power
grids
70
years
ago,
they
made
the
same
move.
If
you
go
back
to
to
to
ships
where
the
name
log
book
and
logs
is
coming
from
hundreds
of
years
ago,
they
made
the
same
move.
Humanity
has
done
this
again
and
again
and
again
and
again
when
they
they
needed
to
to
get
an
overview
over
something
they
started.
Writing
things
down
versus
individual
events,
linking
those
events
and
then
extracting
numbers
from
them.
B
It's
worth
to
mention
that
there
is
also
nice
demo
in
in
building
right,
so
I
think
we
have
even
one
hendrik
who
helped
with
that.
So
look
forward
to
have
like
public
ui
that
you
can
just
view
and
play
around
some
example
observability
system
and
if
you
are
passionate,
let
please
come
and
and
add
more
stuff
to
that
right.
A
A
Also,
it
might
help
you
within
your
internal
company
to
get
more
time
for
your
stuff
if
you
can
show
them
hey.
I
did
this
thing
and
now
this
is
part
of
the
official
cncf
tag.
Observability
demo
kit
for
observability
give
me
more
time
to
work
on
this
kind
of
thing
or
send
me
to
the
next
conference,
or
maybe
give
a
talk
about
it
next
year
or
whatever.