►
From YouTube: Grafana Community Call 2022-08-18
Description
Join our next Grafana community call: https://docs.google.com/document/d/1GpgvanMeNqf-CDegv6E0yAV1s2f7H2knUFuNouqwX3A/edit
What was discussed:
- Navigation
- Query Builder Patterns
- Logs Explore
Learn more at https://grafana.com and if all of this looks like fun, feel invited to see if there’s a role that fits you at https://grafana.com/about/careers/
A
Okay,
so
the
recording
has
started
so
just
as
a
reminder,
obviously
we're
recording
the
recording
will
be
available
on
the
grafana
youtube
channel.
After
this
call,
and
if
you
have
questions
you
can
add
them
to
the
chat,
you
can
raise
your
hand
and
if
you
don't
want
to
appear
on
the
recording,
you
know,
please
feel
free
to
not
share
video
or
join
with
a
name.
That
is
not
your
actual
name
just
out
of
respect
for
privacy
so
go
there.
We
go
all
right.
Welcome
to
our
community
call.
A
We
rotate
different
squads
and
themes
and
features,
so
always
something
interesting
to
check
out
from
the
team
and
this
week
or
this
month.
Rather
we're
going
to
be
here
with
the
user
experience
team,
which
is
us
in
terms
of
agenda,
we're
going
to
just
kind
of
talk
about
a
few
of
our
current
projects
and
and
when
we
say
current
is
interesting,
because
our
ux
current
is
actually
kind
of
like
future.
A
The
thing
that
we're
under
things
that
are
quite
necessarily
available
yet,
but
they
are
either
things
that
are
in
planning
or
things
that
maybe
your
ideas
that
might
not
come
to
fruition
or
they
might
depending
on
you,
know,
kind
of
how
it
goes
as
we
build
and
how
it
is,
as
we
research
and
test
our
ideas,
so
we're
going
to
talk
about
our
new
navigation,
the
query
builder
patterns
logs
explorer
and
then
have
some
time
for
questions
before
I
keep
going.
I
just
want
to
pause.
A
A
So
since
I'm
introducing
I'm
just
going
to
keep
going,
one
of
the
things
I've
been
working
on
for
most
of
this
year,
actually
is
a
new
navigation
for
grafana
and
and
that's
sort
of
like
a
really
broad
term,
so
to
kind
of
narrow
it
down.
We,
we
have
two
things
that
we're
really
focusing
on
with
the
new
navigation.
One
is
our
information
architecture,
and
so
what
is
information
architecture?
A
In
short,
it's
really
how
you
organize
and
label
content
within
an
application
or
within
a
website,
and
what
we
have
found
is
that
as
we're
growing,
our
information
architecture
needs
are
also
growing
and
evolving.
So
we're
finding
that
people,
especially
newer
users,
who
aren't
kind
of
used
to
where
things
are,
are
getting
lost
or
they
get
stuck.
A
That
maybe
should
go
together
in
our
organization
and
then
we
developed
two
information
architecture
proposals
and
we
really
talked
with
our
stakeholders
a
lot
for
these
proposals,
because
we
need
to
not
just
support
how
people
want
to
use
grafana,
but
we
also
want
to
support
our
plans
for
the
future.
You
know
so
it's
sort
of
like,
if
you
think
about
building
a
house,
you
don't
want
to
build
a
house
with
one
bedroom
when
you're
planning
to
have
seven
kids.
A
So
I
mean
maybe
that's
sort
of
an
extreme
example,
but
I
think
it
gives
you
an
idea
of
how
we
want
to
keep
scaling
for
the
future,
but
not
with
seven
kids.
Then
we
did
a
test
called
a
tree
test,
and
so
what
that
is,
is
it's
again
a
research
methodology
where
we
have
people
try
out
these
proposals,
so
try
this
out
and
see
if
they
can
find
the
things
we
ask
them
to
look
for.
A
So
at
this
point
we
now
have
kind
of
what
I
call
a
winning
proposal.
It's
in
air
quotes
because
you
know
there's
still,
you
know
tweaks
and
modifications
happening
and
we're
right
now.
We're
actually
planning
the
implementation
of
that
and
I'll
give
a
little
sneak
peek
preview
of
some
of
it.
When
I'm
finished
with
my
slides.
A
A
A
So,
let's
have
a
look
at
what
that
looks
like
so
so
this
is
today-
and
this
is
my
cloud
account,
so
this
is
going
to
be
both
for
grafana
cloud
and
for
grafana
open
source
as
well
as
enterprise,
and
so
what
you
can
see
when
I
mentioned,
we
can't
just
keep
adding
icons.
You
can
see
on
my
monitor
here
that,
like
you
know,
we
really
would
only
have
room
for
one
more
if
we
keep
going
the
way
that
we
have
been.
A
So
that's
what
I
mean
when
I'm
mentioning
that
we're
sort
of
running
out
of
room
at
this
top
level
in
terms
of
obscuring
content.
These
flyouts,
you
know
like
if
I
want
to
interact
with
this
panel
and
this
flyout
is
kind
of
over
it.
It's
just
sort
of
annoying
that
you
know
you're
kind
of
running
into
things
that
way,
and
then,
when
I
mentioned
that
sometimes
breadcrumbs
work
one
way
and
sometimes
they
work
a
different
way.
A
A
A
We
have
this
is
very
much
work
in
progress,
so
you
know
not
everything's
going
to
look
the
way
that
the
designs
looked.
But
again
this
is
a
demo
environment.
So
we
can
see
that
when
I
mentioned
that
we
could,
you
know,
show
and
hide
this
nav
bar.
We
would
just
click
here
and
you
can
see
it
minimizes
it,
so
it
makes
a
lot
more
room
for
you.
A
We're
also
looking
at
you
know
ways.
That's
actually
hooked
up.
You
know
different
ways
of
making
things
full
screen
the
menu
which
today,
actually
you
can
access
via
this
little
chevron.
Here,
opens
what
we
sort
of
half
jokingly,
but
now
all
the
time
called
mega
menu.
So
in
the
future
that
will
be
the
only
menu.
So
we
don't
have
the
left-hand
navigation
bar
anymore,
and
so
we
don't
have
sort
of
this
content
being
obscured
when
users
hover
over
things.
A
A
B
A
That
is
exactly
the
hardest
thing.
So
that's
a
great
question.
So
we
are
working
with
our
plugins
platform
squad
to
figure
that
out
so
for
grafana,
authored
plugins.
We
will
decide
where
they
go
in
the
navigation,
we're
looking
at
ways
for
plug-in
authors
to
tell
grafana
where
they
should
belong
in
the
navigation
and
in
the
not
just
in
the
navigation
but
in
the
information
architecture.
B
Right
I
mean
this
is
where
you
started
this
right.
There
are
so
many
of
them.
You
have
it
in
the
cloud
account,
as
you
said
yourself,
and
now
more
and
more
community
building
this
application
plug-ins,
and
we
have
three
or
four
of
them
as
well,
so
it
will
be
interesting.
I
mean
how
how
we
should
do
that,
and
of
course
I
mean
the
upgrade
path
is
very
important.
A
Exactly,
and
so
I
think
that,
probably
by
default,
what
we
will
end
up
doing
is
kind
of
creating
a
you
know
this.
This
is
sort
of
an
idea
that
we're
playing
with
but
creating
kind
of,
a
group
for
everything.
But
what
we've
heard
from
people
is
that
like?
Well?
What
if
I
you
know
what,
if
I
use
kubernetes
and
nothing
else
in
grafana,
and
so
one
of
the
other
sort
of
future
state
items
is
to
think
about
how
admins
might
be
able
to
configure
this
menu
for
their
organization.
B
A
I
don't
think
quite
yet,
so
I'm
actually
not
sure
exactly
what
our
timeline
is
in
terms
of
it
being
available
more
widely.
I
think
we'll
probably
start
with
it
being
available
behind
a
feature
toggle,
so
that
people
can
turn
it
on
and
off
and
try
it
out
and
gather
feedback
and
see
if
we
need
to
iterate
anymore,
but
in
terms
of
actual
timing,
I'm
afraid
I
don't
have
a
good
answer
for
you
on
that
right
now:
okay,
okay!
A
C
C
Cool
so
today,
I'll
be
chatting
about
query
patterns
sort
of
what
they
are,
how
they
work.
What
are
the
sort
of
improvements
that
we've
worked
on
and
I
think
it'll
be
better
if
I
just
kick
start
by
sharing
my
screen,
because
I
can
just
take
you
through
some
of
the
current
stuff,
so
I'm
just
gonna
share
my
screen.
Amy.
C
Cool,
so
this
is
what
we
call
the
query
builder
and
just
to
sort
of
explain
what
query
patterns
are.
I
want
you
to
think
of
them
as
in
a
way
that
you
can
kick-start
your
query.
So
if
you
had
a
query,
I'm
just
going
to
reference
a
kitty
because
anna's
got
one
over
there.
So
if
you
had
a
one
plus
one
kt
equals
two
kitties.
What
query
patterns
could
do
is
write.
The
oneplus
one
kitty,
part
for
you
and
all
you
would
need
to
do-
is
just
write.
The
remaining
two
kikis
so.
A
C
A
very
basic
example,
but
it's
just
a
way:
it's
just
an
analogy
to
help
you
better
understand
what
they
are
if
you
want
to
know
where
they're
located.
So
this
is
in
the
low-key
query,
builder
you'll
notice
a
little
drop
down
over
here,
and
these
are
where
we
currently
house
some
of
our
query
patterns.
We
have
about
17
patterns
with
both
loki
and
prometheus
and
just
to
give
you
a
live
example
of
how
it
works.
If
I
select
one
of
these
patterns,
you
can
see
that
it
sort
of
fast
tracks.
The
query
for
me.
C
C
C
The
other
thing
was
there
were
no
descriptions,
so
whenever
you're
scrolling
through
these
patterns,
there's
no
way
of
knowing
what
they
will
do
or
what
they
are,
unless
you
click
on
one
and
then
you
get
the
sort
of
view,
so
it's
at
a
snapshot,
you're
not
getting
much
information
as
a
user
and
one
of
the
other
key
pieces
of
feedback
was
if
I've
started,
writing
a
query.
So,
for
example,
let's
suppose
this
is
a
working
query
which
it
is.
C
If
I
come
in
here
and
I
change
the
query,
I
don't
get
any
sort
of
message
that
says:
hey
you're
about
to
you
know,
replace
this
query.
It
just
simply
replaces
it
so
that
can
be
quite
frustrating
if
you
spend
time,
maybe
not
only
using
query
patterns
but
writing
out
a
long
piece
of
query
and
you
just
come
over
here
and
it
changes
it
for
you
so
just
to
address
some
of
these
issues.
What
we've
started
working
on
is
how
we
can
re-look
at
query
patterns
how
we
can
display
them.
C
So
this
is
one
of
the
intentions
that
we
built.
So,
as
you
can
see,
we've
renamed
the
button
to
kickstart.
Your
query
I'm
going
to
try
and
make
this
a
little
bit
bigger
to
kickstart.
Your
query
and
the
key
difference
now
is
when
I
hit
kickstart.
My
query:
a
modal
appears
and
the
query
patterns
are
separated
by
log
queries
and
metrics
queries,
and
immediately
from
here
I
can
go
into
whichever
section
I
want,
and
I
can
see
a
preview.
A
C
The
query
will
look
like
so
just
disclaimer.
This
is
dummy
queries.
They
reflect
pretty
close
to
real
queries,
but
just
so
you
know
up
front.
I
can
immediately
see
a
portion,
a
raw
query.
What
it
is
I
can
browse
through
them.
I
can
go
to
metrics
query
and
I
can
get
the
same
sort
of
preview
and
already
this
gives
me
a
lot
more
context
before
I
select
a
query
from
here.
I
can
simply
just
select
one.
I
can
complete
my
query
and
I
can
run
it
again.
C
C
If
you
were
to
look
at
the
other
issue
that
was
at
play
was
what
happens
if
a
user
has
a
working
query
and
they
want
to
replace
it.
So
if
you
can
just
remember
on
this
view,
all
you
need
to
do
is
just
come
and
replace
your
current
query
with
sort
of
nothing
stopping
you.
In
this
view,
the
user
has
a
working
query
and
they
would
like
to
explore
more
query
patterns.
They'd
come
on
here.
Click
on
query
patterns,
they'd,
maybe
have
a
list
of.
C
I
mean
I've
just
shortened
this
for
the
example,
but
they'd
maybe
have
a
list
of
20
queries
and
if
they
want
to
use
one
because
they
have
an
existing
query
already,
they
would
get
this
little
disclaimer.
That
says,
hey
you're,
about
to
replace
your
query.
With
this
query
pattern,
you
can
either
go
back,
you
can
either
replace
it
or
you.
C
A
new
query,
so
if
the
user
goes
back,
they
just
go
back
to
this
view
and
they
can
continue
on
if
they
replace
it.
It
would
replace
the
current
query
with
this
query
pattern
and
if
they
go
create
new
what
it
would
do
it
would
leave
the
original
query
untouched
and
just
add
another
query
row
and
a
query
section.
C
C
C
C
We
can
list
them
in
that
view,
or
maybe
have
its
own
view
and
then
the
ultimate
goal
with
query
patterns
is
to
have
customized
patterns.
So
we've
had
a
lot
of
feedback
from
users
that
want
on
an
organizational
level
or
on
a
personal
level.
They
want
the
ability
to
create
their
own
queries
and
use
that
as
as
they
go.
So
if
you're
in
an
organization-
and
you
have
five
common
queries
that
you
use,
you
want
to
be
able
to
sort
of
preset
that
so
that
users
can
use
them
on
a
daily
basis.
So
that's
just.
C
A
C
Different
forms
of
feedback,
I've
spent
some
time
with
some
customers
just
interviewing
them.
You
know
trying
to
understand
their
pain
points
on
the
current
usage
of
query
patterns,
but
also
gathering
from
the
community
and
the
main
common
threads
that
came
up
was
just
the
lack
of
descriptions
and
not
seen
the
actual
raw
query.
A
C
A
C
That's
what's
happening,
question
thanks
and
yet
so
we
do
have
our
loki
community
channel
so
you're
welcome
to
go
on
there.
You
can
reach
out
to
me
on
my
slack
handle
it
is
in
this
slide
as
well,
but
if
you
have
any
feedback
or
anything
you
can
reach
out
on
the
community
channel
and
I
will
gladly
engage
with
you
and
you
can
take
it
from
me.
D
So
lux
explorer
itself
is
already
a
very
great
feature
that
many
use,
but
what
we
heard
from
user
interviews
and
user
testings
is
that
some
features
are
maybe
a
bit
hidden
or
they
want
to
change
it
and
as
we
move
forward
with
locks
explorer
and
we're
looking
into
the
future,
we
want
to
consider
the
user
feedback.
So
when
we
reach
out,
we
don't
only
reach
out
to
paying
customers
but
also
to
our
community
and
we
reach
out.
D
We
read
our
github
issues
right
and
we
want
to
reach
out
to
everyone
who
has
feedback
for
us.
So
on
that
note,
you
can
also
reach
out
to
me
for
any
logs
explore
feedback
but
yeah.
So
I
want
to
show
you
a
few
little
things
that
we've
been
working
on
so
far.
I
would
say
small
feature.
Changes
have
big
impact
and
on
that
note,
I'm
going
to
share
my
screen.
D
D
Then
you
can
see
your
filter
labels
and
at
the
end
of
each
label
you
can
see
a
button
that
says
shell
context.
The
button
always
appears
at
the
end
of
a
lock
line
and
depending
on
how
long
it
is,
the
position
varies
all
the
time
and
we
want
to
bring
in
a
consistency
into
the
inconsistency
that
we
have
currently
just
to
make
it
easier
for
the
user
to
access
the
show
context
model
and
that's
wrong.
D
D
D
Okay
and
nothing
has
gone
on
so
far.
So
here's
the
interface,
you
see,
you
can
see
the
log
lines.
Let's
say
you
filter
it
for
a
label
and,
as
I
said
at
the
end
of
the
label,
at
the
end
of
the
log
line,
the
text,
you
would
see
the
show
context
button,
but
we
want
to
bring
in
a
consistency
and
we.
So
when
you
hover
over
a
log
line,
you
can
see
two
buttons.
D
Maybe
I
can
yeah,
you
can
see
two
buttons.
One
is
the
show
context
button
that
we
already
have
implemented,
but
now
it's
on
the
right
hand,
side
and
we
also
implemented
a
copy
button.
So
what
we've
seen
in
our
and
our
user
interviews
and
testings
is
that
users
sometimes
go
ahead
and
highlight
the
whole
logline
and
that
can
be
sometimes
tedious
and
we
want
to
make
everyone's
life
easier.
So
we
just
implemented.
D
D
D
D
So
some
users
said
they
would
like
to
download
they
weren't
aware
that
they
can
they
can
but
it's
hidden
in
the
future.
So
and
and
the
ui
I
mean
so
you
can
go
to
inspector,
you
can
go
to
data
and
somewhere
hidden.
Here
we
have
the
download
buttons
and
the
request
was
to
make
it
more
visible
and
because
it
made
sense
to
do
it
for
our
ui
and
the
use
cases.
D
We
are
going
to
do
something
here.
We
are
going
to
take
the
download
button
to
the
front
of
the
ui
based
on
the
user
feedback,
and
now
the
user
can
directly
with
just
simple
clicks,
see
it
and
download
it
when
needed,
yeah
and
then
one
more
thing.
This
is
one
of
my
favorites
like
I
said
this
is
small,
but
also
a
copy
icon,
so
the
users
said-
and
this
goes
back
to
filtering
they
like
to
filter
or
they
have
to
filter
for
labels,
to
see
a
specific
log
lines.
D
D
And
this
makes
our
life
a
lot
easier
and
we're
filming
for
it
without
any
copying,
highlighting
or
anything,
and
here
we
are
actually
that
was
it
small
changes
like
I
said,
but
big
impact,
and
what
I
also
want
to
mention
is
I'm
showing
small
things,
but
in
the
background
there
are
bigger
things
happening.
So
there
are
bigger
movements
and
I
hope
in
the
near
future,
but
definitely
in
the
future
you're
going
to
see
a
nice
transformation.
D
B
I
will
take
it
one
step
forward
forward
if
you
can
copy
do
another
buttons
and
you
can
actually
put
it
like
in
the
search
already
I
mean
you
copy,
then
you
you
have
it
in
the
clipboard
and
you
update
your
search
query
right.
Why
not
to
do
another
button
when
you
click
the
button?
It's
already
in
the
search
query
like
what
you
did,
but
in
one
step.
D
Yeah,
good
good,
good
feedback,
a
good
feedback
and
may
maybe
this
is
something
that
we're
going
to
do
for
the
future.
Maybe
we
we
are
already
working
on
it,
but
yeah
the
definitely
good
one.
So
what
you
mean
is
click
on
the
value.
It
goes
automatically
to
the
query
and
you
can
filter
automatically,
but
there.
B
D
B
B
B
D
D
B
I
feel
that
you
have
this
new
button
somewhere,
because
it's
like
now,
it's
everywhere
on
the
left
on
the
right
and
the
middle
and
the
top,
and
it's
I
mean
it's
at
the
point
when,
if,
if
you
added
this
download
button,
it's
kind
of
too
much
so
now,
users
have
access
to
everything,
but
it's
too
many
of
them.
So
you
don't
know
where
to
click.
A
Yeah,
I
feel
like
that's
always
one
of
the
trickiest
things.
Is
you
know
these
sort
of
quality
of
life
improvements?
You
know
they're
sort
of
shortcuts,
but
too
many
shortcuts
they're
no
longer
shortcuts,
because
there
are
too
many
of
them.
We're
starting
to
see
that
I
know
diego
and
I
have
talked
about
this-
a
lot
in
the
in
the
header
for
the
query
builders.
We
have
this
sort
of.
I
call
it
the
icon
parade,
because
it's
just
all
these
little
sort
of
like
record,
save
info,
there's
a
copy
there's.
B
I
think
we
should
just
feedback.
I
shared
before,
like
a
half
a
year
ago,
when
it
was
a
previous
ux
meeting
that
you
have.
I
mean
when
you
create
the
query.
The
queries
then
for
the
different
data
sources.
You
have
the
top
menu
with
a
lot
of
buttons
on
your
right
side,
and
now
you
have
the
code,
the
builder
and
everything
else,
like
a
second
line.
That's
going
to
be
the
third
line,
and
it's
too
many
and
users
get
scared
of
that.
A
Yeah
yeah,
I
mean
at
this
point
I
think
if
grafana
were
like,
like
a
swiss
army
knife,
it
would
be
too
heavy
to
carry
right
because
it
does
all
the
things.
So
that's
what
we
need
to
figure
out
is
what
are
the
most
important
things
so
and
that's
where
you
know
it's
really
interesting,
because,
as
a
ux
team,
we
have
been
scaling
up
two
different.
So
we
have,
you
know
ux
sort
of
like
designing
applications,
but
then
we've
also
been
scaling
up
our
research
capabilities
and
then
also
our
design
system
capabilities.
A
So
we
actually
have
people
who
now
are
dedicated
to
just
learning
more
about
how
people
are
using
things
and
what
people
want
to
do.
And
then
we
have
another
team,
that's
dedicated
to
really
making
our
components
much
more
consistent
and
understandable
and
useful
and
interactive,
and
we're
really
hoping
that
that
will
help
us
with
the
experience
overall
as
well.
So
we're
pretty
excited
about
that
as
a
ux
team.
A
B
Okay,
because
I
mean
you
you're
kind
of
you're,
your
ex
team
and
you
care
about
all
these
buttons
right
and
the
menus,
but
I
mean
the
environment
variables,
it's
the
same
story.
There
are
so
many
of
them,
and
here
the
developer,
you
kind
of
create
a
docker
file.
You
put
20
of
them
the
way
how
your
applications
behave
right,
and
so
it
should
be
a
better
way.
A
D
Yeah,
this
is
a
question
from
michael,
so
I,
what
I'm
hearing
is
that
you're
saying
give
the
options
right
implement
them,
but
if
I
don't
need
them,
let
me
hide
them
right.
Is
that
what
you're
saying
so,
whatever
we're
implementing
make
sure
that
we
don't
overwhelm
the
user
that
doesn't
need
it,
so,
whatever
we
increase,
make
sure
that
you
can
also
collapse,
it
probably.
B
Yes-
and
I
mean
there
is
like
extreme
cases
with
some
clients
who
just
use
a
graffana
as
the
interface
and
they
use
one
appear
and
they
use
the
application
plug-in
as
the
best
application
right.
So
they
don't
need
explorers,
they
don't
need
alerts,
they
don't
need
all
kind
of
functionality.
What
you
have
on
your
dashboard
at
the
beginning,
so
you're
kind
of
now,
with
the
new
features
you
can
disable
it
with
environment
variables.
B
A
I
think
we're
still
figuring
that
out.
Definitely
everything
you've
seen
here,
plus
more
but
yeah
we're
you
know
absolutely
in
planning
for
all
of
the
above,
like
I
mentioned
we're
kind
of
rethinking
the
sort
of
core
dashboard
creation.
Experience
want
to
make
that
easier
because
it
has
grown
in
a
lot
of
complexity
and
then
also
you
know
some
some
other
good
tidbits
for
ease
of
use.
Ease
of
use
is
a
big
theme
for
us
this
year,
and
so
you
know
as
ux's
we're
pretty
excited
about
that.
A
We'll
see
you
know,
I
mean,
I
think,
there's
sort
of
differing
philosophies
on
sort
of
having
major
release
large
items
versus
having
releases
be
a
little
bit
kind
of
like
rolling
up
to
larger
releases.
I
think
this
is
something
that,
like
you
know,
developers
can
talk
about,
maybe
like
over
friendly
drinks
together
like.
A
B
Okay,
no,
I
mean,
I
see
the
value
with
with
rolling
updates,
especially
because
we
have
a
integration
and
we
update
the
release
as
soon
as
possible,
like
in
a
week
or
two
after.
It's
actually
officially
done,
and
there
is
like
not
a
lot
of
breaking
changes
happening
right
and
if
there
is
a
happening,
it's
not
like.
Now
we
upgraded
to
nine
one
zero.
Nothing
changed
kind
of
nothing
like
nothing.
Breaking
happened
right.
So
it's
I
like
this
kind
of
upgrade,
but
still
it's.
I
know
I
know.