►
From YouTube: Inside Prometheus - A Documentary Film
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
Foreign
hello,
welcome
to
a
special
screening
of
inside
Prometheus,
a
documentary
film
on
the
origins
of
the
open
source
Prometheus
project.
My
name
is
Chad
torben
I'm,
the
executive
producer
at
Speakeasy
Productions,
who
is
responsible
for
creating
the
film
Speakeasy
Productions.
We
bring
to
light
the
world
of
developers
moving
them
out
of
the
Shadows
into
the
hearts
and
minds
of
millions
of
people
everywhere.
Our
mission
is
to
Leverage
The
Power
of
film
to
drive
understanding,
participation
and
Adoption
of
Open
Source
projects
on
this
webinar.
A
To
help
tell
the
story,
we
were
able
to
enlist
many
of
the
founders
and
early
players
on
in
creating
the
Prometheus
project,
which
includes
Julius,
Vols,
Bjorn,
ravenstein
and
Richard
Hartman,
who
continues
to
steer
the
community
today.
As
many
of
you
know,
the
project
started
at
SoundCloud
and
it
took
us.
We
got
extra
special
permission
to
film
in
Berlin
at
the
SoundCloud
offices.
A
So,
as
you
watch
the
film
and
you
see
shots
in
the
office
of
Bjorn
and
Matthias,
rample
Who
currently
still
works
at
SoundCloud
today
on
the
project
that
is
all
filmed
in
Berlin
at
the
SoundCloud
offices,
Where
it
All
Began,
which
is
very
special
for
us,
and
we're
very
helpful
and
thankful
to
SoundCloud
for
letting
us
do
that.
These
films
are
really
a
labor
of
love
to
make
we
really
enjoy
making
them.
A
Our
next
film
will
be
focused
on
the
open
source
project
Envoy
we're
hoping
to
debut
that
at
kubecon,
Cloud
native
Con,
in
Amsterdam,
in
2023,
with
more
films
to
come,
there's
no
shortage
of
great
stories
within
the
open
source
Community,
especially
the
cloud
native
Community.
Again.
Our
goal
is
to
inspire
understanding,
participation
and
Adoption
of
projects,
but
also
those
next
great
code,
contributors
and
next
great
projects.
A
If
you
have
an
idea
for
a
project,
we
hope
you'll
watch
this
film
and
get
inspired
to
go
out
and
build
that
project
and
to
create
and
if
not,
build
your
own
project
at
least
contribute
to
one
of
these
projects.
Our
first
film
was
kubernetes,
a
two-part
documentary
on
the
origins
of
the
project
itself,
which
I
hope
many
of
you
watched,
and
you
can
also
see
on
the
honeypot.io
YouTube
channel.
A
C
More
and
more
of
like
normal
companies
went
into
a
state
where
they
had
Fairly
complex
distributed
systems.
They
were
severely
lacking.
Troubleshooting
skills.
F
G
G
I
At
the
time
in
2012,
I
was
still
working
at
Google
in
Zurich
in
Berlin,
SoundCloud
was
just
emerging
as
this
really
cool
new
startup
in
the
music
scene.
Having
the
the
aspiration
of
becoming
the
YouTube
of
sound
had
really
great
Engineers
as
well.
You
know
good
Dynamic
culture
and
just
seemed
like
a
fun
place
to
work.
I
I
eventually
made
that
jump
to
Berlin
and
joined
at
SoundCloud.
Another
ex-googler
Matt,
proud,
had
joined
at
the
same
time,
and
we
noticed
that
SoundCloud
had
a
bunch
of
issues
when
it
came
to
reliability,
latency
of
the
website
and
all
that,
and
we
were
having
trouble
really
figuring
out,
even
where
these
problems
were
coming
from
foreign.
I
C
Even
finding
out,
if
you're
up
or
down,
if
you're
under
100
servers,
then
there's
always
a
server
down.
It's
usually
not
bad,
because
your
distributed
system
is
designed
for
that.
But
you
have
to
find
out
that
it
is
broken,
and
once
you
know
that
now
you
have
to
find
out
what
is
broken
and
yeah.
There
was
just
no
chance.
I
Soundcloud
at
the
time
already
had
built
their
own
in-house
cluster
scheduler
system,
so
this
was
before
Docker
even
existed
and
then
far
be
before
kubernetes
existed,
so
it
was
a
very
modern,
dynamic
and
always
changing
Computing
environment
already,
but
it
was
very
hard
with
the
traditional
tools
to
get
insight
into
what
is
really
happening
in
that
cluster.
We.
I
Graphite
database
was
not
really
Built,
For
This
highly
Dynamic
use
case.
So
when
there
was
an
issue
like
a
latency,
Spike
or
Spike
of
Errors,
we
were
unable
to
properly
pinpoint
it
down
to
a
specific
process,
or
you
know
not
knowing
whether
it
is
a
specific
process
or
the
entire.
You
know
group
of
microservices.
F
C
I
It
worked
in
this
more
Dynamic
world.
You
needed
a
monitoring
system
that
first
of
all
integrates
the
world
of
alerting
and
time
series
and
then
also
have
a
more
flexible
data
model
that
allows
more
dynamicism,
and
that
has
you
know,
on
top
of
it,
a
query
language
that
allows,
for
you
know
flexible
dashboarding,
but
also
powerful
and
flexible,
alerting
at
the
same
time,
so
tying
together.
The
time
series
and
the
alerting
use
cases
into
one
system.
D
I
Not
proud
and
myself
had
just
both
come
from
Google
and
we
were
used
to
this
one
monitoring
system
called
borgmon
at
Google,
which
was
used
to
monitor
all
kinds
of
different
services
and
infrastructure
at
Google
in
a
very
flexible
way,
and
we
noticed
that
when
we
came
to
SoundCloud
that
SoundCloud
already
had
a
very
Dynamic
cluster
scheduler
internally.
So
at
the
time
we
looked
at
the
different
available
open
source
monitoring
systems
and
we
were
a
little
bit
disappointed.
They
were
not
really
great
at
tracking
metrics
in
detail,
especially
in
a
constantly
changing
world.
I
It
was
a
very
big,
ambitious
project.
We
were
trying
to
build
a
complete
new
monitoring
system
and
Paradigm
kind
of
from
scratch.
So
not
only
did
we
have
to
explain
it
properly
to
people
who
had
never
used
such
a
system,
but
also
build
it.
So
I
did
initially
have
a
lot
of
doubts.
Whether
this
project
would
be
worth
it
and
whether
it
would
succeed.
We
were
not
hired
to
build
a
monitoring
system.
We
were
hired
to
make
SoundCloud
more
reliable,
SoundCloud.
F
I
I
A
year
in
you
know,
Matt
decided
to
leave
SoundCloud
and
go
back
to
Google,
and
then
I
was
alone
on
Prometheus
for
a
while
I'm
just
pushing
it
Forward.
Gradually
new
people
joined
the
project
as
well,
so,
for
example,
Bjorn
robinstein
also
left
Google
and
I
had
known
him
already
and
he
got
interested
in
what
I
was
working
on.
So
when
he
joined
SoundCloud,
he
also
started
helping
out
with
Prometheus
pretty
early
on.
C
I
The
building
part
had
so
many
different
components,
so
we
had
to
build
a
proper
time
series
database.
We
had
to
build
a
querying
system.
On
top
of
that,
we
had
to
build
client
libraries
for
people
to
actually
get
metrics
out
of
their
different
processes
and
services
and
hosts.
So
it
took
a
lot
of
faith
initially
both
from
us
and
for
some
people
who
supported
us
to
believe
that
this
you
know
at
some
point
could
actually
start
coming
together
and
start
really
making
a
difference
where
this
project
would
be
worth.
It.
C
We
thought
this
is
very
helpful
for
what
we
are
doing
here,
and
it
would
probably
be
good
if
others
use
that,
but
we
had
no
expectation
that
anyone
except
perps,
a
few
ex-googlers
and
then
very
few-
very
nerdy
people-
might
actually
realize
what
you're
doing
here.
So
we
had
no
expectation
that
this
would
change
how
the
world
is
doing.
Monitoring.
B
I
I
We
are
using
this
monitoring
system
and
it's
not
only
being
used
at
SoundCloud
at
the
moment,
one
and
a
half
weeks
after
our
official
announcement
of
Prometheus
someone
who
we
still
don't
know
to
this
day,
who
actually
is
managed
to
get
Prometheus
onto
Hacker
News
on
rank
one
for
a
whole
day
and
that
really
turned
on
the
lights
for
the
project.
We
saw
that
really
in
our
GitHub
stars
and
our
chat
channels
and
our
mailing
lists
in
the
GitHub
contributions.
Just
everything
started:
shooting
through
the
roof
from
that
day,
on.
J
G
Has
a
simple
user
interface,
a
single
binary
and
then
ease
of
deployments,
and
this
this
is,
you
know,
change
the
the
entire
way
in
which
we
approach
consume
and
develop
with
our
Monitoring
Solutions.
E
H
B
The
pool
model
it
makes
things
much
more
reliable
because
suddenly
those
collections
are
telling
you
much
more
and
it
provides
additional
context.
Additional
information.
Try
it
on
opposite.
Try
ask
those
applications
to
push
data
to
your
monitoring
solution.
Now
things
are
very,
very
tricky.
You
have
to
think
about
buffering
rate,
limiting
service,
Discovery
and
lots
of
complex
stuff
that,
ideally
you
don't
need
to
worry
about
it.
B
I
I
The
kubernetes
people
noticed
that
it
was
similar
to
the
monitoring
systems
they
were
used
to
at
Google,
so
they
chose
to
support
Prometheus
style
metrics
in
all
the
different
kubernetes
cluster
components
that
led
to
a
world
where
you
know
kubernetes
supported
Prometheus
very
well,
but
at
the
same
time
Prometheus
also
supported
native
service
Discovery
and
data
collection
on
kubernetes.
In
the
end
that
led
to
Great
Mutual
support
between
the
two
systems
and
when
you
were
using
kubernetes,
you
were
probably
also
using
Prometheus
in
some
fashion.
E
C
If
you
want
to
claim
there
is
a
conspiracy,
it
really
looks
like
it
like
Prometheus
kubernetes
are
both
like
10
letter
words
they're
both
of
Greek
origin
like
kubernetes,
is
aggregate
abbreviated,
k8s
Kate's,
you
could
abbreviate
Prometheus,
p8s
or
Pace
or
something
I,
don't
know
their
logos
that
were
they're.
All
done
right,
like
it's
blue
with
this
orange,
is
like
perfect,
complementary
colors.
It
really
looked
like
these
systems
were
designed
for
each
other
and
Matthias
sometimes
calls
it
like
twin
separated
at
Birth,
but
yeah.
It
felt
really
like
okay.
Finally,
they
get
together.
E
D
Prometheus
came
in
because
observability
monitoring
becomes
that
much
more
important
when
your
systems
are
Loosely.
Coupled
teams
are
working
on
small
pieces
without
talking
to
other
teams,
so
you
really
need
observability
at
that
time.
So,
hence
Prometheus
was
a
great
fit,
and
today
it
is
one
of
the
pillars
of
cloud
native.
I
J
J
I
met
someone
called
Craig
McLaughlin
from
Google
who
was
working
on
the
kubernetes
project
and
Craig
told
me
that
he
would
like
kubernetes
to
be
in
a
foundation
so
that
it
could
be
an
industry
asset
and
not
just
a
company
asset.
We
talked
about
how
the
cncf
could
come
into
existence.
That's
why
I
said
to
Craig
I
think
Prometheus
would
be
a
wonderful
project
for
the
cncf's
early
days.
We
agreed
that
would
be
one
of
the
projects
that
we
would
try
and
recruit
when
the
cncf
launched.
D
Is
truly
a
special
project
had
a
very
strong
velocity
over
the
years
and
they
joined
cncf
in
2016
and
actually
I,
remember
being
in
the
observability
space.
I
was
working
on
distributed
tracing.
We
saw
Prometheus
joined,
CNC,
wow,
okay,
we
should
try
to
join
in
too
so
it
was
really
a
like
a
stage
Setter.
The.
J
D
I
Now
saw
that
the
project
was
really
independent
had
a
proper
governance.
It
was
associated
with
the
other
projects
in
that
Foundation
right
kubernetes,
especially
the
cncf,
also
just
helped
us
in
a
lot
of
different
ways,
supporting
our
events
like
prom,
corn
or
Prometheus
days,
but
then
also
helping
us
with
PR,
helping
us
with
Cloud
infrastructure
funding
and
just
giving
us
advice
along
the
way.
As.
D
J
Problems
all
the
time
people
talk
about
standards,
standards
are
used
in
two
different
ways.
Sometimes
people
mean
standards
like
TCP,
where
everybody
uses
the
same
way
to
connect
up
a
network.
Another
kind
of
standard
is
what
we
call
a
standard
tool
or
a
de
facto
standard.
It
means
commonly
used
popular
tools
that
everyone
should
understand.
Once
they've
reached
a
certain
level.
H
D
Has
retained
a
narrow
focus,
it
does
monitoring.
It
is
a
Time
series
database
with
a
querying
language,
and
it
does
those
things
really
well
doesn't
spread
itself
too
thin.
I
personally
also
think
that
a
lot
of
the
original,
the
ogs
are
still
deeply
involved.
That
is
just
awesome.
It's
it
inspires
many
to
join
in.
C
D
All
the
people
out
there
who
are
considering
what
should
I
build.
What
would
what
would
resonate?
There
are
other
parts
of
the
cloud
native
application
development
process
that
are
not
commodified
that
are
not
de
facto
standardized.
Look
at
all
those
things
and
decide
where
you
have
the
strongest
inclination
to
build
a
successful.
H
Project
there
are
projects
where
it's
trying
to
achieve
everything,
but
it
ends
up
achieving
nothing
because
there's
so
much
fragmentation,
I
think
Prometheus
community
and
the
core
kept
it
very
straightforward,
kept
it
very
simple,
but
yet
achieved
the
build
that,
like
really
big,
you
know,
ecosystem
around
the
project.
We.
E
A
personal
lesson
I
took
from
Prometheus
is
that
even
if
you
have
the
best
tech
in
the
market
in
the
ecosystem
and
I'm,
obviously
biased
here,
but
I
strongly
believe
that
this
is
true,
even
if
you
have
the
best
tech,
it's
not
enough.
There
are
so
many
other
aspects
to
success
and
it
needs
a
complete
mix
of
not
just
the
technology.
It
also
needs
adoption
drivers.
It
needs
public
speaking,
it
needs
a
healthy
Community.
E
G
A
Welcome
back
everybody
I
hope
you
all
enjoyed
watching
the
film
as
much
as
we
enjoyed
making
it
and,
as
we
discussed
in
the
agenda,
we
have
with
us
now
Chris
anderchuk
CTO
of
cncf,
who
was
really
instrumental
in
helping
make
this
movie
and
and
bring
it
to
production
and
and
conceptualize,
and
bring
the
whole
idea
to
the
Forefront
so
Chris.
Thank
you
for
taking
a
little
bit
of
time
to
join
us
today.
K
K
So
knowing
a
lot
of
these
individuals
personally
and
kind
of
seeing
the
story
play
out
with
just
great
I
think
we
need
to
do
more
of
these
types
of
things
and
you
know
obviously
the
kubernetes
documentary
that
kind
of
preceded
this
one
was
super
successful
and
we're
seeing
a
lot
of
great
feedback
from
everyone
there
in
in
this
kind
of
wonderful
story,.
A
Yeah-
and
so
you
know,
we
didn't
get
to
put
you
in
the
movie,
although
I
think
we
were
we
were
trying
to,
but
we
had
Alexis
there
representing
cncf
and
he
talked
a
little
bit
about
how
Prometheus
came
into
cncf
and
I
know.
You
were
really
instrumental
in
that
as
well.
So
maybe
you
could
just
talk
a
little
bit
about
how
you
came
across
the
project
and
what
that
kind
of
you
know
that
process
looked
like
when
they
came
into
cncf.
K
Yeah,
so
you
know
you
know,
as
people
know,
you
know,
kubernetes
was
kind
of
born
born
uninspired
by
a
project
called
bork.
You
know
you
know
at
Google,
and
you
know
there
was
a
sister
project
called
borgmon
right
that
eventually
inspired
Prometheus.
So
I
was
aware
that
you
know
people
were
trying
to
come
up
with
kind
of
that.
You
know
missing
piece
that
didn't
really
exist
in
in
kind
of
the
kubernetes
and
open
source,
ecosystem
and
I
think
it
was
literally
I.
Think
Julius
mentioned
this
in
the
documentary
it
was
like.
K
You
know
they
posted
something.
You
know
open
source,
a
project
and
eventually
someone
posted
something
on
Hacker,
News
and
eventually
that's
kind
of
how
I
came
across
it,
curse
and
kind
of
played
with
it
a
little
bit
and
was
like
okay,
you
know
kind
of
cool
and,
on
kind
of
you
know,
moved
on
to
my
day
and
then
eventually,
I
think
this
is
like
late
2015.
You
know,
Alexis
was
basically
thinking
about.
K
Like
you
know
what
other
projects
you
know
do
we
need
in
cnci
for
this
whole
ecosystem
to
be
successful,
because
you
know
kubernetes
on
its
own.
Is
freaking
an
amazing
piece
of
technology,
but
you
know
once
you're
starting
to
deploy
Services,
you
need
to
monitor
them,
you
need
to
observe
them
and
you
need
to
ensure
they're
secure
and
so
obviously
you
know
you
know.
Observability
was
kind
of
a
missing
piece
and
you
know.
Lo
and
behold,
you
know
we
kind
of
got
connected.
K
The
Prometheus
team
discussed
of
what
it
kind
of
would
look
like
them
joining,
and
you
know
they
kind
of
went
through
the
process
as
our
second,
you
know,
you
know
project
in
the
foundation
and
it
was
just
you
know,
a
natural
like
peanut
butter
and
jelly
with
both
kubernetes
and
and
Prometheus.
K
You
know
overall
so
and
I
definitely
have
to
give
a
lot
of
kudos
to
Alexis.
For
kind
of
you
know,
driving
a
lot
of
that
initial
thought
process
and
bringing
the
Prometheus
team
into
cncf.
I
K
K
Saw
that
little
graphic,
it
was
like
K-8,
ass
and
pieda
I
like
this
whole
like
funny
logo,
things
but
yeah,
all
all
goodness,
and
you
know
definitely
the
Borg
and
borgmon
relationship
and
kubernetes
and
Prometheus
relationships
are
kind
of
sister.
You
know
or
they're
inspired
basically
by
by
each
other.
So.
A
Yeah-
and
that
seems
like
part
of
their
kind
of
secrets
to
their
success,
I
mean
it's
the
second
largest
project
by
code
commits
and
cncf
right
now.
Did
you
think
it
was
ever
again?
Did
you
expect
it
to
be
this
big
and
like
what
do
you
think
is
sort
of
help
with
their
velocity
like
what
what
has
been
their
secret
sauce.
K
So
I
think
part
of
it.
You
know
one
kind
of
cool
thing
about
Prometheus
I,
don't
know
if
you've
ever
had
like
experience,
setting
up
kind
of
old
school
monitoring
systems
right,
it
was
a
huge
pain.
Like
you
know,
in
the
early
days
we
had
things
like
nagios,
which
was
like
super
popular,
but
a
huge
pain
in
the
ass
to
kind
of
set
up
and
install
and
deal
with.
Prometheus,
eventually
kind
of
you
know,
came
around
and
flipped
a
script
on
a
lot
of
things,
one
with
Prometheus.
K
You
got
a
simple
binary
like
simple
binary,
you
could
run
very
easy
to
set
up
and
kind
of
configure
via
a
simple
configuration
file.
Golang
was
also
kind
of
a
modern
language
which
made
it
a
little
bit
easier
to
contribute.
There
was
none
of
this
crazy,
like
you
had
to
have
agents
on
every
machine
to
kind
of
collect
data
and
forward
them
to
you
know
the
observability
system,
Prometheus
kind
of
flipped
the
script.
K
By
having
this
cool,
you
know
kind
of
model
instead
of
like
classic
like
have
an
agent
on
machine
and
it
pushes
to
the
central
thing:
Prometheus
flipped
it
by
having
this
kind
of
you
know
pulled
model
as
long
as
you
had
a
standardized
interface
that
you
kind
of
you
know
come
with,
and
you
know
honestly
I
think
the
you
know
those
two
kind
of
things
like
single,
simple,
binary,
installation
installation
with
easy
to
use.
Config,
you
know,
pool
model,
for
you
know
getting
metrics
out
of
things.
K
You
know
like
kubernetes
and
other
systems
and
then
I
think
also.
K
You
know
it
was
fairly
full
featured
like
you
know,
you
had
something
called
alert
manager
where
you
could
set
up
alerts
and
like,
like
it,
had
a
very
clean
user
experience,
alerting
that
you
would
kind
of
get
out
of
maybe
a
more
commercial
offering
and
they
just
kind
of
had
it
all
in
one
in
a
simple
binary
you
can
install
so
I
think,
that's
kind
of
one
of
the
reasons
that
it
was
super
successful,
I
think
also
the
fact
that
it
didn't
come
from
a
traditional.
K
You
know
observability
vendor,
or
you
know,
a
vendor
trying
to
sell
something.
This
is
just
born
out
of
you
know
couple
engineers
at
SoundCloud
that
literally
wanted
to
improve
how
the
observability
in
their
companies
I
think
you
know
that
also
helped
kind
of
you
know
them
build
something
that
you
know
they
initially
didn't
want
to
monetize.
They
just
wanted
to
kind
of
build
something
useful
and
share
it
with
with
the
world
yeah.
A
I
mean
I
was
so
happy
when
you
know
it
took
us
a
little
while
to
get
permission
to
film
at
the
SoundCloud
offices
in
Berlin,
but
it
was
something
we
were
really
pushing
for
with
that
group.
I
think,
as
you
may
recall,
you
know
just
trying
to
get
those
shots
on
site
and
try
to
bring
that
original
team
back
on
site.
B
A
K
K
You
know
over
time
and
you
know
I
think
cncf,
Have,
Been,
instrumental
in
kind
of
sharing
these
stories
of
you
know
successes
with
you
know:
open
source
software
coming
from
end
user
companies,
helping
these
companies
legal
departments
and
Engineering
leadership
coming
up
with
more
efficient
processes
on
sharing
things,
and
you
know,
I
think
if
you
kind
of
look
at
it
at
the
end
of
the
day
like
open
source,
Innovation
could
really
come
from.
You
know
anywhere
it
doesn't
have
to
come
from.
You
know
a
Google
or
like
a
large
vendor,
it
could
come
from.
K
You
know
a
SoundCloud,
you
know
a
Spotify
and
you
know
a
small.
You
know
startup
out
there
solving
interesting
things,
and
you
know
it's
just
great-
that
we're
kind
of
enabling
the
sharing
of
software
and
knowledge
into
this,
like
huge
public
Corpus
out
there,
that
everyone
could
kind
of
learn
from
each
other.
It's
just
been.
You
know,
awesome
I'm,
super
kind
of
thrilled
that
we
were
part
of
that
journey
and
truly
helped
the
Prometheus
project
grow
into
something
that
you
know,
I.
K
Think
literally
people
don't
understand
how
almost
every
new
type
of
service
or
product
out
there
that
has
observability
somehow
built
in
generally
exposes
you
know
a
slash
health
or
some
kind
of
endpoint.
That
Prometheus
could
scrape
it's
truly
kind
of
standardized
across
you
know
the
industry.
It's
truly
truly
truly
remarkable
in
in
many
ways.
A
A
So
my
last
question
so
just
I
know
you
don't
have
your
Crystal
Ball,
but
we're
getting
close
to
the
end
of
the
year
here.
You
know
we're
already
permits
already
the
second
biggest
project
in
CNC,
app
I,
don't
think
is
going
to
overtake
kubernetes
just
yet.
But
what
what
do
you
see
here
as
the
the
future
like?
Where
does
the
project
kind
of
go
from
here?
How
do
you
see
it
evolving
and
and
and
so
forth,.
K
Yeah
so
I
I
mean
I,
see
I,
see
a
couple
or
maybe
a
few
things
happening
like
one.
You
know,
there's
an
effort.
That's
currently
going
on
in
Prometheus.
Is
you
know?
Yes,
every
system
out
there,
like
I,
mentioned
almost
supports
Prometheus.
You
know,
you
know
the
exposition
format
as
a
as
you
know,
through
a
metrics,
you
know,
endpoint,
that's
not
really
like
an
official
standard,
it's
more
of
like
a
de
facto
standard.
In
many
ways,
it's
just
everywhere,
there's
a
lot
of
interest
in
kind
of
making.
K
You
know
that
blessed
format,
a
act
like
an
international
standard
right,
whether
it's
through
the
iatf
or
ISO,
so
I
think
they're
just
going
to
kind
of
see
that
eventually
you
know
happen,
and
that
to
me
is
definitely
a
sign
of
kind
of
like
maturation
and
success,
even
though
like
currently
as
we
speak,
it
is
basically
a
de
facto
you
know
standard
other
things
that
are
kind
of
propping
up
are
there's
actually
now
a
lot
of
you
know:
products
out
there
that
are
offering
managed
Prometheus
like
Amazon.
K
As
you
know,
a
managed
Prometheus
service,
Google
I
believe
has
one
also,
and
so
you
know,
there's
a
desire
to
build
kind
of
a
conformance
effort
out
there
to
ensure
that
there's
consistency
across
these
different
hosted
offerings.
So,
for
example,
in
the
early
days
of
kubernetes,
we
were
very
concerned
about
fragmentation
right,
like
oh,
my
gosh
people
are
going
to
fork
kubernetes
and
every
cloud
is
going
to
have
their
own
kubernetes
and
it's
going
to
be
different
and
it's
going
to
break
workload
compatibility.
K
You
know.
Some
of
that
fear
exists
on
a
minor
level
in
Prometheus,
where
you
know
hey,
maybe
a
cloud
provider.
You
know
a
product
breaks
prompt,
you
can
all
compatibility
so
to
me.
Conformance
programs
are
another
sign
of
like
a
maturity
when
it
comes
to
a
project
and
there's
some
development
happening
in
in
that
space.
For
folks
that
did
not
attend
the
last
prompt
con,
which
is
the
Prometheus
conference.
K
I
highly
recommend
checking
out
some
of
the
videos
where
they
kind
of
discuss
some
of
the
work
going
on
in.
In
conformance,
you
know,
the
other
thing
that
I
kind
of
see
is
there's
a
whole
I.
Would
say
layer
above
Prometheus
with
like
things
like
projects
called
cortex
and
Thanos,
which
are
other
cncf
projects
which
basically
work
on
scaling,
Prometheus
I
think
one
of
the
reasons
Prometheus
is
actually
super
popular.
K
Is
that,
like
it's
a
single
binary,
that's
really
really
meant
to
run
on
one
machine,
that's
great
for
most
developers,
but
if
you're
like
trying
to
build
a
service
or
like
actually
a
scale,
the
thing
to
support
massive
workloads
like
some
people
have
you
need
some
type
of
like
clustering.
You
know
sharding
type
technology
and
so
I
think
in
the
future.
You'll
probably
see
some
of
this.
K
Some
of
these
efforts
out
there
like
cortex
and
Thanos,
there's
actually
others
out
there
maybe
merge
into
one
project
and
maybe
even
become
part
of
the
Prometheus
project
itself
in
in
some
ways,
because
these
things
kind
of
have
matured,
so
I
think
you
know,
you'll
potentially
see
that
happening,
but
overall,
you
know
I
think
they're
in
great
shape
and
truly
one
of
our
you
know
success
stories
and
cncf
and
honestly,
some
of
the
friendliest.
K
You
know,
folks,
you
know
that
I've
kind
of
you
know
met
in
the
early
days
when
we
were
bringing
in
Prometheus
and
the
cncf
I
actually
had
Julius
Falls
one
of
the
creative
state
stay
at
my
house
for
a
week
where
we
just
kind
of
chatted,
and
then
you
know
you
showed
me
some
demos
and
the
idea,
like
you
know,
just
like
great,
like
down-to-earth
people
that,
like
truly
want
to
just
kind
of
you,
know,
help
the
the
state
of
observability
in
in
the
industry.
Yeah.
A
They
were
just
phenomenal
to
work
with
and
I
just
love
that
they
trusted
us
with
this
film
and
be
able
to
share
their
insights
with
us,
and
it's
been
great
well.
Thank
you.
Chris
I
mean
talk
about
insights.
It's
always
a
pleasure
to
just
hear
from
you
and
just
get
your
insights
on
the
community
enjoys
it
and
it
was
a
nice
way
to
sort
of
wrap
up
this
webinar.
A
So
we
want
to
just
thank
everybody
for
watching
and
for
listening,
really
appreciate
you
making
the
time
hope
you
love
the
film
as
I
mentioned
at
the
beginning,
like
we're
hoping
our
next
film
was
going
to
be
Envoy
at
kubecon
cloudnativecon
in
Amsterdam
in
2023,
so
we
hope
you'll
join
us
there
and
and
show
up,
and
we
appreciate
it.
Thank
you
so
much
take
care.
Everyone
bye.