►
From YouTube: 2022-01-18 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).
A
B
So
welcome
this
is
a
cncf
sponsored
video,
so
the
cncf
code
of
conduct
applies
welcome
everyone.
This
is
tag
observability
on
the
18th.
B
Both
alolita
and
richard
richie
were
unavailable.
Today,
something
came
up
for
both
of
them
in
their
day
jobs,
so
this
could
actually
be
a
short
meeting.
We
have
an
open
floor,
that's
gonna
be
for
most
of
it,
and
I
have
a
few
minor
updates.
C
Yes,
sir,
sorry,
I
have
to
introduce
myself
yeah,
I'm
working
for
kkr
and
I'm
ahead
of
observability
and
actually
I'm
working
with
open
telemetry.
So
I
just
decided
at
some
point
just
it
would
be
good
for
myself
to
gain
some
additional
knowledge
or
maybe
share
some
information
with
you.
Folks.
That's
why
I'm
here
so
I'm
just
curious
what
exactly
you're
going
to
discuss
what
topics,
what
the
gender!
So,
if
you
can
just
give
me
some
idea.
B
Yes,
I
think
zoom
doesn't
have
scroll
back,
but
in
the
chat
there's
a
link
to
the
meeting
notes
with
all
of
that.
There.
C
B
For
those
that
just
joined
welcome
both
lolita
and
richard,
had,
I
think,
incidents
at
work
like
or
meetings
or
something
come
up
in
in
parallel,
so
there's
an
open,
a
fairly
open
table
today.
If
anyone
wants
to
talk
about
anything
specific
feel
free
just
on
the
agenda,
I
had
a
couple
sort
of
administrator
reminders
coming
up
in
in
may:
we'll
have
elections
for
or
nominations
rather
for
chairs
the
tag.
B
The
technical
advisory
group
has
three
chairs
and
we
started
almost
two
years
ago.
Back
in
two
years
ago,
in
april
may,
and
that's
when
richie
and
I
started,
alolita
sharma
from
aws
was
voted
as
chair
over
the
in
the
late
summer.
So
two
seats
will
be
open.
We
also
have
a
an
immediate
open
need
for
technical
leads.
B
These
are
people
who
are
passionate
and
or
want
to
drive
some
specific
project
or
provide
some
leadership
around
topics
of
observability
consistent
with
our
charter.
So
so
that's
that
the
past
five
meetings
have
been
uploaded
to
youtube
delay
over
the
holidays
and
I'll
put
in
a
link
to
some
of
the
issues
that
are.
You
know
we've
marked
as
help
wanted,
there's
also
another
label
there
for
good
first
issue.
I
believe
so
there's
all
manner
of
ways
that
we've
defined.
B
That's
there
so
just
jump
on
in
you
could
chat,
send
a
shout
out
in
slack
as
well
for
any
questions.
There's
a
bunch
of
people
there
that
I'm
sure
would
be
happy
to
answer
them.
Welcome
to
the
new
people
that
just
joined,
gibbs,
char
and
lucas
happy
new
year
haven't
seen
you
since
last
year,.
B
New
year
we
were
just
saying:
there's
a
fairly
open
agenda.
I
think
this
might
be
the
first
meeting
where
we've
got
more
than
a
few
folks
since
the
holidays,
not
to
not
to
put
you
on
the
spot,
hey
gibbs.
Did
you
have
a
any
update
on
persona
type
stuff,
or
could
we
queue
that
up
for
a
future.
D
Yeah
definitely
don't
have
an
update
right
now,
but
let's
get
that
on
the
agenda
for
next
next
meeting.
B
Cool
I'll
reach
out
yeah,
so
the
only
real
other
update
I
had
other
than
what
I.
What
I
had
just
mentioned
is
on
the
observe
k8
side.
We
kind
of
had
a
few
of
us
have
been
doing
some
work
over
the
holidays
and
in
december
slash
november,
and
we've
got
the
beginnings
of
what
I
think
with
a
charter
and
a
working
document
around
what
the
project
is
and
we'll
be
kind
of
formalizing.
B
The
working
group
with
the
toc
via
email
a
little
bit
later
today,
to
kind
of
throw
it
out
there,
the
pr
isn't,
obviously
merged,
and
if
anyone
wants
to
to
jump
in
or
has
additional
thoughts,
ideas
or
wants
to
contribute,
please
reach
out
feel
free.
B
We'll
we'll
add
you
to
the
repo
we're
just
now
kind
of
formally
launching
ken,
finnegan
and
and
michael
hazelblast
have
been
contributing,
as
well
as
daniel
kahn,
with
some
with
some
feedback,
I
think
we've
more
than
met
the
bar
for
at
least
we've
actually
done
a
little
bit
too
much,
probably
or
more
than
we
needed
to
do
rather
prior
to
being
able
to
formalize
the
working
group
and
launch
it.
B
B
Oh
well
so
again
today,
I
think
we
unexpectedly
have
both
of
our
other
chairs
pulled
away
for
something
urgent,
so
I
actually
don't
have
a
full
agenda
planned
for
today.
So
this
might
be
a
very
quick
meeting.
E
I
I
guess
one
matt
one
thing
to
bring
up
around
the
observe
k8s
is
just
to
see
if
there
was
anyone
else
from
this
group
that
was
potentially
interested
in
being
a
chair
for
that,
because
michael
and
I
kind
of
put
our
hands
up
just
because
I
think
there
was
only
three
of
us
in
that
meeting
at
the
time.
Do
you
want
to
give.
B
A
brief
overview
or
a
cover
sort
of
I
don't
want
to
monopolize
the
time
and
and
things
like
that,
I
would
love
it
if
you,
if
you
want
to
say
a
few
words
about
what
it
is.
E
Sure
I
can
try
and
do
my
best
to
remember
from
last
time
we
spoke,
so
the
idea
behind
observe
k8s
is
to
give
users
the
ability
to
explore
the
observability
landscape,
the
tools,
the
frameworks
whatever
it
might
be,
focused
on
the
cncf
side
of
things,
but
also
willing
to
accept
and
include
additions
from
outside
their
cncf.
That
might
end
up
being
projects
that
we
want
to
seek
to
include
in
the
cncf
in
the
future
and
all
that
kind
of
thing.
E
The
the
goal
is
to
have
a
system
where
users
can
play
around
with
a
tool
and
dive
into
the
observably
in
the
different
aspects,
to
get
a
feel
for.
If
I
make
this
http
request
over
here,
what
does
that
look
like
in
metrics
logs
traces?
How
do
they
all
link
together
and
what
tools
are
used
to
do
all
that
linkage
and
what
kind
of
level
of
detail
I
can
get
to
into
and
all
that
kind
of
thing.
So
we
want
to
have
a
few
different
example.
Applications
we've
talked
about
what
is
it
sockshop
and.
E
I
know
there's
a
couple
of
others
that
I
can't
remember:
we
have
a
list
of
them
in
that
document,
potential
examples
that
we
want
to
take
and
basically
get
observability
working
with
them
to
provide
this
system.
It
will
be
something
that
we
require
some
level
of
infrastructure
to
run
so
that
it
can
actually
be
running
all
the
time
for
people
to
play
with
yeah.
E
That's
been
put
together
to
take
an
area
and
explain,
explain
it
expand
it
out,
create
examples
for
it,
and
so
it's
not
just
a
huge,
lengthy
thing
of
text
to
this
is
how
you
do
observability
give
it
more
of
a
usable
thing.
B
What
I
recall
not
at
all-
and
I
I
think
we
could
there's
the
scope
of
it-
is
such
that
we
could
absolutely
use.
You
know
front
end
back
end.
All
the
ends
help
you
know
both
from
the
ux
and
the
design
of
the
actual
user
facing
site,
as
well
as
sort
of
working
on
more
of
the
plumbing
side,
which
is
probably
where
I'll
end
up
pitching
in
more.
B
As
as
ken
said,
you
know,
we
want
this
to
be
all
cloneable
and
sort
of
a
working
example
that
you
can
quickly
and
easily
replicate
yourself
and
then.
Lastly,
the
working
group
really
is
is
a
time-boxed
construct
for
q1
and
q2
of
this
year
and
in
a
manner
similar
to
how
the
get-ups
working
group
out
of
the
technical
advisory
group
or
tag
on
app
deployment
launched
opengitops
as
a
as
something
that
lives
on,
but
under
its
own,
under
its
own
steam.
B
Here
too,
I
think
the
the
goal
is
to
launch
kh
dot,
io
and
and
all
of
the
github
presence
with
the
lincoln's
and
the
tie-ins
and
the
support
of
the
cncf.
So
there's
a
bunch
of
logistical
stuff
that
we'll
be
hitting
the
project
boards
there
like
transferring
the
domains
and
the
github
organizations
and
dealing
with
the
trademarks
and
just
transferring
all
of
this,
so
that
it's
a
cncf
hosted
or
supported
entity.
But
that
has
open
governance
really.
So
so
really,
this
working
group
is
really
about
launching
that
yeah.
E
And,
as
I
mentioned
like
michael
and
I
kind
of
like,
I
guess
you
say
self-nominated,
but
neither
of
us
are
wedded
to
it.
So
if
there
are
others
that
have
a
really
keen
desire
to
leave
this
working
group,
at
least
for
the
first
couple
of
quarters,
there's
always
the
opportunity
to
renew
the
working
group
at
a
later
time
if
it
was
successful
and
there's
more
work
to
be
done.
So
if
there's
others
that
would
like
to
be
chair,
please
shout
and
one
or
both
of
us
are
happy
to
step
aside.
If
so,.
B
Yeah
so
working
groups,
you
know
the
cncf
is
quite
prescriptive
about
them
about
their
structure,
but
ideally
there's
minimally,
two
there's
two
chairs
and
then
the
working
groups
can
define
whatever
other
titles
as
needed
or
just
do
good
stuff.
But
it's
meant
to
be
an
asynchronous.
B
You
know
work
stream.
C
B
C
And
maybe
after
this
I
can
come
back
because
technically
I
would
raise
some
questions
from
practical
promotion
and
so
so
how
we
understand
this
and
what
we
probably
would
like
to
see
from
observability
perspective.
B
Yeah,
this
is
really
just
you
know,
we've
kind
of
done
some
of
the
homework
to
define
what
it
is
we'd
like
to
do,
but
you
know
it's
just
launching
it
really
over
the
next
six
months
is
really
when
you
know
there
will
be
all
that
sort
of
time
and
all
feedback
is
welcome.
If
you
have
specific
comments,
I
add
them.
You
know
again.
This
is
all
very
new.
I
think
this
is
pr
number
two,
oh
okay,
so
of
the
of
the
repo,
and
it's
really
quite
honestly,
just
sort
of.
C
C
Technically
you
limit
observability
and
their
positions,
so
observability
just
provide
information
about
infrastructure
or,
in
some
cases,
kubernetes
lock,
money,
lock,
collection
and
tracing
one
two
three,
but
actually
what
we
just
find
out
from
technical
perspective,
for
people
who
maintain
or
develop
some
stuff
it's
more
than
important,
but
we
have
business
people
who
would
like
to
have
similar
to
to
monitor
to
to
get
data
observability
on
the
level
of
business,
such
as,
for
example,
they
have
the
problem,
problems
have
been
identified,
problems
have
been
triggered
and
they
have
to
see
when
people
acknowledge
this
problem,
they
would
like
to
see
when
problem
has
been
resolved
and
later
they
would
like
to
analyze
this
improvement
or
this
improvement.
B
Yeah,
I
I'd
recommend
you
give
the
document
a
read.
B
Around
around
the
the
language,
I
think
we
have
an
issue
for
it.
B
I'm
trying
to
pull
it
up
now,
if
not
I'll,
create
one,
but
there
is
a
there's,
a
working
group
on
business,
business,
values
or
something
like
that
and
they
have
a
they've
launched
a
glossary,
cncf
philosophy,
what's
sort
of
the
specific
goal
of
providing
terms
and
definitions
for,
for
you
know,
I
think
things
across
all
of
the
scope
of
the
cncf,
but
but
really
targeted
at
business
folks
versus
strictly
technical
or
engineering
folks,
and
so
I
think
that
is
an
activity
where
we
and
everybody
else
could
absolutely
contribute.
B
You
know
observability
related
definitions
and-
and
things
like
that
to
to
address
that.
I
believe
it's
one
of
the
I'll
I'll
put
the
issue
in
the
here.
It
is
number
38.
I'll
put
it
in
chat
as
well
as
in
the
doc.
But
if
you
are
interested
in
that
specific
topic,
there's
an
example
of
where
absolutely
jump
in
okay.
If
you,
if
you
wish.
C
C
B
So
again,
I
would
encourage
you
to
have
have
a
read:
what's
in
scope,
is
the
cncf
suite
of
open
source
durability
tools
and
other
open
source
things,
but
not
really
commercial
offerings,
so
so
the
and
this
for
for
other
folks
that
it
might
be
their
first
time
here
as
well.
The
technical
advisory
group
on
observability
exists
to
to
both
identify.
B
You
know,
opportunities
and
gaps
in
the
ecosystem
generally
of
open
source
tooling,
as
well
as
for
cncf
specific
projects
and
and
technologies,
and
so
it's
there
to
advise
the
greater
community
and
and
be
a
place
where
end
users,
such
as
yourself,
vendors,
as
well
as
project
contributors,
can
all
kind
of
come
together
in
a
community
forum
to
discuss
topics
of
the
day
raise
issues
I
had
hoped
to
have
somebody
presenting
today,
but
they
were
unavailable.
B
So
we'll
have
is
an
ebpf
based
thing,
so
you
know
there
there's
all
that
stuff
is
in
scope
and
feel
free
to
have
a
look
at
the
charter
as
well.
There's
a
there's,
a
long
list
of
stuff,
that's
all
open,
but
one
of
the
things
what
we
don't
do
is
render.
You
know
formal
opinions.
You
know
we're
not
an
arbiter
or
a
decider,
we're
not
gonna,
say
like
these
are
the
things
to
use.
This
is
really
just
more
of
an
open
community
call.
Okay,
you
guys
appreciate.
B
C
A
Yeah,
do
you
know
if
the
ebpf
will
be
available
next
meeting
and
is
that
psyllium
hubble
based
or
what?
What.
B
So
it
was
really
I
had.
I
had
just
read
about
solo
had
just
open
source
bumblebee,
which
is
sort
of
a
hit
to
build
ebpf
things
I
haven't
just
to
be
fully
transparent.
I
had
just
reached
out
fairly
recently
to
those
folks
to
with
an
invite
to
say:
hey,
you
know,
you've
done
a
new
open
source
thing.
B
Perhaps
it's
new
to
me
at
least,
and
and
so
if
there
are
things
like
that,
if,
if
other
folks
know
of
projects
either
again
and
that
are
cncf
related
or
just
open,
source,
psyllium
and
hubble
would
be
another
example.
I
don't
have
any
personal
connections
there
or
professional
connections,
but
if
someone
does
they're
they're
welcome
to
come,
do
a
a
show
and
tell
or
talk
about
where
the
project
is
going
in.
A
The
future
or
or
whatever
so
yeah
we
have.
Please
don't
take
this
as
a
sales
pitch.
A
It's
not
meant
to
be,
but
wipro
had
developed
an
observability
solution
a
few
years
ago
that
we've
consistently
been
building
on
it's
all
open
source
based,
which
is
why
this
is
of
interest
to
me,
and
we
incorporate
you,
know
some
of
the
cncf
tooling
and
that
observability,
but
we're
also
looking
at
psyllium,
hubble
and
leaf
by
microsoft
and
some
of
the
other
groups
that
are
out
there
and
there's
actually
a
different
leaf
group
in
the
open
source.
That's
having
meetings
and
discussing
observability
and
a
number
of
other
topics.
A
But
that's
that's
that's
definitely
of
interest
to
me
to
because
we
saw
bumblebee.
We
were
going
to
look
at
that
a
little
bit
more
as
well,
so
that
could
circle
around
I'd
be
very
interested
to
see
that
in
this
context,.
B
Yeah,
that's
awesome
if
you
want
to
drop
a
link
into
the
into
the
meeting
notes
or
send
them
in
slack
or
even
wherever
to
that
open
source.
B
Sure,
well
again,
you
know
end
user
stories.
If
you
will
or
or
stories
and
or
learnings
you
know
things
like
that
around
using
opens
using
cncf
based
observability
stuff
is
absolutely
up
the
center
line
of
the
kind
of
thing
you
could
just
come
here.
The
general
format
is,
you
know,
between
10
and
15
minutes.
B
You
know
a
couple
slides
if
you
like,
or
a
demo
and
and
some
q,
a
so
feel
free
to
put
yourself
on
the
agenda.
If
you'd
like
to
talk
about
your
experience
with
using
open
source
tooling,
to
solve
your
business
challenges
or
technical
challenges,
or
both.
A
Yeah
and
we'll
I'll
definitely
definitely
be
looking
to
do
that
as
time
passes.
Where
has
a
lot
of
people
in
our
strategy
kind
of
moments
right
now,
so
when
that,
when
that
part's
over
we'll
circle
back
on.
B
And
there's
some
examples
of
this
on
our
youtube
channel
as
well
from
the
past,
and
I
can,
if
you
want
to
reach
out,
I
can
send
you
some
some
direct
links
to
what
sort
of
those
look
like
they're,
quite
informal.
B
Well
again,
we
can
return
some
time
to
folks
if
there
are
no
other
things
to
discuss.
The
agenda
was
a
little
empty.
Today,
unexpectedly,
okay.
D
Quick
question,
so
I
work
mostly
in
the
open
telemetry
project
and
one
of
the
things
that
I'm
trying
to
do
is
connect
end
users
together.
I
know
that,
like
cncf
has
an
end
user
community
at
the
cncf
level.
I
wonder
how
much
the
kind
of
like
observe
k-8s
and
this
demo
stuff
intersects
potentially
with
that,
but
my
focus
is
really
on
open,
telemetry
the
technology
primarily
connecting
end
users
who
choose
that
standard,
but
I
don't
know
if
anyone
had
any
ideas
in
this
group
of
just
like.
D
B
It
does
you
know,
hotel
is
an
incubating
project
right
and-
and
in
fact,
I
think,
in
in
the
dock,
we
have
released,
as
we've
talked
about
that
you
know
using
hotel,
collector
and
other
open,
telemetry,
client,
libraries
and
things
like
that
is,
is
absolutely
the
sort
of
thing
we'd
like
to
do.
B
I
can
dredge
up
a
link,
but
if,
as
as
an
analogy,
if
you,
if
you
look
at
the
open,
get
ups
organization
that
the
get
ops
working
group
launched,
they
have
like
repos
cloned
they're,
like
you
know,
here's
an
example
of
flux,
argo.
You
know
all
the
way
down
all
the
different
ways
that
you
can
build,
build
and
and
release
to
production
and
manage
you
know
a
generic
app
and
or
maybe
I
think,
a
potato
head.
B
It
might
not
be
under
the
exact
open,
get
off
working
group,
but
potato
head,
which
we
have
linked
in
there
is
a
cute
little
app,
but
they
kind
of
it's
not
opinionated,
saying
you
know
here
is
how
to
do
it
with
this
project.
It's
like
here
are
all
the
projects.
B
You
know
that
you
know
that
that
folks
might
be
using
that
seem
to
make
sense
and
anyone
can
add
a
pr,
but
it's
the
same
thing
deployed
a
bunch
of
different
ways
with
working
examples
that
you
can
interact
with,
and
so
I
think
between
that
and
and
a
big
aspect
of
the
observation
to
have
a
curated
compendium
case,
study
compendium,
you
know
of
of
people's
experiences
or
here's
how
we
did
it
or
you
know,
here's
what
we
learned.
B
You
know
with
discussion
boards
and
really
because
this
is
you
know,
going
to
be
under
the
umbrella
of
the
cncf.
Some
of
the
machinery
around
the
cncf
community
sites
can
be
brought
to
bear
here
for
some
of
the
logistical
support
around.
B
You
know
the
live
streams,
and
if
people
want
to
do
things
like
that,
and
then
lastly
I'll
say,
if
you
check
out
our
issues
and
I'll
put
them
in
the
notes
after
sometimes
I
start
to
talk
and
type
at
the
same
time
for
me,
but
in
any
event,
you
know
having
folks
that
want
to
contribute
either
to
the
tag
or
to
to
observe
kate's.
You
know
we
have
a
youtube
channel,
but
we
don't
really
have
folks
right
now
that
are
that
are
managing
it.
B
That's
another
area
where
active
contributions
are
hardly
solicited
and
welcome
to
to
either
do
interviews
or
you
know,
dotan.
I
can
probably
comment
about
just
some
of
the
some
of
the
things
it
takes
to
manage
something
like
that
in
terms
of
programming
and
whatnot.
So
all
of
those
are
opportunities
as
well
to
help
build
community
and
to
connect
end
users
with
the
projects
and
then
the
vendors
that
support
them.
D
Okay,
great
thanks
for
a
couple
of
those
leads
I'll
I'll
check
out
get
ops.
I
did
see
the
potato
head
thing
just
like
super
briefly
in
that
observe
kate's
list.
I'm
I'm
curious
about
that,
because
that
seems
to
be
one
of
the
biggest
challenges
for
end
users
that
I
encounters
are
like.
I
know
there's
just
so
many
choices
out
there
and
then
also
what
what
is
idiomatic.
D
The
language
implementation
of
this
example
versus
the
underlying
technology,
such
as
open,
telemetry
differences
in
stuff,
and
so
I
think,
I'm
very
excited
to
see
some
of
these
more
user-centric
efforts
take
off,
because
I
think
it
will
help
with
adoption
and
usage
overall.
B
I
think,
having
that
that
vector
feedback
and
to
help
you
know
in
a
product
setting
if
we
were
all
like
if
we
were
from
project
team
like
we
would
very
very
much
want
to
say
like
what
is
our
feedback
cycle
so
that
we
can,
you
know,
have
a
fast
feedback
cycle
and
just
build,
build
the
right
thing
or
address
the
right
concerns
and
so
really
having
having
a
way
to
pipe
that
back
in
you
know
in
a
reasonable
way.
That's
not
like
a
blind
survey
or
something
like
that
is
another
place
where
the
go.
A
B
I
would,
I
would
say,
the
the
former
so
most
of
the
projects
in
the
landscape.
You
know
landscape.cnc
after
the
the
big
eye
chart.
Most
of
those
are
themselves
kubernetes,
workloads
right,
and
so
I
think
the
intention
of
of
naming
it
observe
dash.
K8S
was
you
know
both
it
was
available
and
not
claimed,
so
we
nailed
it,
but
I
think
it's
meant
to
be.
B
I
feel
it's
meant
to
be
inclusive
of
all
of
that,
so
you
know
in
got
guides
or
you
know,
and
everything
you've
been
talking
about,
but
are
about
the
observation
of
kubernetes
itself
and
its
workloads,
which
are
kind
of
almost
the
same
thing.
And
you
know
it
are
the
same
thing
and
I
would
say.
A
B
Oh
yeah
and
thank
you
for
the
feedback
too
right.
You
know
we're
just
kind
of
opening
this
up
now
to
to
see
what
folks
think.
B
So
I
guess
I'll
give
another
minute
if
anybody
else
wants
to
want
to
do
stuff,
but
I'm
okay
with
awkward
silence,
but
I'm
sure
we're
all
busy
too.
B
You
know
what
I
just
realized
that
somehow
again,
I
think
there
might
be
an
old
version
of
something,
but
we
meet
on
the
first
and
the
third
tuesday
of
each
month,
and
I
just
realized
that
github
is
out
of
date
too,
but
the
cncf
calendar
is
up
to
date.
So
if
you
get
the
invite
from
the
cncf
calendar,
that
has
it
sounds
good.
Okay,
so
tuesday.