►
From YouTube: 2021-12-07 CNCF TAG Observability Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Hello,
hello,
we
might
have
a
really
short
meeting
today.
Yeah
a
lolita
has
a
conflict
for
half
of
this
and
there's
some
issue
in
aws.
That's
taking
out
michael
and
bartek.
Has
the
physical
therapy
going
longer
than
expected,
so
we
can
have
good
mix
or
something,
but
we
can
use
the
time,
however,
like
I
suppose,
but
our
attendance
from
from
folks
is
going
to
be
really
low.
Today,
hello,.
A
C
A
B
B
Hello,
so
I
guess
we
are
at
three
or
four
minutes
past.
This
is
a
a
cncf
recording
an
event,
so
the
cncf
code
of
conduct
applies,
and
we
always
say
that
and
we'll
continue
to
so.
The
other
chairs,
as
well
as
our
tech
lead,
are
all
indisposed
today,
unexpectedly,
so
we
have
kind
of
a
an
open
agenda.
We
can.
We
can
quit
early
and
return
time
or
we
can
talk
over
some
of
the
stuff.
That's
been
happening
in
parallel
I'll
send
out.
B
If
folks,
don't
have
it,
here's
a
link
to
the
meeting
doc
feel
free
to
sign
in
and
as
usual,
the
agenda
for
this
meeting
is
completely
open.
So
if
there's
anything,
people
want
to
talk
about
or
mull
about
or
or
even
just
you
know
chat
about.
If
it's
not
super
serious,
that's
that's
fine!
So
that
is
there.
Anyone
who
has
never
been
here
before
that
wants
to
introduce
themselves.
D
Hi,
that
would
be
me,
my
name
is
antu
and
I'm
very
new
to
the
open
source
community.
I've
used
products
from
it
to
track
it
for
years,
but
I've
worked
for
a
company
that
didn't
really
participate
or
put,
you
know,
required
major
approval
to
share
code,
and
so
but
things
are
changing
and
my
interests
are,
I
used
to
work
for
cisco
and
then
create
supercomputer
and
then
recently.
B
D
Oh,
oh
I
I
worked
for
cisco
for
10
years
and
then
crave
for
about
a
year
and
then
vmware
for
a
year
and
a
half,
I'm
part
of
the
great
resignation,
but
my
background
is
in
networking
and
software
defined
networking
and
more
recently,
kubernetes
cni.
D
B
Yeah
in
the
in
the
chat
in
the
zoom
chat,
there's
a
link
to
our
document.
You
can
feel
free
to
sign
in.
Is
there
anyone
else
before
we
covered
the
administrivia
in
that
open
floor
all
right,
so
we
were
going
to
have
a
visitor
today
that
was
gonna.
B
You
know
we
have
kind
of
an
open
agenda,
because
scott
rigby
had
we
had
planned
on
having
him
come
he'll,
be
coming
to
our
next
meeting
on
the
21st,
the
third
tuesday
and
he's
from
the
tag
app
deploy
a
group
and
they
have
a
working
group.
There
called
the
get
ops
working
group
and
they
have
launched
something
called
open,
git,
ops
and
there's
a
whole
work
stream
there
and
in
discussion
with
toc
and
chris
and
some
other
folks.
B
They
had
all
sort
of
recommended
that
we,
the
observability
tag,
reach
out
to
the
app
deploy
tag,
to
get
some
some
guidance
on
how
to
launch
something
and
we'll
get
to
that
in
a
second
and
sort
of
how
to
do
the
policy
and
the
governance
piece
so
that
we
launched
something
that
is
sustainable
and
is
community
driven.
So
he
sends
his
regrets.
B
He
had
a
schedule
anything
on
his
side
that
that,
in
any
event,
he'll
be
coming
next
next
week
in
two
weeks,
rather
so
last
last
meeting
the
second
thing
I
have
in
here
there
was
a
couple
questions
about
how
folks
can
contribute
what
things
can
they
pick
up
and
do
I
put
in
a
link,
we
tag
a
bunch
of
issues
as
help
wanted.
Those
are
great
places
to
start
for
pretty
much
anyone
again.
This
is
a
community
driven
group.
B
That's
that's
vendors,
end
users
as
well
as
project
maintainers
and
members.
So
any
of
those
issues
are
a
great
place
to
start.
Some
of
them
will
be
covered
in
the
observed.
K-8S
work
stream
that
we'll
get
to
in
a
second
third
there's
an
update
from
bartek
who
sends
his
regrets
as
well
he's
finished
his
review
of
the
white
paper.
B
I
think
richie
still
has
a
few
things
and
and
if
anybody
else
wants
to
put
in
comments
the
link
is
there
it's
still
open,
but
I
think
from
from
what
from
what
bartek
said,
both
privately
as
well
as
in
channel,
you
know
that's
approaching
doneness
and
we
can
put
it
out
for
public
comment
and
then
publish
it,
and
the
only
other
thing
that
I
could
mention
is
just
a
brief
update.
B
So
we
we
met
last
week
to
talk
about,
observe
k8s,
which
is
a
working
group
that
we're
launching
there's
a
working
dock
there.
Anyone
has
welcome
to
contribute
to
it
if
you're
interested
in
it.
B
Basically,
the
document
is
sort
of
form
the
charter,
if
you
will
or
sort
of
what
it
is,
the
scope
of
it
and
such
I
think,
a
good
chunk
of
the
help
wanted
issues
and
some
of
the
issues
that
we've
defined
in
github
can
be
satisfied
or,
or
you
know
done
in
the
vehicle,
that
is,
that
working
group
and
that's
the
working
group
that
we're
looking
to
get
some
guidance
and
learnings
from
the
app
deploy
tag
on
how
to
go
about
it,
procedurally,
logistically,
etc.
B
I
think
I
mentioned
last
meeting
too,
but
we've
secured
the
domain
names
that
are
interesting
as
well
as
the
github
org,
which
is
right
now
empty
on
purpose,
so
that
you
know
we
can
launch
it
as
a
group,
once
we
have
some
consensus
and
a
shared
understanding,
there's
a
doodle
that
went
out
we're
gonna
meet
on
thursday
and
then
we'll
get
into
a
regular,
probably
weekly
cadence
and
I'm
gonna
try
to
find
a
time,
that's
good
for
west
coast
people
and
and
you
and
folks,
in
the
eu
and
everywhere
between.
B
So
that
might
mean
we
have
two
different
times
or
something,
but
we're
still
sorting
that
again.
That's
all
I
really
had
on
the
agenda
from
my
side.
However
else
we
want
to
spend
our
time
is,
is
how
how
we'd
like
to
does
anyone
have
questions
or
things
that
they
want
to
talk
about
or
cover
or
put
on
on
the
agenda
for
today.
A
B
I
don't
think
so
so
earlier
in
the
year
some
end
users
got
together
and
decided
to
create
a
white
paper
that
covers
you
know,
defining
some
some
terms
and
providing
particularly
for
folks
new
to
the
space
or
new
to
the
domain,
maybe
not
like
a
full,
in-depth,
rosetta
stone,
but
certainly
covering
the
major
topics
like
you
know,
where
logs
were
traces,
et
cetera
and
and
really
it
was
sort
of
a
whenever
some
of
the
original
folks
are
on
leave
now.
B
So
it's
been
a
bit
quiet,
but
we've
had
a
number
of
contributors
to
it
and
it's
been
hammered
out
over
over
time
again,
michael
hasselblas
and
and
and
some
others
have
been
helping
to
shepherd
it
as
well,
apparently
there's
an
issue
in
aws
and
us
east
one.
So
I
think
that's
where
a
bunch
of
people
are
mitigating
that
we're
dealing
with
it
but
but
yeah.
So
so
the
white
paper
has
been
sort
of
slowly
percolating
and
marinating
and
bartek
just
finished.
B
His
review
he's
our
tech
lead
and
richie
chairs,
richie
hartman
from
grafana
he's
in
the
middle
of
doing
a
review
and
we're
we're
approaching,
where
we'll
put
it
out
for
public
comment
and
public
review
and
and
and
when
that's
done,
it
goes
to
the
toc
to
have
them
sort
of
bless
it
right,
and
that
would
be
our
first
working
group
that
produced
something
from
from
the
tag
to
date.
B
You
know
over
the
last
year
here
and
a
half
a
lot
of
the
activities
in
the
tag.
Well,
for
the
first
year
were
there
was
a
backlog
of
project
review
and
incubation
due
diligence
documents
that
we
worked
on,
and
you
know
we
filled
kind
of
the
rest
of
the
time
over
the
course
of
the
summer
in
the
spring.
Really
you
know
highlighting
interesting
observability
projects
and
and
chatting
about
various
in
topics
like
that.
I
think
the
observe
k,
eights
working
group
is
the
first
working
group.
B
That's
just
that's
not
like
a
paper,
but
actually
something
that
is
clonable.
You
know
that's
actually
running
that
people
can
interact
with
and
I'm
excited
for
that,
but
does
that
help.
A
Provide
some
context,
eric
yeah,
I
I
guess
what
was
what's
the
purpose
of
the
white
paper
and
maybe
what's
lost
on
me.
Is
it
just
to
be
an
introduction
to
this
tag
and
the
terms
or
is
it
a
guidance
on
like
how
to
actually
do
observability
upon
among
different
projects?
B
Yes,
it's
in
the
it's
in
the
google
doc,
okay,
so
there's
a
there's
a
pr
out
with
a
lot
of
the
comments
that
have
happened
in
there,
so
maybe
for
for
other
folks.
If
they
have
the
same
question,
I
can
cover
that
a
little
bit.
One
of
the
purposes
of
the
tag-
and
a
lot
of
this
is
laid
out
in
our
charter-
is
really
to
to
provide
to
provide
you
know
neutral,
perhaps
not
authoritative,
but
certainly
trustable.
B
Guidance,
you
know
in
all
directions
and
one
of
those
is
to
the
to
to
newcomers
to
the
space
end
users
that
might
just
be
getting
into.
You
know
cloud
native,
architectures
and
designs
in
general,
and
so
you
know
we
were
looking.
We
had
some
folks
that
wanted
to
do
some
writing
and
some
folks.
You
know
that
wanted
to
produce
a
white
paper
that
would
really
serve
primarily
newcomers
to
the
to
to
the
observability
space.
B
Many
of
the
folks
that
are
actively
engaged
in
this
domain
are
running
projects
or
our
vendors,
who
are
you
know
deeply
steeped
in
in
all
of
this
right.
Their
vernacular
is
expert
level,
and
so
we
wanted
to
have
something
where
somebody,
if
they
kind
of
tripped
over
the
tag
or
if
they
took
on
a
new
role
and
they
have
to
you
know,
a
monolith
was
moved
to
a
bunch
of
microservices
and
you
know
they
need
to
observe
it.
They
need
to
understand
how
it's
working
or
how
it's
not
working.
B
This
might
be
a
place
for
them
to
start
so
it
seemed
like
low-hanging,
fruit
and
not
controversial,
so
so
the
audience
is
really.
I
think
focus
more
outwardly
to
beginners
or
to
folks
to
to
the
space
it's
less
about
the
tag
itself
and
another
aspect
of
this
group.
Is
that
we're
not
you
know,
there's
not
the
cncf
and,
by
extension,
the
toc
and
these
technical
advisory
groups
are
not
king
makers
right.
So
there's
no
like
opinionated.
B
This
is
how
you
do
it,
and
if
it's
not
this
way,
you
don't
it's
the
wrong
way
right.
There's
not
that
sort
of
thing
it
tries
to
be
a
little
more
generic
and
and
just
inform
about.
You
know
what
are
the
nouns.
You
know
what
are
the
common
workflows?
What
are
the
common
concerns
so
that
if
you're,
just
starting,
you
have
a
place
to
start?
B
Lastly,
I'll
say
out
of
that,
I
think
there's
a
number
of
terms
that
we
can
pull
out
of
that
white
paper
or
that
could
be
contributed
to
the
glossary
project.
There's
a
cncf
glossary
of
terms,
I
believe
it's
cncf,
I
can
find
it
gets
cncf.glossary,
slash
glossary
so.
B
That
was
too
verbose,
but
that's
that's
sort
of
the
the
goal.
A
B
B
Yeah,
it's
a
tag,
observability
of
pull
51.
I
believe
and
there's
an
issue
linked
from
there
and
there's
a
fairly
long
thread.
It
started
out
as
a
as
a
google,
doc
right
and
and
it's
been
moved
to
markdown
as
we
approach
publishing
it.
B
Yeah
so
yeah,
so
again
we
have
a
is
there
anything
folks
want
to
talk
about.
We
could
really
cover
just
about
anything.
I
feel
a
little
flat-footed
as
as
at
the
11th
hour,
we
had
folks
with
content,
give
their
regards
or
regrets
rather.
C
So
matt
you've
been
facing
it
with
bravery,
so
we're
well
done
on
handling
it
so
far,
20
minutes
into
the
meeting
and
having
very
good
agenda
and
coverage.
So
far
I
want
to
bring
if
there
is
time
something
a
pretty.
C
It
might
be
a
red
tape,
but
I've
been
encountering
that
we've
been
chatting
over
the
over
the
slack
channel
for
that
on
that
several
of
us
who've
been
struggling
with
the
calendar
and
I've.
I've
been
wondering
if
anyone
managed
to
resolve
that
it's
obviously
beyond
this
specific
tag,
but
given
that
people
want
to
have
this
specific
tag,
I'm
raising
it
here.
If
any
advice
on
this
one.
B
Is
people
duplicated
individual
events
to
their
calendars
like
a
long
time
ago
that
were
recurring
and
we
used
to
meet
every
other
tuesday
right,
but
we
we
really
wanted
to
be
in
alignment
with
the
overall
cadence
of
the
toc
and
and
the
other
kind
of
groups,
and-
and
so
I
would
say
six
months
ago
or
something
five
months
ago,
we
switched
to
meeting
on
the
first
and
third
tuesdays
of
every
month,
because
some
months
actually
have
five
tuesdays
and
then
things
get
out
of
sync,
and
so
there
was
general
malaise
about
that.
B
So
the
the
cncf
calendar,
I
believe,
is
up
to
date.
That's
that's
what
I
what
I
use,
but
for
folks
that
might
still
have
a
calendar
rather
a
recurring
meeting
from
long
long
ago.
That's
that's
sort
of
where
the
where
the
the
miscommunication
is,
and
unfortunately
it's
not
something
we
can
fix
centrally
right.
It's
it's
things
that
are
living
in
other
people's
calendars.
C
Okay,
so
just
to
follow
up
on
this
one,
the
column
the
cncf
calendar
contains
is
essentially
all
the
meetings
of
all
the
cncfs,
all
the
tags,
all
the
sigs,
all
the
working
groups
and
any
other
creature
within
the
cncf.
Is
there
any
way
to
just
import
the
recurring
meeting
of
the
tag
observability
in
this
case?
Obviously,
I
need
it
for
some
other
meetings,
but
I
guess
the
patent
will
work
for
others
as
well.
B
I
haven't
found
a
way
to
make
it
recurring
you:
can
you
can
go
into
the
google
calendar
and
duplicate
the
event
to
your
calendar,
but
we
can
take
an
action
item
again
to
follow
up
with
amy
she
just
sent
in
slack
a
talkify
which
I've
never
seen.
B
A
You
duplicate
the
recurring
event,
it
will
just
I
mean,
and
it
also
is
the
same
event
every
time.
So
I
think
you
can
just
duplicate
it
and
it
should
be
fine,
or
at
least
it
worked
on
my
calendar
or
it's
worked
so
far.
I
so
I
just
deleted.
I
deleted
the
old
one
and
then
duplicated
the
new
one
after
they
changed
it
to
a
new
time,
and
so
far
it's
been
fun.
I
I
think
I
did
the
same.
C
C
A
A
B
I
I
think
part
of
the
problem
might
be
too
that,
like
in
google
calendar,
you
can
set
up
recurrences,
but
there's
not
a
neat
and
tidy
way
to
set
it
up
for,
like
the
first
and
third
tuesday,
for
example.
It
wants
to
do
like
every
other
and
that
got
us
into
trouble
before,
because
sometimes
we
would
have
meetings.
You
know
three
in
a
month,
sometimes
two
in
a
month,
and
we
just.
C
So,
just
maybe
offering
in
in
the
vein
of
automation,
observability
and
virtualization
and
the
rest
of
the
buzzwords
that
we're
representing
here
as
part
of
the
mandate
is
there
a
way
to
just
send
an
invite
that
people
can
just
simply,
even
if
we
just
generate
it
out
of
the
generic
calendar,
but
just
for
the
sake
of
this
distinguished
forum
or
yeah.
I'm
just
asking
openly.
B
I'm
putting
into
the
notes
taking
an
action,
create
a
calendar,
that's
free
of
drama.
That's
the
perfect
phrasing
yeah
again
right!
So
hopefully
you
know
we
can.
We
can
do
that.
I
did
also
put
a
link
into
the
actual
I've.
Never
seen
this
talkify.
C
B
So
I
think,
there's
a
there's
a
little
save
button
at
the
top.
A
green
button
when
you
go
to
that
link,
looks
like
a
little
three
and
a
half
inch
floppy.
If
anybody
remembers
those
and
that
will
let
you
get.
A
B
Or
you
know
something
that
you
can
import
to.
Google.
B
C
Trying
it
as
we
speak
just
to
validate
it
on
mine,
it
opens
up
as
a
do
not
repeat
event,
so
I
guess
it
will
again
need
to
change
to
every
you
know
first
tuesday,
or
something
like
that,
but
so
I
I
can
do
that
again,
I'm
just
looking
for
a
more
systematic
solution
that
we
can
then
distribute
among
the
broader
teams.
Some
of
the
audiences
not
more
following
on
the
follows
on
the
on
the
slack
and
things
like
that.
Just
make
sure
that
everyone
is
on
the
on
the
loop
on
this
one.
C
B
We'll
fix
something
and
we're
gonna
start
using
the
mailing
list
more,
I
I
will
freely
admit.
I
have
not
hardly
used
it
nearly
enough,
and
I
sometimes
forget
that
many
people
use
email.
My
email
has
just
so
much
email,
so
for
me,
slack
is
cleaner,
but
but
we
will
we'll
we'll
see
if
we
can
resolve
this
and
then
send
something
out
to
the
mailing
list.
C
Brilliant
thanks
a
lot
for
helping
with
this
yeah.
You
know,
while
we've
got
you
here,
dude.
A
C
Okay,
no
worries
so,
first
of
all,
whoever
doesn't
know
me,
my
name
is
dottan
lotan
horvitz
and
I
the
day
job
is
as
a
developer
advocate
that
logs,
the
logs.I
o
and
I'm
also
a
member
here
of
the
tag
and
some
other
relevant
groups
in
the
open
source,
both
in
the
cncf
and
others
like
open
search,
but
mainly
in
the
observability
domain
and
part
of
my
activity
in
the
observability
domain
is
an
a
community
podcast
that
I
started
over
about
a
year
and
a
half
ago
during
the
kovid,
when
I
was
trying
to
carry
on
with
some
of
the
activities
that
have
been
going
on
in
the
community
in
a
virtual
form,
essentially
a
monthly
episode.
C
I
have
the
owner
of
having
a
guest
from
the
community
or
from
end
user
or
from
vendor,
but
someone
who
has
a
direct
connection
to
one
of
these
aspects-
bartek,
for
instance,
that
you
all
know
appeared
on
the
on
the
podcast
and
richie
and
others.
I
hope
to
get
matt
to
agree
to
participate
one
of
these
days.
I
think
he
can
contribute
a
lot,
and
this
is
by
the
way,
also
an
open
invitation
for
for
anyone
here
in
this
call,
and
then
whoever
also
listens
to
their
recording
offline.
C
If
you
have
something
meaningful
that
you
can
share
about
a
specific
open
source
project
that
you're
involved
with
about
activities
even
here
in
the
tag
observability
and
anything
that
is
related
to
this
domain,
also
end
user
experience
how
you
struggled
with
challenges
around
observability,
I
resolve
them
and
anything
that
you
think
is
meaningful.
C
I'd
be
glad
feel
free
to
reach
out
to
me
you
can
catch
me
on
on
the
cncf
slack
at
four
of
its
age,
o
r,
o
v
ats
or
on
twitter,
or
in
github,
or
essentially,
probably
everywhere
at
horowitz,
and
the
topics
are
varied.
For
example,
next
week
I'm
going
to
talk
with
fabric,
the
surname
is
a
bit
difficult
to
pronounce,
but
he's
the
ceo
and
founder
of
polar
signals.
C
If
you,
if
you're
familiar
with
this
company,
is
also
the
person
behind
the
parka
open
new
open
source
project
that
is
around
the
continuous
profiling,
which
is
also
going
to
be
a
significant
part
of
the
conversation,
probably
talking
about
the
signals
of
observability
going
beyond
the
three
pillars
of
observation
to
newer
signals
and
the
contribution
what's
the
gap,
that
is,
that
necessitates
more
signals
and
what
what
can
be
resolved
with
these
signals
and
so
on
so
interesting,
a
discussion
that
also
pertains
to
many
other
open
source
projects
like
a
pixie
project
that
has
been
released.
C
C
B
Cool
yeah
we've
been
playing
slack
tag,
I'd
love
to
I'd
love
to
be
a
guest.
If
you'll
have
me
in
the
future,
sometime,
I've
actually
been
quietly
sort
of
stealthily
incubating
an
open
source
project
in
the
observability
domain.
That's
still
I'm
still
in
benevolent
dictator
initial
implementation
mode,
but
perhaps
when
that,
when
that
stuff
comes
out
a
little
bit,
it
might
be
more
interesting
to
talk.
Then.
D
B
Yeah
it's
it's
kind
of
me
turning
out
on
graph
theory,
because
I
haven't
in
a
while,
and
I
wanted
to
yeah
and
I
put
a
I
put
a
link
to
in
the
in
the
working
doc
for
the
meetings,
as
well
as
the
the
chat
to
your
podcast.
So
I've
been
listening
to
it
for
a
while.
That's
great
thanks
in
a
somewhat
related
bit.
You
know
some
of
those
initial
issues
we've
had
for
a
long
time
since
the
summer,
really
some
of
them
cover
you
know
potent!
B
You
know
we
have
a
youtube
channel
now
sponsored
by
the
cncf.
We've
had
it
for
a
while
and
if
anyone
wants
to
you
know,
make
content,
be
a
video
podcasting
star
like
goten.
B
I
don't
know
that
if
I
would
make
the
best
one
so
I've
not,
but
it's
a
it's
an
easy
opportunity
as
well
everything
from
figuring
out.
You
know
what
the
interviews
or
talks
might
be
about
producing
content,
producing
a
program
to
kind
of
plan
out
that
stuff.
You
know
all
that
stuff's
up
for
grabs.
C
And
this
maps
to
issue
49
it's
already
there.
If
anyone
wants
to
have
a
look
I'll,
just
post
it
here
also
on
the
chat,
if
I'm
not
missed,
I
hope
that
they
mistake
the
yeah.
So
if
you
have
anything
to
contribute,
also
in
terms
of
ideation
of
what
would
be
the
format
or
anything
else,
really,
that's
that'd
be
a
good
place
to
us.
B
Something
other
than
minecraft.
Is
there
anything
else?
I
don't
want
to
waste
people's
time.
I'm
you
know
again
it's
an
open
floor.
We
we
had
a
little
bit
of
a
gap,
so
you
know
like
like,
for
example,
eric.
You
said:
you're
you're,
you're
new.
I
think
you
came
last
last
week,
which
was
also
very
quite
quite
quite
a
small
meeting
with
a
is
there
anything
in
particular,
for
example,
you'd
like
to
work
on
or
you'd
like
to
get
out
of
out
of
this.
B
Great
yeah,
I
mean
check
out
the
issues
in
github
and
it
doesn't
just
have
to
be
the
help
wanted
ones
and
anyone
should
be
able
to
permission-wise
to
to
create
new
issues.
Again,
it's
sort
of
a
coalition
of
the
willing
many
folks
are
actually
paid
to
work
on
observability
I
I
wasn't.
I've
been
an
end
user
for
a
number
of
years
of
all
this
stuff.
So
that's
how
I
kind
of
fell
into
this.
C
But
yeah
so
is
there
by
the
way,
if
there
is
a
bit
of
time,
just
in
terms
of
I
know
that
some
people
met
around
the
reinvent
just
using
the
the
purpose
for
a
face
to
face.
I
was
wondering
if
I
wasn't
able
to
attend,
but
I
was
wondering
if
there
has
been
any
gathering
of
the
of
this
forum
or
a
subset
of
the
forum
and,
if
so,
maybe
interesting
to
catch
up
on
this.
B
You
know
we
had
actually,
I
think
we
had
some
issues
around
it.
We
had
hoped
to
do
something
like
that
at
kubecon.
I
was
at
kubecon
in
l.a
and
I
would
lead
it
and
I
gave
a
short
talk.
It
was
only
27
minutes
covering
the
tag,
but
with
the
travel
restriction
in
place,
you
know
a
lot
of
folks
couldn't
make
it.
So
we
actually
didn't
do
that.
B
I
haven't
had
a
chance
to
talk
to
any
of
the
folks
that
were
in
re
event,
so
if
they
did
meet,
that's
awesome,
I'd
love
to
get
a
readout
of
it
and
see.
If
anything
came
of
it
and
moving
forward,
I
mean
I
have
to
keep
hope
alive
that
you
know
people
will
take,
take
some
take
some
vaccinations
and
the
world
will
open
back
up,
but
we
do
have
you
know
one
of
the
one
of
the
things
that
we
had
identified
last
year.
B
Actually
as
a
worthwhile
activity,
for
the
tag
is
to
create
materials
to
help
people
have
local
observability
meetups
in
their
in
their
own
locales.
You
know,
we've
had
folks
come
saying
that
they
want
to
do
specifically
this
abroad.
You
know
all
over
the
place,
not
not
not
just
north
america,
obviously,
and
so
you
know
making
a
kit
that
might
have
some.
You
know
some
boilerplate
slides,
look
like
content
and
whatever
else
would
help
someone
start
a
local
meetup.
B
You
know
because
reinvent
comes
once
a
year
you
know
kubecon
comes
once
or
twice
twice
a
year
or
once
a
year
for
some
folks,
depending
on
ability
to
travel
right,
so
so
that
that
that,
for
example,
is
something
that
we
could
do
and
and
our
contributions
welcome
many
companies,
I'm
in
I'm
just
outside
boston
and
cambridge
bass.
Many
companies,
at
least
in
cambridge,
have
like
public
spaces
for
that
kind
of
thing,
and
and
they've
been
closed.
B
You
know
for
the
last
year,
but
I
think,
as
things
open
up,
we
can
really
position
ourselves
to
kind
of
augment
sort
of
the
mostly
vendor,
and
mostly,
you
know,
project
membership
of
the
tag
today
with
with
more
of
more
grassroots
practitioner
and
end
user
community,
and
we
can
have
sets
of
meetups
you
know
and
and
and
that
can
bubble
interesting
things
up,
we
could
we
could
give
provide
a
platform
so
that
those
individual
meetups
aren't
isolated,
but
they're
a
network
of
them.
C
Yeah,
by
the
way
I
put
on
the
chat
for
whoever
is
not
familiar
with,
this
is
issue
40,
so
again
matt.
You
know
that,
but
for
whoever
wants
to
contribute
to
the
thought
process
around
how
to
build
up
this
meetup
by
the
way,
I
posted
a
question
there,
maybe
to
understand
the
scope
and
if
you
want
to
have
it
as
designated
meet
up,
so
I
want
to
somehow
create
the
facilitation
to
team
up
with
existing,
for
example,
local
cncf
chapters.
C
For
I
I
for
one
and
a
co-organizer
of
a
local
cncf
chapter
in
tel
aviv,
I'm
best
in
tel
aviv,
and
that's
where
I
run
it.
So
I
just
wondering
if
the
scope
or
the
mandate
that
you
want
to
give
this
topic
is
to
create
designated
activities
or
actually
create
an
add-on
sort
of
facilitation
also
to
plug
into
existing
emitter
groups.
C
Because
from
my
experience
with
communities,
it's
very
the
hard
part
is
to
ramp
up
to
to
build
up
a
new
community,
and
if
you
can
plug
into
existing
local
chapters
that
make
the
the
onboarding
much
easier
again,
we
can
take
it
offline
and
discuss
it
over
the
github.
Of
course
get
an
issue,
but
just
in
that
context
want
to
bring
it
up.
B
No
that's
great,
and
in
fact
I'm
going
to
I
just
went
back
about
five
months
or
so
in
the
document,
and
I
had
written
up
back
then
a
lot
of
these
things
in
a
more
human,
readable
format
and.
B
Right
so
again,
there's
been
additional
ones
added,
but
that's
a
sort
of
a
high
level.
Look
at
you
know
some
of
the
things
that
that
are
actionable
now,
and
some
of
them
are
fairly
low
hanging
fruit
and
you
could
yeah.
You
could
have
a
hand
in
in
defining
the
look
and
feel,
for
example,
of
you
know
we
could
have
a
site
for
the
tag
which
we
don't
have
yet
I
mentioned
that
the
glossary
project
is
another
one.
B
B
But
you
know
one
of
the
things
we
want
to
get
out
of
an
interaction
with
tag
app
deploy
is
to
really
is
to
propose
and
I've
shopped
around
the
idea,
with
various
folks
at
the
tlc,
as
well
as
in
app
in
the
get
ops
working
group,
scott
being
one
of
them,
but
we
could
really
use
an
open
standard
kind
of
like
open
metrics,
you
know
and
and
and
common
formats.
You
know
hotel
formats
and
things
like
that.
B
That's
really
fostered
an
ecosystem
of
vendors
that
provide
a
lot
of
value
and
it's
and
it's
really
been
growing
quite
quickly.
What
we
don't
have
is
like
a
an
open
standard
for
the
data
format
for
recording
or
for
reporting
on.
You
know,
stateful
changes
made
to
deployments
so
like
how
you
know
if
we
want
to
build
common,
observability,
tooling
or
if
vendors
want
to
build
differentiated,
and
I
think
they
would
differentiated
you
know,
solutions
and
user
interfaces
and
ways
to
visualize
and
correlate.
B
B
You
know
where
we
don't
want
to
have
a
bifurcation
or
a
triforcation,
oh
and
forcation.
You
know
we
don't
want
to
have
like
you
know,
all
the
a
whole
bunch
of
different
ways
to
just
report.
You
know
this
commit
caused
this
thing
to
be
built
that
got
deployed
to
this
cluster
right.
So
I
think
that's
an
example
of
like
low
hanging
fruit,
where
the
two
tags
could
could
come
together
and
and
have
an
open
process.
B
That's
one
of
the
things
we
wanted
to
talk
about
today,
but
we'll
talk
about
on
the
21st
about
like
how
would
we
do
that
right
in
a
way
that
is
inclusive,
open
and
is
not?
You
know
a
couple
very
interested
people
from
from
particular
vendors
say
you
know
just
slamming
through
you
know,
with
a
standard,
it
really
needs
to
be
a
community
accepted
standard
or
it
won't
work.
B
D
Yeah
so
I'm
part
of
the
open
network
user
group
owner
and
they
came
up
with
something
called
ski
snf.
I
forgot
all
the
acronyms
stand
for,
but
basically
it's
a
decorator
framework
for
messages
so
that
it
can
be
formatted
post
generation
so
that
it
can
be
part
it
could
conform
to
the
format
of
an
enterprise
or
vendor
application
for
observability,
obviously,
security
tagging.
D
So,
instead
of
having
you
know,
events
generated
in
a
certain
format
or
a
common
standard
which
would
seem
like
we're
still
working
toward.
We
there's
a
decorative
framework
that
will
take
the
events
and
reformat
it
in
the
right
quote:
unquote,
right
or
needed
formats,
so
that
it
can
be
consumed
by
different
observability
frameworks
or
application.
D
Yeah
are
you
talking
about
opennetworking.org.
C
B
If
I'm
understanding
how
you
described
it
correctly,
then
yes,
that
that's
very
much
in
scope,
I
mean,
if
you're,
if
you're
tagging,
network,
packets
or
requests
with
metadata
specifically
meant
for
observability
tooling
to
leverage
yeah.
If
it's,
if
it's,
if
it's
open
source,
you
know
again
whether
or
not
open
source
projects
are
in
the
cncf
formally
or
not,
they
are
still
in
scope
and
one
of
the
purposes
of
of
the
technical
advisory
group
on
observability.
B
In
this
case,
one
of
the
primary
missions
for
it
is
to
provide
guidance
and
and
and
I
and
to
to
the
toc
of
the
technical
oversight
committee
and
the
broader
community
to
say:
hey
these
are
gaps,
or
these
are
projects
that
you
know
might
benefit
from.
B
You
know
either
interoperating
with
open
standards
that
are
come
out
of
the
cncf
or
in
joining
the
cncf
as
a
project.
So
if
you'd
like
to
come
talk
about
it
at
a
future
meeting
or
we
have
another
ten
five
six
minutes
now
yeah,
that's
that's
absolutely
in
scope.
I've
I've
not
heard
of
it
before
I'll
put
it
in
the
notes,
though,
and
if
you,
if
you'd
like
to
to
give
a
little
talk
about
that
that'd
be
cool.
B
The
format
we've
done
in
the
past
is
like
you
know,
roughly,
you
know
15
minutes
for
various
projects
like
this,
where
you
know
you
talk
for
five
or
six
minutes,
you
know
with
a
slide
or
two
or
not,
and
then
and
then
just
have
some
discussion
and
see
where
see
where
things
land.
B
Yeah
it
looks
like
it's
at
you
too,
so
cool,
that's
good!
I'll!
Give
this
a
read!
Thank
you
for
thanks
for
bringing
it.
D
C
Great
by
the
way,
matt,
I
think
we
should
clarify
he
doesn't
have
to
be
the
formal
you
know
owner
or
master
maintainer,
if
you
feel
you
know,
if
you're
up
to
speed,
to
give
a
brief
overview,
15
minutes
overview,
and
you
feel
comfortable
with
that.
Obviously,
if
the
the
a
more
senior
person
is
eager
to
come
and
speak,
it's
fine,
if
not
again,
for
at
least
for
a
brief
intro
feel
free
feel
comfortable
to
to
do
it
yourself.
C
And
if
we
see
that
there
is
a
need,
we
can
definitely
take
a
follow-up
and
then
maybe
invite
a
more
focused
forum
to
follow
up
just
yeah.
I
mean
we've
kind
of.
B
I
I
we've
had
a
lot
of
people
join
and
and
and
chat
or
listen
over
the
last
year
and
a
half
or
so,
but
I
think
now
that
we've
sort
of
been
established
as
an
actual
tag.
You
know,
we've
done
some
good
things,
there's
so
much
more.
We
can
do
really.
The
model
is
that
tags
or
technical
advisory
groups
spawn
working
groups
and
working
groups
have
just
a
couple
of
things
that
make
them
a
working
group.
B
One
is
that
they're
time-bounded,
you
know
there's
artifacts
that
are
agreed
to
beforehand
that
come
out
of
it
and
that
toc
approves
the
formation
of
a
working
group.
So
a
lot
of
this
stuff
is
meant
to
be
done.
Asynchronously
and
this
meeting
can
be
more
like
you
know,
part
scrum,
you
know
or
park
stand
up.
If
you
will
right
where
these
various
working
groups
can
can
report
back.
B
I
think
that
this
time
of
year
in
particular,
where
we've
had
kubecon
and
then
re
invent
and
about
four
or
five
other
conferences
that
I
forget
the
name
of,
and
then
we
come
into
thanksgiving
and
christmas,
it's
called
sort
of
a
lull.
You
know,
but
I
think
that
when
I
was
at
microsoft,
we
used
to
say
when
the
market's
in
a
lull
right
or
when
the
economy
is,
is
a
little
bit
down.
B
That's
the
time
to
double
down
and
do
research
to
incubation
and
all
that
so
that
when
activity
picks
back
up
broadly,
you
know,
you've
got
well-formed
programs
and
projects
to
to
to
attract
contributors
as
well
as
well.
In
that
case
dollars
you
know,
so
I
think
the
same.
D
Another
sorry,
another
question:
yeah:
have
you
guys
thought
about
observability?
You
know
event
notification,
all
the
way
down
to
the
the
hardware
firmware
level.
So
it's
not
just
software
observability,
but.
B
Well,
yeah,
I
mean
I
don't
know
if
anybody
else
wants
to
jump
in,
but
I'll
say
I'll
say
briefly.
I
think
that
you
know
a
lot.
You
know
the
white
paper
covers
this,
but
we
kind
of
think
of
observability
as
a
set
of
signals.
B
You
know
things
that
happened,
one
of
which
is
events
or
blogs,
depending
on
you
know
how
you,
how
you
consider
them
to
look
at
them
and
traces
and
other
things,
but
obviously
all
of
the
data
that's
been
made
accessible
through
evpf
based
mechanisms
as
well
as
lots
of
other,
for
example,
prometheus
exporters
that
interface
with
various
appliances
and
pieces
of
hardware
and
provide
telemetry
and
metrics
to
them.
That's
all
very
much,
yes,
I
mean
part
part
of
a
journal.
B
Yeah
sure
I
mean
that's
a
great
place
to
start
or
we
can
we
can.
We
can
talk
at
slack
as
well.
I
want
to
be
respectful
of
calendars.
We've
only
got
about
90
seconds
before
the
meeting
is
technically
over
and
I
think
another
two
or
three
minutes
before
zoom
just
goes
so,
but
yeah.
Please,
please
join
us
at
slack
or
on
the
mailing
list.
B
Super
and
thank
you
for
joining
and
and
providing
a
link
to
this.
This
is
new
to
me
at
least.
B
Well,
for
not
having
a
specific
agenda,
we
killed
some
time.
So
so,
thanks
for
all
the
comments
and
yeah
I'll
see
you
next
time
or
online.