►
From YouTube: Prometheus Community Meeting - 2018-07-16
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Meeting notes - https://docs.google.com/document/d/12QylAyrWgKzfDJ1ApTwNWSUBQjiZEo3kfp5c2wi6JO0
B
A
different
issue
on
an
existing
bug
was
in
github,
so
us
trying
to
keep
track
of
what
bugs
do
or
don't
exist
was
close
to
impossible.
I
think
the
record
was
was
one
issue
which
we
resolved
in
November
before
to
zero.
Even
came
out
that
had
seven
different
bugs
for
$40.
Are
these
seven
different
behaviours
and
when
we've
got
you
know,
15
20
such
things
in
the
system,
it's
impossible
to
figure
out.
B
B
Get
everything
go
and
fix
the
bugs
that
helped
a
bish,
but
it
didn't
get
us
fully
stable
gratis
yet
so
then,
for
two
Tralee
basically
discuss
this
amongst,
read
his
team
and
said:
let's,
let's
wait
two
weeks
and
actually
fix
these
things
so
in
the
end
was
about
10
ish,
bugs
that
were
identified
and
we
fixed
like
eight
of
them
and
a
lot
of
these.
These
vary
from
hate
us,
basically,
data
corruption
and
now
things
like
shut
down
being
unclean,
which
isn't
a
major
problem
in
and
of
itself.
B
However,
it
causes
loss
of
confusion
among
users
because
they
see
odors
this
error.
Therefore,
they
found
a
bug
on
the
rock
on
an
issue
for
something
else
and
causes
confusion,
and
in
practice
you
know
a
group
like
us
can
handle
maybe
two
to
three
taught
simultaneous
bugs
that
we
can
keep
in
our
heads.
Oh
it's
that
each
to
the
reporting,
would
you
mind
going
over
here
and
that's
fine,
but
we're
out
puts
1015
issues
in
the
codebase
that
just
breaks
down
it
just
takes
too
much
time.
B
So
we're
now
in
the
place
where
it
looks
like
tree
was
good.
We
had
one
false
alarm
this
morning
and
in
fact
the
bug
was
to
tree
one
already
fixed,
so
all
going
well
and
good,
then
probably
Wednesday,
we'll
start
taking
in
full
requests
again.
The
reason
why
it's
Wednesday,
rather
than
Thursday,
is
Thursday
I'll,
be
extremely
busy
and
true
to
Monday.
So
at
least
Wednesday
I
can
take
care
of
all
the
pull
requests.
B
I
have
to
merge
it
unless
a
bug
comes
up,
in
which
case
we'll
fix
it
and
then
the
hope
would
be
Dan.
Sometime
next
week
we
can
get
to
four
hours,
because
you
know
it's
basically
been
a
month
and
it's
not
nice
to
have
users
to
waste
overly
long
to
get
their
changes
in
so
hopefully
now
then
treats
you
will
be
a
good
release
from
ETS
that
people
can
use
in
the
future.
A
C
C
As
long
as
they're
enough,
you
few
is
basically
as
long
as
they're
enough
use
cases,
but
with
this
decision,
I
can
completely
say
that
I'm
really
on
board,
especially
after
trying
to
troubleshoot
few
of
dolls
on
different
service
discovery
providers,
I
mean.
Even
now
we
have
a
pending
bug
with
the
kubernetes
provider.
I
have
added
a
link
in
the
in
the
doc,
which
basically
happens
only
when
we
have
a
high
load
of
over
500
targets
and
I
try
to
replicate
it,
but
there
is
no
way
I
could
do
this.
C
My
on
my
own
laptop,
so
it
has
been
pending
for
quite
a
while.
Now
there
is
a
I
posted
another
link
which
links
to
a
possible
solution
that
is
upstream
in
in
kubernetes,
but
I'm
not
entirely
sure
what
will
happening
there
and
by
the
way
we
are
very
close
to
getting
some
free
credit
with
Google.
So
soon
we
should
be
able
to
try
and
replicate
this
one
on
the
logs
that
we
need.
C
Let
me
just
have
a
look
what
else,
but
anyway,
my
point
was
that,
as
it
may
sound,
that
is
it's
good
idea
to
have
these
built
in
it's
not
funny
at
all
to
troubleshoot
and
know
all
the
clients
for
all
of
these
different
providers.
And
basically,
as
Brian
mentioned,
we
a
small
group
of
people,
so
we
can't
possibly
handle
more
than
what
we
already
have
and
instead
of
what
we
decided
that,
instead
of
adding
in
maintaining
news,
discovered
providers
will
think
in
a
direction
to
enable
users
to
add
their
own
mechanisms
without
breaking
Prometheus.
C
And
the
solution
we
have
so
far
and
I.
Also
added
link
to
this
is
that
we
added
an
example
to
the
official
example
documents
in
the
official
Prometheus
repository.
So
the
example
shows
in
called
how
to
implement
a
sidecar
that
you
can
use
to
implement
your
own
way
of
getting
tired,
just
spitting
out
like
JSON
file.
C
There
was
another
discussion
that
I
by
personally
started
because
I'm
still
not
100%
convinced
that
file
service
discovery
is
the
way
to
go
and
I
started
some
discussion
in
the
developers
mailing
list.
But,
to
my
surprise
it
seems
that
I
mean
so
far.
We
haven't
had
too
many
complaints
to
to
file
service
discovery
and
it
seems
that
it
solves,
if
not
all
most
of
the
the
current
use
cases
so
I
think
so
far.
C
A
There's
a
question
about
how
to
get
access
to
the
document.
Yeah
I
should
have
mentioned
this
in
the
meeting.
Invite
you
just
need
to
be
part
of
the
Prometheus
developer
mailing
list,
and
then
you
will
get
access
to
it,
but
also
the
first
link
that
I
put
into
the
invite
was
incorrect
and
I
replied
with
an
which
everyone
has
at
least
read
access
to.
A
C
There
is
a
lot:
what
will
the
existing
service
discovery
migrate
to
the
new
methods?
No
they're,
not
fast
for
this
right
now.
So,
basically,
we
will
wait
for
feedback,
but
we
haven't
even
discussed
migrating
anything
yet
I
mean
it's
too
early.
We
haven't
yet
even
I,
don't
think
even
we
have
any
users
using
the
new
way,
so
we
don't
have
any
feedback
whatsoever.
C
B
To
be
clear,
this
isn't
a
new
method.
It's
just
an
easier
way
to
write
a
file
service
discovery,
because
the
extra
code
is
basically
just
a
framework
that
happens
to
use
the
exact
same
API.
So
we
use
internally
inside
paradius
because,
like
it's
pretty
easy
to
response
or
discovery
what's
interesting
about
using
the
same
API
is,
is
it
means
that
if
someone
writes
against
these
api's,
we
can
then
move
service
discoveries
in
and
outside
of
for
ages?
So
as
it
stands,
there
are
no
plans
to
remove
any
service
discovery
mechanisms
from
for
me
jeez.
B
It
might
happen
in
future
but
run
around
the
table,
and
it's
also
possible
when
we're
in
a
better
state
in
the
future
future
service
discovery
to
be
implemented.
Third-Party
virus
mechanism
can
we
move
into
the
Regis,
but
neither
of
those
seemed
like
it
happened
anytime
soon,
but
it
means
we
have
the
capability
in
the
future.
Yeah.
C
B
Under
the
operating
section,
there's
an
integrations
page
and
that's
where
it
lists
all
the
integrations
that
aren't
client
libraries
or
exporters,
so
the
finest
teas
from
there
all
the
inner
grandma
hook
receivers.
There's
an
other
section
for
weird
stuff
like
prompt
rocks,
so
I
push
box
and
you
know
so.
You
can
just
send
a
peon
which
will
probably
use
the
same
rules
to
try
courage,
people
to
work
together
on
one.
Yes,.
C
C
B
There
are
some
users
who
have
very
odd
setups,
like
in
kubernetes
I've
got
a
customer,
for
example,
who
bans
any
use
of
shared
volumes
on
kubernetes,
which
is
not
a
sane
set
up,
and
hopefully
it
will
change
your
mind
at
some
point.
But
there's
always
gonna
be
weird
setups
and
the
more
common
case,
because
I
think
that
was
only
one
user.
These
users,
just
don't
want
to
run
a
sidecar.
D
Anyway,
so
prom
cone
is
going
well,
we
released
the
schedule.
I
put
the
link
in
the
meeting
notes,
so
you
can
just
click
and
you
can
see
the
schedule.
We
have
way
too
little
space.
We
have
a
total
of
220
and
seats
and
we
have
200
plus
people
on
the
waiting
list,
which
is
kind
of
bad.
So
next
time
definitely
380
400
people.
D
What
will
be
nice
this
time?
We
will
have
a
lot
larger
reception
area
if
you
have
into
any
of
the
two
prom
Khan's
earlier.
It
was
always
really
really
tight
in
the
reception
area
and
food
was
always
really
really
tight.
This
should
hopefully
be
a
lot
better.
I
didn't
get
final
confirmation
yet,
but
it's
looking
good
this
year
aren't
we
were
able
to
spend
around
15
K
on
diversity,
which
is
awesome,
yeah,
and
we
will
probably
spend
even
more
diversity
next
time.
D
So
that's
also
very
good
and
roughly
10%
of
our
attendees
are
female
or
identifying
as
female
and
not
all
of
those
are
coming
near
diversity
sponsorship.
Several
of
those
are
coming
by
themselves.
Bad
themselves
is
wrong,
but
you
know
what
I
mean
we
didn't
do
any
deeper
stats
as
to
other
other
types
of
of
minorities,
but
that's
there
was
the
easiest
quickest
one
and
else
yeah
everything
is
very
was
looking
good
and
it
will
probably
be
oh
by
the
way
we
will
at
least
try
to
have
a
live
stream.
I
can't
promise
anything
course.
D
E
A
F
A
Okay,
then,
our
next
topic
is
rather
than
Prometheus,
talks
and
meetups.
This
is
kind
of
a
section
where,
just
for
future
meetings,
people
can
insert
talks
that
they
are
giving
meetups,
that
they're
hosting
their
local
meetups
or
just
link
to
slides
or
anything
like
that.
Just
so,
we
can
give
you
a
spotlight
for
any
work
that
you're
doing
Prometheus
related
and
just
one
that
we
were
aware
of
is
happening
at
Aswan.
I,
believe
that
is
this
specific
talk
is
happening
tomorrow.
If
anyone
is
attending
ask
on
Wednesday.
D
A
E
D
E
A
A
A
Okay,
if
there
is
no
one,
then
I
guess
we
can
move
on.
We
can
keep
this
kind
of
slot
open
for
the
next
meetings,
and
people
can
insert
questions
maybe
ahead
of
time,
and
then
we
have
basically
already
become
come
to
our
last
point
of
the
agenda,
which
is
since
we've
been
like.
This
is
the
very
first
time
that
we've
done
this
kind
of
a
meeting.
It
would
be
great
if
people
can
get
their
input
even
before
the
meeting
started.
A
I
already
added
two
two
points
which
is
get
the
link
to
the
document
right
on
the
first
time,
I
did
get
a
lot
of
requests
to
share
permissions
on
the
wrong
document,
which
actually
didn't
exist
anymore,
because
I
moved
it
to
the
to
the
public
space.
So
yeah
I'll
try
to
make
that
happen
next
time,
and
we
were
discussing
earlier
on
IRC
that
it
would
have
been
helpful
if
there
was
a
global
invite
that
is
sent
to
everyone
instead
of
everyone
having
to
go
to
the
main
list
and
accepting
it.
A
We
did
this
consciously
this
time,
but
we
also
said
that
or
a
one-off
meeting,
where
we
just
want
to
try
this
kind
of
format.
We
don't
necessarily
want
to
invite
a
thousand
people
that
are
on
the
mailing
list
at
once,
so
yeah
but
I
think
unless
anyone
thinks
it's
not
a
good
idea,
I
think
for
the
next
time
we
we
can
do
that
I
see
there
was
a
new.
A
F
C
C
Okay,
okay,
well
in
relation
by
the
way
I
just
had
something
else
in
mind
in
relation
to
the
to
the
book
fees,
moratorium,
I'm,
not
sure
if
everyone
here
is
aware,
but
we're
also
getting
some
I
already
mentioned
it,
but
we're
getting
some
free
credits
from
Google
and
myself
and
somebody
else
who
were
working
on
automated
bank
benchmarking,
which
should
help
make
it
making
committees
even
more
stable.
But
it's
still
working
progress.
It's
just
I
wanted
to
mention,
because
we're
working
on
other
things
as
well.
C
And
basically,
what
the
problem
bench
will,
the
automating
benchmarking
will
do
is
just
we'll
be
able
to
run
automated
testings
for
like
sensitive
pr's
like
significant
cold
changes
or
before
every
release,
which
should
help
catch
bugs
even
before
a
release
or
before
merging
appears.
That
is
breaking
Prometheus,
which
the
current
unit
testing
doesn't
really
cover,
because
it
requires
a
little
bit
of
a
high
load
or
basically
deploying
Prometheus
from
like
an
end-to-end
testing
in
an
actual
working
environment.