►
From YouTube: Grafana Community Call 2022-05-19
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
Cool
well
hi.
Everyone
welcome
to
another
grafana
community
call.
We
are
the
observability
experience
squad
and
we
wanted
to.
You
know,
show
you
a
bit
about
what
we've
been
doing
lately
and
you
know
open
up
more
conversations
around
it.
Basically,
so
this
is
the
form
of
our
squad.
Basically,
so
I
am.
I
am
the
engineering
manager
for
this
team.
Jay
is
our
pm.
Some
of
you
might
have
heard
about
him.
If
not
gulping
him
on
all
the
socials.
A
We
have
laura
who's.
Actually,
a
new
joiner
in
the
team
she's
been
here
here
one
month
today.
Congratulations
christina,
who
joined
us
a
few
months
ago
and
she's
been
doing
great
geo
and
pyotr
like
they're
the
veterans
of
this
team.
You
know
they've
been
around
for
like
over
a
year
and
poorik.
I
can
assure
you
he
is
not
our
janitor.
A
He
is
the
product
designer
that
we're
working
very
closely
with
right
now.
Basically,.
A
A
Yeah,
so
we
wanted
to
start
off
by
talking
about
our
mission,
because
this
is
something
we're
very
passionate
about,
so
we
are
here
to
create
tools
through
collaboration
and
innovation
for
software
engineers,
devops
and
sres,
so
they
can
correlate
and
inspect
their
data
in
order
to
respond
efficiently
to
business
and
technical
challenges.
A
But
I'd
say
even
more
importantly
than
this,
we
actually
have
an
internal
mission
as
well,
which
I
really
wanted
to
share
with
you
all.
So
we
actually
again,
we
want
to
create
a
healthy
work
environment
for
our
squad
members
in
order
to
make
them
successful
and
enjoy
their
work
by
collaborating
and
having
fun.
Why
this
is
important
is
because
we
all
wake
up.
A
You
know
in
the
morning
to
work
with
an
amazing
group
of
people
to
do
some
fun
work,
but
most
of
all,
you
know
to
continue
the
grafana
culture
and
values
basically
every
day.
A
So
in
terms
of
what
our
team
does
you
know,
grafana
is
well
known
for
his
dashboards,
so
why
did
we
invest
in
explore?
So
for
those
of
you
that
haven't
seen
explore,
please
go
to
grafana,
there's
an
icon.
On
the
left
hand,
side
navigation,
as
you
can
see
on
this
in
this
screen,
so
one
of
the
major
things
that
we're
responsible
for
is
explore.
A
Grafana
is
actually
focused
on
observability
and
explore,
is
all
about
searching,
investigating
and
exploring
your
data.
Basically
explore
is
a
great
starting
point
into
getting
to
know
your
data,
but
also
a
great
place
to
dive
into
the
nitty-gritty
when
you
get
paged
at
midnight,
for
example,
but
also
a
great
avenue
for
adding
more
panels
to
your
dashboards.
A
So
that's,
basically
what
we
call
search
share
and
save.
We
in
general
serve
a
breadth
of
personas.
Like
I
mentioned
earlier,
so
software
engineers,
sres
devops
incident,
responders
infrastructure
platform,
engineering
and
whatever
else
you
can
think
of,
but
in
general
you
know
to
summarize
all
that
explore
helps
you
understand
your
data
through
deep
dives
and
also
correlation
and
you'll
hear
more
about
it.
Throughout
this
talk.
C
C
So
one
of
the
new
things
that
we're
introducing
in
9
is
something
called
the
command
palette.
You
might
be
familiar
with
the
command
palette
in
other
applications.
It's
we
have.
It
mapped
to
the
command,
k
or
control
k
on
windows.
So
you
hit
that
and
it
comes
up
with
a
little
box
with
some
navigation
options
here.
One
of
the
things
is,
you
can
go
to
search
like
you
normally
could,
but
you
can
also
search
just
in
the
command
palette
directly
and
you
can
take
go
to
a
dashboard
just
like
that.
C
C
You
can
then
go
up
and
close
them,
and
then
you
can
run
query
just
if
you
want
to
keep
paying
it.
You
can
just
keep
running
that
query
over
and
over
again
without
having
to
touch
your
mouse
at
all,
so
yeah
from
that
back
segways
into
the
next
thing
that
we're
adding
to
in
grafana9
is
the
add
to
dashboard
button.
C
C
C
Well,
I'm
just
going
to
shout
it
because
I'm
very
excited
about
this
feature
hit
save
and
now
this
dashboard
just
shows
up
like
you
normally
would
so
with
that.
I'm
going
back
to
the
explore
page
here,
I'm
going
to
go
and
add
a
whole
bunch
of
these.
C
Hit
this
button
again
and
then
go
to
an
existing
dashboard
there
we
are,
and
you
can
just
keep
adding
new
panels
to
the
dashboard,
just
kind
of
as
you're
exploring
if
you
find
something
that
you'd
want
to
save
and
save.
So
all
that
will
be
released
in
grafana9
keep
stay
tuned
for
that.
D
Thank
you
yeah,
so
I
will
talk
about
queer
history.
Migration.
This
is
still
work
in
progress,
but
we
are
also
targeting
grafana
nine,
so
queer
history
is,
is
a
panel
in
explore
that
keeps
tracks
of
all
queries
that
are
run
in
explore
and
so
far
all
the
entries
were
stored
in
browser
local
storage,
and
now
we
are
migrating
all
entries
to
backend
database.
D
This
will
happen
behind
the
scenes
when
query
history
is
open,
and
why
are
we
doing
this?
So
local
storage
has
some
size
limitations.
The
storage,
the
storage
is
shared
among
other
settings
and
it's
also
not
possible
to
see
the
same
query
history
if
you
are
using
multiple
browsers.
So
after
the
migration
will
not
have
these
limitations
and
what
is
more,
it
will
also
enable
us
to
work
on
further
improvements
like
sharing
query
history,
history
with
other
users,
so
that's
it
for
grafana9.
D
What's
next,
our
main
focus
in
upcoming
weeks
and
months
are
like,
broadly
speaking,
observability
workflows
what
it
means
it.
It
covers,
features
that
improve
working
between
dashboards
and
explorer
and
also
querying
data
in
multiple
data
sources.
So,
for
example,
here's
an
example
of
such
research
flow,
which
is
like
incident
management
when
someone
gets
paged
with
an
alert,
goes
to
a
dashboard,
then
from
the
dashboard.
D
It
goes
to
to
explore
page
and
starts
investigating
the
issue
switching
frequently
between
between
metrics
logs
and
traces,
and
our
goal
is
to
to
make
such
workflows
as
smooth
as
possible.
D
So
what
else?
What
are
other
ideas
on
our
radar?
It's
it's
mixed
data
sources
that
you
may
know
from
dashboards
in
explorer.
You
can
only
use
one
data
source
and
we
want
to
allow
using
multiple
data
sources
within
a
single
explore,
page,
multiple
panels,
views
in
explore
the
split
view
that
we
currently
have
allows
you
to
see
only
two
panels
at
the
same
time
we're
thinking
about
adding
more
than
that
also
showing
annotations
in
explore.
Visualizations
something
I
mentioned
before
shared
query
history.
D
So
the
query
history
that
we
have
allo
also
to
to
share
it
with
other
users,
query
scratchpad,
which
is
an
idea
that
would
allow
easily
copy
and
paste
queries
between,
explore,
dashboard
and
and
also
alerts
a
customizable,
visualizations,
so
graphs,
maybe
even
lock,
lock
panel
trace
view
to
add
a
little
bit
more
customizations
to
it
or
maybe
even
explore
specific
plugins.
At
the
moment,
it's
really
hard
to
to
write
third
party
plugins
that
would
extend
explore.
D
It
would
be
great
to
have
this
the
same
way
we
have
for
for
visualizations
and
data
sources,
and
we
are
open
to
suggestions.
So
if
you
have
any
ideas,
how
explore
could
make
your
life
easier?
Yeah,
please
reach
out
to
us
on
on
github
discussions.
You
can
find
the
link
here
or
just
go
to
our
github
and
discussion.
Tab.
C
So
one
last
thing,
a
couple
team
members
will
be
presenting
in
an
upcoming
free
online
conference
in
mid-june
geo
will
be
presenting
alongside
ivana
and
torkel,
about
grafana9,
focusing
on
some
of
the
things
that
we
talked
about
today
and
a
bit
later
that
day
I'll
be
talking
about
an
iot
project
that
uses
a
bluetooth
scale
to
get
body
composition
metrics
into
grafana,
so
feel
free
to
check
out
the
schedule
to
see.
If
there's
anything
else,
that
would
be
relevant
to
your
work.
C
B
Oh,
I
actually
have
a
few
questions
really
cool
stuff.
There
was
some
stuff
in
there
that
I
I
actually
had
no
idea
about,
for
example,
the
the
chris
scratch
pad,
I'm
kind
of
curious
about
it,
you
kind
of
rushed
away
a
little
bit,
but
what
is
it?
Could
you.
D
D
Yeah,
they
came
up
with
the
the
feature
that
we
worked
on
going
from
dashboards
to
explorer
torquel
had
this
idea
that,
instead
of
having
like
very
specific
workflow
dashboard
to
explore
what?
If
we
wanted
to
go
anywhere
because
the
query
that
you
run
in
explore,
you
can
run
in
dashboard,
but
also
in
alerts.
So
the
idea
is
to
have
some
sort
of
like
a.
D
Panel
or
something
that
you
could
drag
your
query
to
to
like
save
them
for
later,
so
you
can
or
click
somewhere
just
to
have
them
in
your
clipboard.
So
you
have
multiple
queries
that
you
are
interested
in:
keep
them
like
in
in
the
pocket
that
it's
always.
A
D
You,
then
you
go
to
different
places
of
of
grafana
like
go
to
a
dashboard
or
specific
panel,
and
then
you
can
take
the
query
that
you
just
saved
like
temporarily,
but
you
may
be
interested
in
okay,
putting
it
inside
the
dashboard
or
inside
the
alert,
so
that
should
improve,
because
I
I
know
that
now
people
often
like
okay,
just
copy
paste,
okay,
they
need
to.
D
They
find
something
explore
it's
now,
it's
easy
to
add
it
to
dashboards
with
explore
to
dashboard,
but
people
still
sometimes
just
copy
paste
entire
query
and
and
move
it
somewhere
else,
though,
it's
not
easy
with
all
all
editors,
because
they're
like
we
built
visual
editors
with
buttons
with
a
lot
of
input.
So
it's
not
super
easy
just
to
copy
copy
the
query,
and
now
with
this
it
should
be
possible
and
much
much
easier.
B
Yeah
like,
like
you
said,
I
mean
I
I
do
it
as
well.
I
I
copy
paste
from
from
explorer
and
then
I
go
to
an
actual
dashboard.
So
I'm
I'm
personally
super
happy
about
the
the
add
to
dashboard
feature.
I've
been
waiting
for
that
for
for
a
long
time.
It's
super
easy
to
go,
go
from
the
dashboard
to,
but
now
that
we
have
that
to
dashboard,
I
think
that's
gonna
complete
that
workflow
really
really
nicely
and
yeah
the
the
scratch
pad.
B
It
sounds
like
yeah
for
sure,
like
some
form
of
workbench,
like
that
you
can.
I
don't
know
if
you've
thought
about
like
sliding
it
out
from
the
from
the
side
and
then
you
can
just
like
add
it
or
if
you
have
like
an
actual
query,
editor
in
the
the
scratch
pad,
so
that
you
can
edit
it
on
the
fly
and
then
you,
oh,
that's
interesting.
D
Idea,
I
think
we
haven't
thought
about
like
editing
them
inside
this,
but
that's
actually
a
cool
idea.
B
Yeah
all
potential-
and
you
also
mentioned
customizable
visualizations-
maybe
maybe
you
mentioned
it,
but
does
this
mean
that
we'll
be
able
to
use
like
custom
panel
plugins
and
explore
in
the
future.
D
Not
yet,
but
probably
so
at
the
moment
in
explore,
you
have,
for
example,
graph
graph
visualization,
which
is
very
simple.
You
can
only
change
it
to
like
bars
or
or
table
like
there's
very
simple,
simple
switch,
so
you
don't
have
all
the
options
that
are
available
in
dashboards
where
you
can
customize
everything,
and
it's
mainly
because
explore
is
more
up
for
artwork
investigation.
So.
D
Doesn't
really
persist
this
way,
but
still
it
would
be
useful
to
to
tweak
it,
especially
now
when
you
can
go
from
explore
to
dashboard
and
already
have
all
the
options
set
up
but
yeah
in
the
future.
Maybe
we
could
also
even
change
because
at
the
moment
it's
it's
basically
time
series
graph
that
it's
for
metrics,
but
maybe
we
could
allow
different
plugins
to
be
used
to
visualize
data.
B
Yeah,
I
I
know
there
there
are
use
cases,
for
example,
if
you're,
if
you're,
if
you're
exploring
the
humidity
in
a
room,
for
example-
and
you
want
to
see
what
different
sensor
picked
up,
for
example,
you
might
actually
want
to
use
a
more
you
know,
a
more
specific
visualization
but
you're
still
into
in
that
mode
of
exploring
and
and
you're
just
throwing
queries
around
and
and
you're
not
actually
building
a
dashboard,
but
so
yeah.
I
totally
get
what
you're
saying
that
you
know.
B
We've
been
focused
on
on
time
series
and
you
know
just
a
table-
works
well
for
a
lot
of
cases,
but
I
I
can
definitely
see
the
the
use
case
for
for
more
custom
visualizations
as
well,
but
yeah.
C
B
D
B
So
I
I
have
to
ask
them
like
is:
do
you
see
a
potential?
B
It
sounds
like
there's
a
potential
for
explorer
to
kind
of
get
closer
to
the
dashboard
feature,
and
maybe
that
dashboard
feature
comes
closer
to
it.
Explore
what
like
like
further
down
the
road
is,
what
is
like
the
one
defining
difference
between
the
dashboard
and
the
explorer
like
if
you
would
have
to
choose
like
one
thing
that,
like
this
is
only
possible
with
explorer,
and
this
is
only
when
you
should
use
it
with
a
dashboard.
For
example,
do
you
have
a
case
like
that.
D
A
D
And
I
guess
in
long
term,
in
future
the
dashboard
will
be
so
flexible
that
you
could
even
create
explore
page
with
some
some
more
customizations
around
it,
but
we
still
want
to
focus
on
on
on
like
ad
hoc
workflows
and
like
incident
management.
What
explore
gives
you
that
you
don't
have
in
dashboards?
There
are
some
some
panels
that
are
not
some
visualizations
that
are
not
available
in
dashboards,
like
lockspanner
has
way
more
features,
because
you
have
more
space
to
actually
play
with
it
and
trace
view.
D
D
So
it's
just
targeting
slightly
different
point
of
view,
but
yeah
I
can
imagine
that
both
can
be
used
and
should
be
used
more
or
less
at
the
same
time
and
there
should
be
like
smooth
transition
between
both
so
because
we
we
also
noticed
that
some
people-
okay,
they
use
dashboards
as
explorer.
Because,
okay,
you
can
customize
visualizations
right
and
we
don't
have
these
features
in
explorer.
Now,
if
you
had
them
yeah,
you
would
probably
be
more
encouraged
to
use
explore
and
we
won't
want
people
to
use
both
us
as
fast-class
citizens
in.
B
Yeah
grafana,
I'm
I'm
definitely
guilty
of
of
using
the
panel
editor
as
explorer,
but
mostly
you
know
it's
it.
It
is
really
quick
to
to
work
with
and
you
again
you
have
access
to
custom
visualizations
but
but
yeah.
So
I
had
one
more
question
for
for
christina,
I'm
personally
a
big
fan
of
command
panels.
I
I
love
it
every
every
every
site
I
join
or
or
sign
up
for
immediately
I
try
to
command
q
or
command
k.
B
I
mean
it's
such
a
game
changer,
but
I
I
was
curious,
like
what
what
led
up
to
implementing
it
in
grafana
was
there
like?
Was
there
a
issue
on
github
that
was
like
getting
a
tons
of
of
a
thumbs
up
or
like
what
was
the
process,
because
it's
not
like
a
necessarily
a
core
like
feature
like
like
quarry
history
or
you
know,
could
you
talk
us
through
it
about
like
what
was
the
process
of
getting
it
into
grafana.
C
C
I
guess
I
don't
really
know,
but
it
started
as
a
hackathon
project
and
that
hackathon
team
did
a
really
really
good
job
of
creating
a
very
thorough
implementation
over
that
week
and
kind
of
as
the
we're
running
up
to
implement
it
for
in
real
life,
for
being
a
little
bit
more
conservative
about
that
implementation
of
just
putting
it
in
a
little
bit
at
a
time
making
sure
because,
there's
you
know
a
ton
of
different
people
using
grafana
in
their
own
way.
C
We
want
to
make
sure
we're
not
breaking
anything
for
them
so
right
now
we
just
have
it
and
like
there's
the
global
commands
and
there's
some
in
explorer
and
we're
just
going
to
be
encouraging
teams
to
grow
it
in
the
way
that
makes
sense
for
them
but
yeah.
Hopefully
that
kind
of
answers.
Your
question
maybe
mahela
knows
before
that,
but
I
don't
unfortunately.
B
No
it
it
totally
does
so.
So
it's
a
hackathon
project
that
kind
of
went
straight
into
grafana,
which
is
really
cool
to
see.
Do
you
do
you?
Have
I
don't
know?
If
you
can
say,
do
you
have
any
other
hackathon
projects
that
are
coming
up
heading
into
explorer.
D
Annotations
in
explore-
yeah-
oh
very
nice
at
the
moment
at
the
moment,
there's
no
way
to
show
annotations
on
on
the
visualizations
because
they
they
have
different
editor,
so
slightly
different
flow.
But
this
is
also
something
that
was
a
hackathon
project
and.
D
The
the
the
common
palette
was
some
other
steam
hackathon
project.
We
just
and
it
didn't
win
the
hackathon,
but
everyone
was
like.
Oh,
this
is
such
a
cool
feature
that
we
should
have
had
this
like
long
time
ago,
why
it's
not
in
grafana
so
yeah
a
lot
of
people
were
excited
about
this
and
that's
why
we
decided
to
work
on
this.
B
Very
cool,
so
I'm
obviously
I
I
work
a
lot
with
plugins,
so
I'm
I
have
to
ask:
is
it
possible
for
plugins
to
to
add
items
to
the
the
global
or
the
like
the
command
handler.
B
There's
a
hackathon
project
for
anything
even
any,
and
if
you're
watching
this,
you
should
totally
go
and
google
for
for
the
doom
project
running
doom
inside
grafana.
That
is
amazing.
It's
a
such
a
interesting
way
of
using
using
grafana.
I
had
a
conversation
with
a
friend
earlier
this
week
about
using
grafana
for
as
an
like,
an
equalizer.
B
Now
that
we
have
streaming
data,
we
can
actually
use
it
for
like
a
as
a
streaming
data
into
it
and
we
can
have
like
equalizers
and
moving
data
in
real
time
and
and
it
really
we're
starting
to
see
so
many
different
use
cases
that
just
weren't
possible
in
the
last
paradigm
of
of
grafana.
D
D
B
They're
flying
by
yeah,
yeah
yeah-
I
it
took
me
a
while
before
I
found
it
actually,
but
it's
a
really
cool
feature.
It's
like
a
tail
right,
yeah,
yep,
yeah,.
E
Now
I
just
wanted
to
circle
back
to
your
question
about
the
process
of
of
getting
this.
In
from
from
academ
project,
I
mean
we
have
some
fairly
robust
forums
for
reviewing
and
christina
was
really
proactive
in
bringing
the
design,
and
you
know,
hackathon
project
is
one
thing:
gathering
requirements
and
feedback
and
and
building
out
the
design
was
a
big
part
of
the
process.
Here.
C
B
So
we're
actually
professionals
here
and
there
was.
B
Let's
not
get
ahead
of
ourselves
here,
yeah.
We
we're
definitely
doing
this
for
the
fun
of
it
as
well,
but
yeah
very
cool
to
see
what
what
you've
all
been
working
on.
Is
there
anything
else
that
popped
up
during
the
discussion
that
you
you
want
to
share.
A
So
pietro
has
already
mentioned
about
our
discussions
being
open
at
all
times.
You
know
we've
recently
restructured,
so
we
actually
have
you
know
a
lot
of
focus
on
explore
right
now,
so
we
would
very
much
welcome
ideas,
but
also
because
we
have
a
million
ideas
already.
You
know
we
do
have
to
prioritize,
but
we
always
welcome
contributions
right.
We're
we're
an
open
source
project
at
our
core,
so
we're
constantly
looking
at
open
pr.
So
we
would
like
to
invite
everyone
to
also
contribute
not
just
to
ideas
but
actually
implementing
those
ideas.
B
So
so
what
is
the
best
way
to
get
in
in
touch
with
the
explore
team?
If,
if
I
have
an
idea
for
for
how
to
improve
explore,
do
I
just
open
an
issue
on
github
and
thank
you
all
or.
C
You
get
to
see
my
that's
my
little
start
tab
thing
but
yeah.
So
in
the
grafana
project.
C
If
you
just
there's
a
discussions,
tab
here
and
then,
especially
under
the
observability
tracing
category,
this
is
where
new
new
feature
requests
go
and
then
we
prioritize
based
on
upvotes
emoji,
reacts
whatever.
So
this
is
a
good
good
place
to
go
for
new
features.
B
I
think
that
we
are
good.
I
think
we
can
start
wrapping
this
up.
It's
been
great
having
you
with
us
for
for
this
month's
community
call.
So
this
is
something
that
we
do
every
month
where
we
invite
a
squad
within
the
grafana
team
to
share
a
little
bit
about
what
they're
working
on
and
what
you
can
expect
in
future
versions
of
rafana,
and
if
there's
anything
that
you
would
like
to
hear
more
about
that
you're
curious
to
hear
from
the
teams
themselves
reach
out
to
us.
B
You
can
reach
out
to
us
on
on
grafana
slack
or
on
the
grafana
forum
or
as
we've
seen
in
the
in
the
in
the
github
discussions
as
well.
So
yeah
I'll
see
you
next
month,
bye
everyone!