►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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.
TAG Observability Update - Matt Young, Everquote & Alolita Sharma, Amazon
Calling all disciplines!
At the CNCF TAG Observability session, we'll introduce the TAG and talk about why you might want to join us!
Projects, Vendors, and End Users are all encouraged to share experiences, ideas, and creations. We welcome writers, product managers, designers, producers, platform operators, enginers, end users, and cloud practitioners. We have ambitious goals and are fostering the growing Observability community. Opportunities in this rapidly expanding domain are plentiful.
TAG Observability welcomes your ideas, participation, contributions and YOU. Come check us out on the 1st and 3rd Tuesdays every month.
A
Hi
everyone-
this
is
alaita
sharma.
I
am
one
of
the
co-chairs
for
the
technical
advisory
group
for
observability
at
the
cncf,
and
I
am
happy
to
present
this
session
on
giving
you
an
update
of
what
we
have
been
doing
in
the
technical
advisory
group
short
also
known
as
tag
and
along
with
matt
young,
who
is
my
fellow
co-chair
and,
of
course,
the
third
co-chair
being
richard
hartman,
who
is
unable
to
join
us
today.
I'd
like
to
first
of
all
do
introductions
and
a
very
quick
introduction
for
matt
young,
who
is
my
fellow
co-chair.
A
Matt
is
a
principal
cloud
architect
at
evercoat
and
is
deep
in
the
midst
of
architecting
infrastructure
services,
developer
focused
tooling,
for
all
things
cloud
at
evercoat.
He
has
had
an
extensive
amount
of
experience
and
specializes
in
research
as
well
as
development
of
embedded
systems,
virtualization
distributed
applications,
enterprise
architecture,
a
lot
of
different
areas
and
matt
also
has
been
an
awesome
co-chair
for
the
cncf
sig
observability
and,
of
course,
in
his
spare
time,
copious
spare
time
finds
sums
in
in
his
family
motorcycles
and
tennis
matches.
B
B
She
brings
with
her
a
wealth
of
industry,
experience
and
background,
not
only
in
the
technical
aspects
of
observability,
tooling,
but
also,
and
perhaps
more
importantly,
for
the
for
the
tag
or,
as
importantly
rather
experience
and
a
demonstrated
track
record
of
building
open
source
communities
and
and
fostering
them
and
shepherding
them
both
from
a
technical
but
also
from
an
interpersonal
and
organizational
perspective.
She
is
a
member
of
the
open
telemetry
governance
committee,
she's
a
board
she's
on
the
board
of
directors
of
the
unicode
consortium.
B
B
Most
recently,
she
is
heading
up
observability
and
open
telemetry
work
at
aws,
so
we
we
are.
We
welcome
her
and
we're
really
looking
forward
to
what
comes
next.
Before
we
start.
I,
I
really
would
like
to
call
out
some
words
that
speak
to
us
from
from
the
70s
and
80s
donella
meadows
was
a
researcher
that
she
was
one
of
the
first
people
was
the
first
person
to
tell
us
that
we
as
a
species
are
going
to
run
out
of
wood
and
oil.
B
She
was
part
of
the
systems
research
group
out
of
mit,
with
mr
forrester
and
posthumously.
A
book
was
published
a
few
years
ago
called
thinking
in
systems,
and
it
summarizes
almost
30
years
of
her
work,
it's
relevant
in
particular
for
observability,
because
that
work
that
she
contributed
to.
In
many
cases,
spearheaded
gave
us
concepts
like
reinforcing
feedback
loops
and
stocks
and
flows.
B
Basically,
the
control
theory
that
was
the
precursor
to
the
declarative
state
and
its
controller
reconciler
pattern
that
we
find
in
kubernetes
and
operators
and
what
has
really
driven
a
lot
of
the
complexity
that
observability
observability
tooling,
has
has
grown
in
the
open
source
space.
To
me,
one
of
her
quotes
that
I
find
the
most
encouraging
and
relevant
here
is
in
spite
of
what
you
majored
in
or
what
the
textbooks
say
or
what
you
think
you're
an
expert
at
follow
a
system
wherever
it
leads.
B
We
welcome
and
desperately
need
folks
of
all
disciplines,
program
managers,
product
managers,
you
know
people
who
enjoy
writing
video,
editing,
all
manner
of
disciplines,
not
just
engineering,
specifically,
not
just
engineering.
So
with
that,
what
is
this
observability
stuff?
You
know
what
what
is
it
you
know
is
it
this?
B
Is
it
just
lots
of
screens
so
that
you
know
everywhere
you
look,
you
don't
need
to
move
a
muscle,
just
eyeballs,
and
you
can
see
all
the
things
maybe
to
set
some
context,
though
you
know
think
back.
You
know
not
not
so
long
ago,
you
know
in
the
beginning
we
had
monoliths
and
they
were
great.
They
weren't
broken,
they
just
worked,
and
then
we
had
to
go
and
break
it
all
or
or
supercharge
it.
B
Depending
on
your
point
of
view,
but
in
in
either
regard
the
complexity
that
microservices
and
everything
that's
come
after
it
from
serverless
idioms
to
event
streaming,
you
know
to
to
big
data
and
and
the
lot
all
of
it
has
dramatically
increased
the
complexity
of
of
observability
tooling.
You
know,
we've
created
wonderful,
complex
monsters
and,
and
we
need
wonderfully
monstrous
tools
to
wrangle.
B
You
know
what's
happening
as
we
as
we
attempt
to
understand
and
comprehend
the
complicated
interactions
and
the
systemic
behavior
of
the
cloud
native
systems
that
we're
so
actively
engaged
in
creating.
So
you
know,
there's
a
lot
of
ways
to
define
observability.
It
has
become
almost
a
buzzword,
but
to
me
monitoring
tells
you
whether
the
system
works
observability
lets
you
ask
why
it's
not
working,
and
in
that
nuance
I
think
we
find
space
and
opportunity
for
a
tremendous
amount
of
innovation
moving
forward.
A
All
right,
so
I
think
you
know
that's
very
good
segue
into
what
you
know
we
are
looking
at
in
terms
of
what
observability
does
for
you
right
and
observability.
Fundamentally,
is
you
know
in
the
quote?
We
looked
at
right
before,
so
it
gives
you,
as
a
user,
the
ability
to
understand
how
your
system
is
functioning
right
and
and
and
if
there
is
a
change
in
behavior
of
the
system,
the
health
of
the
system.
A
How
do
you
remediate
it
and
hopefully,
in
the
long
run,
you
know
move
towards
self-healing
systems
where
systems
are
smart
enough
to
be
able
to,
you
know,
prescribe
and
and
adopt
fixes
to
remediate
a
particular
change
in
behavior
right
and
have
continually
running
optimal
systems
with
that
said
again,
the
types
of
data
that
we
are
looking
at
in
observability
today
are
particularly
focused
on
three
data
signals.
Right
there
are
metrics
which
are
aggregatable.
A
You
could
be
picking
up
delta,
metrics
or
cumulative
aggregations
and
being
able
to
collect
that
from
all
kinds
of
data
sources
to
better
understand.
You
know
what
the
behavior
of
a
particular
pulse
on
the
system
is
at
any
particular
point
in
time
you
have
tracing
which
is
looking
at
traces.
You
know
through
an
application
and
and
how,
in
in
a
span
of
time,.
A
I'm
you
know
an
application
is
that
snapshot
of
data,
and
then
you
have
logging
right
with
logs
which
collect
data.
You
know
constantly
near
records
of
snapshots
of
you
know,
data
being
collected
for
particular
actions
that
are
happening
for
a
particular
data
source
and
then
being
able
to
actually
collect
that
and
then
transmit
it
to
a
monitoring
system.
Where
you
can
look
at
the
behavior
analyze
it.
You
know,
apply
sophisticated
data
patterns
and
be
able
to
analyze
and
assess
the
behavior
further.
Can
we
move
to
the
next
slide?
A
So,
as
you
as
you
see,
you
know,
there
is
fundamental
data
signals
of
metrics
tracing
and
logging.
That
is
already
being
you
know,
used
in
the
monitoring
systems
that
we
have,
especially
for
cloud
native
platforms,
but
also
for
cloud
native
applications
and
as
we
move
into
you
know,
being
making
the
full
stack
of
an
application
observable
all
the
way
from
the
bare
metal
to
the
linux,
ker
to
the
kernel
to
the
operating
system,
kernel
to
the
networking
stack
to
the
middleware
to
the
application
frameworks
to
all
the
way
to
the
application.
A
You
have
continuous
profiling
data,
for
example,
coming
in
and
intersecting.
As
you
know,
traces
and
metrics
you
have
crash
dumps
coming
in.
You
know
real
time
from
different
systems.
You
may
also
have
other
types
of
signals
coming
in
and
also
events
right,
which
which
could
be
construed
as
logs
or
it
could
be
as
events
in
themselves.
You
know
with
some
metrics
wrapped
in
next
slide,
please.
A
So
that
said,
you
know
the
this
is
kind
of
a
moving
target
right
now,
because
there's
a
lot
of
data
that
is
trillions
and
trillions
of
petabytes,
of
data
being
collected
from
systems
that
we're
constantly
monitoring
and
and
as
we
you
know,
move
towards
more
sophisticated
observability
testing.
Fuzzing
chaos.
Testing
are
all
areas
that
will
intersect
with.
You
know
how
we
are
making
systems
more
observable
and
building
end-to-end
pipelines
for
being
able
to
handle
that.
A
So
with
that
said
again,
I
would
like
to
kind
of
just
show
you.
You
know
some
of
the
complexity
that
we
have
had
in
in
this
space
that
we
are
looking
at
in
observability,
as
cindy
striedharan
says,
while
plainly
having
access
to
logs
metrics
and
traces
doesn't
necessarily
make
systems
more
observable.
These
are
powerful
tools,
if
understood,
well,
unlock
the
ability
to
build
better
systems
and,
as
you
can
see,
you
know
that
matters
because
it
optimizes
our
pre-production
pipelines.
A
You
know,
there's
the
types
of
tests
listed
here:
unit
tests,
functional
tests,
performance
tests,
you
know
fuzzy
test,
fuzz
tests,
all
kinds
of
testing
as
well
as
threat,
modeling
security
testing.
You
know
all
are
affected
by
the
ability
for
us
to
actually
have
more
observable
data
and
self-correct.
You
know
behavior
of
systems
if
they're
out
of
out
of
work.
A
Similarly,
for
deployments,
you
know
in
deployment
environments
having
integration
tests,
load
tests,
shadowing
slope
tests
for
releasing
where
you
have
cannery,
you
know:
canaries,
traffic,
shaping
exception
tracking
or
even
for
post
release.
Where
you
have
you
know,
logs
events,
chaos,
testing,
a
b
testing,
real
user
monitoring
events
coming
in
auditing,
you
know,
and
even
on-call
experience,
all
the
way
from
your
customer
and
each
one
of
these
areas
has
data
that
is
collected,
which
you
know
as
we
look
at
the
system.
End-To-End
holistically
gives
a
very
good.
A
B
Thank
you,
so
I
I'll
take
this
opportunity
to
say
that,
in
the
tag
today
in
the
in
the
group
that
we've
formed
over
the
last
little
over
a
year
now
we
have
tremendous
representation
from
the
vendor
community,
as
well
as
the
project
community.
You
know
projects
primarily
focused
on
observability,
tooling,
we'll
we'll
cover
it
a
little
later.
B
So
some
of
the
values
that
we
that
we
took
on-
and
I
I
I
would-
I
think-
that
many
others
in
similar
situations
have
some
of
these
same
values
it.
It's
worth
understanding
the
why
you
know
why
are
we
engaged
in
this?
The
technical
pursuits
are
a
delight
of
their
own
right
and
we
can
look
at
this
as
engineers
and
say
what
are
all
the
ways
that
what
are
all
the
capabilities
we
can
do.
B
What
are
the
cool
things
we
can
we
can
accomplish,
but
people
trying
to
use
this
stuff
in
the
real
world
have
perhaps
a
different
view
of
what's
valuable.
Sometimes
things
that
are
technically
nuanced
and
interesting
might
be
too
complicated
to
understand
or
not
pragmatic
to
deploy.
So
you
know
some
of
those
same
capabilities.
You
know
that
a
leader
covered
translate
directly
here,
but
they
come
up
as
how
do
we
handle
incidents?
B
You
know
when,
when
we're
being
attacked
by
hackers
or
when
we're
being
attacked
by
our
own
bugs,
because
services
are
face,
planting
and
and
and
that
hadn't
been
accounted
for,
what
do
we
do?
How
you
know?
How
do
we
respond?
What's
the
what's
the
workflow,
and
how
can
these
tools
inform
that?
How
do
we
secure
our
intellectual
property,
but
also,
more
importantly,
how
do
we
secure
the
data
that
our
customers
entrust
to
us?
B
You
know
we're
the
stewards
of
that
data
and
as
more
and
more
businesses
go
online
as
verticals
such
as
health
insurance
and
the
medical
and
bio
biology.
You
know
all
of
these.
All
of
these
fields
have
customer
information
and
personal
information
that
might
even
be
not
only
sensitive
from
a
privacy
perspective,
but
in
addition,
it
medically
protected
in
a
regulatory
way.
So
how
do
we
do
that?
How
do
we
observe
these
systems
while
protecting
the
integrity
and
the
and
the
privacy
of
our
customers
on
the
operational
side?
B
How
do
we
do
auto
scaling?
How
do
we
detect
anomalies?
You
know
how
do
we,
how
do
we
know
what
things
are
costing
and
how
we
might
be
able
to
optimize
them
from
a
values
perspective-
and
you
know,
observability
tooling,
that
helps
us
us
achieve
these
business
goals.
You
know
to
be
fiscally
responsible
to
in
a
in
a
perfect
world
not
have
to
scale
infrastructure
costs
with
with
traffic
costs,
for
example,
and
all
manner
of
business
goals.
B
You
know
observability,
tooling
the
ability
to
see
what's
happening
and
why
and
how
these
things
relate
to
each
other.
The
value
they
provide
is
vast
and
there's
again
a
huge
opportunity
to
innovate
in
this
space
and
to
build
a
top
and
with
what's
already
been
put
in
place
over
the
last.
You
know
a
few
years
in
this
space
in
the
which
is
in
its
own
right,
substantial.
B
There
are
so
many
companies
and
and
projects
that
are
thriving
in
the
space
and
part
of
the
tag's
function
is
to
work
with
them.
So
I've
said
tag
a
bunch
of
times.
I
should
really
define
what
it
is.
This
diagram
is
courtesy
of
of
chris,
our
cto
of
cncf
and
the
linux
foundation
in
a
in
a
blog
post.
He
made
announcing
new
toc
members
earlier
this
year
in
the
purple
box.
Here.
B
Special
interest
groups
is
what
we
used
to
be
called
so,
interestingly,
just
over
a
year
ago,
sig
observability
was
formed
and
just
a
less
all.
Within
the
same
year,
sigs
were
renamed
to
tags.
Tag
stands
for
technical
advisory
group
and
tags
exist
to
inform
the
toc
on
gaps
in
the
ecosystem,
as
well
as
to
foster
those
same
ecosystems
by
you
know
in
a
number
of
ways,
consistent
with
their
charter.
B
A
little
over
a
year
ago,
members
of
the
community
came
together
and
created
the
charter
for
tag
observability.
It
was
a
consensus
document
contributed
to
by
over
20
people
from
a
number
of
of
cncf
members.
I've
highlighted
some
some
excerpts
that
are
really
relevant
now,
as
we
look
forward
to
what
what
comes
for
the
next
for
the
rest
of
this
year
and
into
2022.,
and
the
top
level
item
really
is
to
foster
and
sustain
the
observability
ecosystem.
B
B
Nearly
any
project
has
observability
goals
and
concerns,
and
so
you
know
the
the
tag
is
a
place
where
these
these
these
groups
can
come
together
in
productive
discussion.
We
exist
to
identify
gaps
in
the
cncs
portfolio
of
projects.
For
example,
the
octant
project
out
of
vmware
came
to
present
to
our
tag
a
few
months
ago.
They're
an
apache
2
project.
They
are
not
part
of
the
cncf,
yet
they
are
in
scope
because
they
are
an
open
source,
observability
tool.
B
From
speaking
from
our
personal
experience,
I've
benefited
greatly
by
being
able
to
collaborate
with
others.
In
the
space
as
as
at
my
company,
we
have
been
deploying
an
open
source.
Observability
stack
with
some
success
provide
users
with
unbiased
information
again,
as
all
of
these,
as
all
of
these
folks
come
together
under
a
shared
banner.
B
You
know
we
we
can
produce
guidance
and
and
curate
information.
That
is
not
market
texture.
That
is
not
a
pitch,
but
it's
just
you
know
there
to
provide
information
that
can
be
trusted.
It's
a
vendor-neutral
setting
for
thought
validation.
You
know
many
of
the
open
standards
that
we
have
exist,
primarily
because
vendors
have
decided
that
interoperability
is
paramount.
So
lolita
will
we'll
talk
about
this
more,
but
the
tag
exists
specifically
to
provide
that
forum
to
have
those
discussions
in
a
structured
and
safe
way.
B
So
over
the
last
year
the
tag
has
participated
in
due
diligence,
assessments
and
reports,
as
projects
seek
to
move
from
the
sandbox
to
incubation,
I
need
to
be
clear
that
the
tag
is
not
an
arbiter.
It's
not
a
decider.
It's
a
again.
It's
a
it's
a
place
where
domain
experts
congregate
and
are
committed
to
providing
the
technical
oversight.
Committee,
unbiased
usable
actionable
information
as
as
part
of
due
diligence,
so
that
end
users
can
be
assured
that
you
know
incubation
means
a
certain
level
of
assessment
and
and
foundational
homework
has
been
done.
B
The
due
diligence
reports
that
have
come
out
of
these
efforts
and
and
all
of
the
other
due
diligence
reports
across
the
umbrella
of
cncf
projects,
are
I've
found
as
an
end
user
immensely
useful.
I
encourage
you
all
to
check
them
out
if
you're
trying
to
figure
out
is
this
project
a
good
fit
or
how
is
it
a
good
fit?
These
are
a
wealth
of
information
that
is
provided
in
the
open,
so
we're
proud
to
have
contributed
to
a
number
of
those
due
diligence
reports.
B
In
addition,
we've
had
guests
from
from
from
open
source
projects
that
are
are
entering
the
cncf
in
the
sandbox
phase.
Pixie
is
an
example
of
that
new
relic
has
recently
open
sourced
pixie
and
rather
has
donated
pixie
to
the
cncf
and
they're
they're
entering
they
came
and
had
a
chat.
So
the
tag
really
is
a
place
where
it's
a
little
bit
of
what's
new.
A
Yeah,
absolutely
and
and
thanks
matt.
So
if
we
are
in
exciting
times
in
observability,
as
you
know,
are
the
open
source
projects
that
are
all
under
the
cncf
umbrella,
whether
that's
thanos
or
cortex,
or
open
telemetry,
and
many
other
projects
like
pixi,
all
working
towards
specific
goals
that
they
have,
and
you
know,
working
towards.
What's
the
coolest
and
newest
feature
in
their
in
their
repertoire.
A
So
what
we
would
like
to
do-
and
this
is
something
again
I
invite
all
of
you
to
kind
of
come
and
think
about
and
discuss
with
us
is
that
provide
more
guidance
of
what's
coming
in
in
the
ecosystem.
Obviously,
as
subject
matter
experts,
many
of
us
track.
What's
you
know
and
very
actively
work
and
what's
coming
up
and
what's
being
built
in
the
observability
tool
sets
and
toolkits
and
as
well
as
build
that
out,
you
know
to
be
make
available
as
webinars
being
able
to
make
available.
A
As
you
know,
youtube
talks
in
the
cncf
tag
channel,
which
is
something
we
can.
You
know
leverage
a
lot
of
provide
case
studies
from
end
users
as
well.
As
you
know,
different
pipelines
that
end
users
and
developers
are
using
for
these
observability
components
in
the
in
our
open
source
projects,
as
well
as
have
project
demos
through
the
year.
You
know
in
the
umbrella
of
projects
that
are
within
the
cncf
umbrella,
as
well
as
outside.
A
Cross-Collaboration
is
something
very
important,
so
we
do
think
that
you
know
being
able
to
demo
and
learn
from
each
other
is
a
great
way
to
actually
build
interoperability
and
open
standards
towards
making
it
easier
for
customers
to
use
observability
components
out
of
the
box.
Another
area
we're
looking
at
is
work
work.
Group
topics
such
as
you
know,
continuing
to
have
cross
project
engagement
where
we
are
discussing.
As
I
said,
you
know,
collaboration
as
well
as
open
standards,
interoperability,
test,
suites
and
other
ways
to
collaborate
closely
together
as
well.
A
As
you
know,
other
projects,
such
as
gathering
feedback
from
end
users
for
persona
development,
which
is
a
joint
project
we've
been
working
with
other
sister
projects
on
and
and
needless
to
say,
you
know,
there
are
multiple
many
many
many
companies
that
are
you
know,
participate
in
our
discussions
and
have
discussed
over
time.
We
have
tagged
participants
from
multiple
companies.
A
These
are
just
few
of
them
listed
here
thanks
to
everyone,
you
know
for
participating
and
continuing
to
participate,
and
I
would
also
like
to
actually
last
but
not
least
welcome,
all
of
you
to
join
us
for
these
discussions.
You
know
a
a
advisory
group
meeting
or
a
user
group
meeting
is
as
good
as
the
participation
that
we
have
in
them
from
everyone
and
all
of
us
and
all
of
you
and
just
to
call
out.
A
We
have
meetings
on
the
first
and
third
tuesdays
of
the
month
where
there
are
observability
meeting
notes
that
we
maintain
and
you
can
go
and
look
at
them
anytime,
catch
up
on
what
was
discussed,
but
these
meetings
also
recorded.
So
you
can
catch
up
on
our
youtube
channel
the
github
repository
where
you
can
track
all
the
you
know
active
work,
that's
ongoing!
Whether
those
are
evaluations
or
any
other
comments
that
people
you
know
are
adding
or
feedback.
A
A
Ideas,
for
you
know
improving
observability
in
general,
in
terms
of
the
open
source
projects
that
we
have
and
the
different
discussions
that
are
ongoing,
whether
that's
engineering
discussions,
technical
discussions
on
implementation,
whether
that's
design
practices,
good
practices
on
you
know
how
end
users
can
build,
consume,
instrumentation
well
or
confu,
making
configurations
easier.
There
are
a
lot
of
topics
in
this
space
and
as
well
as
you
know,
discussing
solutions
that
work
for
you
and
tools
that
you're
building.
So
that
said,
I
would
love
to
invite
you
again.
A
You
know
to
please
join
in.
I
would
also
like
to
last
but
not
least,
call
out
and
acknowledge
all
the
folks
who
have
actually
participated
very
actively
in
our
meetings
again.
You
know
this
is
a
quite
a
large
list
and
really
it's
been
exciting
through
the
whole
year,
we're
looking
forward
to
having
lots
more
participation
and
lots
more
cool
areas
that
we
work
in
and
observability
in
this
coming
year.
A
So
again
would
love
to
invite
everybody
to
join
in
for
the
for
the
tag
meetings
that
are
regularly
held
as
well
as
follow
us
on
the
channel
slack
channel
and
look
forward
to
having
and
seeing
you
on
on
more
projects
and
observability
at
the
tag
meetings
we
are
signing
off
now.
This
is
our
lisa
sharma
and
matthias
matt
young.
As
coaches
see
you,
there.