►
From YouTube: Grafana UX Feedback Call 2021-02-24
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).
B
A
C
Okay,
thank
you
jess.
Hopefully
I
will
not
go
over
the
time,
although
there's
a
huge,
huge
opportunity
to
do
that
with
that
topic,
definitely
there's
a
link
for
a
short
usability
session
that
you
might
watch
afterwards
if
you
haven't
had
an
opportunity,
yet
I
will
be
referring
to
that
a
bit
so
so
you
can
definitely
check
it
out
and
and
yeah.
I
will
start
sharing
my
screen.
C
D
F
E
C
F
C
C
Yeah,
okay,
so
a
bit
of
an
introduction
this.
This
is
a
complicated
topic.
So
if
I
will
be,
if
I
will
be
speaking
chaotically,
please
stop
me
and
if
you
have
any
questions
like
please
do
as
well,
and
I
think
like
this
is
like
a
perfect
example
of
a
design
problem
which
is
usually
stated
one
way
and
then,
when
we
go
deeper
into
that,
we
understand
that
it
was
not
really
the
problem
that
we
stated
at
the
beginning.
C
But
something
else
is
there
and
on
that
terms
the
misleading
part
might
be
that
we
are
talking
about
a
new
navigation
which
means
that,
oh,
if
we
do
a
new
navigation
and
just
put
the
everything
that
we
have
right
now,
there
grafana
will
be
more
navigable
in
the
future.
But
unfortunately
that
is
not
the
case,
and
there
are
like
few
reasons,
a
few
reasons.
Why
so?
C
First
of
all,
if
you
have
watched
that
that's
a
short
session
that
I've
sent,
you
will
notice
that
people
who
are
not
using
grafana
on
a
daily
basis
get
or
get
lost
on
even
a
basic
level
of
navigating
grafana,
so
reaching
out
dashboards
or
finding
the
specific
dashboard.
And
the
reason
is
that
our
home
page
has
an
icon
of
a
dashboard,
is
a
dashboard
and
when
you
are
clicking
on
the
dashboards
on
the
navigation,
you
actually
land
on
the
home
page
and
not
in
the
dashboards.
C
And
if
you
want
to
browse
dashboards,
you
need
to
open,
not
dashboards,
which
is
a
homepage
on
that
case.
But
you
actually
need
to
launch
a
search
which
is
a
browse
browsing
list
for
the
dashboards.
And
of
course
you
can
reach
that
list
within
the
dashboards
itself.
But
then
you
have
to
you
need
to
remember
that
it
is
called
manage
dashboards.
C
So
it
is
very
complicated
people.
People
get
get
confused
by
that.
What
is
more,
on
our
navigation,
we
just
stuff
more
and
more
things
which
are
either
like
only
two
icons
for
people
who
are
viewers
and
with
restricted
access
to
many
elements
of
grafana,
if
they're,
for
example,
in
an
enterprise
environment,
or
they
have
everything
if
they're
admins
of
a
of
such
an
instance
with
all
the
apps
shortcuts
thrown
there.
So
it's
navigation
is
either
like
huge
or
really
really
really
small.
C
So
in
the
end
we
have
like
a
three
types
of
information
architecture,
like
that's
a
basic
thing
for
most
systems,
so
we
have
like
a
system
information
architecture
so
how
it
works.
Under
the
hood,
we
have
the
ui
that
is
telling
people
what's
the
information
architecture
and
we
have
like
information
architecture
that
is
in
the
minds
of
of
people,
so
a
mental
model
that
people
put
to
the
system.
Thinking,
oh,
how
it
will
work
work
and,
in
our
case,
all
of
those
three
information
architectures
are
are
disembodied.
C
So
there
is,
there
is
no
translation
between
the
system,
ui
and
the
mental
model.
Each
of
those
information
architectures
works
differently.
So
this
is
the
biggest
problem,
actually
that
that
we
are
facing-
and
you
will
probably
see
some
more
so
but
yeah
back
to
the
to
the
project
that
I
am
actually
talking
about.
So
with
thinking
about
the
new
navigation.
C
I
had
like
definitely
a
few
things
on
my
mind,
so
first
of
all
do
not
break
anything
so
changing
the
navigation
potentially
can
disrupt
like
everything,
even
like
our
relations
with
community
and
with
customers
who
are
building
their
own
plugins,
etc,
etc.
So
it
is
important,
at
least
for
me
in
that
project,
to
propose
something
that
can
work
easily
with
what
we
have
right
now,
so
it
will
not
require
like
redesign
of
the
whole
grafana
from
start
to
to
the
end.
C
The
second
thing
is
that
the
vertical
space
is
is
precious
in
grafana,
so
stacking
a
lot
of
navigations
as
a
horizontal
bars,
definitely
is
not
going
to
to
work.
My
goal
was
also
to
to
make
that
navigation,
narrow,
viewport
friendly
either.
If
we
are
talking
about
mobile
or
just
like
making
our
browser
screens
narrower,
it
should
make
a
bridge
to
the
cloud
portal,
which
is
more
and
more
important.
We
are
lacking
breadcrumbs
currently
so
introducing
breadcrumbs
and
introducing
more
levels
of
navigation,
maybe
not
in
that
specific
form.
C
Definitely
and
last,
but
not
least,
probably
will
need
a
new
home
page
or
a
template
for
a
for
a
home
page.
Give
flexibility
like
or
more
flexibility
to
us
and
to
a
third
developers,
maybe
think
about
paid
features
that
might
be
part
of
that
of
that
new
navigation
concept
and
definitely
be
future
proof,
and
so
all
those
things
I
had
in
mind
when
I
was
when
I
was
doing
the
designs,
but
the
thing
that
I
struggled
the
most
was
was
actually
like.
C
What
is
the
metaphor
that
can
explain
grafana's
structure,
because
what
we
have
right
now
is
that
we
have
stocks
and
instances
of
grafana.
So
that's
the
level
0
that
I
sometimes
say
to
myself.
Then
we
have
the
grafana
itself.
So
the
thing
that
we
see
when
we
log
into
grafana-
and
we
have
a
lot
of
apps
that
are
running
within
that
grafana
and
some
of
them
are
core
like
dashboard,
explorer
or
search
on
that
part,
because
just
it's
just
like
a
list
of
dashboards
and
some
are
just
coming.
C
So
I
was
like
wondering
what's
the
metaphor
and
I
couldn't
find
it
in
any
application
or
in
any
app
and
in
the
end
I
found
that
metaphor
in
something
that
is
just
like
at
the
reach
of
your
hand,
and
that
is
basically
the
operating
system
because
grafana
with
all
those
new
features
and
all
those
new
products
that
we
put
into
it,
is
becoming
more
and
more
like
a
observability
operating
system,
and
there
are
many
analogies.
C
So
first
of
all,
the
ops
are
usually
self-contained,
so
the
apps
are
complicated,
but
you
just
run
inside
apps.
Of
course
we
have
like
some
links
between
them,
so
you
can
jump
from
explore
to
dashboards,
etc,
etc,
but
in
general,
most
apps
are
self
contained
and
they
are
usually
multi-level.
So
you
go
deeper
inside
those
apps
as
well.
Some
apps
are
core,
so
you
cannot
remove
a
finder
from
from
mac
os.
C
You
can
install
more.
There
are
some
elements
that
are
like
a
system
status
elements
like
notifications
or
just
a
clock,
and
you
have
a
custom,
customizable
dock
and
a
and
a
mini,
and
on
os
you
switch
users
for
us
we
can
switch
instances
or
or
stocks.
So
the
structure
that
that
gave
me
is
actually
nothing
like.
That
seems
like
a
completely
new
concept,
so
it's
actually
the
navbar
that
is
familiar
to
us.
C
And,
of
course,
we
can
introduce
the
concept
of
the
of
the
home
page,
but
we
can
as
well
have
a
switcher
for
stocks
or
for
instances,
although
I
don't
know,
if
that's
a
thing
right
now,
maybe
it
can
in
the
future,
but
stocks
can
be
changed
or
switched
definitely,
and
we
can
then
have
a
bridge
back
to
the
grafana
cloud.
So
I
will
show
you
mock-ups
in
a
in
a
few
seconds,
but
because
I
was
discussing
this
concept
with
historical
dominic
natalia
in
the
morning
as
well.
C
I
noticed
that
torkel
was
asking
a
lot
about
what
happens
afterwards.
So
what
happens
on
the
level
of,
for
example,
navigating
the
specific
dashboard-
and
this
is
the
part
which
is
actually
in
my
mind,
like
in
progress
and
the
next
step,
so
be
aware
that
what
I'm
showing
you
right
now
is
the
navigation
from
stocks
to
grafana
as
a
metaphor
of
operating
system
and
and
applications,
but
I'm
still
in
progress
of
figuring,
now
figuring
out,
navigation
inside
specific
objects
and
what
are
those
objects?
C
Well,
those
objects
are,
are
those
things
that
people
create
when
they're
inside
specific
apps?
So
so
what?
What
can
be
this
object
or
that
thing?
Well,
it
can
be
a
dashboard,
it
can
be
a
report,
it
can
be
a
data
source,
it
can
be
a
plug-in
and
usually
we
send
it
seen.
We've
seen
this
see
this
in
grafana
in
this
form,
so
either
as
a
dashboard
or
maybe
as
a
playlist,
because
here
we
are
inside
dashboard,
but
we
are
actually
inside
a
specific
place.
C
So
that's
an
object,
or
maybe
inside
a
specific
plugin
in
on
in
that
example,
a
github
one.
The
interesting
part
is
that
we
can
also
have
an
object
of
specific
data
source
on
that
case,
the
csv
data
source
or
an
object
of
a
report.
The
funny
thing
here
is
that,
on
the
reports,
what
you
see
on
tabs
is
a
navigation,
the
first
level
of
navigation
for
reporting
up,
but
what
you
see
here
on
the
data
sources,
although
it
looks
completely
the
same,
that
is
the
navigation
for
that
specific
data
source,
which
is
csv
csv.
C
C
I
just
need
to
find
them
somewhere
here
here
they
are
so
how
that
how
that
structure
actually
looks
like
so
it
doesn't
seem
like
a
rocket
science,
because
it
isn't
because
navigation
is
our
infrastructure
or
our
way
to
move
around
the
city,
and
it's
not
a
fireworks
that
we
see
on
the
christmas
eve.
C
So
what
we
have
here
is
the
grafana
navigation
bar,
as
we
know
it
right
now,
but
limited
to
to
core
applications,
search,
explore
and
dashboards
and
other
applications
being
put
here
as
something
that
is
pre-installed
or
chosen
by
people
just
as
your
doc
or
your
windows.
C
Money
is,
and
the
rest
of
the
screen
is
actually
an
application
with
its
specific
up
navigation
on
the
top,
the
first
level
of
the
navigation
and
the
breadcrumbs
and
maybe
on
the
upper
right
part,
also
as
part
of
navigation,
some
action
buttons,
or
maybe
some
specific
elements
like
settings
and
and
profiles
that
are
usually
distance
from
distance
from
the
rest
of
the
of
the
elements
and
the
the
good
thing
about
that
navigation
is
that
it
works
on
the
narrower
screens,
because
if
we
are
having
less
and
less
horizontal
space,
then
we
can
just
put
those
elements
under
more
or
under
expandable
money,
and
that
concept
works
even
on
mobile,
and
here
you
can
see
the
screens
that
are
320
to
480.
C
So
that's
a
mobile
phones
that
doesn't
exist
even
more.
I
I
believe,
and
the
grafana
navigation
that
resembles
like
mobile
navigation
as
well,
so
other
things
that
go
with
that
concept
and
the
potential
flexibility
for
the
future.
The
second
level
of
navigation
so
possibility
to
not
only
see
the
first
level,
but
also
the
second
level.
C
So
if
we
are
on
the
e-commerce,
that
element
here
would
be
shoes
and
that
second
level
of
navigation
would
be
shoes
for
kids,
shoots
for
sports
and
shoes
for
hiking,
maybe,
and
what
we
can
also
put
on
on
that
structure
is,
for
example,
wizards.
So
then
we
have
a
page,
a
breadcrumb,
so
how
to
reach
that
page
and
then
additional
information
about
the
stepped
process
that
someone
is
following
on
that
page
and
I
haven't
figured
out
all
the
details
yet
because
this
is
first
about
the
structure.
C
But
there
are
a
lot
of
things
that
we
might
consider
like
different
styling
of
the
of
the
navigation
elements,
placing
the
action
buttons
as
well
on
that
nav
bar.
So
it
is
surfaced
more
and
including
a
more
playful
breadcrumbs
that
can
also
unfold
or
show
its
content
when,
when
we
hover
over
those
elements-
and
it
works
as
well
for
colored
versions
of
apps
or
the
whole
whole
navs-
and
the
nice
thing
about
this
about
that-
is
that
with
that
structure.
C
So,
with
that
metaphor
of
grafana
navigation,
understood
as
a
open
operating
system
navigation,
we
have
a
possibility
to
like
imagine
that
yeah
it
can
be.
It
can
be
actually
like
a
dock,
so
I
just
launched
an
application,
and
what
I
have
is
a
dock-like
navigation
and
we
can
even
think
about
it
more
like
a
myro,
maybe
a
style
nav
that
can
expand
and
do
various
things
and
yeah.
C
C
So,
but
let's
dig
deeper,
because
what
this
this
gives
us
is
also
a
possibility
to
have
a
switcher
between
the
stocks.
So
here
we
can
switch
stacks
or
go
to
to
cloud
portal.
We
can
consider
an
expanded
version
of
navigation.
C
So
how
it
would
look
like
on
an
example
of
navigating
grafana
with
that
new
structure
compared
to
the
old
structure
based
on
the
dashboard
it
would
on
home
page
to
dashboards.
It
would
look
like
this
right
now.
We
have
a
homepage
like
that.
I
already
mentioned
that
we
probably
need
to
change
a
home
page,
so
it
doesn't
look
like
a
dashboard.
It
looks
more
like
a
introduction
to
grafana
and
portal
to
start
interacting
with
grafana,
so
it
means
like
always,
expanded
and
always
visible
structure
of
grafana.
C
So
down
to
the
first
level
per
application.
We
might
have
just
big
search
input
here,
so
so
people
don't
have
to
click
if
they
know
what
they're
looking
for
when
entering
grafana
or
even
like
a
possibility
to
show
what's
new,
as
as
that
is
something
that
is
very
often
happening
with
today's
apps
and
then
what
happens
if
we
are
going
to
dashboards?
C
This
is
how
it
looks
right
now
this
how
it
can
look
with
that
concept.
First
of
all,
we
should
have
browse
here,
and
so
the
manage
is
like
a
second
element
here,
but
if
we
click
dashboards,
we
are
actually
landing
on
the
browse
browse
page
that
just
lists
the
dashboards
so
from
here
not
like
from
search,
but
from
here
we
can
actually
enter
the
the
dashboard
and
currently
dashboard
looks
like
this.
With
this
new
concept,
it
can
basically
look
like
that.
C
But
of
course
we
can
play
a
bit
with
that
concept
of
navigating
inside
an
object,
so
we
might
have
just
a
back
button,
but
we
might
also
have
more
like
a
breadcrumb
navigation
that
allows
you
to
jump
back
to
folder
or
jump
back
to
to
the
to
the
dashboards
or
something
more
playful
like
like
this
one
is
is
also
possible,
but
this
I
haven't
explored
much
much
yet,
but
with
that
idea,
if
you
jump
to
settings
for
the
specific
dashboard,
you
will
land
that
on
land.
C
On
the
page
like
that,
and
of
course
this
is
like
the
old
top
navigation
and
we
we
can
redesign
it
a
bit
to
be
more
like
a
many
than
than
tops
in
that
form.
But
here
you
just
you-
can
quickly
go
quickly,
go
back
to
to
the
dashboard,
and
you
know
where
you
are,
and
we
have
that
save
button
not
here
but
about
there,
because
it
is
about
the
whole.
C
The
whole
page.
Other
examples
explore.
I
really
like
that
example,
because
here
nothing
changes
basically,
because
the
explore
app
is
just
name
of
the
app
and
the
select,
and
that
is
great
because,
like
this
is
really
important
screen,
so
we
are
not
changing
anything
here
and
still
it's
a
redesign,
so
double
win
on
the
example
of
configuration.
The
it
looks
right
like
this
right
now
with
the
new
concept
it
it
can.
C
Look
like
that
and
yeah
just
breadcrumbs
can
show
you
or
where
you
are,
and
we
can
explore
like
more
visual
possibilities
with
displaying
that
that
navigation
and
play
a
bit
with
action,
buttons
and
searches
being
also
on
the
level
of
naf
or
the
breadcrumb
breadcrumbs
bar
here,
and
see
how
many
vertical
space
we
save
for
our
lists
of
of
data
sources.
One
last
example
do
I
do
I
have
it
somewhere?
C
C
It
previously
looked
like
it
would
take
like
almost
all
the
screen
and
right
now
it
takes
like
a
fraction
a
fraction
of
that,
and
if
you
go
from
from
reports
again
as
simple,
a
simple
idea
is
possible
so
like
being
inside
an
object,
means
that
when
you're
inside
you
can
just
go
back
or
if
you're
inside
an
object
so
you're,
for
example,
editing
it
you,
you
get
a
breadcrumb
like
navigation
that
allows
you
to
to
go
back,
but
again,
this
is
not
something
that
I
explored.
C
This
is
something
that
oracle
mentioned
when
we
discussed
earlier
in
the
morning,
so
yeah,
that's
it
and,
of
course,
like
don't
put
too
much
attention
into
specific
colors
or
icons
or
fonts
and
all
that
stuff,
because
that
was
just
playing
playing
around
what
I
would
really
like
to
get
from.
You
is:
what
are
the
loopholes,
what
I
haven't
considered
and
all
the
questions
that
can
get
like
that
comes
to
your
head
and
thank
you
very
much.
B
D
You
blew
my
mind
with
your
observability
operating
system
metaphor
early
on
and
I'm
gonna
have
to
mull
that
over,
as
we
think
about
the
the
documentation
and
stuff,
but
the
so
yeah
a
lot
to
unpack
here.
I
really
love
the
that
there
is
a
logical
metaphor
and
the
and
how
predictable
the
navigation
become
one
little
knit
that
is
not
covered
right
now,
but
if
you're
messing
around
with
menus,
that
would
be
a
great
time
the
configuration
menu
is
actually
or
for
organization
admins,
it's
organization
settings.
D
Could
we
please
rename
it
to
something
that
is
not
configuration?
I've
already
noted
this
in
the
note
somewhere,
because
little
little
known
fun
fact
about
this.
The
server
admin
menu
is
for
grafana
server
admins.
You
only
see
it
if
you
are
a
grafana
server
admin,
the
configuration
menu.
You
only
see
if
you
are
an
organization
admin
or
a
team
admin
and
not-
and
not
otherwise,
but
we
call
it
configuration
so.
C
Yeah,
so
I
think,
like
this
odds
to
the
point
that
when
we
initially
thought
or
spoke
about
navigation,
we
had
all
those
problems
in
mind
and
simply
changing.
The
navigation
will
not
solve
those
problems.
So
those
problems
need
to
be
solved
by
restructuring
some
of
the
pages.
C
So
as
the
concept
of
how
to
navigate
the
list
of
dashboards
to
what
you've
mentioned
as
well
right
now
and
to
the
fact
that
sometimes
the
top
navigation
becomes
a
navigation
for
an
object
and
sometimes
an
object
appears
inside
a
top
navigation
for
its
parent
and
so
yeah.
It's
like
pretty
complicated
and
I
think
like.
C
We
need
to
look
like
by
case
by
case
into
how
we
might
improve
that
and
my
goal
at
some
point
just
became
become
the
thing
like
not
to
break
that
those
structures,
because
if
we
do,
then
it
means
that
for
the
8.0
we
need
to
redo
everything
and
that's
like
a
too
big
of
a
of
a
task.
But
but
yeah.
C
Definitely
maybe
that's
that's
an
opportunity
or
a
opening
for
discussion
to
go
like
section
by
section
and
revisit
revisit
that
and
align
it
with
with
the
rest
of
the
structures
that
we
that
we
have
so
I'll.
Definitely
making
note
of
that.
E
It
will
still
work.
I
mean
at
some
point,
like
with
information
architecture.
Like
you
said
you
always
have
to
rethink
how
you
structure
things
at
some
point
and
not
to
try
fit
everything
into
the
navigation,
but
it
seems
very
future
proof
and
what's
important,
is
that
on
this
very
granular
level,
where
people
spend
a
lot
of
time
which
is
like
explore
view
or
dashboards
things,
don't
really
change
with
this
concept
and
it's
still
the
parts
of
grafana
that
are
crucial
for
people.
E
C
Okay
yeah,
thank
you.
That
was
basically
basically
my
goal
because
yeah
we
cannot
do
everything
at
once.
Definitely.
G
A
A
C
Yeah,
I
I
don't
know
to
be
honest.
So
for
me
that
was
like
a
a
level
of
details
that
is
below
that
general
structure,
but
it
all
it
also
like
it
really
depends
on
whether
we
are
showing
that
that
whole
navigation
with
elements
that
are
expanded
already
or
not,
and
if
it's,
if
that
is
in
the
context
of,
for
example,
the
the
home
page
or
if
that
is
in
the
context
of
just
like
you
unfold
that
navigation
to
see
actually
the
whole
site
map.
That
might
be
the
concept
as
well.
C
Maybe
we
can
have
that.
You
just
see
a
a
a
small
drawer
first
and
then
you
can
expand
it
a
full
screen.
I
haven't
played
around
with
that
that
much,
but
I
think,
like
we
can
have
many
of
those
iterations
and
test
what
works
and
what
doesn't
so
yeah.
G
I'm
super
excited
also
because
doing
like
these
branding
exercises
with
like
some
of
the
stakeholders.
This
was
definitely
one
of
the
in
conclusions
as
well.
That
graffana
is
like
an
operating
system
for
observability
and
it
fits
within
this
umbrella
term
that
we
are
the
platform
that
can
support.
G
Different
data
sources
and
applications
and
stuff
so
on
that
front,
like
super
excited,
I'm
actually
curious
with
these
tabs
thing
is
the
idea
that,
like
I
could
open
multiple
like
dashboards
at
the
same
time
and
just
kind
of
like
flip
them
back
and
forth
with
them
like
an
excel
spreadsheet,.
C
Yeah,
so
I
think
like
would
be
hard
because
you
actually
yeah
it's.
I
think
it's
like
a
like
too
much,
because
you
can
basically
like
switch
you
can.
You
can
have
like
explore
to
see
data
in
parallel.
I
I
haven't
heard
a
use
case
before
that
people
want
to
see
or
switch
between
two
dashboards,
because
usually,
if
you
just
want
to
monitor
information
in
parallel,
you
just
put
it
on
the
dashboard
so
or
within
the
sections
of
the
of
the
dashboard.
C
So
I
never
heard
anything
about
having
like
a
two
dashboards
to
see
it
and
to
compare
it
and
to
switch
between
them,
but
maybe
that
that
is
a
case.
I
just
haven't
considered
that
use
case.
G
And
the
other
one,
it's
just
more.
I
left
in
the
comment
as
well.
Maybe
look
at
if
this
is
an
opportunity
to
embrace
like
a
right
mouse
click
in
the
how
you
use
grafana,
because
a
lot
of
other
sas
software,
which
is
like
browser-based
applications.
They
have
started
to
make
their
own
right
click.
So
you
can
click
right,
click
on
the
graph
and
then
say
edit
rather
than
having
to
look
for
this
more
button.
C
C
I
Navigation
at
the
top,
the
only
one
that
we
are
still
considering
or
do
we
still
want
to
try
a
version
in
which
tabs
are
smaller
than
their
to
the
articular
space,
but
there
are
are
under
the
title
and
the
reason
I'm
asking
is
why
you
showed
how
these
tabs
can
take
can
become
responsive.
If
you
with
the
the
window,
there
are
places
where
it's
still
going
to
be
quite
hard
to
do
so.
I
I
C
C
Definitely
that
is
important,
but
I
think,
like
it's,
it's
a
problem
us
with
many
elements
of
the
navigation.
The
question
is:
should
we
maybe
just
have
a
shorter
name
of
for
that,
so
us
with
what
happens.
If
we
have
12
elements
in
the
navigation,
maybe
we
can
have
like
less
than
12
elements
in
navigation
or
introduce
second
level
of
of
navigation.
So
yeah
I
hear
you.
I
will
definitely
like
put
some
mock-ups
on
that
and
check
when
it
starts
to
break
compared
to
what
we
have.
F
Yes,
so
for
me
it's
more
sort
of
like
a
very
high
level
comment,
which
is
I
I
also
really
like
the
os.
For
observability
metaphor,
the
main
question
for
me
is
like,
in
your
opinion,
are
we
sort
of
still
reinventing
the
wheel
here
somehow
in
sort
of
like
I'm
compared
to
other
vendors
right?
F
So
if
someone
already
comes
a
bit
from
the
observability
space,
will
they
be
confused
by
this
sort
of
new
really
neat
way
that
we
do
things
now
or
or
do
we
have
a
chance
of
just
still
feeling
a
bit
intuitive,
because
it's
somehow
still
a
bit
related
to
how
other
people
are
doing
it.
C
So
yeah
they're
confused
right
now.
That's
my
like.
C
Answer
number
one,
especially
the
people
who
are
not
super
familiar
with
grafana,
definitely
and
yeah.
We
we
could
say
that
maybe
we
can
just
take
a
navigation
that
is
already
done
by
someone
else,
but
then,
first
of
all,
we
never
know
whether
it
works.
Actually.
The
second
thing
is
that
there
always
will
be
differences
in
how
each
of
the
products
work
and,
as
I
mentioned
before,
I
really
wanted
that
concept
to
play
nice
with
what
we
have
right
now.
C
So
I
strongly
believe
that
it
does
so
it
is
not
revolutionary
on
a
way
that
we
need
to
redesign
and
restructure
everything
for
that
to
to
work,
so
we
can
have
be
like
incremental
incremental
in
in
the
changes
so
and,
of
course
like.
If
we
have
a
time-
and
I
believe
we
have-
we
can
test
that
that
approach
with
people
run
a
usability
study
and
see
whether
people
understand
it
or.
F
C
C
Here,
yeah
yeah
but
yeah
to
totally
get
it.
But
this
is
why,
maybe,
on
the
surface,
it
doesn't
look
like
a
huge
of
a
change,
maybe
for
or
for
for
many
of
you,
because
it
is
basically
not
that
much
of
a
that
much
of
a
change.
So
this
is
why,
at
some
point
I
restricted
like
myself
from
coming
up
with
a
super
flashy
new
ways
of
navigating
navigating
things.
J
J
I
super
passionate
about
kind
of
what
we
do
here,
because
this
is
so
impactful
and
I'm
I'm
really
loving,
as
well
as
the
high
level
kind
of
looking
at
grafana
as
an
operating
system,
and
I
think,
there's
a
lot
of
sort
of
great
things
in.
In
that
metaphor,
and
and
oh
and
the
home
home
thing
and
kind
of
refining
the
thing
how
you
create
dashboards
yeah,
the
create
menu
on
the
site
is
super
confusing
to
have
that
as
a
top
level
thing.
J
So
I
think
that's
the
only
thing
that
my
own
main
concern
is
like
yeah,
the
using
horizontal
tabs
as
main
navigation
yeah
feels
like
it
breaks
down
into
space
requirements
really
easily,
and
also
it's
much
harder
to
scan
many
horizontal,
read
many
horizontal
things
and
find
what
you're
looking
for
compared
to
sort
of
many
pages
that
are
so
stacked
vertically.
C
I'm
looking
to
explore
that
I
already
did
like
specially
toggle
for
you
this
this
mock-up
here
which,
like
moves
forward
with
our
morning,
discussion
of
how
the
dashboard
settings
might
looked
like
and
how
to
also
incorporate
that
breadcrumbs
part
in
that.
So
so
sorry,
but,
as
I
mentioned
in
the
beginning,
I
haven't
went
into
navigating
the
object.
The
specific
object.
C
Okay,
so
thank
you
very
much
if
you
have
any
additional
comments
like
please
reach
out
to
me,
and
I
will
be
even
super
happy
to
talk
to
you
individually.
If
you
have
any
comments-
and
I
will
read
the
doc
afterwards-
definitely
and
and
yeah
we'll
be
working
on
that.
Probably
seeing
a
lot
of
you
on
next
occasions,
awesome.
A
All
right
here
we
go,
so
I
am
addressing
the
logs
navigation
and
some
of
you
might
already
know
the
problem
because
it's
been
there
in
grafana
for
a
while,
but
just
to
give
you
a
quick
recap,
so
let's
say
I'm
in
next
door
and
I
just
opened
it
like.
This
is
an
mtx
door,
and
now
I
am
picking
some
labels
to
run
a
query
and
I'm
picking
like
purposely
a
big
one.
So
it's
running
now
and
as
you
can
see,
my
time
range
here
is
an
hour
and
like
this
here.
A
What
I'm
seeing
in
the
graph
is
obviously
not
an
hour,
so
the
more
advanced
users
are
probably
familiar
with
this.
But
what
exactly
is
happening
here?
Why
do
I
only
see,
like
I
don't
know,
a
second
or
two
instead
of
my
hour,
that
happens
because
down
here
the
log
lines
are
only
returned
up
to
a
certain
limit,
which
is
currently
one
thousand
all
right.
A
A
A
Do
this
or
something
not
so
convenient,
maybe
maybe
do
three,
but
even
if
I
do
three
seconds
or
five
to
see
more,
I
don't
know,
then
I
would
still
hit
that
limit.
So
how
can
I
change
the
limit?
It's
actually
up
here,
but
here
it
just
says
auto.
So
it's
really
hard
to
understand
that
this,
and
this
are
even
the
same
control
and
change
the
same
thing.
A
Okay,
like
I'm
two
seconds
in
I
want
more,
can
I
just
get
a
button
or
I
have
some
pagination
or
some
controls
to
update
this?
Yes,
so
that's
why
I
jumped
into
ux
solution
mode.
I
did
run
research
last
year
with
explore
users
about
how
this
should
behave
and
people
were
a
bit
on
the
fence.
Like
some
said,
pagination
is
awesome.
Some
said
pagination
is
a
really
bad
idea
and
in
the
end
I
decided
not
to
explore
pagination
because
most
of
the
time
people
use
a
relative
time
range.
A
So
if
you
page
back
in
time
and
then
you
have
a
relative
time
range
here,
what
about
the
newer
log
lines
like
the
the
relative
point,
the
time
where
your
page
one
is,
could
change,
and
then
it
could
just
get
really
confusing
right.
So
that's
why
I
didn't
want
to
do
that
so
instead
I
started
exploring
sigma
here
and
decided
to
just
do
a
load
more
button.
A
So
one
thing
that
I
generally
introduce
that
is
present
in
all
my
solution.
Options
is
this
new
button
here
which
just
loads
1000
more
lines
and
a
clever
little
thing
that
nico
came
up
with
is
also
to
give
not
just
the
load
1000
more
button
and
also
the
1000,
of
course,
should
change
depending
on
what
your
line
limit
is.
A
If
you
have
a
2
000
line
limit,
you
should
be
able
to
just
load
2
000
more
so
basically
just
double
your
limit,
but
this
little
arrow
is
supposed
to
open
a
drop
down
where
you
can
not
just
load
those
2
000
or
I
don't
know
whatever
your
limit
is,
but
have
the
option
to
load
even
more
at
once
up
to
a
certain
point
where
it
makes
sense
and
the
calculation
of
like
what
we
can
offer
the
user,
how
many
more
they
could
load
we
could
base
on
the
relation
between
what
their
current
line
limit
is
and
the
entire
time
range.
A
So,
for
example,
if
I
have
a
five
minute
time
range
here,
then
I
would
like
to
give
some
visual
feedback
of
how
many
percent
of
their
time
range
they
are
currently
seeing
as
a
user,
and
then
we
could
say:
oh
it's
only
16
and
it's
the
line
limit.
So
if
we
have
like
84
more
percent
of
long
lines
too
low,
that
could
be
a
lot
of
log
lines.
A
So
that's
the
first
approach,
just
like
add
this
little
highlight
here
where
they
can
see.
How
much
am
I
currently
seeing
and
then
also
this
little
line
limit
indicator
here
should
have
a
link
where,
if
you
click
there,
you
would
jump
directly
in
the
top
input
here
and
could
edit
it
so
that,
even
if
you
don't
notice
this
at
first,
you
could
click
here
and
then
see.
I
can
edit
that
in
the
top
here
I
understand
and
have
a
little
learning
experience.
A
So
another
thing
that
I
wanted
to
play
with
was
to
somehow
indicate
to
the
user,
like
with
the
scroll
bar,
where
they're
at
in
the
log
logline
timeline,
but
this
is
probably
really
hard
to
understand
so,
like
I
tried
to
play
around
with
that,
but
I
don't
really
like
the
idea
that
much
if
you
have
any
good
ideas
how
to
pursue
that
further,
please
suggest
that,
but
otherwise
I
would
just
drop
it.
A
Then.
A
third
thing
that
I
wanted
to
explore
is
giving
a
more
obvious
feedback
that
people
are
not
seeing
their
full
time
range
because,
at
least
for
me,
if
I
don't
look
at
my
timestamps
here
and
compare
them
to
the
global
time
range
button,
I
wouldn't
maybe
even
notice.
Oh,
this
is
kind
of
different
like
this
is
much
less
so
this
indicator
in
the
bottom.
A
Here,
that's,
maybe
not
prominent
enough,
so
we
could
make
it
a
little
more
prominent
by
giving
some
sort
of
info
box
further
in
the
top
and
then
another
thing
that
I
explored
was
like
this
cut
off.
Histogram
here
is
something
we
only
introduced
a
few
months
ago
before
you
would
always
see
kind
of
something
like
this,
where
you
would
only
see
the
percentage
of
your
full
histogram.
That
was
actually
loaded,
but
this
was
not
here.
So
originally
it
looked
kind
of
like
I
don't
know,
can
I
remove
this
fast
yeah?
A
A
So
we
could
bring
this
back,
but
then
we
would
have
to
add
some
sort
of
feedback
like
this
is
not
empty,
but
you're
currently
only
seeing
five
percent
of
your
time
range
and
there
could
be
more
so
another
option
of
that
would
be
to
add,
also
a
presence
indicator
of
where
you
were
at
within
your
log
lines,
but
that
probably
doesn't
make
as
much
sense
if
you're
just
scrolling
and
the
histogram
goes
away.
So
maybe
we
want
to
play
around
with
a
sticky
histogram.
A
I
also
have
a
vertical
version,
because
elastic
does
that
in
the
fifth
solution,
and
here
is
also
a
version
where
only
part
of
your
histogram
would
be
cut
off,
like
maybe
enough
to
show
a
notification
that,
like
your
histogram,
would
be
bigger,
but
you're
not
seeing
all
of
your
time
range
so
that
we
would
still
have
more
space
to
actually
show
graph
stuff,
but
still
have
space.
For
that.
So
that's
one
idea,
and
then
I
was
looking
at
how
our
competition
does
this
and
for
elastic
locks.
A
A
So
I
was
wondering
whether
we
could
steal
the
vertical
idea
and
experiment
with
that.
So
I
try
to
sort
of
build
that
and
use
the
the
bars
the
problematic
bit
here.
Is
that
the
added
level
of
information
with
maybe
having
I
don't
know
six
or
eight
or
even
more
different
categories
of
log
lines?
That
could
be
tricky
to
do
in
this
vertical
version,
but
I
also
felt
like
the
the
presence
indicator
of
where
I
am
in.
A
The
lines
could
be
nice
and
also
like
this
kind
of
seems
unnecessary
to
have
this
duplication,
so
we
could
even
experiment
with
having
this
one
and
then
saving
on
the
vertical
space
here
and
giving
the
user
more
log
lines
at
once
yeah.
So
these
are
all
my
ideas,
feedback,
please.
Oh
sorry,
I
talked
for
too
long,
but
maybe
we
can
do
five
more
minutes
of
discussion.
D
I've
got
a
start.
I
think
I
really
like
the
info
boxes
and
the
load
1000
more.
I'm
not
sure
that
the
first
couple
of
info
boxes
necessarily
draw
a
connection
between
the
empty
space
in
the
graph
and
the
line
limit,
though
you
kind
of
address
that
in
the
fourth
one
a
bit
where
I.
E
What
it's
called
instagram
instagram
thank
you
felt
a
bit
odd
at
the
beginning,
but
now,
when
I
think
about
it,
you're,
actually
you
can
move
presence
indicator
and
you
just
scroll
through
logs.
So
it's
like
you
go
in
the
same
direction,
both
with
this
histogram
and
log,
so
you
can
see
exactly
where
you're
at.
G
So
I'm
not
too
big
a
fan
of
the
tooltip
and
the
reason
is,
I
think,
in
most
cases,
people
would
not
have
have
the
full
range
of
data
and
therefore
I
think
it
makes
sense
as
a
visual
visual
feedback.
That's
on
the
page,
rather
than
a
notification
that
pops
up.
G
And
that's
kind
of
the
next
thing
like
I
don't.
I
think
you
should
be
very
careful
with
laying
stuck
stuff
on
top
of
the
graphs.
On
the
whole
metaphor,
not
don't
get
in
wave
the
data,
but
it's
the
reason
why
it
would
not
just
be
like
a
snack
bar
pop-up
that
pops
up
for
like
five
seconds
in
one
of
the
corners
and
say
like
we
loaded
five
percent,
just
to
be
aware,
like
when
it's
a
very
low
percentage.
A
C
G
C
So
I
specifically
super
liked
the
tiny
progress
bar
the
tiny
progress
bar
that
appeared
somewhere
on
the
screens.
It
is
really
nice
at
some
point.
I
was
even
thinking
that
maybe
it
could
go
like
next
to
the
logs
title
on
the
panel.
C
The
only
comment
about
thinking
about
something
is
that
if
we
have
this
like
edit
lock
limits-
and
you
can
actually
do
it
in
two
places,
if
I
click
log
limits
where
it
is
like
a
link,
so
just
above
the
logs-
and
I
am
trans
like
focused
on
the
input
above,
I
think,
like
peripheral
vision
of
people
will
not
catch.
C
That
and
people
will
not
understand
what
is
happening
and
I
think,
like
the
further
explorations
of
like
loading
more
things
is
just
maybe
a
a
better
thing
so
to
show
on
those
logs
or
whenever
we
say
like
hey,
we
didn't
loaded
all
the
logs
load
more
and
load
more
and
load
more
to
to
be
like
more
obvious
and
just
leave
away
the
the
default.
The
default
input
feature
where
it
is
and
not
duplicate
that.
H
Yeah,
I
feel
like
I,
my
opinion,
is
apparently
the
opposite
of
what
some
of
the
previous
commenters
have
said,
but
I
really
like
the
idea
of
centralizing
as
much
as
you
can
within
one
widget,
so
the
histogram
that
also
shows
the
range
that
you
cannot
see
on
the
same
chart
as
the
actual
data.
I
personally
really
love
that.
H
I
also
like
having
the
presence
there
and
to
your
point
about
the
presence
not
being
visible,
there's
some
solutions
to
that
like
turning
it
into
a
vertical
one,
as
you
did,
or
I
was
also
thinking-
maybe
once
you
start
scrolling
down
to
to
actually
reduce
the
size
of
the
main
histogram
a
little
bit
to
kind
of
have
the
best
of
both
worlds.
I
have
some
more
notes,
but
I'll
share
them
in
the
dark
later,
so
that
someone
else
can
comment
something
if
they
want.
H
J
No
I
to
me,
I
I
really
like
the
the
horse
or
the
the
vertical
histogram
in
terms
of
just
being
so
connected
with
the
log
lines.
As
you
scroll,
you
see
that
and
it's
very
intuitive,
to
sort
of
place,
your
cursor
on
the
timeline
and
then
jump
to
a
spot
where
there
might
not
be
any
logs
because
they
haven't
loaded
it
and
then
graphone
can
request
data
for
that
time
range
with
some
kind
of
be
smart
around
which
about
the
range
there.
J
So
it
feels
very,
I
don't
know
it
feels
very
connected
to
the
scrolling
and
looking
at
the
histogram,
it's
maybe
sort
of
a
bit
untraditional
or
unconventional
to
have
only
this
view.
But
it's
a
it's
and
it's
technically
a
bit
harder,
I
think
for
our
graph
component,
but
I
think
it's
an
interesting
option.
A
All
right,
yeah,
I
will
follow
up
with
her,
then
so.
Thank
you
so
much
for
all
of
your
feedback.
This
was
super
helpful
as
always.
Thank
you
also
luke
for
your
amazing
and
thorough
presentation.
A
So,
as
we
are
about
to
finish
this
conversation,
thank
you
youtubers
for
checking
in
with
us.
If
you
have
feedback
and
comments
drop
them
under
this
video
and
for
the
graphenes,
that's
here
see
you
soon
and
if
you
have
any
feedback,
how
we
can
make
these
calls
any
better,
just
drop
them.