►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. 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.
2022 Observability TAG Update - Alolita Sharma, Apple & Matt Young, TAG Observability
The CNCF Technical Advisory Group (TAG) on Observability serves as a discussion forum for topics related to observability of cloud native systems and workloads. We also produce supporting material and best practices for end users and provide guidance and coordination for CNCF observability projects working within the TAG’s scope. This session will provide an update on major observability projects in the CNCF, technology updates from these projects and opportunities to get involved in the TAG to build momentum on cross-collaboration across observability projects, data protocols and new areas. We also invite observability practitioners, developers and contributors to join in for this session to discuss features, gaps and open source solutions for end-users.
A
All
right,
hi
everyone.
How
are
you
good
good
good
to
see
a
good
crowd
today
and
and
super
happy
that
you
know
we
at
least
get
a
decent
time
slot
instead
of
in
the
evening
right
so,
but
very
happy
to
see
all
you
see
you
all
again.
Just
thank
you
for
joining
in
we're
going
to
you
know
we
are
we'll
just
introduce
ourselves
very
quickly.
Matt
did
you
want
to
go
first
sure.
B
A
And
I'm
Alita
Sharma
I
am
also
a
co-chair
for
the
tag
work
closely
with
Matt
and
our
technical
lead
for
the
tag.
Observability
also
he's
around
someplace
vartek,
but
he
might
be.
He
has
a
tag
right.
He
has
a
talk
right
after
so
you
might
be
preparing
for
it,
but
just
to
welcome
everyone.
Thank
you
for
coming
in,
please
again
I.
We
would
like
to
see
this
as
an
interactive
discussion,
because,
as
you
know,
the
tag
is
like
a
community
end.
A
User
Group,
you
know
and
I
use
a
group
where
all
of
us
together
working
on
different
projects,
different
open
source
projects,
you
know
kind
of
talk
about
observability.
What
are
some
of
the
latest
projects
that
are
ongoing
in
this
cncf
space,
but
also
you
know
what
we
can
introduce
as
areas
that
are
important
to
developers
and
users
alike
and
and
also
work
closely
with
the
projects
to
make
that
help
them
make
that
happen.
A
All
right,
so
I
think
just
a
sneak.
Peek
wanted
to
call
out
and
your
attention
to
a
super
cool
logo
that
we
actually
finally
adopted
this
year.
It's
the
owl
and
Matt
has
a
very
interesting
story
about
that
later
on
in
the
talk,
but
again
just
wanted
to
call
this
out,
because
you
know
owl
is
known
for
wisdom
and
observation,
they're,
Keen
observers,
so
I
think
it's
befitting
to
to
the
as
the
logo
of
the
tag
just
wanted
to
start
off
with
the
charter
of
the
tag.
A
As
you
know,
the
cncf
has
several
technical
groups,
which
again
work
very
closely
with
the
TOC,
which
is
the
technical
oversight
committee
for
the
cncf
and
the
charter
of
the
observability
tag
group
is
again
to
Foster
review
and
grow
the
ecosystem
of
Open
Source
projects
for
observability
and
that
comes
in
different
shapes
and
forms.
As
you
have
seen,
many
of
you
might
have
seen
the
landscape
graph.
A
There
are
several
categories
of
observability
projects,
ranging
from
monitoring
to
logging
to
actual
cost
and
cost
management,
and
several
other
categories,
if
you
haven't
seen
it
again,
go
to
landscape.cncf.io
and
it's
a
really
nice.
You
know
chart
of
all
the
projects
open
source
projects
within
cncf's
domain
and
also
and
other
Allied
projects
that
work
together
and
collaborate.
A
So
going
back
to
the
Charter
again,
we
work
very
closely
with
several
of
the
projects
to
help
grow
the
ecosystem
and
create
awareness.
We
also
identify
and
Report
gaps
in
the
you
know
if
there
are
user
requests,
so
we
are
seeing
and
great
you
know:
development
of
an
of
a
cool
project
or
a
cool
feature
set,
which
is
then
aligning
with
an
observability
project,
again
continuing
to
grow
the
project,
cncf
portfolio,
share
patterns
and
good
practices
for
observability.
A
All
of
you
know,
many
of
us
are
working
in
the
space
where
we
actually
build
tools,
as
well
as
build
Solutions
and
pipelines
for
observing
our
systems
and
be
able
to
being
able
to
share
good
practices
that
many
of
our
teams
have
identified
or
developed,
or
what
works
for
specific
use
cases.
This
is
a
forum
to
do
so.
A
The
TOC
is
the
final.
You
know
reviewer
and
and
decision
maker
here.
So
with
that
said
again,
I'd
like
to
kind
of
move
on
and
just
highlight
the
cncf
structure.
Many
of
you
may
have
already
seen
this
slide
for
those
of
you
who
know
you
know
and
are
deeply
involved,
there's
a
governing
board
for
the
cncf,
the
technical
oversight
committee
that
I
referred
to
and
I
think
Alina
is
here.
A
Who
is
our
she
used
to
be
on
the
TOC
she's
now
on
the
governing
board,
and
there
are
the
end
user
in
a
community
work
groups
which
are
now
tags
right
and
and,
as
you
can
see,
they're
different.
You
know
areas
that
kind
of
are
focuses
for
each
of
these
types
of
groups
and
and
the
end
result,
which
I
think
is
not
called
out
here,
but
should
be.
A
Is
the
projects
themselves
right
where
we
all
work
on
the
open
source
projects,
and
you
know,
form
and
are
members
of
these
different
groups
all
right
so
with
that
said?
I
want
to
kind
of
hand
it
over
to
Matt
to
step
through
some
of
the
2022
accomplishments
of
what
we
did
as
a
tag
team
this
this
year
for
observability
and
here
over
to
you
cool.
B
Hi
everybody,
so
we
thought
we
would
walk
through
just
a
few
examples
of
some
of
the
more
notable
ones
of
the
type
of
activities
that
that
happen
in
the
technical,
Advisory
Group.
In
our
meetings
and
as
out
as
owelita
mentioned,
you
know
we
are
not
as
a
group
an
Arbiter
or
a
decider
or
an
approver
right.
The
role
is
really
to
facilitate
all
of
these
groups.
B
You
know
productively
engaging
together
and
driving
forward
initiatives
that
make
sense
and
and
are
requisite
so
as
an
example,
as
you
know,
as
many
of
you
may
know,
in
the
open
Telemetry
project
there
have
traditionally
been,
you
know
three
signals
right
into
anyone.
I
guess
you
know
logs
metrics
traces
at
kubecon
EU,
just
about
half
a
year
ago
at
the
open,
Telemetry
meeting
you
know
some
members
of
the
community
and
others
raised
an
idea
that
you
know
continuous
profiling
should
be
added
as
a
signal
type.
B
You
know,
as
I
was
at
ebpf
day
a
few
days
ago,
and
if
you've
been
watching
the
news
or
if
you're
a
nerd
for
profiling
in
general,
you
can
there's
a
huge
amount
of
innovation
happening
using
this.
Quite
this
quite
old
piece
of
tech-
that's
been,
you,
know,
revitalized
and
used
for
for
these
purposes.
So
as
a
tag,
the
way
we
could
facilitate
moving
this
forward.
What
was
as
follows?
One,
you
know
a
lot
of
discussion.
You
know
so.
B
We've
started
this
in
the
late
spring
and
throughout
the
summer
one
of
the
community
members
Ryan
Perry
CEO
of
a
company
called
pyroscope
organized
and
orchestrated
about
a
dozen
meetings
for
anyone
who
wanted
to
come.
You
know
the
first
meeting
had
I,
think
45
or
50
people
across
a
broad
swath
of
you
know,
end
users
to
vendors
to
nerds.
I
am
one
and
we
talked
about
you
know
what
does
this
look
like
right
and
there
are
different
use
cases.
B
You
know
you
know
as
a
small
example,
you
know
some
teams
or
some
some
projects
might
want
to
collect
profiling
data
at
the
edge
on
Lower
powered
devices.
You
know
and
only
collect
the
data
and
stream
it
back.
You
know
to
some
back
ends.
That
will
then
do
analysis,
whereas
other
devices
or
projects
might
want
to
do
the
exact
opposite.
B
B
You
know
those
kinds
of
discussions
were
were
facilitated
by
the
tag,
but
really
in
the
background
you
know
like
the
we're,
a
facilitator
or
a
facilitator,
not
a
dictator,
so
the
the
general
process
was
by
mid-summer.
You
know
a
lot
of
these
ideas
started
coalescing,
so
we
started
a
document
and
then
by
mid-august
we
had
a
vision
document
to
say:
hey
here's,
what
a
group
of
folks
that
have
come
together
that
are
interested
in
this
topic.
You
know
we
have.
We
have
reached
consensus
on
what
it
is.
B
Is
you
know
anyone
can
propose
a
note
happen
and
there
are
many
of
them
and
people
do
as
an
individual,
but
you
know
if
you
can
come
together
and
say:
hey
wait,
20
or
30
people
who
you
know
have
various
expertise
in
this
area.
We
all
agree
that
this
is
sort
of
a
great
path
forward
and
a
vision
so
that
that
gives
more
weight
to
the
proposal
right
because
now
open
telemetry
says
well
they're
not
proposing
a
specific
implementation.
You
know
this
is
just
a
vision
document
that
says
like
here's.
B
What
we
want
to
accomplish
and
there's
lots
of
ways
we
can
do
it.
Maybe
we
can
do
it
multiple
ways
at
the
same
time
for
different
folks,
but
this
is
what
we're
going
to
engage
in
and
so
just
recently,
I
believe
in
September
that
was
merged
right
and
so
now
as
part
of
open
Telemetry.
There
is
an
actual
initiative
to
go.
Add
continuous
profiling
data
as
a
signal
type
to
make
a
fourth
signal,
if
you
will,
and
so
at
the
open
Telemetry
meeting
yesterday,
where
you
know
they're,
typically
a
coupe
cons.
B
This
was
a
topic
and
the
next
topic
was
okay.
Well,
what
happens
next
and
the
community
comes
together
and
agrees
that
okay,
we're
going
to
go,
do
some
deep
work
on
this
and
actually
start
implementing
some
things,
and
we
don't
all
decide.
You
know
how
it's
going
to
happen,
but
we
decide
that
it
is
something
that
people
are
engaging
in
and
and
it
leaves
plenty
of
room
for
folks
to
come
in
and
engage
in
the
process
right.
So
that's
really
the
point.
B
So
that's
one
one
of
the
things
that
we
did
over
the
course
of
this
year
or
that
we
kind
of
softly
allowed
to
happen
or
facilitated
in
some
ways,
but
really
there's
a
community
that
did
it,
but
the
tag
was
a
place
where
they
could
come
in
that
neutral
setting
and
have
those
discussions
in
the
first
place
right
that
were
neutral.
So.
A
A
B
Through
just
brief
show
of
hands
non-binding
who's,
familiar
with
cortex
the
project,
just
so
I
know,
okay,
I
would
say
that
looks
like
maybe
20
of
the
room.
So
you
fifth
of
the
room
bear
with
me:
cortex
is,
in
short,
adorable
a
back-end,
durable
storage
for
time
series
metrics
some
of
the
basic
at
a
high
level.
It's
multi-tenant,
it's
designed
to
be
run
in
Cloud
environments.
On
top
of
you
know,
S3
or
Google,
Cloud,
Storage
or
min.io,
or
some
sort
of
object
store.
It's
designed
to
be
horizontally,
scalable
right.
B
So
what
one
of
the
things
that
happened
with
the
cortex
project
is
some
of
the
original
authors
and
maintainers
cycled
out
of
the
project
to
do
other
things
right,
so
the
TOC
and
others
were
saying,
hey.
Well,
this
is
a
you
know.
A
lot
of
people
are
running
this
in
production
today.
You
know
cortex
is
an
incubating
project,
so
it's
in
that
that
middle
Zone,
where
it's
seriously
being
run
at
serious
scale.
So
it's
important
that
this
this
project
remain
healthy,
and
so
what
could
we?
As
a
you
know?
B
Really
again,
we
don't
have
any
power.
Really
nobody
works
for
us,
we're
not
really
in
charge
of
anything.
But
what
can
we
do
to
to
help
make
this?
You
know
a
successful
project
as
it's
in
our
domain
to
be
interested
in,
and
so
we,
you
know,
talked
about
what
could
be
done
so
talk
talking
with
the
project,
maintainers
to
say,
hey
what
what
would
help
the
project
you
know
because
and
of
course,
his
contribution.
B
Well,
it
didn't
face
it
more
like
paused,
but
you
know
we
ran
H.A
Prometheus
pairs
in
all
of
our
clusters
right
and
so
the
right
ahead
logs
started
to
really
fill
up,
because
you
know
the
durable
storage
is
down
and
we
over
provisioned
things.
So
we
had
like
a
couple
weeks
of
right
ahead.
Log
space
really
discs
are
cheap,
but
when
everything
got
turned
back
on
suddenly
our
whole
infrastructure
needed
to
send
cortex
stuff
and
again
because
we
could
dynamically,
you
know
in
a
pretty
easy
way,
scale
up
and
down
stuff.
B
We
could
scale
stuff
up
and
start.
You
know
bringing
back
all
of
the
the
back
metrics
and
at
one
point,
I
think
it
was
like
two
in
the
morning
and
we
hit
like
20
something
thousand
art
requests
per
second
requires
per
second
or
rather
requests
per
second.
So
and
then
you
know
it
just
handled
it
just
great.
So
it's
a
really
fun
project.
If
you're
into
distributed
systems
and
time
series,
they
could
use
your
help
in
a
variety
of
roles.
B
So
you
know
bringing
visibility
to
that
and
really
kind
of
helping
communicate
out
to
other
projects
to
the
community
and
to
the
leadership
of
the
cncf
like
this
is
what's
up
with
the
project
you
know
and
we're
going
to
help
them.
We
can't
do
it
for
them,
but
we're
going
to
help
share
in
their
success
right
or
help
facilitate
their
success.
So
that's
sort
of
another
type
of
activity
that
we
do
in
the
in
the
group,
cool,
so
I
think
we
have
a
third
one
to
talk
about
as
well.
B
We
thought
it
would
be
fun
to
have
an
observability
speaker
series
right.
So
you
know
if
we've
got
people
that
show
up,
because
they
want
to
nerd
out
and
talk
about
observability.
What
might
they
like
to
hear?
Who
might
they
like
to
hear
it
from
so
we've
had
two
so
far
and
it's
almost
done
processing
on
YouTube.
So
by
the
time
you
actually
maybe
see
these
slides
there'll
be
a.
B
In
September
we
had
Liz
Liz
Fong
Jones
from
honeycomb,
come
and
do
a
talk
on.
You
know,
hybridized
signal
types
and
and
really
a
lot
about
how
Eventing
and
events
really
it's
a
really
cool
talk.
You
should
check
it
out,
Yuri
from
who,
as
many
of
you
know,
had
some
small
parts
you
know
to
do
with
with
the
Jaeger
project.
He
came
and
talked
about
some
of
his
thoughts
around
observability
and
tracing,
and
all
of
that
and
I'll
put
a
link
there
as
a
little
paper.
B
They've
done
a
positional
paper
on
schema,
first
application
Telemetry,
so
the
title
is
sort
of
self-describing.
It's
a
fascinating,
read
and
I
think
you'll
be
talking
about
it
sometime
this
week
or
next
yeah.
So
and
then
we've
got
Jonah
Cowell
coming
who's
a
CEO
of
vlogs.io
and
has
been
involved
in
various
communities
in
observability
he'll
be
coming
to
share
some
thoughts
and
I.
B
A
And
I
think
just
to
add
to
that
again.
The
tag
sessions,
as
many
of
you
know,
are
published
on
the
Google
Calendar
for
cncf
and
and
also
they're,
typically
on
the
first
and
third
Tuesdays
of
the
month.
So
you
know
again
at
least
joining
in
once
a
month
is
a
you
know.
We
had
really
love
for
more
folks
to
join
in
and
have
those
discussions
that
then
you
know
carry
over
into
the
projects
themselves
and
other
strategic
initiatives
and
features
that
you
you
want
to
see
happen
right.
A
A
lot
of
projects
that
come
in
under
you
know,
interrupt
driven,
but
but
then
there's
something
that
we
do
intentionally
and
try
to
plan
for
so
again,
you
know
if
there
are
areas
that
you'd
like
to
see
happen.
We,
this
is
what
we
have
kind
of
collected
from
the
different
discussions
and
suggestions
that
folks
have
made
as
they've
participated
in
the
tag,
or
you
know,
there's
different
feedback,
that's
coming
in
from
different
projects
and
and
here's
some
of
the
areas
that
we
want
to
kind
of.
A
A
The
first
area,
of
course,
is
Matt
you
know
discussed
earlier
is
profiling
and,
as
you
can
see,
that
the
profiling
enhancement
proposal
for
open
Telemetry
landed,
you
know
earlier
this
month,
but
we
would
like
to
see
more.
You
know
detailed
use
cases
outlined
there
and
always
you
know,
as
all
of
us
discuss
these
use
cases
kind
of
taking
that
feedback
back
to
the
project
hotel,
as
well
as
others
right
working
closely
with
other
projects,
psyllium
and
other
projects
that
are
actually
working
on
ebpf
and
getting
a
more
of
a
shared
Vision.
A
You
know,
observing
right
and
graphs
is
a
great
way
to
Envision
that
right,
those
interdependencies,
whether
those
are
learning
and
and
understanding,
different
systems
and
the
correlations
between
them
or
even
understanding
the
data
that
flows
across
those,
and
that
is
going
to
kind
of
go
into
a
bit
more
detail
on.
You
know
what
we
are
looking
at
in
that
space.
Another
area
that
came
up
during
discussions-
and
this
was
something
that
even
Yuri
highlighted
in
his
talk
earlier
this
month-
was
to
look
at
Telemetry
data.
A
A
What
is
what
are
not
only
our
applications
doing,
but
how
is
the
system
interacting
with
them
and
what
you
know
can
we
actually
deliver
the
quality
of
service
at
the
end
of
the
day,
which
is
what
observability
is
all
about?
So
looking
at
exceptions
in
more
detail
is
something
that's
interesting,
because
we
want
to
know
about
the
failures
ahead
of
time
in
our
applications
than
later.
A
Another
area
which
has
been
you
know
very
much
discussed
in
the
in
specific.
You
know,
as
many
of
us
were
run
infrastructure
on
cloud
native
public
cloud
or
you
know,
otherwise,
how
many
of
you
use
cloud
native
infrastructure,
I,
hope
everyone
you
know,
but
if
you
don't
you're,
probably
using
something
on-prem,
but
it
is
a
hybrid
world.
Today,
right
and
understanding
as
more
and
more
of
us
run
applications
on
public
Cloud
infrastructure.
A
We
really
need
to
understand
what
the
usage
is
right
and
and
how
much
does
your
organization
really
spend
in
different
categories
right,
whether
that's
engineering,
whether
that's
actual
you
know,
build,
store
and
actual
vendor
or
whether
that
is
you
know
again
planning
for
what
kind
of
growth
you
need
to
have
for
infrastructure
in
the
next
year,
so
cost
measurement
and
understanding
the
actual
usage
of
systems
and
system
components
is
also
something
that
observability
use.
Cases
are
starting
to
look
at
and
there
are
several
projects
within
the
cncf
observability
umbrella
that
actually
addressed
this.
A
A
couple
of
them
are
open
cost,
as
well
as
Cube
cost,
which
many
of
you
may
have
heard,
but
having
more
integration
across
you
know
providing
that
data
through
standard
observability
pipelines
is
also
another
area.
That
you
know
is
something
that
people
who
care
about
it
are
looking
at
how
many
of
you
care
about
that
cost.
A
You
do
right
so
money,
so
this
should
be
an
interesting
one
and
again
I
invite
you
to
come
over
to
the
cncf
to
the
tag
meetings
so
that
you
know
we
can
all
discuss
and
actually
capture
some
of
these
use
cases,
because
I'd
like
to
better
Define
a
baseline
for
what
those
metrics
are,
what
those
traces
are.
What
do
we
need
to
collect
from
an
observability
standpoint
that
we
can
standardize
and
you
know,
collect
in
a
standardized
way,
which
is
then
built
into
the
collection
mechanisms?
A
You
know
that
you
use
to
be
able
to
pull
from
infrastructure
right.
So
that's
another
area
that
I
think
has
actually
has
a
lot
of
a
lot
of
areas
that
we
need
to
can
kind
of
Deep
dive
into
another
area.
I'd
like
to
kind
of
call
out,
is
correlation
across
Telemetry
data
signals,
and
this
is
again
an
area
where
sampling,
for
example,
is
a
you
know,
specific
use
cases,
many
of
us
instrument
our
applications
and
enable
tracing
for
those
applications.
What
does
correlation
mean
here,
because
how
many
of
you
use
sampling
today?
A
Many
of
you
right,
there's
no
way
that
you
could
handle
the
kind
of
cardinality
and
and
throughput
that
you
get
from
100
of
tracing
turned
on
or
profiling
turned
on
or
metrics
turned
on,
even
for
that
matter
of
logs
right
so
again,
in
one
way
or
the
other,
we
do
do
a
fair
bit
of
sampling
and
correlation.
Then
understanding
you
know
how
our
data
is
actually
providing.
The
right
signals
from
an
observability
standpoint
is
important,
so
these
are
some
of
the
initiatives
that
you
know.
A
A
Secondly,
we're
looking
for
tech
leads.
If
you
want
to
lead
a
specific
area,
you
know,
for
you
know
we
we
do
a
fair
bit
of
analysis,
tech
and
as
well
as
technical
white
papers.
So
if
you
are
interested
in
working
in
any
of
those
areas,
please
join
in
and
it
is
very
simple:
it's
like
you
know,
we
really
invite
everybody
to
kind
of.
A
You
know
use
this
as
your
group
User
Group
and
then
again
also
contribute
to
the
tag
we'd
like
to
see
some
reference
tools,
recommendations
and
there
is
a
GitHub
repo
for
the
cncf.
The
tag
observability
under
the
cncf
domain,
which
you
can
you
know,
come
and
take
a
look
at.
There
are
several
issues
that
you
could
work
on,
and
you
can
also
ask
for
requests.
You
know
there
very
easily
and
that
said
again,
I
want
to
turn
it
over
to
you
Matt.
So
you
wanted
to
kind
of
dig
into.
B
Cool
okay,
so
these
are
some
challenging
questions
that
are
kind
of
hard
to
answer.
Right,
I
don't
have
time
to
go
through
all
of
them,
but
you
know
you
know,
some
of
them
are
a
little
cheeky
but
real
right.
You
know
our
GitHub
stars
and
you
know
popularity
and
market
cap
actually
correlated
a
more
interesting
one
might
be
you
know,
I'm
a
say,
you're
an
I.T
decision
maker
like
who's,
had
to
pick
what
open
source
projects
to
work
with
right.
B
Let's
say
you
wanted
to
answer
the
question
well
before
I
go
dive
in
with
my
teams
or
by
myself
and
and
put
this
project
into.
You
know
something
that
is
directly
Revenue
impactful
who
all
contributed
to
it
and
who
did
they
work
for,
and
many
of
those
companies
are
probably
like,
very
small
so
who
funded
those
companies
and
what
else
did
they
fund
show
me
clusters
right
that
will
make
most
relational
database
systems
just
kind
of
weep.
B
Get
you
to
the
scale
of
you
know
we
kind
of
need
a
graph
to
efficiently
answer.
Questions
like
that
there
are
more,
but
in
in
the
interest
of
time,
I
want
to
fast
forward
a
little
bit
to
the
next
slide.
No,
so
over
the
summer
we've
kind
of
launched
a
project,
it's
nascent
and
we've
done
a
good
deal
of
work
around
project
planning.
So
there's
you
know
a
whole
bunch
of
issues
that
are
marked
as
help
wanted
or
good
first
issue
and
there's
a
lot
of
room.
B
You
know
to
go,
innovate
but
in
a
nutshell,
it's
a
project
that
is
making
a
labeled
property
graph,
so
I
think
neo4j,
D
graph,
redis
graph.
You
know
any
type
of
labeled
property
graph
that
speaks
open
Cipher,
which
is
a
kind
of
like
SQL
for
graphs.
If
you
will-
and
it's
a
Federated
supergraph
made
up
of
a
bunch
of
subgraph
modules
so
that
people
can
work
on
things
independently
and
the
subgraph
modules
are
things
like
cncf
projects
and
git,
all
of
it
and
Twitter
and
Linkedin
and
cves,
and
all
Packages
Etc
right.
B
So
in
order
to
kind
of
work
out
the
individual
data
models
for
these
subgraph
pieces,
that's
a
job
by
itself,
but
having
some
way
to
coordinate
all
this
is
imperative,
so
we're
using
graphql
as
an
interface
definition
language
and
to
get
some
Federation
support.
So
we
can,
you
know,
mix
and
match
these
different
subgraphs.
B
So
we
wanted
to
have
a
project
that
was
sort
of
interactive
and
and
mix
and
match,
and
so
some
of
these
collaborations
that
we
could
I
could
briefly
highlight
are
other
examples
of
the
the
opportunity
that
that
you
all
have,
and
your
friends
too,
to
engage
in
the
tag
because
sort
of
from
that
position
you
can
launch
off
and
do
all
kinds
of
stuff.
So
in
short,
otaga's
observability
tag
s
tag
is
a
security
tag
right,
so
the
packaging
format
metadata,
for
you
know
npm
and
crates.
B
B
What
those
graph
data
models
are
is
an
example
of
the
kind
of
cross
tag
collaboration
where
we
can
leverage
domain
experts
from
different
areas.
Another
is
the
business
value
subcommittee.
You
might
not
know
them
by
by
their
name
that
name,
but
it's
glossary.cncf.io
right.
That's
a
bunch
of
definitions,
they're
doing
other
stuff
like
providing
updated
views
of
the
cncf
landscape
that
are
augmented
with
category
information
right.
B
So
what
projects
are
similar
to
this
or
I
want
to
use
this
GPL
thing
what's
similar
to
it
right,
that's
the
kind
of
recommender
systems
that
we
can
build
with
graphtec
or
graph
data
science
and
sort
of
the
mother
of
all
Rolodex
is
really
you
know.
You
know.
Sometimes
there
are
so
many
working
groups
and
so
many
tags
in
the
cncf
alone.
B
B
Owls,
why
owls
it's
not
the
OverWatch
League,
although
that's
an
excellent
guess
for
me.
Particular
owls
fly
softly.
They
have
little,
they
have
little
feathers
on
their
leading
wings.
So
you
know
Heisenberg,
there's
a
tie
on
there.
You
know
we
want
to
observe
things
without
making
too
much
noise,
while
doing
it.
B
Yeah
binocular
vision,
it's
cool,
their
ears
are
offset
like
this,
so
sound
hits
their
skulls
just
a
little
bit
differently,
so
they
can
directionally
tell
where
things
are
coming
from
again
sort
of
an
observational
thing
and
they
have
grippy
feet
and
Talons.
You
know
if
you've
I'm
guessing
most
of
the
people
in
this
room
have
had
the
experience
of
digging
into
a
bug
or
something
that's
not
quite
working
right
and
you
just
don't
let
go
once
you
pull
the
thread
right
owls.
Are
that
way
when
they're
getting
what
they
want?
B
B
C
B
C
A
I
think
I
think
that's
a
great
suggestion,
because
you,
because
you're
right
that
that
you
know
there
isn't
there
is
a
a
kind
of
an
imbalance
there
right
and
and
definitely
let's
talk
about
it,
because
I
think
that
there
are
several
Storage
Solutions
as
well
as
analysis.
You
know
Plus
Storage
Solutions,
because
I
think
you
know
when
you're
looking
at
different
types
of
data.
A
B
If
you
will
as
a
community
now
that
we've
kind
of
got,
you
know
language,
independent
ways
to
collect
data
in
a
non-crazy
way,
and
then,
with
the
you
know,
the
collector
or
other
mechanisms
you
know,
handle
it
and
get
it
to
a
place.
We
can
do
that
analysis.
Maybe
like
some
of
those
bright
minds
and
coffee-induced
nights.
B
You
know
we'll
be
focused
on
on
exactly
what
you
say
like
now
that
we
have
all
this.
How
do
we
juggle
it?
How
do
we
announce?
How
do
we
analyze
it?
How
do
we
slice
it
dice
it?
All
of
that
so
I
think
it
is
an
astute
observation,
though,
that
there
has
been
a
disproportionate.
You
know
view
on
the
collection
inside,
but
I
would
think
that's
going
to
change
as
an
observer
right.
So.