►
From YouTube: CloudNativeTV /lgtm - Prometheus
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
A
Now
joining
me
today
is
julius,
hey
julius.
How
are
you
doing
hi
there
good?
How
are
you
doing
I'm
doing
very
well?
Thank
you.
I'm
very
excited
to
the
first
ever
lgtm.
I
know
it's
awesome.
Isn't
it
can
you
just
do
as
a
favor
and
for
anyone
that
is
not
familiar
with
you?
Introduce
yourself
tell
us
what
you're
working
on
and
then
we'll
kind
of
talk
about
prometheus.
B
Yeah
sure
so
I
co-founded
prometheus
back
in
2012
and
have
been
with
the
project
in
one
form
or
another
since
then
so,
coming
up
to
the
10-year
mark,
soon,
yeah.
So
right
now
or
since
you
know,
I
I've
been
freelancing
around
it
for
the
last
couple
of
years
and
since
beginning
of
last
year,
I've
continued
that
as
a
one-person
company
called
prom
labs,
so
helping
people
use
prometheus,
get
the
most
out
of
it.
B
Trainings
consulting
and
also
building
a
couple
of
commercial
offerings
around
it,
but
prom
labs
is
completely
separate
from
the
prometheus
project.
Just
want
to
make
that
clear.
The
prometheus
project
belongs
to
the
cloud
native
computing
foundation
and
has
an
open
governance
with
you
know,
people
from
many
companies
being
on
that
voting
team.
B
Sure
so
prometheus
is
a
time
series
based
monitoring
system
that
is
especially
well
suited
for
monitoring
cloud
native
workloads,
but
also
works
for
other
types
of
workloads.
Basically,
you
know
you
run
it
as
a
server.
You
configure
it
to
pull
metrics
from
different
sources
that
you
care
about.
Those
could
be
services
could
be
devices
you
know
and
expose
metrics
to
some
intermediary
agent
and
then
stores
all
those
numeric
metrics
as
time
series,
and
then
it
gives
you
a
query.
B
Language
called
prom
ql
that
you
can
use
for
alerting,
dashboarding
ad
hoc
diagnostics,
basically
to
dig
around
in
your
system
state
and
figure
out.
What's
wrong
and
also
you
know,
potentially
wake
up
people
at
night.
If
something
is
broken,.
B
A
Yeah
and
I
think,
there's
probably
not
anyone
in
the
audience
or
even
just
in
the
world-
that's
running
kubernetes
that
probably
doesn't
have
a
prometheus
running
in
there
somewhere.
I
think
we're
almost
out
of
state
of
ubiquity
there
and
I'm
very
excited
for
this
little
tour
of
the
the
code
and
contribution
pipeline
today
so
julius.
If
you
could
please
just
kind
of
get
your
screen
set
up
and
I'll
cover
a
little
bit
more
housekeeping
before
we
move
on
sure.
If
you
have
any
questions
audience,
you
can
drop
them
into
the
twitch
chat.
A
We
do
have
an
eye
on
it.
We
will
do
our
best
to
try
and
answer
the
questions
as
we
go,
so
anything
on
prometheus
and
contributing
to
marine
phase
would
be
ideal
and,
of
course,
if
you're
not
following
the
cncf
twitch,
yet
now's
the
time
click
that
button
follow.
We
have
so
much
more.
Many
awesome
shows
coming
up
soon,
all
right
julius.
Are
you
ready?
A
B
I'll
zoom
a
bit
yeah,
that's
the
problem
when
sharing
the
entire
screen.
That
was
kind
of
the
easiest
for
me
here
with
multiple
windows
in
the
end,
and
so
on
that
I
want
to
show.
Hopefully
this
will
be
somewhat
in
the
readable.
B
Okay,
always
a
trade-off.
Okay,
yeah
just
wanted
to
kind
of
start
out
on
the
project.
Homepage
prometheus.io,
so
prometheus
is
a
you
know
quite
large
project.
By
now
it
consists
of
multiple
components.
It
has
you
know
in
open
governance.
The
community
page
here
explains
kind
of
how
you
know
different
avenues
of
how
you
would
engage
with
the
community
on
different.
You
know
chat
channels,
there's
an
official
inofficial
community
maintained
slack
channel
as
well.
B
This
you
know
email
lists
and
we
have
both
of
that
for
kind
of
the
user
side
with
which
is
this
whole
thing
and
the
contributor
side
right,
which
is
in
the
contributing
section
just
so
that
kind
of
the
usage
issues
get
a
bit
separated
from
development
issues.
B
We
also
host
openly
and
recorded
developer
summits
once
in
a
while,
where
we
decide
how
to
steer
the
project,
and
you
know
what
things
to
do
next,
you
have
a
code
of
conduct
as
well,
which
is
the
same
as
the
cncf
code
of
conduct
legal
umbrella.
As
I
already
mentioned,
part
of
the
cloud
native
computing
foundation-
and
you
know
how
we
actually
make
decisions
in
prometheus-
is
oh
yeah.
B
At
the
very
top
is
kind
of
explained
in
our
governance
document-
and
you
can
you
can
see
you
know
the
current
team
members
here,
so
you
know
they
do
come
from
different
companies.
It's
it's.
The
only
special
status
that
I
have
you
know
remaining.
Is
that
I'm
a
co-founder,
but
I
don't
control
anything
besides
having
a
vote
on
that
team,
so
amazing
team
doing
great
work
on
things.
B
B
Oh
yeah,
thank
you.
Oh
this
is
a
yeah.
This
is
a
precise
thing
that
I
have
to
zoom
right.
So
you
know
prometheus
is
a
larger
ecosystem
with
a
bunch
of
integrations
and,
for
example,
the
prometheus
server
and
the
alert
manager
are
different
components
that
would
live
in
different
repositories.
B
But
then
you
also
have
all
these
eight
agents
that
can
expose
metrics
four
different
types
of
systems,
which
we
call
exporters
and
they're
all
you
know
we
have
a
couple
of
official
ones
that
have
their
repos
here
we
have
instrumentation
client
libraries
like
client,
java,
client,
golang
and
so
on,
but
I
think
you
know
what
we
want
to
focus
on
today
would
be
the
prometheus
prometheus
repository
which
that
that
houses
all
of
the
main
prometheus
server
code.
B
B
So
this
this
houses
all
the
main
prometheus
server
code,
that
you
know
the
server
that
actually
collects
your
metrics
runs
from
ql
and
does
all
the
main
magic
that
you
know
prometheus
likes
to
do
any
questions
so
far
or
I
will
just
go.
C
D
D
A
B
I
mean
we
do
have
other
repositories
for
the
different
other
components
for
the
other
binaries.
So
mainly
this
has
only
the
primitive
server
binary.
There
is
one
exception
to
this,
which
is
it
has
two
binaries
in
the
cmd
directory
here
one
is
the
prometa
server
and
the
other
one
is
little
cli
tool
called
prompt
tool
which
helps
you
to
do
things
like
validate
configuration
files
to,
and
things
like
that.
You
know
some
interactive
things,
but
also
things
you
can
use
during
a
ci
check
before
you
apply
a
promises.
B
A
B
Yeah,
I
can
actually
show
you
oh
yeah
here
it
is.
I
wrote
a
document
back
in,
I
think
it
was
like
2019
or
so
by
now,
it's
in
prometheus
documentation,
internal
architecture.md,
which
I
wrote
with
the
aim
for
new
contributors
to
find
to
understand
the
actual
structure,
the
layout
of
this
repository.
B
So
all
these
boxes
you
see
in
here
they
basically
represent
what's
happening
inside
the
prometa
server
and
a
lot
of
these
boxes
also
kind
of
mirror
the
directories
we
have
in
the
code
base
in
the
github
repo
it's
slightly
out
of
date.
Now,
since
it's
a
couple
of
years
old,
but
most
of
the
structure
is
still
the
same.
B
So
you
know
a
couple
of
storage
bits
have
changed
and
and
so
on,
but
roughly
how
the
different
pieces
fit
together
is
still
very
similar.
I
then
you
know
document
all
those
different
pieces.
You
would
see
in
the
diagram
above
with
links
to
the
code,
so
it
starts
with
the
main
function,
which
is
really
the
central
input
entry
point
where
the
server
starts
up
loads,
its
configuration
file
looks
at
its
command
line.
Flags
constructs
all
those
other
boxes.
B
D
B
And
then
you
know
it
has
all
these
links
to
the
actual
code
where,
for
example,
here
is
hash
by
its
level
set
and
it's
final
script
url
and
it
takes
you
there
and
it
shows
you
where
that
is
happening
now.
You
know
not
all
of
these
links
will
be
fully
up
to
date
anymore,
but
they
should
give
you
give
you
the
idea.
I
I
should
really
find
some
time
to
update
this
document.
Sometime
would
be
really
cool.
B
I
mean,
basically,
you
have
to
go
through
the
entire
code
base
to
read
it
just
to
kind
of,
or
at
least
yeah
repoint
like
see
if
things
still
fit
together
in
the
same
way
and
then
link
to
the
most
recent
code
version
with
an
absolute
link.
You
know
all
these
links
here.
They
do
include
the
prometer's
version
and
not
the
latest
main
head
yeah
yeah.
So
this
is
a
good
starting
point.
B
I
think,
for
people
who
want
to
get
an
idea
of
how
the
code
in
this
repository
is
structured
other
than
that,
like,
let's
say
you
have
a
rough
idea
of
what
all
this
looks
like
and
where
you
want
to
make
a
change.
B
There
is
a
contributing
contributing.md
in
all
of
our
repositories,
so
also
in
this
one,
but
also
in
the
other
ones,
and
that
goes
a
bit
further
into
you
know
the
considerations
you
would
want
to
make
before
contribution
and
during
a
contribution
and
how
how
you
would
actually
build
the
contribution
so
yeah.
This
is
just
a
link
to
further
down
to
here.
B
So,
basically,
you
know
the
the
general
rule,
I
guess
with
as
with
most
open
source
projects,
if
you
just
want
to
fix
a
typo
or
something
small,
very
uncontroversial
just
send
a
pull
request.
It's
not
a
problem,
but
if
you
know
once
you
want
to
do
something
where
some
discussion
is
warranted
first,
and
it's
not
clear
that
this
is
something
that
everyone
is
okay
with
or
agrees
on,
that
this
is
a
right
design
decision
or
so
then
it
makes
more
sense
to
have
a
small
discussion
on
the
mailing
list.
B
First,
so
you
know
just
kind
of
use
your
best
judgment
there.
If
it's
got
a
couple
of
lines
of
code
change,
just
send
a
pull
request.
Maybe
you
know,
but
you
don't
want
to.
You
know,
spend
a
day
working
on
a
huge
change
only
for
then
someone
to
say
like
this
really
doesn't
fit
in
with
the
vision
or
or
so
on,
right,
yeah,.
A
I
think
that's
so
important.
It
can
be
easy
to
be
really
focused
on
your
own
individual
use
case
in
context,
and
something
seems
like
it's
really
obvious.
No,
of
course
I
should
do
this,
but
you
got
to
think
wider
and
broader
I
mean
prometheus.
Is
a
project
being
used
by
tens
of
thousands,
if
not
hundreds
of
thousands
of
teams
and
developers.
A
B
They
they
have
to
be
considered
the
kind
of
need
to
fit
in
they
kind
of
you
know
they
shouldn't
have
weird
interactions
with
other
features
that
you,
as
the
one
user
needing
that
aren't
in
that
moment,
aware
exactly.
B
At
the
same
time,
we
have
become
also
consciously
decided
to
reconsider
a
lot
of
times
in
the
past,
where
we
have
said
no
to
you,
know,
re-evaluate
some
of
those
positions
and
be
more
open
towards
you
know,
potentially
adding
some
new
prom,
ql
features
and
and
other
you
know,
service
discovery,
implementations
where
we
had
been
more
on
the
conservative
side
before
so
I
think
you
know
generally,
we
are,
you
know
pretty
open
now,
but
of
course
you
know
you,
you
can't
put
everything
you
can't
make
everyone
happy,
that's
always
impossible
cool.
B
So
then,
let's
see
what
else
do
we
have
here?
Yeah
we
have
a
couple
of
guides
around
our
coding
style
in
general.
All
of
our
commits
need
to
have
this
kind
of
signed
off
by
line
that
you
may
be
familiar
with
needs
to
have
a
line
that
has
your
name
and
email
address.
Otherwise
the
ci
check
will
also
fail.
B
B
Great
and
so
now
to
actually
contribute.
You
probably
want
to
you
know
first
check
out
the
code
and
then
be
able
to
build
it
and
run
the
tests
you
need
goal
for
so
basically
recent
version
of
go
for
building
the
back
end
and
then
npm
and
you
know
yarn
stuff,
so
node
node.js
stuff
for
the
front
end
to
be
able
to
build
the
front
end
as
well,
so
yeah
that
that
has
become
a
requirement.
B
I
want
to
show
one
kind
of
cool
thing.
You
can
actually
use
gitpod.io
to
spin
up
a
pre-built
dev
environment,
so
you
know
this
url
here
I
actually
will
copy
it.
So
you
can
see
it
more
clearly
up
here.
It's
just
gitpod.io
and
then
you
can
add
any
repository
url
there
in
this
case,
github.com,
prometheus,
prometheus
and
github
will
get
pod
in
this
case.
B
Will
check
out
that
repository
and
then
give
you
an
in
browser,
vs
code
style
experience
and
if
you
do
have
a
dot,
git
pod
yaml,
like
a
config
in
your
repo.
It
will
not
only
check
it
out,
but
it
will
also
execute
some
pre-built
steps
like
it
will
build
the
prometer
server.
It
will
start
it
up
for
you
and
so
on
so
I'll,
just
let
that
load.
B
I
do
not
have
the
setup
to
actually
you
know
like
commit
from
here
and
and
submit
back
to
to
github
that,
but
that's
just
due
to
the
way
that
I
I
didn't
want
to.
Oh
for
some
reason
I
couldn't
give
it
the
the
right
github
permissions
yet,
but
that's
more
of
a
personal
decision
like
normally.
You
could
theoretically
completely
use
git
pod
as
an
in
browser
way
to
develop
prometheus
and
to
build
it.
So
I
I
use
it
a
lot
for
like
when
I
do
get
a
pull
request.
B
You
can
also
just
say
goodpod.io
hash
and
then
the
url
of
the
pull
request
and
it
checks
out
that
pull
request
starts
it
up,
and
I
can
like
immediately
play
around
with
changes
to
the
pro
request
in
this
editor
here
and
then
start
it
up
again
and
then
you
know
give
feedback
on
the
pull
request.
Saying
like
hey.
You
know.
I
tried
out
this
one
thing,
so
I
don't
have
to
locally
check
out
someone
else's
code
code,
review
branch
so.
A
Yeah
pretty
cool,
I
think
one
of
my
my
favorite
things
about
using
get
code
in
this
fashion
as
well,
is
like
their
build.
Servers
are,
like
you
know,
32
cores
and
64
giga
ram,
or
something
silly
like
that.
So
you
know
you're
not
using
your
own
cpu
and
memory
to
build
fairly
large
projects
and
it's
much
quicker
in
this
environment.
So
yeah.
B
Yeah
here
the
the
full
vision
of
git
pod
is
ultimately
you
move
all
the
development
into
this
cloud
editor
and
you
don't
have
any
local
fans
running
anymore,
right
and
yeah,
so
maybe
I
will
get
there
as
well.
So
because
you
know
you
do
have
a
terminal
here.
I
could
stop
this
prometheus
editor
and
then
you
can
do
all
your
get
commands
here
and
look
at
what's
going
on
you
can
you
can
create
a
new
branch?
You
know
foo
and
then
you
could.
You
know,
push
that
and
so
on.
B
But
then,
if
I
do
that,
you
know
I
would
have
to
grant
it
more
permissions
in
my
github
account.
So
that's
just
something
you
need
to
be
aware
of
so
for
today.
I
just
wanted
to
point
this
out
as
an
awesome
way
to
kind
of
get
on
board
it
without
having
to
install,
go
and
node.js
and
yarn
and
so
on
locally.
If
you
have
no
problem
setting
up
that
stuff
locally,
that's
also
fine.
I
will
now
do
the
next
steps
locally.
B
Just
because
then
I
can,
you
know,
actually
commit
the
stuff
and
so
on,
but
you
can
also
do
it
to
get
part.
Maybe
I
should
point
out
two
little
build
things
here.
Yeah
I
haven't
even
mentioned
the
readme
yet
which
of
course
also
exists
which
you
know
goes
a
bit
into
the
architecture
as
well
just
zooming
out
a
bit
for
overview.
You
know
the
different.
You
know.
B
Source
yeah
yeah-
I
just
wanted
to
see,
what's
actually
on
the
page,
all
right,
so
this
offer
gives
a
bit
of
a
you
know
how
to
use
this
repo
instructions,
plus,
if
you
do
search
for
readme
in
the
entire
repo
here,
you
see
that
many
of
these
sub
directories
will
contain
readme
by
themselves.
For
example,
service
discovery
has
read
me
as
well,
which
explains
the
design
of
the
service
discovery,
components,
and
you
know
what
should
go
into
this
repo
and
how
they
should
be.
You
know
if
you
want
to
add
a
new
one.
B
What
interface
do
you
have
to
follow
to
to
make
that
happen,
and
so
on?
So
you
can
find
a
lot
of
more
detailed
information
in
those
sub
in
those
sub
readmes.
B
That's
a
t
t
nice
works
on
on
git
lab
as
well.
B
As
for
the
the
structure
of
this
repository
here,
like
cmd
as
we've
already
seen,
contains
the
two
actual
command
line
tools,
the
server
and
another
little
helper
tool,
and
then
we
do
have
just
a
bunch
of
directories,
kind
of
mirroring
some
of
the
larger
components
of
prometheus
service
discovery,
alert
notification,
sender,
the
actual
prom
ql
engine
is
in
the
prom
qr
directory
rule
management
scraping
like
this
is
the
thing
that
really
the
code
part
that
really
fetches
metrics
from
targets,
and
you
know
then
sends
them
to
the
storage
and
the
storage
lives
here
and
a
bunch
of
more
things
right
so
yeah.
B
B
Clone
this
repository
that
we
have
just
seen,
I
think,
there's
also
instructions
here
right.
You
can
always
just
go
to
this
button
copy
this
url
here.
I've.
A
B
I
wonder
if
I'll
have
that
installed,
I
don't
okay,
that's
cool,
so
I'm
just
doing
it
the
old-fashioned
way,
good
clone
so
checking
out
this
repository
two,
as
you
will
see
an
lgtm
directory
here,
especially
for
the
show.
B
We
have
all
the
files-
oh
yeah,
so
building
like
theoretically
the
go
part
you
could
just
run
by
you
could
just
build
it
by
saying
like
go,
build
cmd
prometheus
the
package,
so
that
works.
But
we
have
also
a
make
file,
which
has
a
couple
more
steps
like
it
will
make
sure
that
it
will
actually
also
build
the
latest
ui
assets
for
you
and
it
will
inject
like
it
will
compile
them
into
the
static,
go
binary
that
we're
building
and
it
will
also
inject
you
know
it
will
set
some
linker
options.
B
C
B
Yeah,
it
does
take
a
little
bit
of
time,
but
not
too
long
like
maybe
I
don't
know,
maybe
a
minute.
It
builds
prometheus
and
from
tool
like
at
the
moment
right.
It's
building
that
react
app,
creating
a
production
build
for
that
it
writes
those
assets
into
a
directory
where
it
then
kind
of
encapsulates
them
in
a
go
file
that
is
then
compiled
into
the
actual
prometa
server
binary.
B
B
Okay,
so
make
test
after
you
make
a
change
right,
you
will
kind
of
want
to
make
sure
that
all
the
tests
still
pass
and
now
optimally.
If
you
make
a
significant
change,
you'll
probably
also
want
to
add
a
test
for
it
or
adapt
an
existing
test
to
make
things
pass
again.
A
B
Oh
yeah,
that's
a
good
idea,
so
we'll
just
let
those
two
run:
let's
go
to
the
issues
list
so
like
going
back
to
the
repo.
If
you
go
to
the
issues
tab,
you
will
see
a
bunch
of
issues
there.
We
we
have
the
number
of
labels
with
different
meanings.
So
if
we
go
to
the
labels
here,
you
know
we
we
try
to
tag
issues
by
the
actual
component
of
the
server
that
they
touch.
B
C
Low,
oh
wait
and.
B
We
have
two
pages
here:
that's
why
I
didn't
find
it
low-hanging
fruit
and
we
also
have
a
not
as
easy
as
it
looks
level
which
has
come
in
handy
because
often
issues
do
come
in
where
something
seems
like
a
trivial
change
initially
and
then
you
know
we're
like
oh
well.
B
This
actually
touches
like
these
10
things
over
here
and
would
completely
like
invalidate
some
invariants,
and
I
don't
know
like
someone
really
has
to
think
about
this
much
more
before
we
just
make
this
change,
and
so
maybe
you
know
as
a
first
time
issue
those
wouldn't
be
the
yeah
avoid
those
good
ones
could
be
the
low
hanging
fruit
ones
in
general.
It's
just
you
know
small
changes
and
help
want
it,
and
I
can't
tell
you
like
the
100
difference
between
those
two
labels.
At
the
moment
you
know
they're
relatively
similar.
B
Sometimes
you
do
see
them
used
together,
but
I
guess
help
wanted
us,
especially
an
invitation
to
the
outside
world,
where,
for
example,
open
bsd
right
like
we
don't
have
open
bsd.
So
it's
really
cool.
If
someone
has
open
bsd
and
they
can
test
on
there,
then
you
know
especially,
would
we
would
appreciate
their
help.
B
This
kind
of
thing
right
so
both
of
these
can
be
great
for
the
purposes
of
today,
to
actually
find
an
issue
that
we
can.
You
know,
look
at
understand
and
just
send
a
pull
request
for
within
the
scope
of
this,
of
the
show.
I've
actually
created,
one,
which
is
this
one
here
for
the
react:
user
interface.
B
Oh
someone
already
reacted.
That
was
true,
okay,
so
this
is
a
very
you
know.
It's
going
to
be
a
trivial
change,
but
the
the
idea
here
is
just
to
go
through
the
motions
of
what
it
takes
to.
You
know
make
a
change,
make
the
tests
pass
check
out
the
branch
push
it
to
github,
make
a
pull
request
and
and
see
how
that
goes
right.
B
B
And
yeah,
so
you
know
it
allows
you
to
input
promql
expressions
like
rate
oops.
I
know
it's
so
slow
off
some
metric
and
now
I'm
already
wondering
like
what
are
my
metric
names
and
it's
not
really
auto
completing
and
it's
not
syntax,
highlighting
either.
It's
not
also
also
not
showing
me
that
I'm
doing
anything
wrong.
So
we
added
a
new
experimental
editor.
That's
based
on
code
mirror
with
a
completely
new
like
auto
completion,
syntax
highlighting
and
inline
linting
framework.
B
D
B
Because
you
know
it,
it
has
all
these.
It
has
way
more
auto
completion
than
has
syntax
highlighting
it
has
things
features
like
this
one
here
where
you
can
build
your
query.
Pretty
quickly
shows
you
help
and
types
and
so
on,
for
the
different
metrics
you're
working
with.
So
this
is
a
new
editor
which
you
can
turn
on
or
off
right,
that's
the
old
one.
This
is
the
new
one.
B
Instance
is
something
something
so
you
can
see.
Definitely
it
will
make
your
life
less
painful
when
working
with
pronquill
we,
we
didn't,
make
it
the
default
here
immediately
when
we
added
it
because
you
never
know
you
release
it
to
a
bunch
of
users
and
they
might
find
a
lot
of
problems
with
it.
But
so
far
the
situation
has
seemed
okay
and
it
does
seem.
You
know
it
does
add
a
significant
advantage
in
the
prom
ql
editing
process
over
the
old
one,
so
it
would
be
great
to
actually
make
it
the
default.
B
So
the
goal
of
the
issue
would
be
to
default.
This
checkbox
here
to
be
true,
and
eventually
you
can
also
see
there
might
be
an
opportunity
here
to
hide
all
these
top
level
config
options
under
a
config
menu
somewhere,
because
they're
kind
of
getting
out
of
hand-
and
if
your
window,
you
know
becomes
a
bit
narrower,
then
they
don't
even
fit
on
one
line
anymore,
but
that's
that's
for
a
different
day.
Okay,
so
back
to
this
issue
here,
let's
actually
look
at
what
our
code
is
doing
here,
so
it's
still
running
some
tests.
B
B
I
guess
we
won't
really
talk
about
like
how
to
configure
prometheus
itself
in
in
this
talk
more
about
contribution,
right,
yeah,
yeah,
so
I'll,
just
kind
of
skip
that,
but
now
yeah
we
could
start
it
and
you
could
try
it
out
and
see
you
know
if
it
behaves
as
you
expect
in
here.
I
don't
have
a
prometheus
yammer,
yet
I
would
have
to
copy
it
from
documentation.
B
Examples,
prometheus
yaml
put
it
here
and
then
by
default
it
would
pick
it
up
and
run
and
so
on,
okay,
cool.
So
how
are
these
go
tests?
I
don't
know
if
you
kind
of
start
something
I
will.
I
will
terminate
them
for
now,
because
yeah
we
let
for
now.
Let's
actually
just
start
visual
studio
code
in
here,
which
you
know
I
recommend
as
an
editor,
but
there's,
of
course,
other
people
who
prefer
others.
B
A
B
Hide
the
sidebar,
so
I
happen
to
know
where
this
code
lives.
If
you
don't
know
where
the
code
lives,
that
says
use
experimental
editor,
we
could
also
go
and
find
it
right
like
we
can
not
search
and
replace.
I
could
just
use
just
search
for
that
and
now
I
find
it
in
panel
list
dot
tsx,
and
I
also
let
also
find
it
in
a
test
file
here
and
here's
where
I
would
really
want
to
zoom
in
zoom
zoom
zoom.
B
It's
this,
maybe
one
more
right.
I
have
one
more.
A
B
One
more
okay,
cool
so
I'll,
keep
this
test
file
open
and
then
also
the
actual
implementation
file,
close
the
sidebar,
maybe
even
zoom,
in
one
more
step
here.
B
Okay,
so
now
we're
deep
in
the
react
code-
and
I
guess
the
whole
react
web
app
is
a
bit
too
much
to
explain
right
now,
but
you
know
even
not
knowing
a
lot
of
react.
You
could
maybe
find
out
where
the
default
is
set.
So
there's
a
checkbox
here
and
when
it's
changed
it's
it's
calling.
This
set
use
experimental,
editor
value
to
the
checked
value
of
the
checkbox
right
and
like,
where
does
that
initial
default
actually
come
from,
is
kind
of
the
interesting
bit
here.
B
So
default
check
comes
from
use,
experimental
editor,
so
we'll
search
for
like
where
that
actually
is
the
first
occurrence
of
that
is
in
that
react
component
here.
So
the
panel
list,
we
are
using
a
react
hook
again.
Probably
can't
really
go
too
much
into
react.
Details
now,
but
we're
kind
of
you
know
locating
a
place
in
the
browser's
local
storage,
which
is
where
this
is
stored.
This
boolean
bit
under
the
key
use
new
editor
and
the
second
parameter
here
here-
is
a
default
value
so
by
default.
Currently
this
is
set
to
false.
C
B
And
we
could
now
run
the
full
tests,
but
we
can
also
just
run
the
react.
App
tests.
B
Why
do
they
not
because
we
actually
do
have
a
test
in
panelist
test
dot
tsx
that
checks
what
the
default
is
for,
that
experimental,
editor
check
box.
So
if
we
go
to
that
test
file
which
I've
conveniently
already
opened
here,
you
know
it's
kind
of
duplicating
that
information
from
the
actual
code
file,
but
yeah
it
just
just
kind
of
checks
that
these
check
boxes
are
present
with
the
expected
default
value
and
the
expected
default
is
still
false.
So
I
will
just
set
that
to
true.
D
B
And
the
test
runner
automatically
detects
this
through
a
file
watcher
and
just
reruns
the
necessary
tests,
and
hopefully
everything
will
actually
pass
yep.
So
now
everything
has
passed.
I
can
terminate
this
this
interactive
test
runner
by
pressing
q,
and
you
know
now.
I
would
probably
just
like
build
the
entire
thing
and
just
kind
of
make
sure
that
everything
works
together.
B
This
is
one
thing
I
can
do
like
this.
This
will,
you
know,
compile
the
react
app.
It
will
build
it
into
the
go
app
and
build
the
go
app
and
so
on,
but
I
could
also
I'll
open
yet
another
tab.
B
I
could
also
just
have
my
main
prometer
server
already
running
and
then
only
test
ui
changes
by
going
to
web
ui
react
app
and
just
saying
yarn
start
and
what
that
will
do
is
it
will
start
up
the
react
ui
itself
only
and
any
api
calls
to
the
backend
prometheus
server
will
be
routed
to
this
prometheus
server
on
port
1990
running
in
a
you
know
in
this
different
terminal
tab
here,
so
that's
kind
of
a
little
config
option.
We
have
in
our
package
json.
B
Where
you
can,
you
know
you,
you
can
just
leave
the
actual
binary
with
its
back-end
api
running.
If
you
only
want
to
do
front
end
changes,
you
just
do
the
yarn
start
and
the
nice
thing
about
that
is
that
you
know
that
will
then
automatically
in
a
bit
open
the
ui
in
the
browser
here
running
against
that
binary
server,
that's
running
it
can
take
a
second
on.
B
Load,
because
this
is
a
completely
new
repo
and
the
nice
thing
about
this-
is
that
any
change
you
make
to
the
code
will
immediately
cause
the
react
app
to
reload
that
part
of
the
page.
So
you
can
do
like
really
interactive
development,
whereas
if
you
had
to
do
a
full
make
build
on
every
ui
change
to
iterate
would
then
be
really
slow
right.
So
this
this
allows
you
to
iterate
really
quickly
come.
C
B
C
D
A
B
B
Yep,
I'm
a
bit
surprised
by
how
long
it's
taking,
but
I
think
it's
just
because
it's
you
know
doing
too
many
things.
Oh
I
will
I
will
just
you
know:
oh
it
should
it
should
be
done
in
a
second,
though
I
think
it's
just
mainly
this
main
build
here,
which
is
also
doing
things
in
parallel
and
so
on.
Hugging
hogging
everything,
and
so
you
know
my
h-top
wow,
okay
yeah.
B
Oh
there
we
go
right.
The
eye
has
actually
loaded
yeah,
so
you
know
I
I
could.
Actually
you
know
if
I
couldn't
now
like
make
changes,
and
they
would
just
appear
here
without
me
having
to
even
reload
the
browser
window,
so
that
that
gives
you
a
nice
way
to
do
like
iterative
ui
development.
But
in
our
case
you
know
we
I'm
already
pretty
confident
that
this
was
a
good
change,
so
I'm
just
gonna.
B
I
mean
it
already
built
the
prometa
server,
so
I'm
just
gonna
terminate
this
for
now
and
actually
just
start
up
the
new
parameters
binary
and
see
in
an
incognito
browser
without
any
local
storage.
If
it's
doing
the
right
thing
right,
so
I
could
just
go
to
localhost
1990
and
see
yep.
That
default
is
set
and
it
has
a
new
editor
awesome.
Okay,
cool!
So
now.
B
I
see
my
div
here.
It
looks
reasonable.
I
have
you
know
a
little
test
change,
an
actual
code
change.
Now
I
want
to
create
a
branch
for
this,
so
you
know
I
could
create
a
new
git
branch
and
call
it
let's
call
it
change
new
editor
default
or
so
now
I
should
probably
have
mentioned
that
you
probably
will
not
like
as
a
first
time
contributor.
You
will
not
have
right
access
to
the
actual
prometheus
repository,
so
the
first
step
you
will
want
to
likely
make
is
to
fork
it
right.
B
You
will
go
to
the
to
the
actual
repository
and
you
click
the
fork
button
here,
which
creates
a
private
fork
under
your
username
of
that
whole
repository,
and
then
you
would
clone
that
locally
instead
of
this
one,
and
then
you
would
push
your
pull
request
branch
to
your
fork
and
then
from
your
fork.
You
would
create
a
pull
request
in
my
case.
I
happen
to
have
right
access
to
this,
so
I
typically
push
my
review
branches
directly
to
the
prometheus,
to
this
repository
here,
not
to
a
private
fork.
B
Okay,
so
I'm
creating
my
branch
and
now
I'll
create
a
commit,
and
in
this
case
I
want
to
just
commit
all
all
changes.
I
don't
have
any
other
changes
laying
around
that.
I
wouldn't
want
to
commit
so
I'll.
Just
do
the
dash
a
here
and
add
in
this
case
I
think
just
a
single
line
here,
you
know,
make
the
new
from
ql
editor
the
default.
B
If
you
do
look
at,
I
think,
is
it
commits
some
previous
commit
messages.
Some
are
pretty
free
form.
Others
have
like
a
little
prefix
here,
so
I
may
you
know
we
don't
have
strict
rules
around
this
in
prometheus,
around
kind
of
like
the
semantic
commit
naming,
but
if
you
fix
something
it
can
be
nice
to
kind
of
start
out
with
fix,
or
you
know
fix
colon
or
so.
B
So
we're
going
heading
back
to
the
issues
in
the
repository
and
finding
this
issue
url
and
we're
just
going
to
mention
it
in
the
actual
commit
message-
and
you
see
I
have
my
my
whole
git
flow
locally,
with
some
hooks
set
up
in
a
way
that
it
already
automatically
adds
the
signed
off
by
line.
You
can
find
ways
on
the
internet.
How
to
do
that
or
you
can
just
manually
write
it,
but
it's
super
handy
if
you
just
have
like
a
little
commit
helper
tool
that
helps
you
do
that
cool,
so
it's
committed.
B
I
can
see
it
in
my
git
history
now
here
I
can
push
it
so
this
push
normally
would
go
to
your
private
fork
in
this
case,
I'm
saying
it
directly
to
prometheus
prometheus
and
then,
if
I
reload
this
page
here,
you
know
soon.
B
I
should
see
a
little
banner
at
the
top,
even
telling
me
like
hey.
You
just
recently
pushed
some
changes.
I
could
also
oh
wait.
I
have
to
go
here
right
there
you
go
yep
had
recent
pushes
less
than
a
minute
ago.
You
could
also,
you
know,
go
somewhere
and
do
it
manually,
but
normally
this
is
the
way
I
do
it.
I
just
say
like
okay,
compare
my
recent
changes.
That
is
that
I
pushed
I
want
to
create
a
pull
request.
B
Now,
if
you
are
well,
the
there's
like
a
little
commented
out
template
bit
in
here.
That
just
tells
you
a
couple
of
things
that
you
shouldn't
forget
before
submitting
a
pull
request
right
like
check
that
there
are
tests
and
that
they
that
they
pass
and
so
on
and
so
on.
B
Okay,
so
I'll
just
create
the
pull
request
here
and
let's
see
if
anyone
is
actually
online
to
review
it,
I
could
now
assign
a
reviewer-
and
you
know
my
favorite
reviewer
here
could
be
in
this
case
julian,
who
actually
suggested
that
this
could
be
a
good
issue
for
this
show.
B
I
have
no
idea,
if
he's
actually
currently
watching,
but
so
he
may
or
may
not
like
this
change
now
and
if
he
likes
it,
he
would
you
know,
actually
click
on
some
buttons
below
and
say,
like
you
know,
I
approve
this
or
you
he
would
just
send
a
thumbs
up,
but
in
any
case,
no
matter
whether
he
approves
it
or
just
sends
a
thumbs
up
or
something
we
want
these
tests
to
pass
and
go
green
before
we
actually
merge
it
right
and
in
general
the
rule
is
like
even
oh
look,
he
approved.
B
B
Yes,
I'm
also
guilty
of
that,
like
apologies
to
anyone
who
contributed
where
I
just
completely,
you
know
lost
sight
of
something
which
happens
to
me
on
a
regular
basis,
but
such
is
the
thing
when
you
you
know.
Often
you
have
so
many
things
flying
around
and
yeah
priorities.
It's
tough.
A
Comment
from
dan
pop
saying
what
a
responsive
community
falco,
I'm
jumping
ship,
so
it
looks
like
you're
getting
a
pop
on
a
prometheus
team.
There
he's
on
his
way.
A
That
manually
to
somebody,
but
I'm
assuming
first-time
contributors,
aren't
going
to
really
have
the
ability
to
do
that.
What
what
is
the
procedure
and
protocols
for
them
when
they
open
in
your
pill,
request.
B
Excellent
question
yeah
so
often
I
actually
I
mean
yeah.
If
you
have
kind
of
the
you
know,
people
already
know
who
is
responsible
for
a
part
of
a
repo
you,
you
may
just
cc
them
or
select
them
as
a
reviewer.
We
do
have
a
whole
maintainers.md
file
here
which,
by
the
way
it
is
mentioned
from
the
contributing
md
I
mentioned
initially,
which
is
like,
if
you
have
it
at
a
suitable
maintainer
which
are
listed
in
the
maintainers
md,
and
so
this.
B
This
gives
you
an
idea
for
the
different
parts
of
this
whole
repository,
who
is
most
responsible
for
what
kind
of
the
default
maintainers,
and
we
have
julian
as
the
main
and
default
maintainer
for
the
the
rest
of
the
repo.
That
is
not
explicitly
mentioned
here
so,
but
you
know
you
can
also
choose
to
not
mention
anyone,
but
it
can
help
to
mention
someone,
because
it
gives
people
a
more
clear
sense
of
responsibility
that
they
should
look
at
something
you
know.
B
Otherwise,
you
you
don't
know
so
it
can
sometimes
it
it's,
as
so
often
with
you
know,
in
any
work
situation
where
you
have
always
more
things
flying
around
that
you
can
do
it
always
in
the
end.
In
practice,
you
just
poke
someone
a
bit
more
and
eventually
you
know
they
they
will
notice
okay,
so
we
yeah.
We
will
probably
you
know,
it'll
take
a
while
for
some
of
these
tests
to
go
green
shouldn't.
B
Take
super
long,
but
probably
you
know,
won't,
won't
be
able
to
merge
it
right
now,
probably
shortly
after
the
show
cool,
but
that
is
basically
the
flow.
Finally,
then
you
know
I,
I
would
click
on
the
button
here.
That
would
eventually
go
green
and
allow
me
to
just
say,
yep
merge.
B
You
cannot
do
that
as
a
contributor,
if
you
don't
have
right
access
to
this
repository,
so
normally
that
step
would
be
done
by
you
know
by
a
team
member
of
prometheus
who
has
right
access
here.
B
This
is
kind
of
the
positive
flow
where
everything
just
kind
of
works
itself
out,
there's
an
immediate.
It
look
looks
good
to
me,
coincidentally,
the
name
of
the
show,
but
of
course
there
can
be
situations
where,
like
the
usual
case
for
larger
changes,
will
be
that
there
you
know
there
will
be
some
comments
by
the
reviewer,
maybe
either
pointing
out
a
bug
or
making
some
suggestions,
how
to
make
code
cleaner,
more
maintainable
or
like
have
you
thought
about
this?
B
Would
this
be
a
better
way
of
doing
it
and
you
know
feel
free
to
discuss
and
but
yeah
in
the
end,
of
course,
the
the
people
who
decide
what
gets
merged?
How
are
the
the
promises
team
members
and
the
maintainers
of
of
the
repository
awesome.
A
We
have
a
couple
of
comments
in
the
chat
as
well,
but
from
someone
I
assume,
is
maybe
familiar
with
the
project.
But
they've
said
that
there's
also
a
code
owner's
file
to
help
find
employers
responsible
for
a
single
piece
of
code,
and
they
also
mentioned
that
the
cis
actually
provide
a
preview
environment
for
the
ui,
which
you
can
also
check
out
as
well.
B
Yes,
I
should
totally
mention
that
oh
yeah,
so
the
code
owners
file
we
introduced
very
recently,
mainly
because
I
wanted
to
get
notified
whenever
someone
sends
a
pull
request
that
touches
the
web
ui
directory,
because
before
that
I
would
just
often
miss
these,
and
this
is
actually
nice
way
for
you
to
have
github
notify
you
when
a
pull
request
touches
a
certain
sub
directory.
So
that's
that's
really
cool
yeah.
So
going
back
to
our
pull
request,
let's
see
if
that
ci
check
that
you
mentioned
is
already.
B
So
you
have
one
ci
check
here:
that's
the
netlify
deploy
preview,
which
gives
you
an
actual
deploy.
Preview
of
the
react
front
end
and
we
see
the
correct
checkbox
set,
haven't
zoomed
in
here,
so
that
works
and
the
way
it
it's
not
running.
You
know.
Netlify
only
holds
static
files
in
this
case,
which
is
only
the
the
front
end,
so
we
kind
of
have
a
little
magic
proxying
set
rule
in
the
build
step
and
natalify
that
points.
B
This
react
front
end
at
a
demo,
prometheus
server.
We
have
running
from
the
demo
from
from
the
prometheus
project,
so
you
know
this
will
actually
have
some
some
permanently
running
prometheus
server
that
it
is
pointed
to
and
that
it's
showing
the
data
for.
A
A
A
That
makes
sense,
and
I
can
imagine
people
may
probably
work
on
this
in
isolation.
I
think
it
would
probably
more
likely
that
you
make
changes
to
the
front
end
and
isolation
from
back
end
changes,
yeah,
yep,
all
right
awesome.
That
is
great.
Thank
you
for
for
walking
us
through.
B
A
Yeah,
if
anyone
has
any
questions,
you've
got
a
few
minutes.
Please
get
them
into
the
chat
and
we'll
do
our
best
to
tackle
them.
We
had
a
couple
of
comments
throughout
that
we
can
cover
just
now.
So,
let's
see
audacious
farl
says
I
was
told
that
golang
builds
are
fast
well,
they're,
incremental
they're,
faster
after
the
first
name,
but.
B
I
think
they're
relatively
fast.
It
was
super
fast
initially
like
when
we
started
out
with
prometheus
it
built
in
like
six
seconds
or
something
and
yeah.
Then
we
added
more
and
more
and
more
service
discovery
code,
and
you
know
even
just
adding
kubernetes
client
libraries
in
there
and
things
like
that.
You
know
really
ends
up
making
things
larger,
and
you
know
this
now
the
binary
is
94
megabytes.
B
I
remember
a
time
when
was
like
16
or
so,
but
you
know
in
these
this
day
and
age,
it's
nice
to
have
a
lot
of
functionality
baked
in
there.
B
As
well
right
I
mean
it's
a
large
project,
it
has
a
lot
of
functionality,
it
supports
service
discovery
for
a
lot
of
different.
You
know
cloud
providers,
container
schedulers
and
other
mechanisms
and
yeah
there's
a
lot
of
things.
You
know
so
obviously
the
the
react
stuff
isn't
there
as
well.
A
B
A
Sure,
that's
fair,
okay!
Well,
I
don't
think
we're
going
to
get
any
more
questions,
but
with
that
I'll
just
say,
thank
you
again,
julius.
It
was
really
great
to
go
through.
All
of
that,
you
know,
I
think,
there's
a
lot
of
great
tips
there
for
anyone
who's
looking
to
contribute
to
the
prometheus
project
and,
of
course,
if
you
need
any
more
help
you
can
reach
out
to
either
of
us
on
twitter,
we'll
do
our
best
or
open
an
issue
on
the
premiums
repository
and
we'll
do
our
best
to
help
you
out
as
well.
A
That
is
it
from
us
feel
free
to
tune
up.
You
should
definitely
tune
back
in
to
cloud
native
tv
in
a
few
hours
in
two
hours
time
pop
will
be
hosting
spotlight
live
it's
going
to
be
a
great
conversation
with
the
kubecon
panel,
the
chairs
of
cubecon.
So,
looking
forward
to
that
julius,
I
will
leave
you
there.
Thank
you
again
so
much
I
will
speak
to
you
again
and
to
everyone
watching
have
a
wonderful
day.
Thanks.
Thank.