►
From YouTube: Spotlight Live - Thanos
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
A
All
right,
ibartek
welcome
to
spotlight
live.
How
you
doing
thank
you
for
having.
A
Day
so
before
we
get
started,
I'm
gonna
do
some
housekeeping.
Is
that
okay,
you
know
sure
awesome.
So
we
are.
This
is
the
cncf
disclaimer.
This
is
an
official
live
stream
of
the
cncf
and
is
such
a
subject
to
the
cncf
code
of
conduct.
Please
do
not
do
anything
in
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Please
be
respectful
of
one
another.
Another
subject:
that's
very
close
to
our
hearts
by
thick
is
kubecon
kubecon,
north
america.
A
We're
going
to
talk
about
that
in
a
little
bit
folks,
registration
for
kubecon
and
cloud
nativecon,
north
america
2021
is
now
open
for
in-person
and
virtual
explore
all
the
registration
options
go
ahead
and
you
know
there's
a
link.
It'll,
probably
put
the
link
up
hold
down
one
second
and
boom
there.
You
go
I'll
leave
that
up
for
a
little
bit,
so
bartik
we're
talking
thanos
today
I
want
I
want
to
ask
you
a
serious,
serious
question.
A
B
Nice,
nice
good
question,
and
I
think
there
was
a
time
in
the
very
beginning
of
of
this
project,
where
we
were
afraid
to
tell
the
truth,
and
I
talked
to
my
manager.
We
were
trying
to
make
some.
You
know,
marvel
jokes
right
and
my
manager
was
that
from
legal
perspective,
do
not
poke
the
beer,
do
not
poke
the
beer.
I
was
like
all
right.
Okay,
let's
we
had
like
amazing,
you
know
jokes
and
whatever.
So
at
the
end,
we
didn't
joke
too
much.
B
We
were
silent,
but
actually,
when
we,
you
know
proposed
donated
project
to
the
cncf,
they
made
a
proper
furrow.
You
know
copyright,
trademark
checks
and
apparently
there
is
no
trademark
contact
thanos,
so
we
can
joke
around
just
fine,
and
so
I
can
tell
you
the
truth
and
the
truth
is
that
our
you
know
and
my
past
job
at
the
startup.
It
was
called
improbable
amazing,
startup
around
you,
know,
games
and
distributed
systems,
and
we
were
part
of
the
infrastructure
team.
B
We
were
looking
for
some
monitoring
metric
kind
of
solution
that
will
will
solve
our
needs
and
we
will.
B
But
maybe
yeah,
maybe
let
me
finish
the
naming
and
then
I
can
talk.
Okay,
all
right,
all
right
go
ahead
at
the
end,
I
want
to
just
quickly
go
into
the
topic
why
we
even
named
thanos,
and
the
reason
is
that
we
were
having
like
communities
microservices
and
each
of
those
services
used
to
have
some
name
right.
We
we
have
like
a
scarlet
iron
man,
aquaman
and
like
store
and
like
oh
and
and
those
we
are
trying
to
find
a
meaning
right.
B
So
every
time
you
create
a
new
micro
service,
you
were
responsible
to
find
a
correct
name
right
and
we
were.
We
were
kind
of
playing
around
different
names
and
that's
why
it
came
with
thanos
and
I
think
it
to
be
honest.
It
might
you
know
it
might
be
kind
of
feel
silly,
but
actually
I
think
it
contributed
to
some
popularity
right.
B
B
Sure
so
now
we
we
used
to
have
like
a
minor.
I
mean
many
contracts
reflect
smaller
indie
games
and
they
were
actually
pretty
playable
and
the
kind
of
idea
behind
the
the
whole
game
studio
or
like
it's
not
a
game
studio
by
the
way
improbable
is
like
just
a
platform
that
allows
to
game
studio,
to
actually
develop,
games
easier
right
and
actually
it's
still
ongoing
and
the
the
newest
game,
the
scavenger
you
can
kind
of
google
it
around.
B
It's
actually
a,
I
think
it's
a
better,
so
you
can
actually
either
buy
or
even
try
it.
So
the
whole
general
idea
is
that
you
make
a
game
in
a
very
easy
way,
but
actually
you
distribute
this.
B
So
we
have
used
to
have
a
game
called
the
world
adrift,
which
was
actually
pretty
fun
game
where,
where
there
was
like
ships-
and
you
could
like
build
those
ships
and
they
were
flying
around
the
islands
at
the
end,
if
the
ship
was
broken,
the
one
piece
of
the
ship
that
you
could
just
harvest
you
know
fell
down
in
some
island
in
one
year.
You
will
play
this
game
in
one
year
of
real.
You
know
lifetime.
You
will
go
to
this
place.
If
no
one
touched
this
part,
it
will
be
still
there.
A
B
Yeah,
you
kind
of,
were
you
had
to
like
it?
I
guess
you
were
with
us
yeah.
No,
I
like
I
like
I
don't
like
I
mean
I'm,
I
I
would
love
to
have
time
for
comics,
but
I
really
like
the
movies
and
like
this.
This
kind
of
you
know
also
star
wars
also
other
stuff.
So
I
guess
typical
person,
but
yeah.
A
B
Sure
so
thanos
is
a
monitoring
system
at
the
end.
What
it
does
it
you
know,
allows
you
to
collect
metrics,
which
is
which
is
a
certain
observability
signal,
among
others.
So
one
way
of
observing
your
your
software,
how?
What
is
the
state
of
your
software?
What,
if
the?
What
is
the
healthness?
Maybe
you
want
to
trigger
some.
You
know
some
notification
if
something
goes
wrong
and
how
to
define
those
things.
All
of
this
is
part
of
the
monitoring
system,
so
we
allowed
to
to
kind
of
collect
those
metrics
and
store
them.
B
So
it's
at
the
end.
It's
a
distributed
database.
You
can
call
it
and
you
know,
obviously,
as
a
database,
you
can
access
this
data
and
you
can,
you
know,
run
some.
I
don't
know,
alerting
cruise
recording
rules
and
and
really
store
it
efficiently.
So
the
goal
of
thanos
was
to
really
do
what
prometheus
is
doing,
but
just
on
scale
and
then
cheap
and
then
continue
the
same
amazing
functionality
through
like
a
very
stable
prom,
ql
language.
B
It's
like
a
language
of
querying
those
data
which
is
really
really
loved
by
many
many
thinking,
many
people
in
the
community.
B
So
what
we
did
in
in
the
you
know
in
the
essence,
what
we
did
with
thanos,
we
kind
of
took
the
promises
we
split
into
pieces
and
put
into
microservices
right,
and
we
have
similar
functionality
just
scaled
and-
and
this
is
what
makes
it
powerful
right
and
also
highly
available,
and
so
on.
One
additional
thing
that
we
were
we
added
on
top
of.
Let's
say
this
setup
is
you
know
we
had
the
goal
to
make
sure
this
is
cheap,
long
term.
B
So
you
know
in
the
end,
when
you
collect
lots
of
metrics,
you
are
having
lots
of
data
right,
so
you
need
to
have
like
a
cheap
storage
and
we
thought
that
object,
storage,
which
will
which
is
available
on
every
possible
cloud
provider,
and
it's
super
cheap
to
store
data
there.
We
believe
that
you
know
it.
It
is
actually
amazing.
You
know
place
where
you
can
store
all
of
this
data,
especially
because
you
don't
really
use
all
of
metrics.
To
be
honest,
like
you,
you
want
to
cover
them
all,
but
actually
you
use
them.
A
One
of
the
couple
things
I
was
looking
at
the
website-
and
I
know
of
you
all
because
of
you
know
my
what
I
work
on
right
and
so
in
terms
of
like
unlimited
retention.
That's
what
we
were
talking
about.
The
cheap
aspect
that
you
can
throw
this
in
ns3
bucket.
The
global,
clear
query
thing
from
promptql
was
genius
all
right:
it's
the
the
way
that
you
all
interact
so
directly
with
prom
ql.
A
It's
it's
phenomenal,
because
I
can
literally
write
one
promptql,
query
and
query
all
of
these
things
versus
one
disparate
exporter
and
all
these
different
nodes,
which
to
me
is
pretty
goddamn
awesome
like
that
to
me,
is
the
big
draw
of
this,
and
so
like
talk
to
me
about
like
again,
is
what
was
the
problem,
the
original
problem
you
were
trying
to
solve
with
honestly
like
it's
not
like
hey,
you
know
you
just
want
to
make
this
distributed
thing.
It's
like
what
was
the
problem
you
wanted
to
solve
here.
B
That's
a
very
good
question
right,
like
especially
just
doing
something
distributed
for
fun
is,
is
the
the
biggest
anti-pattern
ever.
You
should
avoid
doing
this,
like
it's
a
complexity,
it,
it
is
actually
complex.
Any
distributed
system
can
have
complex
situations
right
and,
to
be
honest,
yeah
global
view
was
the
main
main
goal
here
and
I
think
the
the
fortunate
situation
or
like
unfortunate
that
triggered
this
project
was
that
at
improbable
to
accommodate
those
different
game
studios
and
maybe
players
on
different
continents
and
different
locations.
B
We
were
running
like
30
communities
clusters
in
the
very
beginning
of
kubernetes,
to
be
honest,
like
we're
running
with
this
ourselves-
and
you
know
that
was
a
problem
at
the
end
for
a
metric
system
because,
like
prometheus,
that
was
supposed
to
be
localized
is
that
you,
we
suddenly
have
30
clusters,
so
you
need
to
have
a
global
view,
bird
eye
view,
whatever
you
call
it
to
gather
all
those
information
and-
and
we
really
wanted
to
aggregate
so
some
applications.
B
Some
game
could
flow
between
clusters
and
get
migrated,
and
all
of
this
is
part
of
the
same
application.
So
I
would
love
to
have
informations
and
aggregations.
You
know
no
matter
where
it
is
all
right
so
and
to
be
honest,
it
was
like
four
or
five
years
ago,
almost
not
almost
like
literally
five
years
ago,
when
I
joined
improbable
and
we
we
had
those
problems.
B
This
is
this
was
like
very
beginning
of
you
know
the
whole
world
starting
to
noticing
those
problems
right,
because
when
I
am
now
kind
of
architect
in
red
hat
for
for
observative
things,
then
the
main
problem
right
now
are
and
not
only
observability
problems
but
anything
else.
Hey.
We
suddenly
have
multiple
clusters.
We
treat
clusters
as
a
cattle,
not
as
a
pet,
which
means
that
we
kind
of
create
them
and
destroy
them
in
a
second
right.
B
So
this
was
never
a
problem
before
and
now
everyone
is
moving
in
this
direction,
so
those
federated
solutions
are
must
have-
and
this
is
why
you
know
thanos
were
were
born
in
the
burned
in
a
or
like
burnt
born
in
a
in
a
correct
moment
right
and
because
we
maybe
were
were
having
those
issues
prematurely
prematurely,
then
than
other
companies
right.
A
That's
incredible
and
again
it's
like
you
were
definitely
the
early
adoption
aspect
and
then
being
able
to
like
take
that
and
then
you
know
something
you
gave
to
the
masses.
Let's,
let's
talk
about
that
for
a
second:
when
did
you
decide
hey,
you
know
what
let's
take
this
thing
it
opens
in
probable,
like
you
all
open
sourced
it
pretty
much.
Was
that
an
early
decision
were
you
like?
Let's
do
this
like
who
who
who
helped
that.
B
Oh
yeah,
that's
that's
extremely
good
question
because
having
an
open
source
project
and
like
doing
open
source
things
for
especially
a
startup,
a
very
focused
startup
with
minimal
amount
of
engineers
has
is
like
a
huge
investment
and,
to
be
honest,
it
would
not
happen
if
not
somehow
prometheus
community.
Let's
say
because
how
the
project
started
is
that
we
have
this
problem
of
like
hey.
We
need
federated
monitoring
system
and
we
want
to
have
long-term
storage
and
cheap
operational
costs
and
high
availability,
and
we
already
used
prometheus.
B
So
that's
a
great
system
that
we
just
want
to
build
upon
and
we
tried
different
things
and
at
the
end
it
was
fabian
raynard's.
Like
amazing
engineer
now,
working
at
google.
He
had
this
idea
that
maybe
you
can
use
object,
storage
and
we
can
use
exactly
the
same
format
as
primitives.
B
I
don't
know
how
it
looks
like,
but
I
feel
this
will
work
who
wants
to
pay
for
this
work
and
improv
was
like
yeah.
Let's
meet,
we
we
kind
of
met
in
the
kubecon
at
some
point
2016
or
17
yeah.
We
just
started
collaboration,
so
he
kind
of
stopped
his
work
at
coreos
and
for
three
months
got
contracted
by
improbable,
and
I
was
kind
of
the
engineer
working
on
observability,
so
I
kind
of
joined
this
effort
and
his
main
kind
of
because
he
was
part
of
prometheus
team.
B
His
main
criteria,
for
even
you
know,
joining
this
collaboration
was
hey.
This
has
to
be
open
source
from
scratch,
so
to
be
honest,
improv
was
was
not
even
thinking
twice
because
it
was
very,
I
mean.
B
Well,
maybe
they
were
thinking
about
this,
but
what
I
mean
is
that
they,
it
was
not
like
a
huge
conversation,
because
there
was
a
you
know,
someone
willing
to
do
it,
someone
capable
of
doing
and
some
some
some
good
idea
and
his
requirements
was
to
to
have
it
open
source
and
there
was
there
was
no
strong
feelings
to
to
to
make
it
no
right
but
like
that
was
that
way
it
was.
I'm
super
grateful
that
improv
will,
like
you
know,
accepted
that
offer
for
and
and
kind
of
we
we
collaborated.
B
We
designed
everything
and
in
three
months
we
shipped
this
to
be
honest,
like
in
in
obviously
like
basic
form,
but
the
truth
is
like
he
left,
like
this
contract
or
think
went
to
google
and
for
politic
well
for
legal
reasons.
He
could
he
couldn't
even
contribute
again
to
to
thanos.
So
I
was
kind
of
continuing
this
work
and
really
this
is
where
the
true
you
know,
investment
from
improbable.
B
Actually,
you
know
appear
right
this,
because
this
is
the
moment
where
you
need
to
ongoing:
do
ongoing
investment
on
community,
getting
more
people
involved
and
and
just
paying
this
engineer,
to
kind
of
look
on
those.
You
know
contributions
and
and
really
open
source
factors,
and
this
is
where
improbable,
where
we're
kind
of
doing
some
of
it,
and
I
mean
super
grateful-
and
this
is
why
this
is
super
successful.
But
at
the
end
I
had
to
sacrifice
a
lot
of
free
time
too.
A
You
know
that's
the
nobody
talks
a
lot
about
about
that
like
in
terms
of
like
open
source,
like
you
know
like
it
ends
up,
there's
the
superstars
and
the
core
maintainers
of
certain
projects.
You
know
I
we
I
work
on
falco,
right
and
so
like
there's,
there's
parts
of
this
where
it's
literally
like
you
know,
there's
core
maintainers
like
lorenzo
and
leo
and
folks
on
my
side
that
are
just
you
know,
killing
and
doing
so
much
work
and
stuff
like
that.
A
A
B
Let
me
think
about
that,
so
I
think
you
know.
First
of
all,
it
was
definitely
very
important
to
start
like
building
community,
so
I
know
I
spent
many
many.
I
know
hours
to
just
talk
to
different
people
and
collaborate
and
really
establish
some
kind
of
process
that
will
just
gather
more
people
gather
more
community
because
looks
like
the
project
got
some.
B
You
know
movement
people
started
to
use
it
adopt
it,
but
you
know
it's
hard
to
motivate
anyone
from
those
companies
to
actually
even
mention
they
are
using
it.
That
was
really
a
blocker
for
for
some
people,
so
I
knew
that
internally,
you
know,
you
know
huge
projects
are
which
companies
are
using
channels,
but
I
couldn't
even
speak
about
that
because,
legally
whatever
so
at
the
end,
it
was
very
hard
work
to
and,
like
maybe
you
know,
a
little
bit
of
strategy.
B
You
know
tactical
thinking
and
maybe
some
discussions
around
how
to
get
those
people,
those
companies
to
contribute
or
even
share
that
they
are
using
or
share
some
feedback.
That
was
the
first
step.
The
second
step
was
to
actually
have
and
start
really
a
secure
environment
for
people
to
speak
up,
and
I
was
really
again-
I
was
like
you
know,
true,
open
source
developer,
a
synchronous
work,
no
slack,
no
chat
like
this
is
like
not
efficient.
I
don't
want
to
do
it
at
some
point.
B
I
was
like
okay,
whatever,
let's
create
the
slack
channel,
and
actually
I
was
that
was
actually
the
stepping
that
the
trigger
for
actual
contributor,
because
there
are
so
many
people
who
are
afraid
to
ask
maybe
silly
question
in
github
issue
because
for
them
github
issues
like
wow
huge
proposal.
No,
it's
not
for
us.
It
would
be
fine
if
they
would
just
ask
this
question,
but
they
were
just
looking
for
this
easy.
B
You
know
small
step
where
which
was
just
slack
and
and
just
hey,
crea,
just
just
say
something,
and
then,
with
with
this
momentum,
people
started
to
help
each
other,
and
this
was
a
trigger
for
actual
community,
and
I
I
cannot
say
this.
You
know
enough.
Just
start
this.
Damn
chat
like
you
have
to
have
it
like.
There's,
no,
you
you
might
not
like
it.
You
might
like.
B
Irc
who,
by
the
way,
no
one
use
irc
this
time
around,
so
you
need
to
have
a
slack
right,
there's
no
other
way
and
or
whatever
is
the
most
popular
kind
of
chatting
platform,
but
in
the
in
the
end,
that
was
a
major
goal
and,
of
course,
a
major
sorry
step
and
of
course
you
know
trying
to
get
maintainers.
So
having
contributor
is
one
thing,
but
then
how
to
get
that
step,
and
there
is
this
balance
between
hey.
I
want
to
have
some
bar
of
the
maintainer
they
has
to
know
about.
B
You
know
this
stuff.
They
have
to
be
friendly.
There
is
so
much
it's
like
an
it's
like
a
hard
interview
to
pass,
except
that
you
don't
have
money
after
that
right,
so
it's
really
challenging,
but
you
just
need
to
show
value.
I
think
mentoring
help
as
well.
We
have
lots
of
maintainers
based
on
the
mentorship.
We
do,
and
literally
all
of
our
mentees
have
like
a
nice
job.
So
so
I'm
super
happy
with
that
with
the
effect
of
it.
So
you
know
mentorships,
community
and
and
kind
of
having
a
safe
space.
B
So
people
can
see
the
value
like
they
see.
Oh,
I
will
now
maintain.
Oh
now,
many
companies
want
to
hire
me
because
I
have
have
this
skill
and
that
was
the
trigger
of
you
know.
Oh,
this
is
actually
valuable
to
be
like
a
maintainer
and
sometimes
we.
What
I
recommend
is
that
you
know
it's
rarely
the
case
that
a
person
have
a
is
familiar
with.
The
whole
code
base
try
to
figure
out
like
one
portion.
Okay,
you
are
a
maintainer
for
this
particular
you
know
part.
B
So
at
least
you
help
on
this
on
this
position
like
front
end,
for
example-
and
you
don't
need
to
you
know,
know
about
like
everything
else,
but
you
at
least
meet
like
those
criteria,
and
we
have
the
occasion
when
you
know
we
join
well.
We
we
get
someone
as
a
maintainer
and
he
immediately
got
the
job
right
like
in
sre
space,
because
you
know
he
know
he
knew
that
he
was
part
of
the
tunnels.
B
So
someone
someone
someone
told
me
once
because
there
was
some
interview
of
someone
and
then
in
some
company
and-
and
he
didn't
have
a
lot
of
even
questions.
B
He
just
said
I'm
thanos
contributor,
on
something
and
or
like
maintainer,
and
someone
said
from
this
interview
or
this
company
said
we
don't
need
to
check
you
that
much
you
maintain
tunnels,
you
we
know
you
cannot
be
a
so
I
mean
that's
a
good,
that's
a
good
actually
value
as
a
maintainer.
I
guess
so
so
this
is.
Those
are
some
motivation
points
where
you
can
bring
right.
A
If
there's
projects
and
again
so
you
know,
thanos
is
an
incubated
project.
The
falco
is
an
incubator
project.
This
project
anybody's
watching
this.
I
think
exactly
what
he
said.
It's
like
you
know.
Having
that
being
able
to
ask
those
questions
showing
grad
of
gratitude,
I
think,
is
the
biggest
thing
is
like
hey.
Thank
you
for
doing
that.
Thank
you
for
putting
this
in
here.
We,
you
know
we
send.
A
We
have
a
contributor
of
the
month
is
what
we
do
and,
and
basically
we
send
some
swag
out
to
them,
and
we
say
thank
you
so
much
it
because
you
know
people
are
taking
time
out
of
their
day.
This
isn't
their
day
job
their
day,
job
isn't
maintaining
thanos,
thanos
or
falco
or
cube
it's
not
out
of
that,
and
that's
the
part.
I
think
that
you
know
any
any
burgeoning
projects
in
the
sandbox.
B
Totally,
I
want
to
add
to
this
point
because
we
had
for
some
time
and
there
it
was
like
a
contributor
idea
to
every
friday.
B
We
actually
have
an
issue
even
open
to
create
a
bot
for
this,
but
probably
both
will
be
not
like
rewarding,
but
but
still,
if
I
think
there
is
enormous
help
that
people
do
and-
and
it
allowed
me
to,
for
example,
focus
on
delegating
and
and
teaching
and
and
all
the
stuff,
and
I
don't
need
to
be
constantly
on
the
main
tunnels
user
channel,
because
people
are
helping
each
other.
So
it's
enormous
right
and
there
is
health.
B
Would
be
nice
still
some
kind
of
kudos
spot,
whatever
right,
yeah.
A
Man,
I
like
it
carlos
panado,
if
you're
watching
this
get
that
bot
ready
come
on,
got
some
work
for
you,
my
man
all
right,
so
I'm
gonna
ask
you
this,
because
you
know
again,
I'm
in
the
space.
You
know
I
work
for
cystic.
You
know
we
have
like
a
back
in
store
for
for
metrics
and
and
also
like,
obviously
runtime
security
stuff
with
falca
and
cystic
secure.
A
But
there's
one
thing
is
like
I've
seen
there's
a
lot
of
other
projects
that
have
very
similar
kind
of
you
know
traits
right,
it's
kind
of
a
store
for
metrics
right,
we
think
of
like
cortex
or
m3.
What
do
you
think
like
that?
But
I
always
hear
thanos
it's
kind
of
this
is
the
thing
this
is
the
the
key
kind
of
flagship
store.
So
my
question
to
you
is:
what
differs?
What
makes
what's
the
difference,
what
makes
you
stand
out
besides
those
other
tools.
B
Yeah,
that's
that's
a
you
know,
tough
space
to
be
in
right
like
there
is.
There
is
so
much
demand
that,
by
the
way,
there
is
a
place
for
everyone
like
if
every
of
those
projects
will
have
like
a.
I
don't
know
like
found
a
company
behind
that
like
we
would
still
have
customers
enough
customers
right.
So
that's
a
good
thing
like
there's
still
place
for
this.
For
this
competition.
It's
not
like
it's
a
very
niche.
B
However,
you
know
there
are
still
differences
and,
first
of
all,
yeah
there
is
a
demands.
There
are
different
people
having
different
ideas
about
how
the
back-end
should
work
right
so,
and
I
think
what
is
very
unique
in
thanos
is
that
we
really
grown
this
solution
from
prometheus
project
itself.
So
we
use
you
know
native
protocols,
we
stick
to
the
native
apis,
but
even
on
storage.
Everything
is
the
same.
So
you
what
we
do
literally
internals
is
like
we
combine
everything
into
this.
B
Those
tsdb
whatever
time
series
database
of
promote
use,
blocks
which
are
our
directory
of
files,
and
we
literally
kind
of
put
it
in
object
storage.
So
if
you
would
download
the
thing
and
run
promptus
on
top
of
it,
it
would
just
work
right.
It's
exactly
the
same,
and
this
is
super
powerful
because
we
could
leverage
the
same
tooling,
the
same
knowledge
that
prompted
you
spent
six
years
or
seven
to
teach
people
about
right.
So
pronquel
is
one
of
the
most.
You
know
the
most
powerful
and
flexible.
B
You
know
metric
querying
language,
but
it's
also.
It
has
a
steep
curve
of
learning
like
yes,
every
you
know,
sequel
or
whatever
other
languages
right.
So
since
people
already
adopted
that
it
was
much
easier
to
use
this
right.
So
that's
why
all
those
decisions
were
optimized
for
this.
You
know
in
integrity
and
also
it's
worth
mentioning
that
you
know
we
treat
this
as
a
family,
so,
for
example,
when
our
students
or
our
you
know,
maintainers
on
contributor,
they
especially
mentees
like
they
want
to.
B
You
know
they
have
a
project
and
task
to
do
a
feature
to
do
on
thanos.
We
say:
hey
contribute
this
to
prometheus.
First,
maybe
we
can
share
that.
We
can
reuse
that,
with
with
promote
use
code,
there's
community
there's
other
people
who
can
take
a
look
on
that
and
if
you
contribute
during
this
time
into
pro
materials,
we
count
this
as
a
contribution
to
thanos,
because
we
literally
the
we're
literally
importing
the
same
code.
So
this
reusability
was
very
important
for
us
because
we
don't
we
we
don't.
B
You
know,
program
the
prom
ql
engine
from
scratch,
like
a
compaction
from
scratch,
storage,
format,
reading
and
writing.
Those
are
very
complex
pieces
of
code
like
like
literally
unreadable,
sometimes
because
it's
so
optimized,
it's
memory,
mapping,
it's
so
so
much
stuff
and
we
directly
import
this
code
right,
and
this
is
very
unique
right
because
there
are
so
many
companies
that
m3db,
like
amazing
system,
came
from
uber.
So
you
know,
uber
has
to
create
something,
like
I
don't
know
like
five
years
ago
from
scratch,
because
there
was
nothing
there.
B
So
no
one
blamed
them
to
to
have
like
a
solid
system.
They
want
to
share
and
open
source.
So
it's
great,
and
actually
they
are
very
you
know,
happy
to
collaborate,
and
then
they
are
adding
integration
points,
so
they
are
supporting
from
ql.
B
They
are
supporting
a
write
protocol,
so
you
can
send
data
from
primitives
to
to
m3b
not
only
to
thanos
and
the
same
with
cortex
codex
is
special
because
it's
kind
of
grown
from
the
promotions
maintainers
just
different,
primitive
maintainers,
and
it
was
actually
created
one
year
before
thanos
and
you
know
we
would
love
to
use
it
and
we
tried
in
temple
to
use
it
and
it
didn't
work,
but
I'm
I'm
we
are.
We
are.
B
B
There
are
some
technical
things
that
we
want
to
try
out
and
and
in
practice,
what
we
see
is
that
our
teams
collaborate
very
much
like
we
have.
You
know:
cortex
maintainer,
marco
estanos
maintainer,
for
example.
I
was
contributing
to
cortex
many
times.
I
know
it's
codebase,
because
they
actually
import
thanos
code
and
we
import
their
code
and
like
we.
This
is
great
collaboration
that
end
up
with,
like
massive.
A
A
Why
I
have
an
m3
or
excuse
me
a
thanos
when
you
can
kind
of
integrate
these
if
everybody's
working
on
them,
because
it
almost
confuses
the
end
user,
but
is
it
because
of
like
you
said
it's
it's
the
context
each
one
is
is
providing
it's.
Each
one
has
a
different
thing
that
it's
doing
to
a
certain
degree.
B
At
the
end,
they
are
doing
similar
things.
There
are
minor
feature
differences,
but
at
the
end,
especially
cortex
and
antennas,
we
really
maintain
the
same
apis
and
stuff,
and
nowadays
we
have
the
same
storage
with
some
differences,
and
so
this
is
a
very
good
question,
but
I
will,
I
will
ask
you
you
know:
would
you
like
to
you
know
your
focus
project
like
cortex
or
thanos,
and
would
you
like
to
suddenly
adopt
you
know
100
000
lines
of
tech,
depth,
right
and
and
for
for
for
cortex
team?
B
It
would
be
adapted
to
have
thanos
kind
of
components
in
code
for
thanos.
It
would
be,
you
know,
cortex
code,
so
at
the
end,
this
is
a
significant
work
and
to
to
merge
those
things,
and
we,
we
kind
of
you
know,
talk
about
many
many
times,
but
I
want
to
show
the
advantage
of
all
of
this,
like
we
learn
from
each
other.
So
much
right,
we-
and
I
was
talking
about
many
times-
is
that
we
we
we
collaborate.
I
know
what
they
are
working
on.
B
They
are,
they
know
what
we
work
on
and
you
know,
for
example,
it
allowed
cortex
to
totally
not
don't
work
on
down
sampling
right
because
they
hey
hey,
we
tunnels
have
it
and
we
will
kind
of
integrate
that
if,
if
it
will
be
needed,
so
they
can
experiment
on
that
right.
We
are
not
doing
any
shuffle
sharding
like
they,
the
cortex
is
doing
and-
and
maybe
they
kind
of
chosen
a
different
direction
of
compaction.
I
don't
want
to
go
too
low
level
details,
but
essentially
they
are
using
small
blocks.
B
We
are
doing
large
blocks
and
you
know
those
are
different
trade-offs,
so
being
able
to
simultaneously
kind
of
experiment
with
those
two
paths.
In
the
same
time
it
it
was
actually
enormous
enormous.
You
know
a
value
for
for
all
of
us,
so
we
make
different
decisions
because
our
teams
have
a
different
culture.
We
are
diverse,
so
it
actually,
you
know
because
we
treat
each
other
friendly
and
we
kind
of
reuse
each
other
code.
If
it's
useful.
This
is
super
super
massive
massive
help
so
far
right
nowadays.
B
Nowadays,
I
see
cortex
maintainers
very,
very
busy
right
like
they
got
this
amazon
kind
of
user
and
I
don't
think
they
kind
of
contribute
back
so
cortex
maintainers
are
trying
to
hide
things.
So
there
are
some
interesting
stuff
going
on
and
I
think
it's
it's
worth
to
see
that
as
a
lesson
as
well
how
how
that
really
evolves,
but
so
far
it's
it's
a
super
useful
project
and
and
yeah
just
check
it
out.
What
what
do
you
do?
You
do
you
need,
from
the
user
perspective,
all
right.
A
No
worries
yeah,
it
makes
complete
sense.
So
I'm
going
to
ask
a
question
about
just
a
lake
somebody-
and
this
is
probably
something
you
should
probably
go
on
raw
codes
lgtm.
But
how
does
somebody
contribute
and
get
involved
in
thanos
at
some
point
shameless
plug?
I
shouldn't
be
plugging
that
guy
we're
mortal
enemies
but
go
ahead.
You're
competitors
right
we're,
not
competitors.
I
have
one,
that's
it
so
anyway.
Moving
on.
B
Let's
go
yeah,
so
it's
actually
very
easy.
Just
go
to
the
thanos
io
and
click
the
community
button
and
you
should
have
beautiful
documentation.
What
steps
you
could
you
could
do
to
maybe
pick
your
first
issue
or
maybe
you
are
you
want
to
give
a
nice
feedback
or
maybe
you
want
to
help
us
to
create
tutorial,
or
maybe
you
want
to
share
your
case
study
or
blog
post
or
or
any
talk
that
you
made
around
thanos
and
our
project
and
what
we
do,
and
maybe
you
want
to
be
mnt,
I
we
are
doing
heavily.
B
We
are
heavily
investing
in
mentorship
and
we
are
doing
those
sessions
every
I
mean
three
times
a
year
and
like
this
year
we
have
like
four
mentees,
and
now
we
have
another
four.
B
So
it's
kind
of
madness,
and
but
like
it's
super
useful
for
everyone,
I
think
so
what
you
can
do
just
just
really
apply
for
those
programs,
because
by
the
way
those
are
not
for
students
like
you
might
be
very
skilled,
smart
engineer
who
is
like
in
like
some
close
source
company,
which
you
know
doesn't
give
you
lots
of
opportunity
to
to
be
part
of
the
community,
and
you
want
to
just
try
to
join
open
source
effort,
and
maybe
I
don't
switch
a
little
bit
and
the
focus
we
would
like
to
show
you
the
value
we
have
so
many
like
senior
engineers,
for
example,
jessica,
on
the
prometheus
mentorship
program
like
we,
we
she
was
working,
full-time
and
still
participating
as
a
mentee,
and
I
was
super
useful
for
her
to
learn
how
to
how
open
source
looks
like
right.
B
A
B
Yeah,
why
not
right,
I
think,
yeah
exactly
the
question
is
why
not
like,
I
think
you
know
people
still
learn
a
lot
from
books
like
technical
books.
I
I
love
reading
them
and
especially
if
it's
about
like
generic
programming
whatever
or
like,
maybe
technology
that
doesn't
really
get
obsolete,
that
quick,
it's
it's
worth
reading,
but
no
one
really
write
books
like
we
have
only
those
fancy
people
who
are
doing
streams
right
but
and.
B
B
Just
kidding
like,
I
think
I
think
it's
just
you
know
more
rewarding
to
do
a
video
more
consumable
for
users.
So
I
really
understand
this
effort,
but
I
think
it's
not
many
people
write
book
right
and,
and
it's
not
sexy
anymore,
and
I
talked
I
really
wanted
to
find
a
cora
co
outer-
and
I
really
found
I
mean
frederick-
is
helping
me
for
the
ring
brunchik,
who
is
now.
A
B
Yeah,
I
don't,
I
don't
know
anyone
who
doesn't
like
frederick.
I
don't
think
anyone
such
like
that
exists.
So
frederick
is
amazing
person
and
he
agreed
to
write
one
chapter
with
me.
So
that's
that's
amazing,
about
profiling
by
the
way,
because
he's
creating
this,
you
know,
he's
the
ceo
of
the
polar
signals,
a
company
behind
profiling,
continuous
profiling
and
stuff.
So
anyway-
and
you
know
I
was
trying
to
find
a
co-author
and
it
was
so
hard
to
because
everyone
was
calculating
money.
B
I
was
like
oh,
this
will
take
me
500
hours
of
my
you
know,
and
this
means
this
money
and
oh,
I
don't
see
this
happening
right.
So
I
really,
if
you
do
it,
usually
you
really
do
it
for
for
just
maybe
values
of
of
teaching
others
and
yeah
other
stuff.
So
to
be
honest,
my
other
motivation
I
want
to
share
is
that
there
was
import.
B
Maybe
people
from
you
probably
would
laugh,
but
there
was
this
kind
of
spreadsheet
and
probably
is
like
many
of
us
are
having
this
in
companies
where
we
want
to
share.
Who
is
good
at
what
thing
and
there
is
a
spreadsheet
with
like
a
scale
from
0
to
10,
where
0
is
like?
I
have
no
idea
what
this
technology
is
about
and
10
is,
I
wrote
a
damn
book
about
it,
so
I
want
to
be
10
right.
B
I
was
always
like
eight
and
like
in
gold,
like
whatever
I
was,
and
I
write
book
about
golang
and
performance.
I
didn't
share
the
title.
I
don't.
I
didn't
even
share
really
publicly
what
it
is
about.
So
I
slowly
started
to
start
to
talk
about
that,
but
I
really
really
wanted
to
try
this
out.
A
Well,
do
it
best
of
luck
and
I'll
probably
end
up
having
you
on
the
podcast
and
we
can
talk
about
it
live
when
when
it's
about
to
launch
I'll,
probably
buy
like
10
copies
and
give
them
away
see.
That's
just
just
that's
that's
the
thing
I
do
man
anyway,
so
I
guess
a
question
from
my
man
naren
thanks
for
being
on
the
for
joining
the
stream,
but
can
newcomers
to
kate's
utilize
thanos
or
is
it
focus
on
the
enterprise
use
case.
B
Yeah
good
question:
actually,
I
would
say
it's
mainly
for
cubanist
customers
because
well
it's
in
the
cncf
kind
of
ecosystem,
so
it's
kind
of
communities
is
that
our
main
targeted
orchestration
system.
Of
course
we
make
it
sure
it's
like
a
containerized,
so
you
can
run
it
everywhere,
but
we
have
some
special
discovery
mechanism
and
things
that
makes
it
much
easier
to
work
on
kubernetes
and
it
is
actually
used
a
lot
in
the
smaller
companies,
and
I
seen
this
and
I
I
will
tell
you
why.
B
B
So
then
you
install
additional
two
micro
services
and
then,
if
you
say
oh
now,
I'm
a
super
user
and
I
want
like
multi-tenant
and
like
amazing
scalability,
then
I
can
think
about
maybe
receiver
and
maybe
remote,
right,
replication
and
and
there's
like
lots
of
steps.
You
can
do.
You
can
mix
all
of
this.
So
it's
very
actually
welcoming
for
just
experimentation,
different
parts
and
and
not
implementing
everything
and
getting
you
know
immigrating
and
like
all
those
big
step,
we
are
iterating
right.
Trying
to
have
this
process
of
iteration.
A
B
Oh
man,
I
think
it's
really
something
related
to
what
you
said
that
you
know
it's.
It's
very
important
to
delegate
at
some
point
right
the
work-
and
I
think
I
I
we
built
like
an
amazing
team
right
now
in
thanos,
where
I
can
go
to
vacations.
Finally,
right
and-
and
you
know
I
can
focus
on
on-
maybe
some
more
advanced
stuff-
and
maybe
you
know
I'm
active
in
the
sick
or
like
tag
observability
now
as
a
technique,
I'm
writing
book
and
I'm
doing
lots
of
stuff
around
observability
for
different
signals.
B
I
yeah
I
have
passion
to
to
kind
of
improve
this
step
and
make
use
of
pool
based
kind
of
observability
collection
mechanisms
better
and
so
on.
So
that's
the
future.
For
me,
I
would
say
I
would
love
to
explore
those
things
while
making
sure
tunnels
can
integrate
into
that.
Well,
for
example,
we
created
a
new
project
called
observatorium.
B
I
can
plug
that
right
and
observatorium.io
just
literally
go
there
and
you
can
see.
This
is
like
a
platform
which
allows
you
to
deploy
tunnels
with
other
observability
signals,
because
at
the
end
you
want
metrics
sure.
But
you
know
there
are
other
cool
stuff,
like
logging,
everyone
logs
everyone
do
at
some
point
some
tracing
and
continuous
profiling,
and,
to
be
honest,
you
can
totally
you
know,
combine
all
of
this
and
we
are
making
sure
as
autonomous
we
integrate
with
other
signals,
making
sure
the
correlation
story
makes
sense.
B
You
can
jump
from
the
metric,
you
can
say
you
can
have
an
alert
and
you
have
some.
You
know
amount
of
errors
for
some
service.
You
are
on
call
and
there
is
incidents,
and
then
you
know,
but
what?
What?
What
are
the
errors
like?
What's
going
on
you?
Could
you
click
the
exemplar
which
is
kind
of
the
way
to
link
into
the
tracing
example
situation
that
happened
in
your
actual.
B
You
know
container
in
a
actual
binary
things
of
the
tracing
and
and
this
exemplars
kind
of
support,
and
then
you
jump
into
trace
and
see
exactly
who
and
what
error
happened
and
in
what
kind
of
circumstances.
So
those
correlation
capabilities
is
when
you
have
like
a
consistent
model
of
you,
know:
configuring
different
systems.
B
So
that's
why
observatory
was
was
created
and-
and
we
know
it
takes
some
time
to
integrate
tunnels
with
those
other
systems
making
sure,
for
example,
exemplars
are
supported
and
they
are
in
some
way,
but
we
want
to
kind
of
extend
this.
B
So
all
of
this
is
kind
of
grown
out
of
thanos,
and
this
is
really
also
you
know.
Best
practices
grow
right.
We
are
starting
thanos,
I
mean
cncf
meetups,
like
literally
today
we
have
the
first
one,
so
mantis
meetups,
how
what
we
mean
since
the
augmented
meetup,
which
we
mean
is
a
series
of
meetups,
where
we
want
to
make
sure
mentees
have
like
a
way
to
practice
public
speaking,
but
also
learn
the
I
mean,
teach
them
about
the
learnings
they
get
and
we
get
from
the
mentoring
as
well.
B
So
we
want
other
cncf
project
to
also
participate
in
this
group,
and
I
had
a
link
somewhere,
but
I
don't
have
it
right
now
so,
maybe
later
I
can
send
it,
but
at
the
end
we
are
doing
those
things,
and
you
know
I
mean
there
are
so
many
good
best
practices
that
came
out
of
tunnels
like
including
book
right.
This
is
why
I
write
this
book
because,
like
not
many
people
know
how
to
optimize
go
right,
so
this
is
another
step
that
I
want
to
focus
on.
B
A
A
All
right
all
right,
thank
you
so
much
biotech
for
being
on
the
spotlight.
I'm
gonna
do
some
housekeeping
and
I'll
basically
go
here.
We
are
everyone.
So
next
week
on
monday,
we
have
duffy
cooley
he's
the
this
week
in
cloud
native,
we're
gonna
be
talking.
Also
tim
tim
banks
is
on
solid
state,
and
then
we
have
cloud
native
latinx
bunch
of
shows
next
week
a
lot
of
fun.
You
all
thank
you.
So
much
remember
to
follow.
Please
make
sure
to
follow
the
the
cloud
native
here,
the
twitch
channel.