►
From YouTube: Grafana UX Community Call 2020-05-04
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
Recording
we
want
you
to
also
drive
those
discussions
so
right
now
we
are
suggesting
the
topic
which
is
panel
at
it,
but
we
are
super
happy
to
use
those
calls
to
discuss
any
other
themes
or
features.
You
would
like
to
have
a
us
discussion
around
there's,
always
the
same
url
for
the
meeting,
and
you
can
subscribe
to
our
calendar
for
updates
and
this
this
presentation
will
be
available
in
the
public
ux
community
called
document
before
we
start.
Is
there
something
anyone
would
would
like
to
ask
about.
B
Take
this
as
a
nut,
I
have
a
question:
who
are
you
diana
and
what
do
you
do
with
rafana
labs.
A
C
Cool
cool
yeah,
I'm
david-
I
I
joined
grafana
about
two
years
ago
and
I'm
the
director
of
ux
and
I've
built
out
the
ux
team
with
diana's
help
as
a
sort
of
small
in-house
consultancy,
and
it's
I
think
it's
we
can
call
it
success.
They've
been
embedding
themselves
into
little
feature
teams
and
delivering
small
too
large
features
like
especially
in
our
four
graphana.
Seven
super
happy
with
how
it's
going
and
yeah.
I
guess
over
to
you,
jess.
E
So
hello,
my
name
is
lucas.
I
john
joined
last
month
so
probably
on
this
call
I'm
the
least
experienced
person
with
grafana
and
I
do
much
less
stuff
than
david
and
and
jess
and
diana,
but
I
try
to
do
more
and
more
with
each
month.
So
so
do
we
have
patrick
or
song
on
the
call,
I
think
not
so
probably
back
to
you
diana
yeah.
Thank
you.
A
So
patrick
and
song
are
not
here
today,
but
they
also
contributed
to
what
you
will
see
for
the
new
panel
edits,
or
does
it
truly
a
team's
effort
so
with
sorry
something
got
stuck
so
before
we
jump
to
the
panel
topic.
We
just
would
love
for
you
to
know
that
you
can
easily
reach
us
if
there
is
something
you
would
like
to
discuss,
give
feedback
on
or
maybe
grafana
isn't
working
the
way
you
would
expect
it
to
work.
A
You
can
reach
out
to
us
at
public
grafana
slack
we're
the
most
active
in
grafana
phil's
channel.
So
if
there's
anything
that
you
would
like
to
share,
you
can
post
it
there.
You
can
write
to
ux
grafana.com.
A
If
you
would
like
to
be
part
of
future
research
just
reach
us
and
we
will
get
involved
with
whatever
you
would
like
to
discuss
or
be
a
part
of.
D
A
Exactly
yeah,
so
when
it
comes
to
today
we
have
two
short
announcements.
We
will
show
you
a
new
panel
at
it
and
the
whole
story
behind
it
and
we're
hoping
for
a
for
discussion
around
this
and
also
your
feedback
and,
as
a
very
last
thing
today,
we
will
share
some
features
and
projects
that
we
plan
to
work
on
and
we'll.
Let
you
know
how
you
can
get
involved
if
you,
if
you're
interested.
A
Also
on
that
note,
I,
if
you
have
some
questions,
that
you
would
like
us
to
answer
you,
can
either
ask
this
or
write
on
the
chat
on
zoom
and
jess,
david
or
lukasz
will
take
a
look
and
make
sure
we
answer
all
the
questions
as
we
as
we
go.
A
Okay,
so
short
announcements,
the
most
important
one,
probably
graphana
7.0
is
available
for
beta.
So
if
you
want
to,
you
can
download
it
and
see
what's
new
also
grafanacon
will
happen
online
this
year
we
have
a
lot
of
great
speakers.
A
Well,
I
managed
to
fit
seven
of
them,
but
there's
way
more
than
what
you
see
on
this
screen,
but
if
you
would
like
to
take
part
in
it
just
register
on
on
grapanam
online
page,
it
will
be
all
available
in
in
this
in
this
presentation
and
also
if
any
of
you
would
like
to
take
notes
just
could
you
share
a
link
to
the
document
in
the
chat,
because
I
can't
open
it.
I
will
do
it.
A
Okay,
then,
just
will
share
the
link
to
the
document,
okay,
so
new
panel
that
it,
which
is
the
topic
for
today,
we
want
to
show
you
two
things:
two
dimensions
of
new
panel
edit,
so
one
is
new
layout
and
more
user-friendly
panel
edit.
A
That
is
more
intuitive,
helps
you
in
your
work,
makes
your
workflow
more
seamless,
the
other
part
of
what
we
want
to
show,
and
that
is
a
part
that
dominic
will
show
you
and
elaborate
on
are
some
new
features
that
hopefully
will
streamline
the
experience
between
different
types
of
visualization
visualizations
that
you
may
work
with,
so
how
it
all
started.
Basically,
there
were
a
couple
of
things
that
we
knew
for
quite
some
time.
A
So,
first
of
all,
the
current
wide
full-width
visualization
layout
was
really
hard
when
it
comes
to
presenting
options
in
a
scannable
way.
We
were,
it
was
a
lot
of
empty
or
wasted
space.
There
was
some
confusion
behind
panel
level
and
dashboard
level
options.
A
We
knew
that
the
icons
that
are
main
navigation
on
the
left
hand
side
are
not
very
intuitive
and
a
lot
of
kind
of
very
basic
options.
When
you
think
about
it,
I,
like
a
title
description,
were
hidden
quite
deeply,
so
that
was
something
that
we
already
knew
and
based
on
that,
we
started
with
something
we
can
call
our
first
educated
guess
so,
based
on
this
knowledge
would
build,
and
actually
that
was
patrick,
who
is
not
here
today.
A
He
built
a
concept
for
a
new
panel
edit
and,
as
you
can
see,
it's
not
very
detailed
concept.
Basically,
the
only
thing
it
shows
is
that
some
of
the
options
will
be
in
the
sidebar.
Some
of
the
like
more
query
related
things
will
be
at
the
bottom
pane,
and
that
was
basically
it.
A
We
took
this
and
we
went
to
talk
to
some
of
you,
so
we
run
research
in
several
rounds.
We
have
run
17
interviews.
We
talked
to
both
our
clients,
who
are
using
paid
version
of
rafano,
so
our
users
were
using
open
source.
A
During
all
this
research,
we
have
gathered
almost
300
observations.
That
is
everything
you
told
us
that
is
currently
not
working
in
the
panel
added,
how
you
would
like
panel
edit
to
work
and
also
your
direct
feedback
to
the
concept
that
we
showed
so
just
to
show
you
the
process.
In
a
nutshell,
it
was
a
very
intense
half
a
year
of
work,
so
we
started
with
the
initial
concept
that
patrick
created.
A
We
took
it
for
a
ride.
To
get
your
feedback,
we
summarized
findings
and
started
thinking
about
design
decisions
that
we
have
to
make
going
forward.
Based
on
that,
we
have
revised
the
concept
and
then
decided
to
talk
to
you
again
to
get
some
more
detailed
answers
to
some,
not
so
trivial
questions
and
what
we
will
show
you
today
is
the
very
final
version
that
went
through
those,
and
I
went
through
this
this
process
just
to
show
you
a
couple
of
findings.
A
This
is
not
everything
we
found
out,
but
I
think
these
are
the.
I
think
the
findings
that
were
most
crucial
for
us
so
first
finding
was
that
creating
panels
for
first-time
users
is
really
overwhelming,
and
it's
not
only
because
they
often
have
to
learn
about
grafana
so
much,
but
they
also
have
to
find
out
about
different
types
of
visualizations
how
they
work.
What
some
of
the
things
mean?
A
The
other
thing
was
that
we
have.
We
have
two
entry
points
for
creating
a
panel
and
you
could
either
start
with
query
or
you
could
start
with
the
visualization
type,
and
that
was
very
confusing
for
users,
so
they
were
wondering
whether,
if
I
start
with
visualization
will
I
have
different
options
available
than
if
I
start
with
query
and
the
other
way
around.
A
On
top
of
that,
we
found
out
that
the
people
we
talked
to
were
saying
that
80
percent
of
visualization
types
that
they're
using
is
graph
and
that
reality
changes
so
and
in
addition
to
that,
in
whatever
workflow
people
were
describing
to
us,
query
always
was
before
visualization
type.
So
it
no
longer
made
sense
to
keep
two
entry
points
and
I
think
one
of
the
finding
that
was
at
least
for
me
incredibly
important,
was
something
that,
before
this
research,
I
really
thought
about.
That.
A
Much
was
that
creating
and
editing
panels
are
two
different
workflows.
They
happen
through
the
same
screen,
but
they
are
distinctive
workflows
with
own
challenges
and
old
pain
points
and
creating
a
panel
from
scratch
is
not
the
same
as
trying
to
edit
panel
after
six
months
or
a
year
and
trying
to
figure
out
what
was
done.
A
So
we
got
apart
from
those
findings.
We
got
some
general
feedback,
like
general
response
that
it
was
great
direction.
We
should
keep
going
with
that.
There
was
also
feedback
on
stuff.
That
is
not
really
surprising
that
the
labeling
and
descriptions
have
to
be
better.
There
are
some
improvements
into
the
workflow
that
we
can
introduce,
but
the
main
game
which
is
being
able
to
work
on
aquarium
the
visualization
at
the
same
time
was
the
the
biggest
advantage
yeah.
So
this
is
this
part
was
hopefully
brief,
part
about
the
research.
A
Okay,
I
know
some
of
you
are
part
of
this
research,
but
if
you
would
like
to
ask
us
about
something
specific
to
the
research
that
I
have
mentioned,
just
write
in
chat
and
we'll
try
to
answer
this
yeah.
So
based
on
this
research,
we
formulated
design,
principles
and
design
principles
were
the
principles
against
which
we
would
evaluate
our
designs
and
the
prototypes.
A
So
there
were
four
of
those
one
was
make
obvious
what's
possible.
So
a
lot
of
people
that
we've
talked
to
were
surprised
that
you
can
edit
access
or
legend,
and
I
haven't
noticed
that
before
so.
It
was
very
important
for
us
to
make
it
obvious
and
easy
to
discover
what
you
can
manipulate,
and
on
that
note,
if
you
can
manipulate
something-
and
it
was
manipulated
that
we
should
show
that
this
particular
config
option
was
changed,
whereas
some
others
were
untouched.
A
There's
some
of
the
things
in
the
panel
that
it
require
breaking
flows
and
going
outside
of
panel
edit
to
change
variables
being
one
of
those
and
with
the
current
version.
We
are
we're
aware
that
we
are
not
able
to
fully
address
this,
but
we're
trying
to
put
at
least
some
quick
links
that
allow
users
to
make
the
workflow
a
bit
more
seamless,
and,
as
I
mentioned,
we
wanted
to
put
like
always
look
from
those
two
perspectives,
so
creating
panel
from
scratch
and
editing
panel
after
a
half
a
year
or
a
year.
A
So
all
in
all
the
research.
The
initial
research
has
answered
a
lot
of
questions,
but
when
it
came
to
details,
we
ended
up
having
even
more
questions.
A
So
we
actually
called
you
again
and
talk
to
you
about
where
we
should
put
variables
whether
they
should
be
in
a
separate
tab,
whether
they
should
be
in
the
sidebar
or
at
the
top
of
the
visualization.
A
We
asked
you
about
placement
of
the
visualization
type
picker,
whether
it
should
be
at
the
bottom
of
the
visualization
like
it
is
right
now
whether
it
should
be
in
the
sidebar
and
if
in
the
sidebar,
whether
it
should
have
a
separate
tab
or
not,
and
on
top
of
that
we
spent
some
time
working
with
this
change
indicator.
So
if
some
section
was
changed,
how
we
can
present
this,
how
can
we
make
it
obvious
for
users
that
this
particular
field
was
changed
and
either
by
users
or
overwritten
by
a
data
source?
A
So
we
asked
you
which
type
of
change
indicator
would
work
best
for
you,
whether
it's
a
dot,
whether
it's
it's,
it's
icon.
That
specifically
shows
what's
the
source
of
the
change.
A
A
A
Also,
one
of
the
people
that
I
talked
to
suggested
that,
having
linked
to
a
documentation
in
a
context,
would
be
a
great
help,
so
it
is
possible
now
to
show
for
us
links
to
documents
on
the
base
on
the
level
of
section
or
as
single
configuration
option.
A
We
have
also
new
options
when
it
comes
to
showing
this
visualization
render
here,
so
we
can
have
feel
fit
or
exact,
and
let
me
show
you
how
it
works.
A
A
Yeah,
it
will
keep
the
aspect
ratio
regardless
of
the
size
of
the
screen
and
exact
is
the
exact
size
it
would
be
now.
Something
is
not
working.
Exact
shows
how
it
would
be
shown
on
a
dashboard,
and
I
think
I
just
found
it
back
and
as
I
mentioned,
you
can
toggle
all
the
all
the
options
that
I
that
I
available
over
here.
A
F
F
So
if
you,
if
you
resize
it
to
a
small
one,
then
you
could
see
the
exact
size.
Okay,
I
mean,
if
you
resize
the
panel
on
the
dashboard,
not
yeah.
Okay,.
C
So
I
had
a
I
had
a
problem
the
other
day
when
I
tried
this,
where
the
when
I
wanted
to
edit
a
panel
and
it
had
a
certain
visualization
type
already
when
I
switched
to
the
the
panel
visualization
thing
that
showed
all
the
icons
the
selected
one
was
all
the
way
down,
and
for
me
that
was
a
bit
annoying
like,
for
example,
I
I
was
looking
at
the
logs
panel
and
logs
is
all
the
way
down
and
it
may
be
a
common
case
for
you,
then
yeah
and
and
but
it
was
yeah.
C
Yeah
like
what
was
selected:
oh
yeah,
no,
the
main
problem
was
there
was
a
display
error
and
the
panel
was
empty
because
the
query
was
wrong
and-
and
I
had
no
means
of
telling
what
the
what
the
panel
type
was,
because
the
panel
was
empty
and
and
then
so.
I
went
to
the
visualization
tab
here
to
that
panel
thing
and
I
had
to
scroll
and
I
had
to
first
of
all
because
we
changed
everything.
I
didn't
really
know
how
to
how
to
tell
which
was
selected.
C
A
Okay,
great,
that's
not
good.
Does
anyone
else?
Thank
you,
david.
That's
really
great
feedback.
I
think
we
even
discussed
this
a
bit
at
some
at
some
point
that
we're
discussing
idea
on
how
to
show
what
is
actually
which
visualization
type
is
actually
chosen.
A
G
I
have
a
question
yes,
so
the
the
visualizations
part
of
this
is
exposed
to
the
community
plug-ins.
So
is
all
this
compatible
with
all
the
older
community
plugins
or
do
those
need
to
be
updated
for
this
native
layout.
F
I
think
I
I
I
I
did
so.
The
question
was:
if,
if
the
old
plugins
community
plugins
will
work
with
the
new
with
the
new
architecture,
slash
new
layout,
slash
apis,
correct.
F
Okay
yeah,
so
the
question
is
yes:
we
have
introduced
some
changes
to
the
apis.
That
will.
F
Basically,
wrong
button.
We
have
introduced
some
changes
to
the
api,
of
course,
for
for
the
plug-in
engineers
to
to
kind
of
make
it
easier
to
integrate
with
with
the
new
functionalities
but
there.
But
there
is
one.
F
One
thing
that
we
need
to
remember
is
that
a
lot
of
our
plugins
community
plugins
are
implemented
in
our
old
architecture,
which
is
based
on
angularjs,
and
we
don't
expose
a
new
components
to
the
angularjs
compo
plugins,
because
we
want
people
to
implement
the
the
plugins,
the
the
plugins
and
migrate,
the
plugins
to
the
new
architecture.
F
So
if
diana,
if
you
don't
mind
switching
to,
for
instance,
the
actually
graph
panel
is
a
good
example.
If,
if
you
go
to
the
graph
panel,
one
more
time
to
the
edit
mode.
F
And
if
you
close
the
panel
type
pane
and
open
the
display
settings,
for
instance,
or
access-
oh
yeah,
exactly
this
is
okay.
So,
as
you
can
see
jacob
the
layout
over
here,
it
doesn't
look
great
and
that's
because
this
is
an
angular
panel,
and
this
means
that
it
uses
angular
components
and
those
are
not
100
compatible
design
language
wise
with
with
the
new
design
language
that
we
are
introducing
with
grafana
7.0.
F
But
a
lot
of
community
plugins
will
unfortunately
look
not
100
integrated
with
this
new
design
language
and
that's
just
because
of
the
of
the
fact
that
they
are
using
the
old
architecture,
but
all
of
the
plugins
that
are
going
to
be,
but
all
the
plugins
that
are
going
to
be
migrated
or
implement
it
in
react.
F
Those
are
going
to
be
basically
seamlessly
integrated
with
with
the
new
design
language
and
later
on,
I'm
going
to
show
you
a
demo
of
a
couple
of
new
features,
and
I
can
also
pinpoint
that
how
it
looks
like
with
the
new
with
the
new
design
language.
Sorry
for
a
long
answer.
F
I
Try
to
chime
in
I'm
testing
community
plugins
at
the
moment,
so
most
of
them
look
okay,
the
problem
that
they
might
have
is.
They
are
too
wide
so
say
the
display
tab
here,
for
example,
if
you
have
a
a
drop
down
or
which
is
much
much
wider,
that
you
get
some
sort
of
horizontal
toolbars
and
it
looks
a
bit
weird,
that's
the
biggest
issue
so
far,
yeah.
A
Let
me
so
mario
was
able
to
share.
Can
you
see
slack.
A
Yep
all
right,
so,
as
you
can
see
all
those
confusing,
can
you
describe
you,
mario?
We
can.
A
Yeah,
so
by
default,
the
width
of
the
sidebar
caused
the
drop
down
to
appear
instead
of
tabs,
and
it
was
a
bit
confusing
because
yeah
that
actually
happened
to
me
as
well.
When
I-
and
I
think
diana
actually
noticed
that
and
we're
well
aware
of
this-
and
this
is
something
that
we
want
to
fix.
So
as
much
as
long
as
we
will
be
able
to
show
tabs
we'll
be
showing
tabs
and
this
drop
down
will
be
only
kind
of
a
last
resort.
A
Okay,
some
new
icons
that
you
already
got
a
glimpse
of
song
design,
all
new
icons
for
panel
edit
in
7.0.
I
hope
you
love
them
as
much
as
we
do.
It
was
also
a
bit
of
a
journey
for
us
yeah.
We
answered,
I
think
this
part
of
questions.
F
I'm
gonna
introduce
myself
as
everyone
from
the
ux
team,
it
I'm
software
engineer,
working
the
front-end
platform
team
and
together
with
the
team
and
diana
and
jess
and
patrick,
we,
we
worked
on
the
new
panel
edit
experience
for
7.0,
but
apart
from
that,
we
also
work
on
a
couple
of
other
features
which
are
very
closely
coupled
with
a
new
panel.
Edit
experience.
F
Those
are
quite
advanced
features,
so
I'm
gonna
try
to
explain
those
as
simple
as
possible,
so
feel
free
to
like
disturb
me
and
ask
any
questions.
While
I
speak,
it's
no
problem,
so
two
features
that
I'm
going
to
show.
F
You
are
field
configurations
and
the
field
overrides
which
basically
are
aimed
to
unify
the
way
panels
are
configured
especially
the
panel
data
display
options
and
the
other
feature
is
called
transformations
and
and
transformations
are
basically
a
way
for,
for
people
manipulating
the
data
to
actually
filter
rename
reorganize
the
data
in
the
client
application
without
the
need
for
writing
additional
queries
or
yeah.
Basically,
writing
additional
queries
querying
the
databases.
F
So
let
me
share
my
screen
again.
I
need
to
find
the
button
over.
K
F
Okay,
cool
just
to
give
you
a
quick
impression
on
how
the
old
edit
mode
looked
like.
This
is
what
it
was
before
a
couple
of
tabs
on
the
left.
I
and
I
showed
that
before
and
now
the
new
edit
mode
looks
pretty
much
like
this,
so
there
is
quite
a
huge
first
huge,
visible
change
that
we
made.
I
can't
recall
if
you
mentioned
that
diana,
but
there
is
one
thing
that
is,
I
think
it's
worth
mentioning
about.
F
The
visual
architecture
of
this
new
panel,
edit
mode,
is
that
we
kind
of
divided
in
it
into
three
distinct
sections.
F
The
section
over
here
that
you
can
see
with
the
table
is
basically
a
preview
section
where,
where
your
visualization
is
kind
of
available
for
a
preview,
then
at
the
bottom,
the
bottom
pane
is
a
data
related
section.
So
everything
that
relates
to
querying
data
transforming
data
alerting
based
on
the
data.
F
It
belongs
to
this
bottom
pane
and
the
right
pane
is
all
about
the
visualization
settings,
the
visualization
visualization
settings
per
se
and
by
visualization
settings
I
mean
like,
like
general
visualization
settings
like,
for
instance,
whether
a
graph
should
be
shown
as
a
as
a
line
graph
or
as
a
bar
chart,
but
also
a
fine-grained
visualization
settings
like
how
a
single
particular
value
on
the
visualization
should
be
processed
or
shown
to
the
to
the
consumer.
Basically
sorry
what
was.
F
F
Any
any
questions-
or
it
wasn't
a
kid
talking-
sorry,
okay,
I'm
going
to
continue
cool,
so
so
the
first
I'm
going
to
present
that
on
the
based
on
the
table
panel,
since
it's
easiest
way
to
to
kind
of
show
the
data
and
and
see
the
visible
changes
like
straight
away.
So
in
this
table
I
have
some
data
from
multiple
sensors
showing
the
temperature
humidity
and
the
pressure.
I'm
not
sure
if
this
data
is
correct
or
not
it's
like
completely
random
data.
F
So
I
hope
you
don't
mind
so
the
the
first
thing
they
wanted
to
show
you
is
the
what
we
called
field
options
and
by
field
options.
We
mean
every
single
column
in
the
in
this
table.
That
you
see
is
something
that
we
call
a
field.
Basically,
so
for
every
single
column,
you
can
set
a
particular
set
of
options
and
we
have
grafana
camps
built
in
with
set
of
standard
field
options
that
are
available.
F
Those
are
options
like
you
need,
like
number
of
the
decimals,
to
show
the
title
field,
the
title
name
of
a
particular
column,
etc.
So
so
given
given
this
these
options,
we
can,
for
instance,
say
that
hey.
I
want
the
data
to
be
displayed
in
a
celsius
right,
so
I
can
set
my
unit
to
be
celsius
and,
as
you
can
see
right
now,
all
the
data
that
in
the
table
has
celsius
unit
applied.
F
But
of
course
this
is
wrong
because
the
humidity
and
the
pressure
is
not
something
that
you
express
in
the
celsius
so
we
have
introduced.
We
have.
We
have
another
concept
related
to
that
which
is
called
field
options
overrides
which
allow
you
to
specifically
target
set
of
fields
or
subset
of
the
fields
available
in
the
visualization
and
apply
like
a
different
options
to
those.
F
So,
for
instance,
I
can
say
that
the
humidity
the
humidity
field
needs
to
be
expressed
in
like
humidity
units,
so
I
target
the
humidity
column,
and
I
select
that
I
want
to
change
the
unit
of
that
column,
and
I
can
say
that
this
particular
column
is
going
to
be
expressed
with
this.
F
F
Unit,
that's
basically
expressing
expressing
hectopascals,
so
these
are
the
very
basic
settings
that
we
can
set,
what
we
call
the
the
standard
options,
but
apart
from
the
standard
options,
the
plugin
developers
can
also
can
also
support
what
we
call
custom
field
options.
So
this
is
the
react-based
table
panel
built
in
into
into
grafana
it's
a
new
table
panel
introduced
in
7.0
like
completely
rewritten
compared
to
the
previous
versions
and
right
now
those
couple
of
those
custom
field
options
are
available
for
for
this
panel.
F
So,
for
instance,
I
can
say
that
I
I
want.
I
want
the
temperature
cells
to
be
actually
displayed
with
a
background,
color
right,
but
again
the
the
field
options
apply
to
all
of
the
fields.
F
So
again,
I
need
to
create
an
override
that
will
target
this
specific
column
and
for
this
case
it's
going
to
be
a
temperature,
and
I'm
going
to
say
that
cell
display
mode
cell
display
mode
is
a
custom
table
option,
and
I
can
say
that
it's
going
to
be
the
background
is
going
to
be
in
a
color
and,
as
you
can
see,
the
colors
are
different
over
here,
because
I
have
specified
previously
at
thresholds.
So,
basically
the
base
threshold
is
in
this
color.
F
I
need
to
yeah
it's
orange
and
everything
above
40
is
going
to
be
rendered
as
red
and
all
those
all.
These
features
like
this
feature
field
options
and
the
field
override
standardizes
settings,
like
thresholds
and
the
ones
that
I
mentioned
before
the
standard
ones.
You
need
minimax,
decimals,
but
also,
but
about,
but
apart
from
the
standard
ones.
F
It
also
allows
to
customize
the
thresholds,
value,
mappings
and,
and
the
data
links
for
those
of
you
who
are
not
familiar
with
data
links,
basically
a
way
for
for
the
users
of
grafana
to
like
create
dynamic
links
that
you
can
link,
for
instance,
with
external
services
like,
for
instance,
services
that
that
you
use
for
digging
through
logs.
F
B
L
F
Actually,
I
think
you
s
you
still
can,
but
we
want
to
limit
that
to
to
a
single
one,
because
it
doesn't
really
make
sense
in
a
table
panel
right,
because
if
you
have
like
two
two
links
in
a
table,
it's
still
rendered
as
a
single
link.
So
so
this
is
something
that
we're
gonna
fix
for
stable
version
but
excellent
question.
But
if
you
want
to
target
like
that,
the
temperature
and
the
humidity
and
the
pressure
that
those
basically
link
to
different
services,
you
can
use
the
overrides
to
to
do
that.
F
So,
let's
assume
that,
like
currently
okay,
let's
say
that
the
humidity
needs
to
be
a
link
to,
like
I
don't
know
some
some
one
page.
You
can
create
an
overwrite
for
for
the
with
the
data
links
and
create
a
specific
data
link
for
humidity.
F
To
pressure.
F
F
Okay,
then,
let's
jump
on
some
other
new
feature
that
we
are
introducing
with
with
7.0
and
it's
the
feature
called
transformations,
and
this
feature,
as
I
mentioned
before,
is
strictly
related
to
to
the
data
itself
that
that's
available
in
the
panel.
So
it's
located
in
the
bottom
pane
of
the
new
panel
editor
experience
and
it's
located
as
a
as
a
next
step
or
next
or
a
tab
next
to
the
queries
tab.
F
So
this
is,
there
is
like
a
quite
a
natural,
it's
a
it's!
It's
a
result
of
the
placement
of
the
transformations
is
actually
kind
of
a
natural.
It
reflects
the
natural
process
of
how
you
work
with
your
data.
So
first
you
want
to
query
your
data
so
that
they're
available
in
the
panel.
F
But
then,
if
you,
if
your
specific
queries,
return
a
data
that
is
like,
I
don't
know
somehow
incomplete
or
incomplete
in
a
way
like
they're
missing
some
math
operations
that
that
are
not
available
in
your
in
your
data
source,
we're
introducing
the
transformations
that
allow
you
to
do
that
to
to
some
extent.
F
So
if
you
go
to
the
transformations
tab,
you
have
some
transformations
available
like
straight
away.
F
We
started
the
design
process
with
that
with,
like
a
very
small,
add
transformation
button,
but
we
quickly
realized
during
the
feedback
sessions
that
we
run
every
week
that
hey
this
is
not
gonna
work,
because
we
don't
people,
don't
know
what
the
transformations
are
and
like
what
transformations
are
available
for
for
them.
So
thanks
lucas
for
the
feedback,
this
is
the
actual
implementation
of
it.
F
So
right
now
we
have
all
of
the
available
transformations
presented
for
for
the
users
when
they
haven't
created
any
so
far,
so
there
are
a
couple
of
the
transformations
available,
but
let's
start
with
like
a
simple
one,
which
is
called
filter
by
name
filter
by
name,
is
basically
a
transfer.
Let's
imagine
that
you
have
this.
F
This
table
that
consists
of
four
fields,
stand
temperature,
humidity
and
pressure,
and
you
and
in
your
visualization
you
want
to
only
show
time,
temperature
and
humidity.
So
what
you
can
do
here
is
you
can
basically
click
on
the
pressure
and
without
making
any
new
queries,
the
data
is
displayed
without
the
pressure.
F
So
this
is
a
very
a
very
simple
one
right,
but
then
we
have
more
advanced
one
like,
for
instance,
change
order,
hide
and
rename
previously
called
organize,
but
the
change
order
hider
rename
is
more,
is
a
better
name.
So,
as
the
name
suggests,
you
can
first
change
the
order
of
the
columns.
F
So
let's
say
that
the
humidity
gonna
be
first
and
then
you're
gonna
have
a
temperature
and
time
and
again,
this
is
done
without
any
queries
to
the
to
the
data
source,
and
you
can
also
rename
rename
the
the
columns
to
something
more
meaningful,
like
capital
time
capital
t
time,
it's
definitely
more
meaningful,
sorry
yeah,
so
so
so
this
is
more
advanced
one,
but
then
we
have
even
more
advanced.
F
F
So
what
you
can
do
here,
for
instance,
you
can
have
a
binary
operation
that
creates
a
new
field
like
a
dynamic
field
which
is
a
result
of
a
math
operation
between
any
other
fields.
In
your
in
your
in
your
data,
so
for
instance,
in
this
case
we
can
have,
we
can
select
that
we
want
a
sum.
F
It
doesn't
make
sense
at
all,
but
we
you
we
want
a
sum
of
humidity
and
the
temperature,
and
this
creates
a
new,
a
new
field
which
is
basically
a
sum
of
those
two
did
it
sum
correctly.
Yes,
it
did
yeah,
so
the
so
the
transformations
are
still
in
a
beta.
It's
like
an
early
early
stage
concept,
but
we
decided
to
put
it
into
7.0
to
get
as
much
feedback
as
possible
yeah
and
pretty
much.
That's
it.
A
A
So
if
you
get
a
chance
to
play
with
it,
a
bit
feel
free
to
get
in
touch
and
give
us
feedback.
We're
super
we'll
be
super
happy
to
to
get
your
thoughts
on
it.
Meanwhile,
I
just
know
there
is
a
comment:
love
the
future,
okay,
great
jacob.
We,
if
you
get
a
chance
to
try
it
out
and
you
have
any
comments,
how
to
improve
it
and
how
it
can
be
even
better,
then
just
reach
out
and
let
us
on.
F
Yeah
jacob
we
are,
we
are
aware
that
the
transformations
are
kind
of,
at
least
in
the
beta,
a
version
of
7.0
they're,
quite
buggy
still,
unfortunately,
and
we're
making
our
best
two
to
actually
squash
as
many
bags
as
possible
before
the
stable
release.
F
So
if
I
may
have
a
suggestion
for
you,
if
you,
if
you're
gonna,
try
those,
then
it's
the
best
way
to
to
start
with
those
is
to
start
with
the
table
panel
because
they
can
because
then
you
can
see
like
straight
away
what
happened
to
your
data
and
if
you
are,
as
dana
mentioned,
if
you
are
confused
with
any
of
the
options
that
are
available
in
the
transformations
reach
out
to
us
on
slack
and
let's
talk
about
it,
how
to
make
it
better.
A
There
are
a
bit
there's
a
bit
more
feedback
in
the
graph
on
a
face
channel,
so
one
is
to
be
able
to
name
overrides
because
you
end
up
having
overrides
one
two
three,
so
thank
you
for
that.
Mario.
That
is
something
that
we've
also
discussed,
and
I
think
we
need
to
revisit,
and
also
jamie
mentioned,
that
it
would
be
good
to
be
able
to
collapse
and
expand
all
the
sections
in
the
sidebar.
F
So
I
will
take
this
into
account
as
well.
Sorry,
it
does,
does
it
mean
like
collapse
and
expand
all
of
the
sections
at
once?
Okay,.
B
How
long
are
the
transform
code
like
code
exists?
Is
it
like
after
you
make
that
change
it
stays
or
do
you
like?
Is
there
a
recovery
point
that
you
can
do
for
it
just
curious
on?
Is
there
a
way
for
you
to
be
able
to
revert
back?
If
you
made
a
change
and
you
want
to
recover
it.
B
F
But
what
you
are,
are
you
asking?
If
we
like
from
the
development
side,
we
have
a
way
of
doing
that
or,
if
you,
as
a
user
of
the
transformations,
have
a
way
to
do
that,
a
user,
oh
yeah,
of
course,
yeah
you
can.
You
can
always
delete
the
transformation,
as
diana
mentioned,
we
also
planned
for
the
future.
We
also
plan
to
be
able
to
allow
to
reorganize
the
transformations
in
a
like
more.
I
don't
know
you
experiment
with
those
and
the
transformation
pipeline,
because
the
transformations
are
applied
one
after
another
right
so
the
so.
F
The
order
here
is
important
because
result
of
every
single
transformation
is
passed
to
the
next
one.
So
we
also
want
to
introduce
our
ability
to
reorganize
those
if
it
happened
that
you
created
those
in
a
wrong
order,
for
instance,
and
and
you
don't
want
to
create
everything
from
scratch,.
L
B
L
L
Just
a
suggestion,
and
if
you
guys
don't
have
we
don't
have
time
anybody
who's
doing
it,
click
on
a
panel
title
and
then
click
inspect.
It's
a
nifty
new
feature
that
we've
added
in
7.0
it'll
help
you
troubleshoot
and
stuff.
A
F
Okay,
cool
yeah.
Actually
this
is
one
of
the
most
important
features
of
of
grafana
7.0.
Can
you
see
my
screen
back
again.
D
F
Okay
cool,
so
so
the
feature
that
diana
mentioned
is
called
panel
inspect
and
it
basically
is
aimed
to
help
you
troubleshoot
the
data
that
came
into
your
panel
from
the
queries
so
from
the
panel
menu.
I'm
not
sure
everyone
is
familiar
with
the
panel
menu
already
or
not,
but
it's
the
menu
available.
When
you
click
on
the
panel
title,
we
have
added
this
new
option
called
inspect
and
what
inspect
does
it
opens
a
drawer
on
the
right
height
right
hand,
side
of
the
screen
that
displays
you,
the
road
data
with
applied
transformations?
F
So
basically
it's
like
a
tabular
data.
It's
very
it's!
Actually,
I'm
gonna
show
it
yeah,
maybe
on
this
panel,
because
that
one
is
yeah
there
you
go
so
it's
like
a
regular
table
that
displays
the
data
in
a
like
a
row
format
with
transformations
applied
that
kind
of
samurai
that
allows
you
to
deback
whether
whether
the
data
in
the
graph
is
actually
a
correct
one
or
not,
and
of
course,
a
really
important
addition
here
is
that
you
can
actually
download
the
data
in
a
csv
format.
F
This
panel
is
also
available
from
the
edit
mode
and
I'm
going
to
the
edit
mode
on
purpose,
because
I'm
going
to
add
a
new
query
now,
so
this
panel
now
has
a
two
queries
in
it
right.
So
when
I
inspect
the
panel
now
this,
these
two
options
appear
at
the
top,
which
basically
are
a
simplified
transformations.
F
So
having
those
two
series,
I
can
join
them
by
time
and
download
the
csv
of
those
two
series
joined
by
time,
which
is
super
useful,
going
forward
with
the
inspect
panel.
We
also
have
like
a
stats
tab
which
shows
you
some
performance
overview
of
your
queries.
F
As
you
can
see,
this
are
not
very
like
a
deep
matrix,
but
we're
gonna
work
on
like
improving
those
to
to
have
some
more
details
about
how
much
time
did
it
take
to
to
actually
render
visualization
how
much
time
did
it
take
to
to
proceed
to
to
apply
transformations
etc.
But
this
is
on
our
roadmap.
F
Another
tab
over
here
is
it's
called
json
and
it
basically
is
useful,
especially
for
people
who
are
working
with
the
provisioning
or
want
to
dig
deeper
into
what's
the
underlying
model
of
the
of
the
panel.
So
the
panel
json
is
something
that
we
is
something
that
we
that
represents
a
panel
in
our
like
a
dashboard
model.
Basically,
so
all
of
the
properties
are
available
here
and
those
are
those
basically
describe
your
entire
panel.
F
There
is
also
a
panel
data
which
is
basically
a
response
from
the
the
data
that
was
processed
and
passed
to
to
the
panel,
but
it's
displayed
in
a
kind
of
a
raw
json
form,
and
last
but
not
least,
is
the
data
frame
structure.
I'm
not
going
to
go
deep
into
what
data
frame
is
it's
basically
a
a
data
model
that
we
use
to
to
work
with
data
under
the
hood,
and
you
can
inspect
that
model
over
here
and
the
very
last
tab
is
called
query.
It's
it's
a
query
inspector.
F
Basically,
it
allows
you
to
see
what
was
the
actual
request
and
response
sent
to
the
back
end
in
order
to
perform
the
query
that
you
have
created
in
your
in
your
in
your
query.
Editor.
You
need
to
quit.
You
need
to
click
refresh
over
here,
because
this
will
trigger
the
new
queries
in
order
to
collect
the
data,
and
I'm
not
gonna
do
that
now,
just
because
I'm
on
a
test
data
source,
so
I
will
get
no
results
so
yeah.
This
is
the
inspect
mode.
F
A
M
No,
I
can't
see
any
any
questions
on
slack.
F
Okay,
are
there
any
plans
to
store
some
of
the
stats
around
query,
load
times,
etc?
So
we
can
monitor
the
monitor.
F
Having
accessible
via
dashboard
is
a
great
improvement,
but
I
would
love
to
be
able
to
view
it
over
time.
So
I
can
see
the
impact
of
the
changes
I
make
to
my
dashboards
and
data
sources.
I
don't
I
haven't
heard
any
anything
about
such
features.
Daniel
are
still.
L
No,
I
mean
the
you
know
that
in
the
graphonic
configuration
you
can
actually
enable
grafana
to
send
data
about
itself
to
oh
yeah,
the
metric
said
endpoint
and
you
might
be
able
to
find
it
there.
I'm
not
positive,
though.
F
But
jamie
we
we
haven't
planned,
we
have,
we
haven't,
had
any
plans
about
integrating
that
in
that
into
the
inspect
top,
but
that's
actually
a
great
idea.
It
might
be.
It
sounds
like
something
that
might
be
super
useful,
but
diana
you're
right
that
probably
the
metrics
that
we
collect
from
from
the
grafana
itself
might
be
something
that
you
can
track
the
progress
or
track
the
changes
that
you've
made
to
your
to
your
queries
with.
But
I'm
not
sure
I
can
get
back
with
that
question.
A
Information
right
anyone
else,
any
questions,
thoughts.
A
D
Jamie's
question:
in
the
slack
channel
the
slack
channel
mario.
F
Okay,
when
adding
an
overwrite,
the
only
option
is
filter
by
name.
Do
you
plan
to
add
more
options
there?
Yes,
we
do,
but
we
just
couldn't
squeeze
that
into
into
7.0,
but
we
do
have
plans
to
to
add
some
more
options
there.
F
What
one
of
the
like
a
super
I
mean-
maybe
not
super
quick,
but
quite
easy
thing
that
we
could
do
to
improve
there
and
we
plan
to
do
is
to
enable
regular
expressions
in
the
filter
by
name
because
currently
it
all
you
can
only
select
by
you-
can
only
select
from
the
from
the
options
that
are
available
there.
But
we,
we
plan
to
add
pretty
much
the
same
thing
that
we
added
to
the
transformations
that
the
filter
about
name
can
also
accept
regular
expressions.
F
So
so
so
you
can
expect
that
fairly
soon,
probably
not
in
7.0
stable.
If
we're
gonna
do
the
point
release,
maybe
that's
gonna
be
introduced
in
in
some
of
the
point
releases,
but
other
than
that.
I
I
I
think
that
7.1
might
be
like
a
reasonable
estimate
for
for
some
new
override
filters.
What
we
call.
A
Okay,
it's
been
over
an
hour
so
before
I'll.
Thank
you
all
for
joining
I'm.
I
would
love
to
ask
you,
because
this
is
our
first
community
call
and
we
experiment
a
bit
with
the
format
at
the
way
we
run
this
discussion.
What
can
we
do
better
next
time.
A
And
just
be
honest,
we're
super
happy
to
to
know
how
to
make
this
even
more
exciting
for
you
and
useful.
H
Time
and
quite
honestly,
be
bold,
like
now's
the
time
yeah
I
mean
next
call
is
also
the
time,
but
anything
literally
anything
you
want
to
be
talking
about
anything
you
want
to
be.
You
want
to
see
on
the
agenda
anything
even
if
you
think
it's
a
stupid
question
most
likely.
It's
not
a
simple
question.
Just
go
ahead,
be
bold!
You
don't
bite
promise.
L
L
Because
if
somebody
says
oh,
they
have
all
these
errors
in
the
docs,
it's
like.
Oh,
they
read
the
docs
and
if
you
know
you
say,
oh
I'm
having
trouble
with
this
feature,
they're
using
the
feature
and
they
have
thoughts
about
it.
So
please,
let
us
know
we
love
feedback.
C
I
think
it'd
be
good
if
the
presentations
are
a
tiny
bit
shorter.
I
think
yeah
we're
a
bit
long
and
I
do
like
it
when
we
read
out
kind
of
like
what
problems
people
have
so
maybe
from
the
failed
channel.
If
we
collect
some
historic
ones,
yeah
cool.
A
So
if
you
have
any
ideas
for
future
topics,
then
then
just
feel
free
to
suggest,
and
yes,
we,
a
color
on
this
topic
or
a
feature
and
we'll
discuss
everything
you
want
about
it.
A
Thank
you.
Jamie
really
happy
that
you,
like
the
part
about
the
g
about
the
journey.
A
All
right,
okay,
also,
if
you,
if
the
feedback
for
this
session
comes
to
you
later
today
or
tomorrow,
then
also
post
on
grafana,
fails
we'll
take
it
to
our
hearts
and
hopefully
make
even
better
than
xcx
coming
up
to
go.
Thank
you,
adele
yeah.
A
I
guess
one
final
announcement
is
that
we
will
be
running.
We
will
be
running
a
bit
more
research
around
onboarding
about
around
lucky
and
scrolling
logs
around
did,
I
say,
onboarding
probably
settled.
There
was
sorry
one
more
thing
on
my
list.
A
Yeah
then,
just
let
us
know
if
you,
if
you
want
to
be
a
part
of
this
okay,
thank
you.
Everyone
have
a
great
day
or
evening,
depending
where
you
are
and
hopefully
see
you
next
month.