►
From YouTube: Grafana Mimir Community Call 2022-04-28
Description
Second Grafana Mimir Community Call, in which we discussed coming features in Mimir 2.1 and asked the community about their issues with getting started with Mimir.
Join us on the last Thursday of every month. Please see the linked document for meeting notes, agenda and details on how to join: https://docs.google.com/document/d/1E4jJcGicvLTyMEY6cUFFZUg_I8ytrBuW8r5yt1LyMv4/view
A
A
A
A
No,
so
this
feature
is
already
ready
and
it
will
be
part
of
mimir
2.1.
The
next
feature
that
oh
jesus,
I'm
sorry,
I'm
not
sure
how
to
pronounce
your
name.
Yes,
I
saw
satisfied
cases
works
on
is
a
support
for
out
of
order
samples,
so
jesus,
if
you
want
to
take
over
and
tell
us
a
little
bit
more
about
it.
Now
is
your
time.
B
I'm
super
excited
right
now
because
I
sure
did
not
do
this
on
purpose
but
like
we
are
ingesting
samples
now
in
the
depth
cluster
since
three
minutes
ago.
So
like
I'm
a
bit
yeah
looking
at
the
graphs
while
while
attending
this
goal
as
well,
yeah
and
yeah,
so
we
expect
to
have
support
for
out
of
some
out
of
order
samples
in
like
maybe
a
month
from
now
or
perhaps
a
bit
later
like
we.
B
B
The
reason
why
we
do
this
is
because
we
want
to
be
careful
writing
out
the
for
the
samples
because
of
the
design
can
have
performance
like
a
performance
impact
on
on
the
database.
So
that's
why
we
don't
want
to
allow
very
old
samples
to
come
in.
It
could
do
it,
but
we,
I
think
we
think
it's
it's
more
common
to
have.
You
know
like
five
minute
old
samples
than
a
year
old
sample,
so
the
use
case
we
are
trying
to
solve.
B
B
B
B
B
Sometimes
we
get
up
too
many
out
of
bound
samples,
and
that
causes
an
issue
in
mimir,
and
so
we
we
want
to
to
also
test
that,
like
like,
send
more
more
and
more
of
the
further
examples
that
go
far
far
in
the
time
and
see
and
see
how
this
is
handled.
Yeah-
and
I
mean
I
mean
if
anyone
has
any
suggestions
for
the
tests
they
are
welcome.
C
B
B
Yeah
then,
there's
also
a
an
interesting
detail
here.
Out
of
order
introduces
a
new
type
of
chunk
to
the
prometheus
dsdb.
So
that's
a
breaking
change
that
makes
newer
versions
not
compatible
with
old
versions.
So,
like
a
rollback
from
this
version
would
not
be
possible,
but
we
have
done
a
change
in
the
middle
where
we
we
made
prometheus
discard
unknown
chunks
in
case
it
finds
any
so
like
that's
a
step
in
the
middle
for
this,
and
it
introduces
the
possibility
to
roll
back
in
case.
There
was
any
any
trouble
that
we
didn't.
D
B
B
B
So
the
way
you
the
compactor,
you
mean
the
comparator
component
in
beaming.
Right
that
reads
the
block
and
and
there's
it
yes,
but
it
actually
uses
the
prometheus
compactor
code
yeah.
So
the
way
this
is
yeah,
so
we
are
leveraging
on
that
compactor.
So,
basically,
when
when,
when
the
tsdb
compacts
the
the
memory
map
chunks,
it
will
generate
a
persistent
block
for
in-order
data
and
then
potentially
overlapping
blocks
for
out-of-order
data,
and
then
we
are
leveraging
on
the
compactor
to
to
see
them
all
and
immerse
them.
A
A
D
Yeah
sure
so
we
already
have
support
for
backfilling
blocks
into
the
beer,
but
it's
a
manual
procedure
where
one
will
upload
the
old
blocks
into
object
storage,
so
the
compactor
will
take
care
we'll
make
use
of
them.
So
what
I'm
doing
is
basically
add
the
support
into
into
mimir
for
sending
blocks
for
backfilling.
D
D
D
So
I'm
hoping
it
will
be
done
in
not
too
long.
Although
there
are
some
architectural
questions
being
discussed
in
the
in
the
pr
specifically
which
component
in
which
to
put
the
the
backfill
api
at
the
moment,
it's
in
the
in
the
distributor
component,
but
there's
but
there's
discussion
as
to
whether
we
should
move
it
perhaps
directly
to
the
compactor
instance
to
to
avoid
to
avoid
the
distributor
having
to
send
the
the
files
to
to
investors.
D
A
A
E
So
maybe,
as
a
short
interjection,
only
two
things
first
feel
more
than
welcome
to
write
yourself
into
the
agenda
into
the
attendee
list,
in
particular,
if
you're
external,
I
messed
up
that,
should
have
been
world
writable
from
the
start
marker
just
fixed
sorry.
The
other
thing
is
in
particular
for
the
external
people.
Please
please,
please
feel
super
welcome
to
pipe
up
at
any
point
in
time
like
this
is
not.
This
is
not
grafana
talking
to
you.
This
is
supposed
to
be
a
conversation.
E
E
A
A
A
C
C
Yeah
right
yeah,
I'm
me
and
few
other
people
are
starting
network
to
further
simplify
mimir
from
an
operational
perspective,
both
getting
mimir
up
and
running
on
the
day,
zero,
as
well
as
operating
media
over
the
time
so
yeah.
I
just
have
a
very
open
question
to
you:
you
can.
We
can
discuss
it
right
now,
like
in
a
time
box,
fashion,
10
minutes
or
so,
and
then,
if
you
want
to
reach
out
to
offline
on
slack,
to
continue
the
discussion,
I'm
very
happy
to
do
it.
C
We
are
receiving
many
questions
on
slack
and
some
of
them
are
about
the
configuration.
So
I
think
just
you
know
scrolling
the
slack
community
channel.
We
we
we
can
learn
a
lot
about
it.
I've
already
seen
a
few
times
the
question
about
how
to
configure
the
gcs
and
s3
bucket
authentication,
and
I
think
that's
one
of
the
one
on
one
of
the
information
which
are
lacking
from
our
documentation.
So
probably
there's
a
good
opportunity
to
improve
the
documentation
about
the
bucket
configuration.
F
F
Like
plans
in
in
place
to
improve
that,
one
of
which
is
that
there
will
be
support
for
getting
secrets
from
environment
into
the
mimir
config,
so
that
you
don't
have
to
write
it
into
your
config
and
also,
which
would
mean
eventually,
that
the
config
doesn't
have
to
be
a
secret
in
kubernetes,
so
that
you
would
get
like
nice
diff.
When
you,
when
you
change
your
config.
F
And
also
you're
thinking
of
possibly
making
like
wiring
the
storage
settings
into
the
values
and
not
direct
and
kind
of
templating
it
into
the
configuration,
because
right
now
I
see
that
one
challenge
is
that
the
storage
has
to
be
configured
at
multiple
places
and
it's
kind
of
a
hassle
to
know
when
to
set
which
one
and
how
many
places
I
have
to
set
it.
So
one
way
around
that
is,
you
know,
making
the
ham
chart
do
that
for
you.
G
We've
also
had
a
a
few
questions
from
community
members
around
capacity
planning
and
we've
got
some
things
in
the
docs,
but
it
doesn't
cover
all
components
like
like
memcache,
and
I
I
think
we
could
also
we
could
add
some
more
information
about,
like
expected
instance
sizes
or
something
like
that.
Like
you
know,
if
you're
in
google
cloud
use
these
type,
if
you're
an
aws
use
these
type,
something
like
that.
C
F
And
to
add
to
that,
I
think
it's
kind
of
obvious
that
we
need
like
more
documentation
about
how
to
use
features
with
hemp
chart,
because,
judging
by
the
feedback
on
the
slack
channel
and
and
the
hand
chakra
pool
people
are,
are
clearly
interested
in
the
am
chart.
So
you
know
it
needs
better
documentation.
F
F
No,
I
was
just
wondering
because
if
we
talked
about
new
features
for
mimir,
maybe
I
should
have
put
into
the
agenda
like
upcoming
things,
for
the
hand
chart
as
well
and
the
hem
chart
is.
There
are
pull
requests
to
requests
in
the
works
to
support
multi-zone,
so
zone,
aware
replication
of
injester
storage,
get
phase
or
lag
manager.
F
C
C
The
solution
was
simple,
was
just
storing
all
the
tsb
blocks
under
a
prefix
in
the
storage
like
under
blocks,
for
example,
so
that
it
doesn't
conflict
with
the
ruler
and
the
alert
manager.
Anyway,
I
think
I
think
that's
something
we
can.
We
can
work
on
handy
if
I'm
not
mistaken,
is
working
on
apr
to
allow
to
configure
the
the
packet
prefix
in
mimir.
G
C
C
A
Well,
we
don't
really
have
more
items,
we
have
open
mic.
Cryo
has
already
already
talked
about
the
new
helm
features,
and
I
put
your
item
speaking
about
global
configuration
for
storage
there,
so
we
are
actually
at
the
end
of
agenda.
Now,
I'm
wondering
oh,
you
have
a
question
about
it.
Anything
hold
you
back
from
trying
there
and
I'm
wondering
if
there
is
anyone
who
did
not
try
me
here
but
would
like
to
but
is
for
whatever
reason
stopped
or
maybe
hold
back
held
back.