►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
everybody
good
morning
well
it's
morning
for
me:
it's
7
12
in
the
morning
for
me
for
my
guest,
it
is
much
later
in
the
day,
but
my
name
is
cat
cosgrove,
and
this
is
the
road
to
cubecon
in
the
run-up
to
kubecon.
We're
doing
a
few
special
shows
interviews
with
people
talking
about
some
of
the
colo
events
talking
about
cncf
projects
in
a
little
bit
more
detail
than
we
might
otherwise
and
on
and
on
and
on.
A
But
first
I
have
to
say
that
this
is
an
official
cncf
live
stream,
which
means
all
of
us,
including
you
in
the
twitch
chat,
are
beholden
to
the
cncf
code
of
conduct,
which
essentially
boils
down
to
just
be
nice
to
each
other.
Please,
anyway,
again,
I'm
kat-
and
I
am
joined
today
by
richard
hartman
richard
good
morning,
good
afternoon,
how's
it
going.
A
I'm
all
right
so
we're
here
to
talk
about
prometheus
observability
and
specifically
we're
here
to
talk
about
prom
con,
but
first
of
all,
usually
when
I
host
these
shows
it's
a
very
like
101
level
thing
where
I
either
actually
don't
know
what
a
project
does,
or
I
pretend
that
I
don't
know
what
a
project
does
to
try
to
get
a
more
like
broad
kind
of
junior
level.
I
don't
have
any
surrounding
context.
Understanding
of
what
a
tool
is
so
can
you
tell
me
a
little
bit
about
prometheus
yeah.
B
Prometheus
is
a
time
series
database.
Basically,
you
record
values
which
change
over
time.
It
might
be
temperature
at
your
home.
It
might
be
the
number
of
times
you
opened
your
door
and
both
of
those
are
not
the
cloud
native
examples,
but
they're
rather
easy
to
to
to
visualize,
basically
prometheus
stores
event.
No,
let
me
start
it's
a
time
series
database,
which
stores
only
numeric
data,
so.
A
B
Have
events
you
can
collapse
them
into
numbers
like,
for
example,
counting
things
or
similar,
but
it's
all
numbers,
which
means
you
can
do
math
with
everything
which
is
stored
within
prometheus
as
prometheus
has
its
own
language,
with
which
you
can
query
the
data
and
visualize
the
data
and
export
it
via
api
and
generate
alerts
and
everything.
You
have
this
one
functional
language
to
do
actual
vector
math
on
your
data
and
it's
pretty
quick
and
pretty
successful.
Other
things
no
yeah.
B
Well
I
mean
it
has
the
same
label
system
as
kubernetes,
which
is
kind
of
convenient.
It's
very
convenient
almost
as
if
pork
and
pork
one
had
been
designed
for
each
other
yeah.
Sorry
for
the
101
content.
There
are
two
projects
within
google
borg
and
borgmonborg
is
the
orchestrator
and
borg
modesty
monitoring
thing
and
the
open
source
equivalents
are
basically
kubernetes
and
prometheus.
B
A
That
actually
was
a
very
thorough
intra-level
explanation.
Thank
you
for
that.
I
appreciate
it.
I
also
think
that
prometheus
has
one
of
the
coolest
logos
in
the
cncf
landscape.
It's
just
it's
very
pretty.
It
stands
out
so
props
to
whoever
designed
that
logo,
but
you
have
a
colo
event
for
kubecon.
Cubecon
is
coming
up,
I'm
flying
down
there
next
week.
I
assume
you
will
not
be
there
right.
No
will
you
be
there
virtually.
A
A
A
Oh
we'll
definitely
get
accept,
get
it
accepted
somewhere
like
we're,
we're
not
gonna.
Let
that
one
die
on
the
cutting
room
floor.
That's
that's
gonna
happen.
So
if
anybody
watching
this
later
wants
to
listen
to
me
and
celeste
horgan
talk
about
communications
and
docs
writing
for
small
open
source
projects
from
the
perspective
of
an
anime
hit
us
up
anyway,
I'm
not
the
subject
at
hand.
You
are
so
in
advance
of
kubecon.
There
are
a
bunch
of
co-located
events
with
different
sub
subjects.
A
B
So
as
it's
a
co-located
event,
basically
through
through
the
normal
qcon
channels,
you
must
register
for
kubecon
to
be
able
to
register
for
prom
con,
both
virtually
and
and
in
person,
obviously
same
as
coupon
itself.
We
have
more
virtual
than
in-person
attendees
from
the
numbers
which
I've
seen,
which
kind
of
stands
reason
we
hope
to
flip
it
from
what
I
know.
It's
slated
to
be
yet
again,
the
largest
pre-event
as
per
usual.
B
When
we
do
it,
yes,
like
initially
in
2015
or
16
in
seattle,
16,
it
was
a
co-located
event.
Then
we
split
it
out
into
its
own
thing.
Now,
for
the
last
few
cubecoin
last
two
queue
cons,
we've
been
collocated
again
because
it
made
a
lot
of
things
easier
to
plan
with
sure
with
kovit,
basically
yeah
but
yeah.
We
we
have
the
largest
room,
which
we
will
definitely
not
film
anyway,.
B
A
B
A
B
Like
family
thing
we
deliberately
designed
for
which
is
not
what
but
get
in
pretty
much
any
other
conferences,
it's
usually
meant
to
be
a
mixture
of
101
content
and
in
depth.
We
have
a
little
bit
of
intermediate,
but
usually
we
tend
we
tend
to
like.
We
try
to
have
it
equal,
but
we
tend
to
optimize
towards
101..
I
love.
A
A
You
have
more
resources
than
some
projects
right,
but
it's
it's
a
thing
that
I
think
gets
ignored
a
lot
and
that
I
think
that's
a
huge
mistake
to
ignore
it,
because
even
an
experienced
engineer,
who's
completely
new
to
your
tool
or
this
type
of
tool
does
kind
of
need
to
be
treated
like
a
beginner
and
it
can
kind
of
it
can
make
projects
seem
artificially
more
difficult
to
use
at
first
than
they.
They
really
are
so
mad
mad
respect
to
actually
focusing
on
101
content.
I
appreciate
that,
but
continue
I'm
sorry.
B
B
Also
with
documentation
with
tutorials
like
it
doesn't
need
to
be
code,
we
have
more
than
enough
work
and
we
have
not
a
lot
of
people
who
who
who
do
the
work.
So
anyone
who
is
listening
and
wants
to
get
involved
absolutely
like
open
doors
all
the
way
and
just
for
anyone
who
wants
to
explore
this
one
one
thing
the
the
way
I
usually
structure
the
schedule,
and
that
has
worked
nicely
for
all
types
of
conferences.
A
B
You
structure
the
day.
Of
course,
it
basically
allows
everyone
to
to
get
a
little
bit
up
to
speed
before
before
the
really
heavy
stuff
comes,
and
then
you
have
a
mellow
end
of
the
day.
We
couldn't
do
this
this
time,
because
we
have
this
hybrid
event
and
and
the
av
staff
needs.
I
think
it
was
15
to
20
minutes
to
switch
between
virtual
and
and
on-site
presentation,
which
means
we're
basically
having
one
large
cut
over
in
the
middle
of
the
usa,
which
is
how
all
the
other
events
are
structured
as
well.
A
B
It
is
so
yeah,
it
didn't
work
out
this
time,
but
usually
it
works
out
yeah
for
the
the
more
in-depth
things
the
most
important
one
is
sparse
histograms,
which
is
one
of
those
things
which
have
been
asked
for
for
ages,
but
which
are
super
hard
to
get
right,
and
the
thing
is,
if
you
do
it
wrongly
you're,
basically
stuck
supporting
that
thing.
Even
if
you
deprecated
blah
blah
blah
you,
you
cannot
really
get
rid
of
it.
B
A
B
A
They're
removed
now,
as
of
this
version,
they
are
removed,
so
they've
been
deprecated.
The
v1
beta1
apis
have
been
removed
in
this
version.
So
if
you
upgrade
to
the
the
current
stable
of
kubernetes,
yeah
you're
not
going
to
have
access
to
a
bunch
of
those
apis
anymore,
so
I'm
glad
to
see
y'all
are
keeping
that
in
mind
and
avoiding
making
similar
decisions,
even
though
it
maybe
may
make
things
a
little
bit
slower
to
release
or
or
harder
to
build.
A
In
my
opinion,
we've
had
some
some
rather
dramatic
events
in
the
last
couple
of
days
with
the
facebook
outage
and
the
twitch
leak
this
morning.
So
care
about
your
tooling
but
yeah
yeah.
The
virtual
hybrid
thing
is
making
events
difficult,
but
it
seems
like
y'all
are
handling
it.
Pretty
pretty
graciously
is
there.
Are
there
highlights
that,
like
big
talks
at
prom
con
that
you
want
to
shout
out
things
that
you
think
are
particularly
interesting?
B
Yeah,
let's
split
those
two
so
for
for
the
prom
con
side,
the
most
interesting
one,
this
time
is
sparse,
histograms
and
how
they
have
been
implemented.
What
this
actually
means
for
the
users,
that's
one
of
those
things
which
are
is
super
experimental,
but
still
it
is
extremely
impactful
and
also
it
has
huge
impact
beyond
just
prometheus.
Of
course,
nobody
will
be
will
be
shocked
and
surprised
to
hear
that,
for
example,
open
metrics
and
open
telemetry
are
also
looking
at
high-resolution
instagrams,
and
ideally
they
are
not
incompatible,
but
actually
work
the
same.
B
B
Slash
case
study
type
talks,
this
time,
which
is
nice,
that
it
worked
out
this
way
where
there
are
several
companies
and
and
people
are
just
talking
about
how
they
made
it
work
in
their
own
specific
scenarios,
where
we're
trying
to
basically
no
approach
should
be
repeated
within,
like
say
two
to
three
years,
so
it's
always
new
to
to
people
who
rejoin
or
join
the
community
or
who
watch
the
things.
That's
not
getting
like.
B
A
B
A
B
B
It's
substantial,
which
means
there's
a
lot
of
incentive
to
to
play
nice
with
that.
With
that
ecosystem,
there's
a
lot
of
incentive
for
companies
to
to
be
perceived
as
prometheus,
compatible.
There's
two
main
pathways
to
do
this
one
is
to
invest
a
ton
of
work,
and
several
companies
and
projects
have
done
this.
The
other
is
to
invest
a
ton
in
marketing
they're,
not
exactly
equal
in
outcome.
B
Those
two
approaches,
and
basically
we
we
realized
through
support
questions
through
discussions
with
various
users,
with
various
other
projects,
with
various
vendors
that
we
need
to
actually
level
set
and
that
we
need
to
introduce
a
mechanism
where
any
project
or
vendor
can
prove
to
their
users
to
their
customers
that
yes,
they're
actually
compatible
to
prometheus,
which
is
unfortunate
on
the
one
side,
because
I
would
much
prefer
if
we
didn't
have
to
do
this.
But
I
mean
it's
similar
in
kubernetes
world.
B
On
the
other
hand,
one
of
the
benefits
of
this
is
it
has
forced
us
to
write
a
lot
of
things
down
we're
not
nearly
done,
but
we
have
written
a
lot
of
specifications
and
such
which
we
didn't
do
before,
because
we
didn't
really
need
to,
but
now
that
we
need
to
test
against
something
we
need
to
write
the
specs
down.
Once
we
have
written
this
back
down,
we
can
actually
version
that
spec,
which
allows
us
to
to
have
a
good
upgrade
path
which
unblocks
us
in
this.
B
We
need
to
support
certain
things
forevermore,
because
if
I
declare
this
1.0,
then
I
can
just
make
a
2.0
of
the
premises,
remote
right
interface
or
what
have
you
and
I
can
say-
okay.
This
will
be
supported
for
x,
amount
of
time
and
after
that
you
have
to
change,
and
all
those
things
are
are
the
positive
unintended
consequences
of
the
of
the
conformance
program,
and
I
will
talk
about
this
on
october
14th,
which
is
basically
the
shim
of
of
a
talk,
and
then
I
optimize
towards
q.
B
I
mean
anyone
who's
listening
to
this,
in
particular,
junior
people,
don't
listen
to
all
the
people
who
tell
you,
you
must
hustle
24,
7
and
blah
blah
blah
blah
blah.
You
should
actually
get
some
rest,
and
I
I
paid
a
price
for
this
so
yeah,
but
there
are
more
intense
and
less
intense
periods
of
time.
This
is
currently
a
more
intense
one.
A
A
A
B
A
I
think
you're
minus
one
yeah,
the
main
conference
starts
the
13th,
so
12
is
day
zero
you're.
You
are
minus
one,
so
yeah
well
I'll
stop
by,
because
I
can
I'll
get
there
that
day,
there's
a
lot
of
competition
for
colo
events,
but
this
one
seems
pretty
stacked
and
I
actually
like
genuinely
not
putting
on
a
show.
Don't
don't
really
know
that
much
about
prometheus,
so
the
fact
that
there
is
some
intro
level
content
on
the
schedule
is
extra.
Appealing
to
me
personally,
I
can
actually
learn
from
that.
A
A
B
So
from
the
prometheus
as
a
project
perspective,
we've
been
putting
a
lot
of
effort
into
into
appearing
more
open,
and
I'm
choosing
this
phrasing
extremely
deliberately,
we've
always
been
very
open.
I
I
I've
been
doing
open
source
for
two
decades.
I
I
I
strongly
believe
that
we've
always
been
extremely
open
in
all
ways
of
participation.
B
There
are
also
some
some
cyclic
discussions
and
such,
but
by
and
large
those
stores
were
open,
yet
we
were
often
perceived
as
not
being
easy
to
engage
with,
which
is
unfortunate,
basically
and
we've
been
putting
a
ton
of
work
into
into
fixing
that
perception,
which
means,
for
example,
that
all
the
dev
summits
are
fully
open.
Everyone
can
join,
anyone
can
suggest
stuff
for
the
agenda
they're
on
youtube.
B
Anyone
can
also
join
during
the
thing
and
is
strongly
encouraged
to
speak
up
with
whatever
they
have
like
those
kinds
of
things
we
have
office
hours.
We
have.
We
have
working
groups
now
like
for
tsd
or
for
the
documentation
and
such
which
are
fully
open
to
join
we're
aggressively,
trying
to
increase
the
contact
surface
for
people
to
to
come
and
join,
because
you
were
saying
we
have
a
lot
of
resources.
Honestly,
that's
not
the
case
we
sh,
given
the
size
like
when
it
compares
to,
for
example,
kubernetes
it's.
B
Basically,
we
we
have
half
a
dozen
people
who
who
really
consistently
chip
away
between
half
a
thousand
and
ten
like
we
have,
I
think,
17
or
16
maintainers
as
of
right
now
or
team
members
with
a
few
more
maintainers
for
subsystems,
and
none
of
them
are
full
time
on
prometheus.
So
absolutely
we
have
more
than
enough
work
and
we
are
really
really
trying
to
to
get
this
across
that
those
stores
are
really
really
open.
Like.
A
Wide
open,
like
you're,
begging
people
to
walk
through
them.
Yes,
I
get
it,
it
could
be
like
it
can
be
overwhelming
trying
to
figure
out
how
to
contribute
to
an
open
source
project,
and
it
can
be,
it
can
be
like
a
it
can
feel.
Really
daunting
right.
You
feel
sometimes
especially
new
developers
will
feel
like
maybe
they're
stepping
on
people's
toes.
What?
If
I
do
something
wrong
and
embarrass
myself
in
public,
I
don't
understand
the
git
flow
for
this.
Oh,
they
don't
really
need
my
help,
because
I'm
not
an
expert.
A
Usually
the
maintainers
are
like
really
friendly
and
you
you
can
just
reach
out
and
and
ask
if
something
is
unclear
about
the
contribution
process
and
it
doesn't
have
to
be
code,
contributing
contributing
docs
or
like
samples
or
something
is
also
super
helpful
and
often
like.
That
is
a
thing
that
open
source
projects
are
super
lacking
in
they
don't
they.
They
can't
often
hire
technical
writers
so
like
we,
we
have
to
write
the
docs
ourselves,
which
you
know
I
wish
we
could
all
have
technical
writers
and
pay
them
what
they're
worth.
B
B
That's
here
and
speaking
in
particular,
of
documentation
like
website,
updates
or
or
website
tech
on
on
the
back
end.
Writing
documentation
is,
is
one
of
those
things
where
you
can
really
really
use
some
help.
In
particular,
of
course,
we
are
currently
refocusing
the
documentation
from
from
just
a
reference
documentation
as
a
first
and
foremost
novice
to
intermediate
documentation.
B
Basically,
we're
stuck
yeah
we're
now
just
changing
the
main
documentation
to
to
be
really
user-friendly,
because
that's
one
of
those
things
which
which
we
are
not
doing
very
well
historically,
to
be
honest
sure,
because
we
keep
having
those
waves
of
adoption
and
from
from
the
inside,
you
can
actually
really
see
those
waves
coming
from
different
areas
just
arriving
in
in
the
prometheus
ecosystem.
And
too
often
it's
not
as
easy
to
onboard
yourself
onto
this
whole
thing
as
as
it
should
be.
B
It's
not
even
bragging,
like
I
I've
I've
I've,
my
I
come
from
the
operations
side.
My
my
sanity
really
depends
on
on
point
alerting
and
on
on
being
able
to
resolve
incidents
which
are
popping
up
left
and
right
quickly
and
without
losing
too
much
sleep,
it's
yeah
and
having
played
with
or
having
depended
on
a
lot
of
different
systems.
I
can
honestly
say
I've
never
seen
anything
which
is
as
easy
to
use
and
as
performant
and
as
overall
good
as
prometheus,
but
that's
not
reflected
in
documentation.
B
In
particular,
if
you
have
like,
I
said
we
have
a
functional
language
to
do
vector,
math
on
your
on
your
on
your
data
and
that's
based
on
label
sets.
You
can
make
n-dimensional
matrices
instead
of
having
tree-like
structures,
and
all
of
this
is
super
nice.
But
if
I
say
it,
it
sounds
super
scary
and
you
won't
know
what
that
actually
means,
and
there
needs
to
be
an
easy
way
to
actually
onboard
onto
this
thing
to
to
get
familiar
with
it.
B
A
A
B
No,
they
don't,
but
I'm
currently
collecting
stuff
for
a
choose.
Your
own
observability
adventure
type
of
thing.
I
want
to
create
a
lot
of
small
like
one
to
maybe
three-minute
pieces
which
are
a
directed
graph
of
learning,
so
you
can
say
I'm
I'm
starting
here
and
I
want
to
get
to
that
place
in
in
understanding
what
that
space
actually
is,
and
as
part
of
that,
I
want
to
go
through
a
few
of
those.
B
B
If
you
have
field
graph
like
with
with
the
where
you
have
that
pretty
line,
and
you
you
fill
with
color
underneath
yeah,
please
don't
do
this
unless
you
have
cumulatives,
where
you
signal
that
you're
actually
adding
something
versus
just
visualizing
a
line.
They're
super
pretty,
but
if
you
overuse
them,
it
gets
really
confusing
in
part
of
making
good
dashboards
open
parenthesis.
B
This
is
not
perfect
for
accessibility
if
you
overload
the
visual
system,
but
it's
useful
for
for
humans
as
a
general
rule,
but
you
still
need
to
take
like
you
need
to
have
more
more,
not
basic
but
more
high
contrast
and
such
dashboards.
Also.
That
being
said,
that's
a
super
quick
way
to
visualize
if
something
is
just
a
line
or
if
it's
just,
if
it's
something
which
is
cumulative,
if
you
have
something
which
is
a
finite
resource
with
which
has
an
upper
limit,
a
natural
upper
limit,
but
also
goes
up
and
down.
B
The
thing
which
I
like
doing
is
that
on
the
left
y
axis
I
have
whatever
the
actual
count
is,
and
I
come
from
the
networking
space.
So
that's
super
common
that
use
case
where
you
have
x
amount
of
traffic
on
an
interface,
but
at
the
glance
it's
really
hard
to
see
if
that's
10,
megabyte
or
megabit
or
10
gigabit
or
just
10
kilobit,
if
it's
just
a
line
going
like
so
so,
on
the
right
hand,
side
I
like
to
do
the
percentage,
so
I
see
the
absolute
usage
of
the
thing
at
the
same
time.
B
So
even
if
I
have
a
super
flat
graph
on
the
left
side
y
axis,
which
I
want,
because
this
increases
the
vertical
resolution
dynamically
to
to
whatever
level
of
of
of
of
changes
I
have
at
that
time
or
in
that
time
frame.
I
can
still
add
a
glance
see
what
what
the
absolute
absolute
usage
is.
But
you
need
to
design
the
two,
so
you
make
this
left
one
thick
and
the
right
one
and
with
by
doing
that,
you
have
already
like
you
see
it
once,
and
you
already
know
what's
happening.
B
A
They're
beautiful
but
they're
so
hard
to
read,
I
get
overwhelmed
looking
at
them
immediately
and
it
just
I
don't
know
my
eyes
tend
to
just
like
glaze
over
everything.
At
that
point
once
I
don't
really
want
more
than
like
four
to
six
graphs
on
a
dashboard
at
any
given
time
before,
like
beyond
that,
it's
not
it's
just
too
much
for
me
to
look
at.
We
have
another
question
from
twitch:
if
you've
got
time
for
it,
is
there
an
abstraction
available
or
in
the
works
for
prometheus?
B
A
B
A
Yeah
they
do
it's,
it's
a
huge
thing.
It's
why,
whenever
I'm
building
like
a
workshop
or
writing
a
new
tutorial,
I
for
if
it's,
if
it's
geared
towards
beginners,
the
first
thing
I
do
is
borrow
some
students
from
a
local
boot
camp,
and
I
give
the
workshop
or
the
tutorial
to
them
and
take
note
of
like
where
they
run
into
problems
like
where
I
forgot
to
explain
something
because
I'm
an
expert
I
just
forget
to
that.
Not
everybody
has
contacts,
and
this
is
a
thing
that's
inherent
in
human
nature.
A
B
Yes
and
no,
there
are
bits
and
pieces,
or
there
are
large
pieces
in
on
the
grafana
side,
where
there
are
certain
things
can
can
be
done
in
ui.
I
think
quite
a
few
of
those
are
are
paid
closed,
source
features,
but
I
don't
actually
know
I
don't
tend
to
use
them.
I
I
prefer
the
other
way.
So
I
don't
really
know
yeah.
B
B
B
B
A
B
B
So,
there's
more
than
enough
ways
to
to
get
in
touch.
We
also
have
office
hours
which
are
in
different
time
zones
or
happen
at
different
times,
so
people
from
different
time
zones
can
can
attend
where
we
just
walk
through
whatever
someone
might
be,
having
trouble
with
there's
tons
and
tons
and
tons
of
ways
to
to
get
this
feedback,
and
or
this
this
help
and
the
nice
thing
is,
we
have
a
lot
of
of
people
who
who
also
help
out
it's
not
just
us,
I
mean
ideally
once
you
learn
it
stick
around
help.
A
Yeah
make
note
make
a
note
every
time
you
run
into
a
wall.
I
do
this
every
time
I'm
like
working
with
the
new
products
in
general,
like
anytime,
I'm
using
a
new
open
source
tool
when
I'm
first
trying
to
like
stand
it
up
or
run
through
the
the
tutorials
the
quick
start
guides.
Whatever
I
make
a
note
of
everywhere,
I
run
into
a
problem
or
everywhere.
A
I
think
that
something
wasn't
clear
enough
in
the
documentation
or
sometimes
the
documentation
is
just
straight
up
wrong,
that
that
happens
less
frequently,
but
it
does
happen
with
some
tools.
I
make
a
note
of
it
and
then
I
either
contribute
the
changes
back
or,
if
I
know
the
maintainer,
I
will
like
reach
out
to
them
personally
and
hand
it
over
as
an
assist.
It
really
is
appreciated.
A
Stuff,
like
that.
So
if
you're
new
and
you're
running
into
trouble
like
open
source
project
maintainers
do
want
their
tools
to
be
easy
to
use.
It's
like
we.
We
want
that.
It's
not
always
achievable,
but
we
want
it.
So
you
know
tell
us
when
things
are
a
problem
we
are
running
up
on
time.
Is
there
any
closing
words
other
than
register
for
prom
con
follow
cloudnativetv
on
twitch?
Follow
you
on
twitter.
A
B
A
Yeah,
well,
hopefully,
things
are
a
little
bit
more
controlled
by
then
and
we'll
all
feel
safer
going
to
conferences,
I'm
still
pretty
questionable
about
it,
but
I
will
be
cubecon
n
a
so
y'all
I'll,
see
you
in
a
in
a
week
virtually
and
live
you.
I
will
be
seeing
virtually
not
live,
but
thank
you
so
much
for
coming
on
here
and
answering
my
questions
and
talking
about
prometheus
and
prom
con
and
monitoring
and
shouting
out
the
community
and
y'all
contribute
to
open
source.
A
B
A
Yeah
good
all
right.
Well,
everyone
thanks!
Everyone
thanks!
If
you
did
get
vaccinated.
Thank
you.
If
you
didn't
consider
it,
please
please
do
it
thanks
for
everything
thanks
for
talking
to
me,
you've
been
fantastic.
I
hope.
Prom
con
is
a
huge
success
and
I
hope
your
announcements
and
your
and
your
talks
go
well.
It's
a
lot
of
talks.
You
gotta
give
twitch
thanks
for
thanks
for
watching,
and
I
guess
twitter,
I'm
assuming
a
bunch
of
y'all
came
from
twitter
too
any
closing
words
for
you,
no
you're.