►
From YouTube: Grafana Community Call 2022-03-17
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
I'm
obviously
not
marcus,
but
anyway,
let's
see
bear
with
me.
This
is
the
first
of
mine
doing
this.
So
if
I
miss
anything,
probably
michael,
you
know
better
than
me
how
to
introduce
this.
This
calls
I
feel
pretty
chipping.
A
Sorry,
okay,
but
anyway,
so
another
grafana
community
called
this
time
user
essentials.
I
think
a
lot
of
times.
We
talk
a
lot
of
plugins,
so
today's
gonna
be
a
bit
different
because
we
work
actually
in
the
core
part
of
grafana.
But
let's
see
so
yeah,
this
chord
is
being
recorded.
If
you
don't
want
to
be
on
camera
turn
it
off.
You
don't
want
to
ask
questions
out
loud,
write
it
on
the
channel
will
be
here
and
the
recording
will
be
available.
A
D
A
Yeah,
oh
well,
we
have
animations,
oh
okay,
that
was
unexpected,
so
yeah
we
meet
the
first
thursday
of
every
month
like
today.
The
next
one
is
the
21st
of
april
and
if
nothing
changes.
Otherwise,
I
hope
marcus
will
update
everyone
and
during
each
meeting
we
have
different
squads
talking
about
different
things
about
what
we
do
and
hopefully
get
some
questions
or
not.
A
So
we
are
user
essentials
and
we're
going
to
talk
about
yes,
so
we're
going
to
talk
about
who
we
are,
what
we
do
a
bit
of
a
principles
behind
what
we
do
and
which
areas
we're
responsible
for,
because
I
think
by
the
by
our
name.
You
can't
really
tell
but
trust
me.
We
couldn't
come
up
with
anything
better
and
I
think
that.
A
Well,
I
think
once
you
explain
what
we
do,
it
all
makes
sense
because
we're
responsible
for
a
lot
of
things.
So
it's
hard
to
pick
one
name
that
covers
them
all
and
we
also
walk
a
little
bit
through
the
different
projects
that
we've
been
working
on,
that
we're
currently
working
on.
There
are
pretty
big
initiatives
and
then,
if
someone
has
questions,
we
can
try
to
answer
them
pretending.
B
C
Me
I'm
ash,
I'm
a
front-end
developer
here
at
grafana,
also
working
in
the
user
essentials
team
based
in
the
uk.
I've
been
here
now
for
about
nine
months,
so
I
kind
of
joined
just
after
alexa.
E
I
am
josh
dev
on
the
year's
essentials
team,
originally
from
australia,
but
now
I'm
based
in
london
living
here
for
a
few
years
and
I
joined
grafana
about
a
year
ago.
E
I
was
originally
working
in
cloud
data
sources,
so
working
making
data
sources
for
like
the
aws
and
google
cloud
and
things
like
that,
but
then
move
to
user
essentials
to
work
on
this
sort
of
stuff,
ciao.
F
Yep,
so
I
guess
that's
me,
sorry,
I'm
well,
I'm
also
based
in
the
uk,
but
I'm
originally
from
portugal
and
I'm
currently
in
portugal.
Yeah,
I'm
also
a
news,
essential
team.
I've
started
two
weeks
ago,
so
this
might
also
be
very
new
for
me.
This
presentation,
but
yeah,
see.
A
It's
new
for
everyone
and
so
yeah.
When
we
talk
about
what
we
do
and
we
talk
about
mission,
it
doesn't
get
clear,
but
we
do
try
to
provide
the
best
journey
for
our
users
and
the
data,
because
our
main
focus
it
is
the
user
experience
we're
engineering
team,
but
we
do
focus
in
trying
to
improve
that
experience
from
the
core
application.
A
Those
are
our
principles.
We
we
try
to
do
a
good
job
and
those
are
the
things
that
we
try
to
keep
in
mind
and
while
we
do
it
we're
probably
collaborative
we
try
to
provide
a
platform
also
for
others.
That's
easy
to
use
and
graffana
is
a
pretty
complex
product.
We
try
to
make
it
easy
and
write
nice
code.
We
actually
have
quite
a
few
initiatives
around
improving
the
code
quality
of
our
application,
so.
A
A
So
if
you
think
about
graffana
use
that
if
you
ever
use
grafana
you're,
probably
gonna
touch
something
that
we
build
we're
maintaining
and
we
also
respond
for
some
of
our
car
visualizations
that
are
not
super
use
case
specific,
like
yeah,
the
bag,
gage
and
all
those
and
also
data
pipeline,
really
things
like
transformations
and
overrides
and
there's
an
etc
here.
But
I'm
gonna
stop
because
it's
a
really
long
list,
but
overall
user
experience.
How
can
we
make
a
users
know
how
to
use
grafana
and
understand
the
data
and
find
a
way
around?
A
Am
I
am
I
correct?
Okay,
I
see
people
nodding
good
and
now
I'm
gonna
start
login
and
I'm
gonna
leave
who's.
Gonna,
start
navigation
ash.
Take
it
on
also
mike.
If
you
have
any
questions
on
the
way
or
you
just
want
to
root
for
us
and
be
like-
oh
my
god,
guys
you're,
the
most
amazing
people,
I've
ever
met
feel
free
to.
C
So
yeah
navigation
has
been
one
of
the.
I
guess
main
focuses
for
our
team
relatively
recently,
and
part
of
that
stems
from
the
fact
that
we
we
get
a
lot
of
feedback
that
users
of
grafana
sometimes
get
lost
in
the
product.
Almost
you
know,
you'll
click
through
to
a
dashboard.
You
won't
know
how
to
get
back
to
where
you
were
and
various
things
of
that
ilk
where
we
can
improve
on
certain
aspects
of
the
navigation.
C
So
I
thought
we'd,
I
thought.
Maybe
one
thing
to
do
would
be
to
touch
on
some
of
the
things
we've
done,
that
maybe
people
haven't
noticed
so
much
because
they're
kind
of
I
like
to
think
of
them,
as,
like
paper,
cut
fixes
you
don't
really
notice
as
they're
happening,
but
over
time
they
really
build
up.
So
and
some
of
those
are
kind
of
listed
here.
We've
got
some
before
and
after
screenshots
from
the
top
and
bottom,
and
this
is
what
I
mean
about.
C
Some
of
them
are
quite
subtle,
because
I
guess
the
the
top
screen
shot
on
the
right
here.
Top
right
and
bottom
right
look
quite
similar,
but
there
is
actually
a
lot
of
improvements
we've
put
in
to
the
code,
so
yeah,
we've
added
support
for
the
light
theme
in
the
navbar
we've
added
full
keyboard,
accessibility
to
the
nav
bar
as
well.
I'm
sure
alexa
will
touch
on
that
when
we
talk
about
accessibility,
which
has
been
another
one
of
our
kind
of
big
initiatives.
C
Recently,
we've
introduced
a
new
mobile
navigation
menu,
some
smaller
things
like
active,
page
state,
hover
and
focus
state.
So
you
can
see
here
on
the
nav
bar
in
the
top
right,
although
we're
on
the
explore
page
you'd
have
no
way
of
knowing
that,
because
we
never
used
to
show
an
active
page
state.
C
Whereas
now
we've
added
this
active
page
state
and
we've
improved
plugin
ordering
before
it
was
kind
of
somewhat
random,
it
was
basically
whichever
plugins
came
back
first,
which
also
didn't
help
with
kind
of
navigation
clarity.
When
you,
you
know
you'll
refresh
the
page
and
suddenly
your
plugins
are
in
a
different
order.
So
we
fixed
that
we've
added
external
link,
icons
and
we've
tried
to
make
some
kind
of
smaller
tweaks
to
improve
the
visual
clarity,
and
what
I
mean
by
that
is
some
of
our
hover
menus
had
a
tendency
to
kind
of
blend.
C
In,
with
the
background,
we've
tried
to
add
better
highlighting
and
shadows
to
those
hover
menus
to
really
emphasize
and
show
that
they're
a
hover
menu
and
it,
and
that
also
comes
in
with
like
hover
and
focus
states.
We've
tried
to
really
improve
those.
So
you
know
when
you're
hovering
and
focusing
on
something.
C
And
then,
in
terms
of
what
we're
currently
working
on
now
and
the
next
big
focus
for
our
navigation,
it's
around
a
more
kind
of
intuitive
and
expandable
navbar
menu.
C
C
C
So
we've
we've
mocked
up
a
prototype
and
we
did
some
user
research
with.
I
think,
basically,
anyone
we
could
get.
We
were
asking
on
slack.
We
were
asking
in
yeah
in
our
community
forums
and
we've
done
some
user
research
there
and
took
that
on
board
and
we're
now
kind
of
comfortable
sharing.
I
guess
and
moving
forward
with
a
design
that
we
think
we're
happy
with.
C
Checkbox
and
they'll
appear
in
this
saved
items
list,
so
that
should
be
really
useful
for
people
that
only
have
three
or
four
things
they
really
need
to
go
to
in
grafana.
They
can
just
stick
them
in
the
saved
items
list
and
they'll
always
be
there.
C
I
think
we've
also
had
some
feedback
as
well
that
this
you
know,
be
really
useful
to
pin
certain
dashboards
there,
maybe
save
certain
dashboards
that
people
go
back
to
again
and
again,
and
I
think
that's
again
something
we're
looking
into
with.
I
don't
think
we're
100
committed
to
implementing
it
yet,
but
it's
something
we're
actively
looking
at
for
future
grafana
releases.
D
G
D
Okay,
because
I
remember
it
was
the
moment
when
it
was
black
and
I
kind
of
never
paid
attention
to
that.
I
might
you
see
it's
kind
of
kind
of
when
you
show
them
the
with
a
lot
of
icons.
I
see
that
it's
easier
right
to
navigate
integration,
which
is
related
to
the
cloud,
mostly
right
in
most
cases
or
reports,
which
is
the
feature
for
enterprise.
So
it's
not
going
to
be
available
for
open
source
right.
C
D
C
Oh
yeah,
I
see,
I
see
yeah,
so
reports
is
an
enterprise
specific
feature.
Yes,
so
it's
all
going
to
be
there.
Okay,.
D
My
question
is
actually
because
my
youtube
is
a
little
bit
different,
my
customers,
some
of
my
customers,.
D
The
one
particular
application
we
developed
for
them
and
they
don't
feel
interested
in
explore,
for
example,
or
alert
some
of
them
don't
use
alerts.
Is
it
somewhere
in
the
road
map
that
you
can
hide
some
of
these
icons,
not
known
or
kind
of
freedom
of
the
main
menu
at
all,
because
we
recently
developed
one
of
the
applications
for
the
customer.
He
has
his
custom
home
screen
where
everybody
logged
in
then
there
is
the
dashboard
on
the
top
panel
right
there
links
from
using
them
and
from
the
main
screen.
D
C
So
I
I
think
we've
talked
a
lot
about
yeah,
either
showing
and
hiding
specific
specific
things
in
the
nav
bar.
We
had
a
prototype
for
that.
At
one
point,
I
think
as
well,
just
like
completely
hiding
the
nav
bar
has
also
been
a
thing
where
we've
thought
about
that,
so
either
hiding
it
or
even
giving
yourself
more
customization
so
that
you
can
hide
it.
But
then,
if
you
move
your
mouse
near
it,
it
will
come
out
things
like
that.
So
it's
they're
all
things
we've
discussed.
C
If
it's,
I
think,
if
it's
like
a
feature
that
basically
when
we've
done
the
user
research,
the
the
users
we've
spoke
to
have
kind
of
said:
that's
not
our
biggest
concern,
but
maybe
we
just
haven't
spoke
to
the
right
users.
Yet
so
if
hiding
things
in
the
navbar
is
a
a
big
feature
that
people
want
that
you
want
in
particular,
I
would
say,
definitely
race
race,
something
on
our
github,
raise
a
discussion
and
upvote
it
and
the
more
upvotes
it
gets.
C
You
know
it's
hard
to
ignore
when
a
lot
of
users
want
a
particular
feature.
D
Right
I
mean
this
is
what
I'll
say
that
my
use
case
is
a
bit
different
and
especially
when
we
started
to
work
a
lot
with
iot
iot
and
devices
like
raspberry,
pi
or
dressers.
They
have
smaller
screens,
but
there's
a
smaller
resolution
right,
which
is
the
side
of
them
so
to
keep
with
space
right
for
your
actual
panel.
It's
actually
spacing
as
well.
A
D
Okay,
but
I
like
the
new
just
like
this
they're
moving
with
the
settings
button
and
the
configuration
to
the
bottom
make
sense.
I
hope
that
as
much
I
can
see
the
new
one.
You
have
a
space
for
the
application
for
this
and
a
good
job
is
the
organism
we
kind
of
I
kind
of
missed
this
feature
for
from
grafana
7
when
we
started
implementing
different
application
plugins
and
when
you
have
three
or
four
of
them,
they
started
shuffling
around
yeah.
So
it
was
my
muscle.
B
My
turn
okay,
so
today
I
just
wanted
to
mention
accessibility,
so
across
graffana,
since
I
think
last
year,
or
maybe
before,
we
have
been
taking
more
putting
more
priority
into
accessibility
and
our
team
is
one
of
the
big
like
promoters
or
yeah,
but
the
one
who
is
kind
of
like
putting
a
lot
of
effort
into
making
accessibility
improvements
and
the
one
that
is
trying
to
pull
other
teams
into
the
same
kind
of
accessibility
mindset.
So
in
general
improvements
in
the
last
couple
of
months,
we
did
the
keyboard
navigation
for
the
main
network.
B
Also,
we
were
using
fastpass,
that
is
from
microsoft,
to
just
fix
some
accessibility
issues
that
are
high
like
detectable
using
this
specific
tool,
and
it
was
a
lot
of
work
from
our
team,
but
also
data
sources
and
other
teams.
There
is
a
lot
of
in
terms
of
accessibility.
There
is
a
lot
of
work
in
grafana
that
we
want
to
make.
But
of
course
it
is
a
culture
that
we
have
to
build
inside
grafana
and
outside
rafana,
one
of
the
things
that
we
introduce
as
well
in
order
to
avoid
regressions.
B
Whenever
we
add
something
new,
is
we
add
it
into
our
pipeline
poly
ci?
So
the
idea
is
like
this
tool
just
scan
specific
pages
or
like
core
pages
in
grafana,
and
then
we
get
some
accessibility
failures
and
if
we
introduce
when
we
open
a
pr
failure,
the
pr
will
not
pass
the
pipeline
so
that
we
avoid
some
regressions
so
far.
I
think
we
are
only
testing
core
pages,
but
we
are
planning
to
add
more
pages
into
this
tool.
B
Unfortunately,
the
tool
is
only
detecting
up
to
30
percent
of
accessibility
issues.
So
it's
not
super
huge,
but
is
a
good
start
in
terms
of
automation
and
something
that
is
ongoing.
Work
that
probably
will
continue,
because
accessibility
is
something
that
you
just
need
to
continue
work
on
it
is
we
created
inside
rafana.
I'm
part
of
that
group.
B
Oh
wait.
My
english
is
broken,
I'm
so
sorry
we
created
that
accessibility
working
group,
one
of
like
or
two
members
of
our
team-
are
there,
and
the
idea
of
this
group
is
to
break
accessibility,
knowledge
gap.
So
what
we
realize
is
accessibility
is
a
whole
new
world,
and
you
cannot
like
get
that
in
an
easy
way.
You
have
to
continuously
keep
accessibility
in
mind
whenever
you
are
building
something
or
whatever
you
are
reviewing
something.
B
So
this
group
is
trying
to
bring
an
initiative
that
tries
to
break
this
gap,
and
last
week
we
had
a
hackathon,
an
internal
hackathon
and
something
what
that
we
did
in
that
hackathon
was
to
run
some
hunting
sessions.
So
we
had
like
a
hunting
session
where
we
were
like
trying
to
use
graffana
only
with
the
keyboard,
and
we
got
quite
a
lot
of
issues
like
39
issues
in
some
across
some
pages
that
we
were
testing
and
we
fixed
like
10
11.
Something
like
that.
B
I
don't
remember
that
they
were
high
priority,
so
we
are
continuously
doing
work
across
the
holographana
to
gather
accessibility
issues,
but
also
to
fix
them.
So
we
want
to
involve
more
teams
here.
Something
that
we
would
like
to
get
from
the
community
as
well
is
to
get
some
accessibility
issues
reported
in
our
github
project.
B
So
would
be
super
great
if,
if
you
find
something
that
like
you,
cannot
use
the
keyboard
in
a
specific
flow
that
you
always
like
follow
would
be
nice
like
you
just
go
and
report
it,
and
our
idea
is
just
to
tackle
them
like
in
delegate
to
the
teams
and
if
we
can
fix
it
sooner,
we'll
be
nice
and
what
else?
What
else
I
wanted
to
mention
yeah
it's
just.
We
are
taking
accessibility
more.
We
are
putting
more
focus
on
accessibility
and
we
definitely
want
to
make
the
final
more
accessible.
B
That's
true
as
well,
so
if
you
want
to,
if
you
want
to
fix
issues,
maybe
also
something
that
we
can
share,
I'm
not
sure
where,
but
is
the
accessibility
board
the
github
board?
And
then
we
can
always
put
some
beginner,
not
beginner
like
what
is
first
issue
good
first
issue,
good
first
issue,
or
they
help
want
it,
because
these
issues
are
not
super
complicated.
It's
just
like
simple,
but
not
always
simple
things,
but
things
that
people
can
collaborate
and
contribute
to
graphite
as
well.
B
C
Yes,
I
think
it's
worth
mentioning
as
well,
but
like
a
lot
of
the
accessibility
work
has
helped
us
to
write
better
code
for
for
everyone,
because
you
know
we're
avoiding
a
lot
of,
I
guess,
anti-patterns
with
our
code
sometimes
and
yeah
I
mean,
even
just
with,
like
contrast,
ratios
and
stuff
that
helps
everyone.
So
I
think
it's
been
like
a
great
piece
of
work
so
far,
and
it's
only
going
to
make
the
product
better.
E
I
guess
this
is
another
spin
on
accessibility.
One
way
you
can
make
a
product
more
accessible
is
making
sure
that
it's
translated
in
the
language
that
your
users
use
grafana
in,
so
globalization
is
an
effort
that
we
are
starting
to
look
into
for
the
essentials
team.
I
was
actually
surprised-
or
I
don't
know
how
surprised,
but
internationalization
is
one
of
the
oldest
issues
in
the
repo.
It's
definitely
like
the
most
active
old
issues.
It's
got
like
you
can
see
there
like
over
600.
E
Sorry
260
comments
on
it
and
it's
still
pretty
active
to
this
day
of
people
chiming
in
offering
to
help
translate
grafana
or
to
say
they
want
to
use
it
in
their
language
or
whatnot.
So
it's
cool
to
be
able
to
say
that
we
are
going
to
be
working
on
this.
E
There
is
yeah,
there's
a
there's,
not
a
super
lot
to
say
about.
I
guess
this
effort.
Apart
from
we
are
doing
it.
We
are
starting
along
with
translating
the
parts
of
grafana
that
people
with
viewer
permissions
would
use.
So
that's
focusing
on
things
like
the
navigation
core
dashboard
things
like
that
in
and
like
user
settings,
and
things
like
that,
translating
that
for
everyone,
the
languages
that
grafana
will
be
investing
in
professional
translations,
for
we
are
thinking
of
french,
german
and
spanish
as
the
first.
E
But
that's
what
we're
looking
at
at
the
moment,
sure
yep
and
also
taking
we're
also
looking
at
the
a
model
for
accepting
community
contributions
to
translations.
E
You
know
the
cool
thing
about
grafana
is
there
is
a
quite
a
large
community
out
there
and
as
we've
seen
in
that
issue,
there's
lots
of
people
at
least
saying
that
they're
really
eager
to
contribute
translations,
so
we're
looking
into
tools
and
and
models
to
make
that
as
easy
as
possible
for
the
community
community
to
submit
that.
So
we're
we're
looking
through
that
now.
A
E
A
A
Yeah,
we
don't
want
to
super
strongly
commit
to
things,
but
we
are
hoping
that
we
can
have
like
this
viewer
experience
of
grafana
translated
sometime
in
the
middle
of
the
year,
more
or
less,
and
then
from
the
yeah.
We
we
need
to
see
like
it's,
it's
a
pretty
straightforward
project
in
terms
of
we
know
what
the
end
result
should
be
graphene
in
multiple
languages,
but
the
thing
that
we're
going
to
stumble
upon
the
way
there
are
a
lot
of
unknown
risks,
especially
when
it
comes
to
ux
and
the
change.
A
I'm
learning
how
to
make
to
our
our
interfaces
and
all
those
things
and
we're
going
to
have
to
see
this
in
the
case
by
case
basis,
so
we're
actively
working
on
it
but
yeah.
What
is
the
whole
girlfriend
are
going
to
be
translated
as
a
whole.
That's
really
hard
to
tell,
because
there
are.
There
are
a
lot
of
components
here
too
right.
We
can
also
talk,
then
about
plug-ins
and
all
or
a
lot
of
different
things.
So
we'll
see.
E
I
think
an
interesting
and
interesting
part
of
this
globalization
effort,
as
well
as
things
like
visualizations,
and
how
we
show
numbers
and
data,
and
things
like
that
like
how
much
do
can
we
do
we
want
to
like
how
exactly
do
you
translate
and
localize
it's
for
the
user's
preferred
locale,
which
is
a
lot
to
think
about,
but
really
cool.
D
Okay,
because
reviewing
some
of
the
open
source
repositories
for
data
sources,
I
saw
that
the
grafana
team
actually
created
some
interfaces
to
to
have
all
the
messages
in
one
plate,
messages
and
the
bottoms
right
so
to
ease
it
easy
to
go
I'll
say
that
later
on-
and
I
saw
that
it's
congress.
So
it's
great
to
hear
about
it.
D
E
Yeah,
I
agree
it's
something
that
we
need
to
have
a
story
there
for
how
all
sorts
of
plugins
have
visualization
plugins,
how
data
source
plugins,
how
application
plugins
how
they
can
be
translated,
because
not
only
you
know,
there's
a
whole
bunch
of
third-party
plugins
available,
but
grafana
ourselves.
We
make
we
make
external
plugins
and
we
want
to
be
able
to
translate
them.
We
don't
know
exactly
how
that's
going
to
happen.
E
D
A
A
So
it's
fine,
I
mean,
I
think
the
questions
came
as
we
presented,
which
is
really
appreciative.
I
don't
know
if
there
are
more
questions.
Yo
do
you
have
any
questions.
B
So
far
was
only
using
the
browser
extension
because
we
don't
have
it
in
our
like
yeah
in
a
github
action
or
anything,
and
the
only
thing
that
we
run
automatically
in
our
pipeline
is
policy.
I
so
every
time
that
you
open
a
pr
or
in
main
we
are
running
policy
ai.
That
is
also
checking
for
accessibility
issues,
so
I
think
pali
and
fastpass
identified
almost
the
same.
The
only
thing
is
probably
use
a
different
engine
like
underneath
compared
with
fastpass.
B
C
A
Like
I
think
that
navigation
is
definitely
something
that
we're
looking
for
and
hello
nine
and
then
there
are
some
all
the
the
rest
of
the
things
to
be
honest
with
we're
still
defining
them
exactly.
D
H
Yeah,
I
think
I
think,
we've
been
pretty
careful
recently.
C
To
avoid
breaking
changes
to
plug-ins,
I
know
the
plug-ins
platform
team
are
pretty
pretty
good
at
cracking.
A
Next
community
call,
so
I
don't
want
to
spoil
what
they
call
this
yeah,
but
yeah
they're.
I
think
they're
quite
a
lot
of
news
in
terms
of
tooling
and
things
that
they've
been
working
on
to
to
improve
the
whole
packaging
story
like
it's
definitely
been,
if
not
the
most
one
of
the
top
priorities
that
they've
been
working
on,
so
we
hope
you'll
feel
it
too.
D
C
E
D
C
A
Yeah
yeah
you're
right,
I'm
I'm
really
now
the
if
it
hasn't
come
up.
Yet
there
is
a
public
communication
that
will
go
out
from
the
whole
angular
deprecation.
D
H
Okay,
I
just.
D
A
G
Nice,
nice
jumper,
by
the
way
natalia.
A
Christmas,
okay,
awesome:
everyone
yeah
see
you
around
have
a
good
day.