►
From YouTube: Grafana UX Community Call 2020-06-01
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
C
Okay,
let's
see
it's
recording
now
perfect.
Thank
you,
richie,
all
right
yeah.
So
that's
what
happened
with
your
feedback
from
last
time,
yeah,
whatever
you
want
to
share
today,
put
it
on
slack
put
it
in
the
chat.
Probably
jess
will
take
notes
as
she's
really
good
at
it.
Yeah
and
we'll
show
you
next
time
what
will
happen
with
all
this
feedback
and
hopefully
we'll
be
able
to
cater
for
most
of
the
things
that
you
mention
yeah
some
announcements
we're
hiring.
C
So
there
is
more
and
more
work
on
our
play
that
we
want
to
make
rafana
as
good
as
possible,
but
there's
only
six
of
us
at
this
point.
So
if
any
of
you
know
the
designer
who
would
love
to
join
griffana,
let
them
know
the
link
to
this
presentation
will
be
in
the
doc.
This
role
is
also
available
on
our
website.
C
A
couple
of
words
of
the
projects
that
are
coming
our
way
and
and
research
will
be
running.
So,
if
you
have
anything,
you
would
like
to
share
about
your
onboarding
experience
or
how
it
is
or
was
starting
to
use
grafana.
We
would
love
to
hear
you
if
you
have
any
experience
with
grafana
cloud.
Please
let
us
know-
and
we
would
love
to
have
a
chat
about
this-
we're
also
looking
into
some
improvements
in
the
search
and
navigation
area
and
logs.
C
So
if
any
of
this
resonates
with
you,
if
you
have
any
comments
on
any
of
those
topics,
please
let
us
know
and
reach
us
at
uxsoftgotha.com
yeah.
We
also
together
with
graphana
7.0,
launched
our
storybook,
and
we
have
a
republican,
ui
library
and
I
will
hand
over
to
twice.
D
B
How
would
you
look
at
that
perfect
yeah,
so
my
name
is
tobias:
go
ahead,
I'm
a
front-end
software
engineer
here
at
carfana
and
I'm
gonna
talk
a
little
bit
about
kind
of
how
we
have
worked
with
implementing
our
design
system
and
with
our
library,
grafana
ui.
B
So
grafana
has
been
growing
growing
kind
of
organically
over
the
past
couple
of
years,
and
the
problem
with
that
is
that
it
kind
of
gets
a
little
bit
out
of
hand.
So
we
have
like
the
design
is
very
inconsistent
across
the
product,
and
that
is
something
we
want
to
kind
of
change
with
with
our
like
our
design
system.
So
it's
both
for
like
making
grafana
a
more
consistent
product,
but
also
for
plugin
developers
who,
like
wanna,
be
they
want
their
plugin
to
look
like
a
part
of
your
phone.
B
Basically
so
we're
working
with
this
and
we're
also
providing
guidelines
on
like
how
to
use
these
elements
and
where
to
use
them
and
when
not
to
use
them,
which
is
kind
of
a
good
tab.
B
So
we
want
to
make
this
kind
of
publicly
available
so
especially
for
for
plugin
developers.
D
B
For
internal
people
who
who
want
to
easily
access
it,
so
we
have
web
kind
of
two
links
you
you
can
go
to
developers.graphon.com
ui
and
you
will
be
redirected
to
like
the
latest
release
of
grafana
ui
or,
if
you're
really
like
on
the
edge
here,
you
can
go
to
ui
canary
and
you
will
receive
the
freshest
of
the
freshest
straight
out
of
the
press
and
we
have.
We
have
some
written
documentation
for
these
components.
Some
we
don't
but
we're
getting
there
we're
working
on
it.
B
So
I
thought
I'd
show
you
around
a
little
bit.
So,
let's
see
where,
where
did
I
put
it?
No,
oh
by
the
way,
here's
the
temperature
in
my
apartment
really
hot!
Oh
my
god!
This
is
in
the
way.
B
On
a
little
bit
how
to
use
storybook
quite
interesting,
I
thought
I
thought
I
guide
you
through
it
a
little
bit
so
on
the
left.
We
have
like
all
these
components
we
use
somewhere
in
grafana
and
let's
have
a
look
at
a
button
here.
Maybe
so
we
have
a
canvas
tab
which
basically
is
just
the
component
in
itself,
where
we
can
kind
of
interact
with
it
and
play
around
with
it,
and
here
to
the
right,
you
have
what
we
call
knobs,
which
is
basically
a
way
to
like
control.
B
What
kind
of
properties
you
want
you
want
for
the
component
so
yeah
we
maybe
want
a
pen
icon.
No,
we
can
get
it
cool.
We
can
change
variance
here,
so
you
can
play
around
with
it
a
little
bit
and
to
the
right
here.
We
have
the
story
so
to
speak,
which
is
basically
like.
It
shows
you
how
it
is
implemented.
B
B
Examples
like
how
to
use
it
and
when
to
use
it
and
where
to
use
it
and
at
the
bottom
here
we
have
kind
of
a
props
table
for
for
the
component
to
see
basically
what
you
can
use-
and
these
should
be
reflected
in
in
the
canvas
here,
but
we
don't
have
it
for
for
all
components
yet
so
we're
working
on
it.
B
B
So,
where,
where
are
we
currently,
then
we're
kind
of
establishing
a
process
around
around
this
design
system
for
how
to
add
and
remove
components
in
kind
of
a
good
manner?
B
So
basically,
if
you
find
an
error
or
some
missing
documentation,
definitely
to
tell
us
like
you
can
use
slack
or
git
tab,
or
maybe
just
say
it
here,
and
if
this
is
something
you
you
need
we
we
will
definitely
like
we'll
fix
it,
no
problem
and
kind
of.
Interestingly,
do
you
miss
a
component
in
our
design
system?
Is
there
something
that
you
think
like
hey?
Maybe
someone
else
would
like
this
too,
like
definitely
don't
hesitate
to
to
contact
us
and
we'll
we'll
get
around
to
it
so
yeah.
B
I
guess
that's
kind
of
a
short
introduction
to
to
store
book
and
kind
of
the
work
we've
done
around
the
design
system
and
yeah
a
little
bit
about
how
we
implemented
it
so
definitely
check
out,
store
book
and
just
tell
tell
us
how
you
feel
about
it.
C
C
C
Okay,
I
mean
we
will
still
if
you
have
any
comments
later
on
and
if
you
want
to
first
play
with
our
storybook,
then
there's
a
bunch
of
stuff
on
twitter
about
this
you
can
reach
also
to
buy
us.
You
can
wrote
the
ux
community
yeah
we're
happy
to
have
a
discussion.
Also,
if
you
want
to
contribute,
then
let
us
know
all
right.
So
moving
on
to
some
7.0
features.
C
C
C
Yes,
okay,
so
one
of
the
first
things
I'd
like
to
show
you
is
something
that
I
just
worked
on,
and
that
is
a
query
history.
So
whenever
you
go
to
explore
now
you
have
query
history
available,
which
is
your
own
query.
History.
C
If
you
click
on
it,
you
get
a
drawer
with
a
week.
C
Of
queries
that
you
have
used,
I
have
to
close
this
a
bit
yeah.
You
can
search
by
a
data
source
a
rather
filter.
In
this
case
you
can
switch
the
data
source
and
run
a
query.
If
you
want
you
can
choose
some,
you
can
mark
some
queries
as
your
favorite
ones
and
have
them
at
hand.
C
C
C
So
did
any
of
you
had
a
chance
to
use
query
history
or,
if
not,
do
you
have
any
comments
or
feedback
or
maybe
questions.
C
Yeah
we
get
this
question
from
time
to
time.
Currently
this
is
only
for
for
you,
so
it's
locally
stored.
So
if
I
may
ask-
and
it's
perfectly
fine,
if
you
don't
want
to
disclose
this,
would
it
in
what
use
case?
Would
it
be
useful
for
you
to
have
it
shared
with
your
team,
for
instance,.
D
One
way,
I'm
thinking
of
if
there
was
someone
that
ran
too
large,
of
a
database
on
a
postgres
and
it
took
down
our
like
dev
or
test
instance,
one
time
and
if
we
were
able
to
go
back
and
see
what
kind
of
queries
that
they're
running
we
could
critique
and
possibly
help
them.
Not
take
our
instance
down
that.
That
was
one
way
I
was
thinking
of
it,
but
educational
tool
yeah
exactly
not
that
it
would
be
and
and
just
being
able
to
share
it
with
someone
else.
D
I
know
you
could
share
your
screen,
but
if
they
were
able
to
look
through
what
kind
of
queries
you
were
running,
I
think
it
could
help
them
learn
and
be
able
to
see
how
other
people
are
running,
queries
and
maybe
work
towards
a
better
process.
A
Yeah,
it's
a
very
interesting
point
because
we
have
done
some
research
around
this
feature
and
almost
everyone,
especially
the
not
so
advanced
users
that
we
interviewed
said
that
they
would
love
to
look
at
other
people's
queries.
So
they
would
like
a
team
feature
to
see
how
others
do
it
and
learn
from
that.
But
most
of
them
were
a
little
bit
ashamed
of
having
everyone
see
their
queries
because
they
were
all
a
bit
like
yeah.
A
But
my
queries
are
so
bad
and
I
make
so
many
mistakes
and
a
lot
of
them
fail
and
then
everyone
can
see
how
many
failed
queries
I
enter.
So
what
do
you
think
about
this
sort
of
moral
dilemma
of
feeling.
D
You're
not
skilled
enough
yeah
yeah.
I
hear
you
on
that
because,
like
that's,
that's
something
like
you
know,
you
have
to
learn
that
failure
is
not
always
a
bad
thing.
I
I
personally
think
I
would
appreciate
being
able
to
see
when
someone
else's
query
failed,
maybe
just
as
like
an
admin
perspective
of
like
I
can
look
and
help
support
them,
but
I
I
definitely
get
like
there
is
you
there's
associated
shame
with
like
maybe
taking
something
down
or
taking
a
dashboard
down,
but
I
think
just
from
a
perspective
of
insights
it
would.
D
It
would
be
useful
to
be
able
to
look
and
see-
and
maybe
that's
like
a
feature
where
you
could
toggle
it
on.
So
other
people
can
see
your
queries
and
then
toggle
it
off.
So
it's
just
private.
You
know
what
I
mean
or
be
able
to
choose.
I
think
that
would
be
really
nice
because
then
it
kind
of
gives
you
the
ability
to
be
anonymous
and
not
show
off
what
you
got
going
on.
I
don't
know.
D
Yeah,
it
kind
of
makes
me
think
of
like
github
repos,
where
you
can
make
it
private
or
public
or
shared
just
in
the
sense
of
like
there
is.
There
is
a
way
to
have
private
code,
but
if
it
is,
I
mean
we're
all
sharing
an
instance.
You
know
like
if
you're
yeah
like,
if
you
accidentally
take
it
down.
Why
wouldn't
you
want
to
learn
how
to
improve?
I
think
that's
part
of
the
nature
of
technology.
I
don't
know.
A
A
C
I
think
it's
super
interesting
how
a
lot
of
users
talk
about
educating
people,
especially
every
time
we
show
a
query
history
like
we
had
several
instances
when
we
discussed
how
to
help
someone
educate
their
own
team
and
that
query
history
was
kind
of
an
immediate
answer
like
having
shared
queries
or
predefined
queries
by
a
query.
History.
C
C
Okay,
so
we've
created
by
inspect
drawer,
so
you
can
access
it
either
from
the
dashboard
by
clicking
I
or
using
this
menu
over
here.
C
Or
you
can
just
go
to
edit
mode
and
use
link
in
the
edit
mode.
So
what
you
get
is
all
the
data
you
can.
You
can
get
all
the
stats
about
total
request,
time,
processing,
time
number
of
queries
that
you
are
run
and
total
number
of
rows
that
you
got.
You
get
the
json
one
and
you
can
get
info
on
raw
request
and
response,
but
because
some
queries
can
be
very
expensive,
we
don't
run
them
by
default.
C
Also,
you
can
download
download
a
csv
file
yeah
and
that
pretty
much
sums
up
the
inspect
drawer
did
any
of
you.
I
mean
it's
been
around
for
a
bit
longer.
It
wasn't
released
with
7.0.
It
was
released
a
bit
earlier,
so
did
any
of
you
have
had
a
chance
to
to
use
it
at
any
question.
C
Okay,
yes,
that's
perfectly
fine
and
we
ended
up
in
the.
I
think
I
believe
you
were
here
for
the
last
call,
so
you've
probably
seen
it
the
new
panel
edit,
which
now
has
a
sidebar
in
which
we
have
all
the
settings
for
basically
modulating
visualization.
C
C
A
All
the
things
that
you
can
do
in
this
panel
edit.
So
I
think
like
once
you
like
swallow
and
breathe,
and
I'm
like
okay
now
I
I'm
reading
everything.
That's
here
another,
oh
there's
so
much
stuff
to
do
here.
Then.
I
think
this
is
really
helpful,
at
least
to
me,
like
I'm,
not
the
most
technical
grafana
user.
I
still
have
to
play
around
a
lot
to
see
what
everything
does
and
I
feel
like
seeing
all
the
things
that
I
can
do
and
having
more
tooltips
that
are
directly
visible
and
stuff.
That's
super
helpful
to
me.
B
So
something
that
I
notice
is
kind
of
you
you
don't
like
before
I
I
always
had
kind
of
a
need
to
look
for
things
like
oh
where's,
this
store,
and
now
it's
like
the
visualization
settings
like
it's
under
like
panel
field
and
overrides
tabs,
and
if
you
just
click
through
those
three,
you
will
probably
see
what
you're
looking
for
kind
of
immediately.
C
I
think
one
of
the
things
that
is
coming
hopefully
very
soon
is
an
additional
feature
that
will
make
it
even
easier
for
panel
for
you
to
browse
options
in
panel.
Edit
is
a
filtering
option
for
the
sidebar,
so
you
will
be
able
to
basically
type
in
any
configuration
field
you're
interested
in,
and
it
will
just
show
you
those
options
immediately
so
that,
together
with
collapse
and
expand
all
which
is
the
feedback
we
got
last
time
should
even
more
improve
the
discoverability
and
the
navigation
through
the
whole
new
partner.
C
Oh
yeah
and
the
change
indicator,
so
one
of
the
things
that
we
found
out
during
research
was
that
a
lot
of
our
users
would
love
to
not
necessarily
when
the
panel
is
created
from
scratch,
but
when
it's
being
edited
after,
let's
say
a
couple
of
months
or
half
a
year,
and
especially
by
someone
who
then
created
the
panel
in
the
first
place.
C
So
what
we
will
add
here
is
a
change
indicator
which
will
show
you
which
of
those
options
were
changed,
meaning
which
of
those
sections
were
manipulated
by
someone
to
create
this
visualization.
C
Yeah
any
thoughts.
C
Improve
all
right,
sorry,
this
is
there's
not
that
much
that
I
would
like
to
share
today.
Is
there
anything
you
would
like
to
discuss
regarding.
A
For
example,
as
diana
mentioned
in
the
future,
we
want
to
tackle,
search
and
navigation
and
that's
usually
a
topic
that
people
have
a
lot
of
opinions
about.
So,
if
there's
something
where
you
have
any
thoughts
of
the
top
of
your
head,
please
now
is
a
good
time
to
mention
them
or
in
our
slack
of
course,.
C
Yeah,
I'm
too
quick
with
quitting
yeah,
so
next
month
will
be
all
about
logs,
so
jess
will
probably
run
this
community
call
and
we
would
love
to
show
you
what
we
what
we're
working
on
when
it
comes
to
logs,
probably
andre,
will
also
show
you
tracing
that
we
have
just
integrated
into
grafana
and
we
would
love
to
get
your
thoughts
on
that.
C
Is
there
something,
and
that
is
only
our
suggestion.
So
if
there's
anything
runthorn
or
adele,
you
feel
like.
Maybe
it's
worth
tackling
next
time.
Just
let
us
know-
or
maybe
you
already
have
an
idea
that
would
be
nice
to
discuss
next
time.
D
I
don't
know
if
everyone's
there
or,
if
I'm
just
doing
something
wrong,
but
every
time
I've
tried
to
like
run
queries
on
there
and
do
like
a
reduce
or
something
it
gives
me
unexpected
error
and
it
could
be
a
complete
user
error
and
I'm
just
goofing
up,
but
I
think
that
would
be
really
valuable
to
me
to
have
a
better
insight
into
how
that
works
and,
like
ideal,
ideal
ways
to
utilize
it,
like
maybe
best
use
case
scenarios.
D
Just
I
mean
I
I
think
I
understand
the
element
of
like
what
it
is,
but
I
don't
think
I
am
using
it
properly
or
even
like
docs
to
read
through.
That
would
be
beneficial.
C
Yeah,
I'm
pretty
sure
it's
us,
not
you.
We
get
the
comment
about
transformations
quite
a
lot.
It
was
just
introduced
and
we'll
be
definitely
working
on
making
it
even
better
I'll
talk
to
dominic.
He
was
presenting
transformations
last
time
and
I
will
also
pass
this
information
to
the
rest
of
the
team.
C
Yeah
that
we
got
a
lot
that
we
get
a
lot
of
comments
on
that
and
other
would
love
to
maybe
have
some
bigger
intro
to
transformations
and
some
better
documentation
that
I
think
something
can
work
on.
But
are
you
aware
where
we
at
currently
with
transformations.
E
Where
we're
out,
I
suppose
the
the
bad
thing
about
it
is
that
it's
broken
on
7.0
one.
At
the
moment
we
did
a
patch
release
and
broke
them
and
yeah
it's
going
to
be
another
few
days
where
we
get
out
the
next
patch
release,
so
they
only
work
on
7.0.0
at
the
moment
or
on
latest
master,
otherwise.
Otherwise,
it's
sorry
a
beta
beta
phase.
I
would
say
so.
E
We
don't
quite
support
everything
yet
that
we
used
for
like
the
old
table
styles,
but
they
are
still,
I
think,
already
very
useful,
depending
what
you
want
to
do.
So,
like
a
a
good
example,
so
I'm
working
on
a
data
source
for
our
forum
and
it
has
a
very,
very
limited
api.
So
you
can't
like
get
out
that
you
can
just
get
out
like
a
number
per
day
and
that's
it
and
then
with
transformations.
For
example.
E
I
could
do
things
and
you
know,
get
the
sum
over
30
days
and
and
things
like
that,
which
you
could
not
do
with
query
language.
E
So
if
you,
if
you're,
if
you
have
like
a
very
limited
data
source-
and
you
can
already
backfill
that
quite
a
lot
with
the
transformations
and
there's
lots
more
features
coming
in
in
the
upcoming
releases,
so
we
are
basically
adding
more
and
more
transform.
So
it's
going
to
get
more
full-featured
over
the
next
two
or
three
releases,
and
it
also
enables
a
whole
bunch
of
new
visualizations,
which
you
also
would
be
working
on.
E
D
Yeah
I
mean
I
I
just
wanted
like
best
use
case
scenarios,
but
I
think
we
just
updated
to
7.1.0.1
yesterday.
So
if
it's
not
even
a
feature,
we
can
use
at
the
moment
I'll
just
stay
tuned.
A
C
But
I
think
also,
although
are
you
able
to
share,
or
what's
your
use
case
for
those
transformations.
D
So
I
mean
that's
what
I
was
more
trying
to
understand
like
what
the
like.
I
have
data
sources
that
I'm
using,
and
I
like
one
use
case
I
can
think
of-
is
I'm
actually
pulling
in
like
cloudera
manager,
hadoop
clustering,
other
directories
and
I
wanted
to
reduce
by
directory
type.
I
have
written
out
my
queries
already
and
then
like
kind
of
did
them
by
variable,
but
I
think
that
the
transform
feature
would
be
really
great
for
that.
D
It
would
make
it
simpler,
because
I
wouldn't
have
to
pull
those
queries
as
much,
but
I'm
not
sure
if
that's
the
best
use
case
scenario,
I
don't
know
what
the
best
use
case
scenario
is
for
everything,
because
I'm
so
new
to
the
transform,
and
that
was
more
where
I
was
coming
from
yeah.
What
did
that
answer?
Your
question.
E
I'm
not
sure
I
quite
quite
got
it.
How
was
you,
how
are
you
hoping
to
reduce.
D
There
was
like
so
I
my
column
is
directory,
like
it's
called
directory
name,
and
I
would
like
to
be
able
to
just
search.
I
don't
know
if
it
is
the
reduce
or
what
feature
it
was.
I
really
haven't
played
with
it
that
much
because
every
time
I've
tried
it.
Actually,
it
just
said
unexpected
error,
so
I
I
would
like
to
be
able
to
have
it
sorted
by
directory
name.
D
Does
that
make
sense?
Is
that
a.
E
E
It
it
is,
but
it's
still
like
in
beta
that
is
not
there
yet.
So,
yes,
I
think
we
will
be
adding
things
like
soar
and
limit
yeah.
D
E
Not
sure
when
that
will
be
exactly
701
or
702,
where
you'll
be
able
to
say
sort
by
a
column
and
then
say
you
know,
give
me
the
top
five.
D
Okay,
yeah:
no!
That's
exactly
what
I'm
trying
to
do
so.
D
B
E
Yeah,
so
not
quite
yet
yeah.
Unfortunately,
I'm
really
sorry
about
the
the
the
bug
we
we'll
try
not
to
let
that
happen
again.
C
Yeah,
apparently
I
was
talking
to
myself
but
yeah,
so
we're
moving
slowly
toward
the
the
end
of
this
course.
So
does
anyone
else
or
maybe
you
are
they'll
have
yet
another
topic,
yeah
we'd
like
to
discuss.
C
Okay,
I'll
take
this
as
a
no
thank
you
so
much
everyone
for
joining
next
month,
like
I
mentioned
we'll
discuss
all
stuff,
looks
related
yeah
once
again,
thank
you
for
joining
us
and
having
giving
us
really
great
feedback
yeah
and
we'll
keep
you
posted
in
the
meantime.
If
there's
anything
pressing,
please
post
on
grafana,
fails
or
reach
out
reach
us
at
ux
graphite.com.