►
From YouTube: Loki Community Meeting 2022-05-05
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
I
wonder
if
it's
a
permissions
thing
nope
there
we
go
all
right,
welcome
everyone.
What
is
it
the
may
5th
low-key
community
call
2022..
A
And
so
here
we
go.
There
are
some
some
cool
features
that
are
going
to
be
coming
out
now.
The
first
one
is
not
explicitly
like
part
of
loki
but
has
been
a
really
cool
side
project
that
vlad
has
been
working
on
on
the
side
and
it's
a
log
qld
bugger.
So
this
is
an
interactive
visual
tool
for
writing.
Log
qr
queries
and,
more
importantly,
being
able
to
understand
them
being
able
to
see
what
is
filtered
and
what
is
disregarded,
that
sort
of
thing
it
should
land
in
our
docs.
A
A
So
in
this
example
query
the
sum
rate
you
can
see
that
there's
a
four
hour
period
selected
now
we
see
this
a
fair
amount
of
the
time
where
people
will
have
very
long
kind
of
look
back
ranges
like
this
and
historically
we
can
still
split
and
shard
these
queries,
but
each
you
know
individual
unit
of
work
would
have
that
four
hour
look
back,
and
so
this
gets
really
egregious
the
longer
it
becomes
and
over
the
more
data
and
the
more
expensive
the
query.
A
So
in
this
case
it
would
run
you
know
something
like
four
one
hour
segments
and
then
merge
them
together,
and
so
this
is
just
another
kind
of
dimension
of
time,
sharding
that
we've
introduced
in
the
loki-
and
it
has
been
pretty
compelling
so
we're
looking
forward
to
sharing
some
some
numbers
and
benchmarks
shortly,
but
it's
in
the
main
branch
and
we'll
be
kind
of
in
our
whenever
we
cut
our
next
release
the
next
bit-
oh,
hey
travis!
You
want
to
have
to
put
you
on
the
spot.
A
Do
you
want
to
talk
about
the
faster
deletes
for
query
time
filtering?
Would
you
want
me
to
talk
about
it.
B
No,
I'm
happy
to
talk
about
it.
Yes,
so
this
is
the
thing
that
we've
been
working
on
and
we're
like
super
excited
to
do
basically
delete
since
they
exist
today.
Allow
you
to
delete
entire
streams
as
part
of
retention,
and
what
we've
been
working
on
is
sort
of
faster
deletes.
B
Almost
real-time
deletes
where
basically
you're
going
to
be
able
to,
instead
of
just
a
whole
stream
selector
put
in
basically
any
log
ql
selection
for
some
set
of
logs
and
see
it
sort
of
disappear
from
query
results
on
the
order
of
minutes
and
then
sort
of
as
part
of
the
retention
stuff
get
cleaned
up
still,
so
that
you
can
delete
like
personally
identifiable
information
or
whatever
that's
sleeping
your
logs.
Much
more
quickly.
A
A
Yeah
definitely
next
up
I
had
teased
some
tsv
work
in
the
last
community.
Call
it's
still
going.
I
don't
really
have
anything
like
demo
or
super
cool
to
show
other
than
that.
We're
just
making
steady
progress
on
that
front,
and
that
looks
like
the
end
of
everything
that
we
have
for
today's
call.
C
I'll
just
mention
really
quick:
there
was
that
request
recently
to
basically
extend
the
json
pipeline
stage
to
allow
dropping
of
log
lines
that
actually
are
not
correctly
formed,
json
and
along
the
way
it
seemed
to
me
like.
Maybe
we
might
want
to
in
the
future,
support
that
for
other
log
format,
types
like
log
format
or
something
like
that.
So
I
wrote
a
short
doc
I'll
open
a
little
issue
and
then
we
can
just
see
how
many
people
say.
Yes,
they
would
like
something
like
that,
but
for
now
it's
just
going
to
be
json.
A
C
A
A
All
right,
then,
well
we're
clocking
in
eight
minutes
this
time
the
short
and
sweet
we'll
see
everyone
next
time
and
take
care.
I
will
stop
recording.