►
From YouTube: SIG Instrumentation Usage Metrics Collector 20230125
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
Hello
and
welcome
to
today's
special
edition
of
Sig
instrumentation,
we
are
having
a
kickoff
meeting
for
our
new
sub-project
usage.
Metrics
collector
and
I
have
the
pleasure
of
Hosting
today's
meeting,
but
I
would
love
to
go
around
and
do
intros.
We
have
a
lot
of
new
faces
lots
of
people
that
I
don't
normally
see
it's
the
instrumentation
meetings,
which
is
amazing
if
you
haven't
already
I,
dropped
a
copy
of
the
link
to
the
meeting
notes
in
the
chat.
Please
feel
free
to
put
your
name
on
there.
A
So
my
name's
Elena
I'm,
currently
one
of
the
co-chairs
of
Sig
instrumentation
I
work
for
apple
and
I'm
gonna
go
through
these
three
things
in
the
intro
section,
so
I've,
given
my
name
a
little
bit
about
my
background
with
kubernetes
I'm,
chair
of,
say,
instrumentation.
What
do
I
want
to
get
out
of
the
sub
project?
I
am
one
of
the
folks
who
has
been
working
on
donating
this
code
to
kubernetes
and
making
it
awesome
and
bringing
in
new
collaborators.
B
C
Hello,
hopefully
you
can
hear
me
I'm
Louis,
actually,
I've
been
a
traveler
for
a
few
years.
I've
mostly
worked
on
building
super
kubernetes
clusters
and
the
tooling
to
build
those
at
scale
I'm
now
part
of
a
team
that
is
mostly
concerned
with
efficiency
and
auto
scaling.
So
you
can
see
the
interest
and
having
good
metrics
I
will
pass
the
Baton
to
Katrina.
D
E
I
think
what
at
this
point,
what
I'm
very
interested
in
is
you
know,
as
we
share
this
technology
with
the
community
I'm
very
curious
to
know
like
areas
of
resonance
with
problems
that
you
may
already
be
trying
to
solve
areas
of
like
dissonance
right
like
if
there's
something
about
the
pro
the
approach
that
we're
taking
in
this
collector.
That
is
incompatible
with
problems
that
you're
trying
to
solve.
That
will
also
be
very
interesting
to
know,
and
you
know
I
think
those
are
are
the
main
two
things
but
comedy
comes
in
threes.
So
if.
C
E
F
Hi
I'm
ty
from
Shopify
I'm,
also
on
Louie's
team.
We
spoke
a
bit
part
part
of
the
reason
we're
interested
in
this
is
driving
good
recommendations
for
resource
requests.
We
spoke
a
bit
about
this
at
a
cncf,
I,
think
Sig,
ux
anyways,
so
just
interested
in
in
seeing
kind
of
high
resolution,
metrics
options
and
sorry
I'm,
gonna,
say
Richard.
Next,
sorry,
if
I'm
not
getting
that
correct.
Oh.
G
A
Thank
you
very
much,
Rita
and
I'd
like
to
add
to
that
briefly
before
we
pass
on
to
another
person.
If
you
are
looking
for
org
membership,
and
you
want
to
contribute
on
an
ongoing
basis
to
the
sub
project,
but
you're
not
really
sure
about
that.
Zig
instrumentation
is
a
great
place
to
get
started
with
kubernetes
and
we
are
very
happy
to
sponsor
you
if
you're
active
in
any
of
our
sub
projects
for
kubernetes,
sigs
or
kubernetes
membership,
as
makes
sense.
So
please
let
like
any
of
the
leads
know.
A
H
Wrong
hi
I'm
John,
currently
I'm
working
for
rabbit
in
on
the
monitoring
team
and
over
the
last
year,
I've
been
trying
to
contribute
to
Prometheus
operator
and
also
discovering
the
space
and
seeing
what
other
projects
would
interest
me
and
what
do
I
want
to
get
out
of
this
sub
project
I'm
guessing
it's
a
bit
like
like
David
I,
came
here
to
learn
about
the
project
and
how
we
could
use
it
and
I'm
passing
the
Hot
Potato
to
Kevin.
If
I'm
not
mistake,.
I
C
J
Right,
let's
see
I
started
working
on
kubernetes
about
two
years
ago
at
Apple
before
that,
I
was
actually
doing
something
really
different.
I
was
doing
computational,
mechanics
and
machine
learning.
What
that's
the
story
for
another
day,
but
yeah
I've,
Been,
Working,
On,
The
Collector
for
the
past
year
and
changed
and
I'm
excited
to
share
the
cool
stuff
we've
been
doing
here
at
Apple
and
Hot
Potato
too
hot.
K
Great
okay,
yeah
hi,
I'm
Han
I'm,
a
Staff
software
engineer
at
Google,
I'm
I,
I
coach,
our
seek
instrumentation
with
Elena
we've
been
doing
that
for
a
while
I've
been
working
on
kubernetes
for
the
past,
like
four
and
a
half
years,
API
machinery
and
instrumentation
mostly
I,
also
specialize
in
storage
layer
stuff
but
yeah
I'm.
Looking
forward
to
this
usage,
metrics
collector
and
seeing
what
it's
all
about.
A
A
Okay,
then,
let's
take
a
look
at
can
I
make
this
go
away.
Please
no
I
just
can't
see
my
URL
bar,
because
Zoom
is
covering
it
and
I,
don't
know
how
to
make
it
like
move.
Maybe
I'll
try
to
move
it
to
the
bottom
of
my
screen,
yeah,
okay
or
in
the
smack
dab
middle
okay.
So
let's
take
a
look
at
our
repo
I
want
to
do
a
quick
sort
of
just
like
Code,
walkthrough
overview.
I'm.
Sure
folks
will
have
some
questions.
A
A
A
K
E
A
Yeah
I
thought
I
deflaked
it
darn,
okay,
yeah,
there's
been
some
issues
with
these
tests.
I
ran
into
like
I,
saw
that
they
were
very
sneakily
getting
killed,
so
I
increased
the
the
the
memory
limits
for
them,
but
okay,
so
there
are
probably
people
who
have
never
seen
test
grid
before
as
well.
So
we
have
this
repo
where
our
code
lives
and
then
in
order
to
set
up
testing
for
it,
we
have
a
repo
and
kubernetes
called
test.
Infra
and
I.
A
So
as
long
as
you
have
the
test
grid
link,
you
can
copy
that
and
you
can
go
to.
Okay.
Here
are
the
definition
of
the
test.
So
I
was
talking
about
adding
resources
like
to
the
requests
and
limits.
Well
here
they
are
they're
defined
right
here,
and
so
you
can
see
exactly
like
what
image
is
this
running
with
what
command
does
it
run?
In
our
case,
it's
running
make
test
which
then
you
know
like
okay.
Well,
let's
look
at
the
make
file
of
this
repo.
A
It
is
a
little
bit
messy,
but
what
is
it
doing?
I
set
it
up
recently
so
that
it
goes
and
goes
and
runs
our
tests
and
outputs
it
in
junit
format
and
that's
how
they
show
up
in
test
grid
so
hooray.
So
we
have
a
make
file
and
we
have
two
Targets
for
our
CI.
We
have
verify
and
test
if
you're
interested
in
more
targets
and
you're
interested
in
CI
things.
Please
talk
to
me
in
terms
of
the
code
itself.
A
A
So
this
launches
some
basic
Prometheus
metrics.
If
you
want
to
to
scrape
directly
off
of
a
given
node
or
something
like
that,
this
was
this
code
was
initially
added,
mostly
for
debugging,
so
you
can
launch
a
containerdy
client
and
it
will
scrape
some
metrics
directly
from
c
groups
off
of
a
node,
so
it
is
we're
using
Cobra,
for
it
is
configured
via
command
line
this
one.
A
We
also
have
any
questions
about
that
before
I
move
on.
So
very
briefly,
this
is
sort
of
a
debugging
app
that
we
used
question
y.
So
we
want
to
get
high
fidelity
metrics
for
kubernetes.
We
want
to
be
able
to
present
those
in
a
relatively
consumable
format-
that's
not
too
high
cardinality.
So
how
might
we
do
that?
Well
in
order
to
get
stats
on
various
processes
running
on
a
Linux
system,
we
need
to
look
at
the
containers.
The
containers
are
running
c
groups.
A
The
c
groups
come
with
all
sorts
of
fun
stats
with
them,
so
these
are
collected
in
other
parts
of
the
project
via
C
advisor,
for
example,
but
C
advisor
looks
a
lot
of
things.
We
don't
really
need
to
look
at
all
of
those
things
if
we
just
want
to
focus
on,
for
example,
CPU
utilization
and
memory
utilization.
So
there
are
inevitably
something
somewhere
is
going
to
have
to
go
and
look
at
c
groups.
A
But
if,
if
a
thing
is
a
container,
but
what
if
a
thing
is
not
a
container,
then
in
that
case
it
might
be
more
helpful
to
talk
directly
to
the
container
runtime,
because
in
the
container
case
it
will
go
and
maybe
look
at
the
C
group.
But
if
it's
something
else
like
a
micro
VM,
it
should
have
some
way
of
getting
the
stats
for
the
utilization
for
that
runtime.
A
A
A
E
E
E
H
G
E
E
Is
the
go
type
for
the
main
configuration
API
for
The
Collector
and,
let's
see,
let's
take
a
look
at
this,
so
we
have
C
group
metrics,
which
are
what
they
sound
like.
They
are
metrics
derived
from
information
that
we
get
from
scraping
the
c
groups.
There
are
so-called
cluster
scope,
metrics
one
of
the
least
favorite
things
for
me
in
software
engineering
is
naming
things
and
I'm
unhappy
with
the
name
clusterscope
metrics.
What
does
it.
G
E
It
means
it
is
about
taking
information
which
is
stored
on
some
cluster
scoped
resource
in
a
kubernetes
cluster
and
emitting
metrics
from
it,
and
we
can
talk,
maybe
in
a
future
meeting
about
exactly
what's
happening
there.
Next
we've
got
extensions,
so
these
are.
Are
these
are
user
defined
user
in
the
sense
of
the
person
running
this
code
in
cooperation
with
their
users
that
are
running
workloads
can
Define
certain
labels
on
the
workloads
that
are
then
transformed
into
metrics
labels
and
about
I'm
doing
my
best
here
if
I
say
anything
wrong,
just
holler.
E
E
So
in
the
version
of
the
component
that
we
had
to
collect
metrics
before
we
built
this,
we
did
not
have
a
config
driven
scheme
for
defining
the
metrics
and
aggregating
them.
So
we
were
doing
things
like
we'd
have
to
make
code
changes.
If
we
wanted
to.
You
know,
compute
a
new
layer
of
aggregation,
and
one
of
the
things
that
we
have
found
to
be
very
convenient
about
this
new
scheme
is
that
things
that
we
used
to
be
doing
in
code
that
we'd
have
bugs
in
code
are
now.
E
You
know
crushed
in
the
mind
Vice
of
a
few
people
that
built
this
collector
and
we
can
write
some
rules
which
are
much
easier
to
understand
than
the
code
and
actually
I
think
you
know
given,
given
the
amount
of
time
that
we
have
I
think
it
might
be
good
ehash.
If
we
take
a
look
at
one
of
the
integration
tests,
because
I
think
that'll
bring
that
together
for
folks
and
I,
don't
really
think
that
we
have
a
meaningful
amount
of
time
to
really
start
getting
into
the
code
of
The
Collector
itself.
A
We
actually
only
had
three
minutes
so
I'm
wondering
if
maybe
we
want
to
try
to
plan.
You
know
I
think
we
should
meet
again.
You
know,
half
an
hour
is
probably
not
long
enough
by
any
means
and
I'm
wondering
you
know
what
times
might
work
for
folks
and
then,
if
anybody
has
any
brief
questions,
because
we
haven't
really
had
a
chance
to
go
into
that
if
you're,
okay,
with
that
Paul.
A
Awesome
does
this
time
generally
work
for
folks,
and
when
would
we
want
to
meet
again?
Presumably
people
might
want
a
chance
to
go.
Look
through
the
code.
Ask
questions
that
kind
of
thing.
I
tried
to
pick
a
time
that
would
generally
be
workable
for
folks
in,
like
west
coast,
East,
Coast,
Europe
I
know
we
can't
go
much
later
than
this
for
folks
in
Europe.
So.
A
J
Okay,
yeah,
we
can
try
to
do
a.
This
was
a
really
good
overview
by
the
way
for
ihas
and
Paul.
You
can
do
a
deeper
dive,
the
next
time
into
like
how
the
collector
works,
because
it's
a
manager-
and
it's
also
a
custom,
metrics
exporter.
We
can
go
into
those
details
and
also
about
the
aggregation
Logic
for
that
and
how
the
node
samples
also
push
to
The
Collector
and
how
the
aggregation
is
actually
done
in
the
background.
So
we
can
go
over
the
details.
I
A
A
A
Yeah
and
feel
free
to
yeah
use
the
Sig
instrumentation
slack
room
to
ask
questions
feel
free
to
reach
out
to
any
of
us.
I
think
we're
all
on
kubernetes
slack,
although
you
may
not,
our
usernames
may
not
be
here,
but
I'm
e
hashman.
You
can
definitely
reach
out
to
me
or
post
in
the
channel
for
folks
who
are
like
what
channel
pound
Sig
instrumentation
on
kubernetes
slack
and
the
link
is
actually
at
the
top
of
our
dock
here
somewhere
I
think
yeah.