►
From YouTube: Grafana Mimir Community call 2023-02-23
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
This
is
our
February
community
meeting,
not
a
lot
of
communities
around
really
in
this
meeting.
We
also
have
not
not
a
lot
of
agenda
points
this
week,
so
we
can
talk
briefly
about
the
native
histograms
progress,
which
is
the
biggest
feature
in
progress,
I,
think
and-
and
we
can
do
it
quickly
gradually.
We
want
to
say.
B
Something
yes
so
I'm
in
the
team
that
is
working
on
Native,
Instagrams
and
member
and
latest
histograms
is
a
new
feature
in
promo
tools
that
we
are
introducing
in
nimir
as
well
to
keep
API
compatibility
and
we've
already
merged
the
right
path,
support,
meaning
that
you
could
potentially
ingest
native
histograms,
although
you
cannot
query
them.
So
it's
not
super
useful
at
the
moment
and
we
are
working
on
the
read
path
and
I
think
the
code
is
almost
ready,
but
we
need
to
split
it
up
because
it's
like
90
plus
files.
B
B
So,
potentially
it
could
push
and
and
and
then
just
histograms
on
the
open,
dormitory
endpoint
as
well
I
mean
maybe
I
can
you
know,
receive
and
and
ingest
them,
but
I
would
make
a
note
also
that,
having
worked
on
it
now
for
basically
two
plus
months,
I
see
that
native
histograms
is
kind
of
in
progress
work
in
progress
in
Primitives
as
well,
so
that
this
is
definitely
going
to
be
an
experimental
feature
in
mimir
for
the
start
and
we'll
see
how
long
it
takes
to
make
it
to
stable
status.
A
C
Yeah
sure
so
I
think
it
was
Marco
who
originally
had
the
idea
that
we
could
use
the
cardinality
of
queries
that
we
have
already
seen
in
the
past
to
inform
the
query
charting
for
similar
queries
or
for
the
same
query
that
runs
again,
but
for
a
different
time
right
currently
or
previously
to
this
change
being
merged.
The
the
sharding
of
the
query
would
happen
according
to
a
fixed
number
maximum
number
of
shards,
which
in
case
the
the
query,
doesn't
actually
touch
a
lot
of
Series.
C
We
we
take
that
estimate
for
how
many
series
this
query
is
likely
to
touch
next
time
and
use
it
to
limit
the
number
of
shards
that
that
are
going
to
be
used
to
execute
this
query.