►
From YouTube: Grafana Community Call 2021-04-15
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
Amazing,
okay,
shall
I
get
started.
A
Hey
everyone,
my
name
is
matt
abrams.
Welcome
to
the
community
call.
I
am
the
first
community
support
engineer
at
grafana
and
I'm
going
to
be
moderating
the
talk
today
and
we
are
going
to
be
just
running
through
trying
something
out
we're
calling
it
community
matters.
A
Sorry,
I'm
getting
a
lot
of
messages
right
now
doing
a
thing
called
community
matters
where
first
we're
gonna
have
a
little
presentation
from
one
of
my
teammates
about
some
of
the
new
projects
that
the
community
team
is
working
on
to
help
support
the
community
and
then,
after
that,
we're
going
to
open
it
up
to
this
kind
of
like
free
session,
where
we're
going
to
work
through
some
of
the
things
I'm
going
to
talk
about
some
of
the
things
that
I'm
interested
in
learning
from
the
community,
and
you
can
hopefully
give
me
some
feedback
on
all
that.
A
So
I
think
that's
all
you
need
to
hear
about
me.
Diana
is
going
to
give
a
presentation
really
quickly.
She's
diana
payton
is
a
senior
technical
writer
from
the
doc
squad
on
the
grafana
team
and
she's
going
to
be
talking
about
very
briefly
about
the
new
docs
homepage
and,
I
believe,
exporters
as
well.
So
diana.
C
B
Around
here
in
startup
land
pleased
to
see.
C
B
All
right,
so
this
is
the
brand
new
docs
home
page
and
topic-
doesn't
look
that
different,
except
for
this
lovely
search
bar
which
I'll
demo
for
you
in
just
a
moment
but
down
here
we
used
to
have
kind
of
an
odd
thing
where
there
was
an
icon
and
then
the
title
and
the
whole
thing
was
not
clickable,
and
now
you
can
click
everything
and
also,
instead
of
being
organized
in
products
and
projects
they're
all
kind
of
in
one
bucket,
because
we've
got
some
kind
of
quick.
B
You
know
find
things
quickly.
Popular
content
up
here
and
then
down
here
is
all
of
our
various
docs
sets
and
there
will
be
more
small
tweaks
coming
soon,
but
that's
kind
of
a
big
improvement,
at
least
from
our
perspective
and
last
community
call.
I
demoed
the
new
sitewide
search
bar,
which
you
can
access
anywhere
by
clicking
this
little
guy
right
here.
But
if
you
do
a
search
in
here,
let's
say
oh
geez
install
grafana
with
docker,
then
you
will
get
a
search
already
filtered
for
just
docs.
So
that's
just
a
nice
little
usability
thing
there.
B
B
But
now
the
prometheus
expert,
quick
starts
page
is
live
with
seven
exporters
currently
up
and
I
believe
more
to
come
and
if
you
want
to
know
about
the
various
exporters
available
for
prometheus,
just
go
here
and
you
can
find
out
all
sorts
of
useful,
nitty
gritty
information
about
using
exporters
and
how
to
increa,
integrate
them
into
your
grafana
cloud
account
because
that's
hilary
roll
all
right.
That's
about
what
I
had.
B
A
Yeah,
it's
it's
really
incredible,
and
it's
actually
thank
you
for
for
all
of
that,
and
I
think
it
makes
like
a
really
nice
bridge
into
what
I
was
hoping
to
kind
of
like
kick
off.
This
community
call
to
talk
about
a
matter,
that's
of
particular
interest
to
me
and
I'm
hoping
that
the
community,
all
the
community
members
on
this
call,
can
help
me
with
this.
A
I'm
new
to
grafana
myself.
You
know
today
is
actually
my
one
month
anniversary
with
the
community
and
before
joining
grafana.
I
had
never
really
my
former
company
used
graffana
and
we
all
loved
grifana,
but
I
had
never
really
used
grafana
seriously
and
and
so
I'm
still
very
much
learning-
and
I
find
myself
in
this
position
of
being
like
a
very
avid
and
enthusiastic
and
ambitious,
but
very
early
stage.
A
What
is
that
kind
of
workflow
look
for
look
like
for
you
like.
Where
are
you
going?
Are
there
resources
you
like?
What
are
you
trying
to
learn?
I'm
just
I'm
very
curious
to
hear
what
I
can
learn
from
you
about
how
you're
using
resources
in
like
the
broad
grafana
ecosystem.
A
A
B
A
shoe
I
apologize
if
I
slaughter
this
yeah
sorry
man,
I
took
german
in
high
school,
not
nation
language,.
D
So
yeah,
so
this
is
true
from
linkedin,
so
I
pretty
much
learned
the
grafanas
through
docs.
I
think
eighty
percent
of
my
time
spent
on
the
dogs
and
the
rest
20
is
just
googling
and
also
ask
questions
in
the
slack
channel.
D
So,
promoting
using
this
court
right
now
right.
B
Has
a
question
that
they
ask
and
get
answered.
Somebody
else
in
you
know
two
months
in
line
has
the
same
question
and
does
a
google
search
for
it
then
they'll
be
more
likely
to
find
the
answer,
okay
and
in
our
forums,
because
there's
no
hope
in
the
slack
it's.
It
doesn't
remember
things
for
very
long.
Okay,.
D
A
Yeah,
the
the
I
think
it's
community.fauna.com
and
it's
can
be,
I've
found
it
it's
actually
a
very
powerful
resource
for
finding
answers
to
stuff,
because
there's
chances
are.
If
you
have
a
question,
it's
probably
been
asked
in
there
before
that's
kind
of
the
thing
that
I'm
discovering
for
a
lot
of
stuff,
there's
a
lot
of
like
institutional
knowledge
buried
in
in
that
discourse
channel.
So
it
can
be,
and
people
are
pretty
good
about
answering
right
now,
so
it
could
be
a
good
place
to
get
feedback.
A
A
Just
like
read
them
all
from
you
know
top
top
to
bottom.
That
would
be
really
important
for
me
to
do.
Rtf.
B
D
E
F
Well,
it's
even
worse,
they
store
everything,
and
then
they
just
force
you
to
pay.
If
you
want
to
get
into
the
history
and
it's
explicitly
forbidden
in
their
in
their
contract
terms
or
in
their
service
terms,
to
extract
any
messages
out
of
slack,
in
particular
with
the
non-paid
version,
which
is
one
of
the
reasons
why
I
don't
like
slack
too
much
but
like
in
theory,
we
can
do
it,
but
in
practice,
if
slack
notices,
they
will
just
shut
everything
down
or
that
top
down.
Or
what
have
you
so.
E
So,
can
I
ask
you,
you
mentioned
like
80
from
the
documentation
and
20
from
the
from
slack?
Is
that
is
that
the
same
ratio
now
than
compared
to
when
you
first
started
learning
grafana
or
has
that
changed.
E
Yeah
just
curious,
if
you,
if
you
had
like,
if
you
learned
grafana
years
ago,
and
then
you
come
back
to
the
documentation
or
do
you
go
to
places
like
slack
or
discourse
more
but
yeah
documentation
seems
you
you
see
it
seem
to
have
a
a
lot
more
to
to
to
gain
from
the
documentation.
It
sounds
like.
A
A
Anybody
else
have
any
input
of
how
they're
how
they're
learning,
grafana
or
favorite
resources
that
they
like
or
we
can.
I
also
have
some
related
questions
you
know
like.
I
saw
somebody
actually
before
the
meeting
put
made
some
notes
in
this
doc,
because
some
of
the
other
questions
that
I
had
you
know
related
to
how
you're
learning
grafana-
and
this
is
maybe
something
you
might
want
to
chime
in
on-
is
you
know?
How
are
you
using
grafana?
A
I
think
there's
like
the
common
grafana
use
case,
but
it
feels
like
a
lot
of
the
people
that
I'm
interacting
with
in
the
forums
and
who
are
playing
with
grafana
are
really
pushing
its
limits
or
using
it
in
like
unorthodox
ways
or
interesting
ways
or
innovative
ways.
So
I'm
always
curious
to
like
learn
more
about
how
people
are
actually
using
grafana
in
the
wild.
D
So
so
I'm
I'm
working
on
a
internal
tools
where
we
originally
built
the
ui
on
top
of
the
on
top
of
the
amber
and-
and
we
have
some
internal
ui
libraries
based
on
the
amber
butters.
But,
to
be
honest,
the
amber
is,
has
a
really
really
stiff
learning
curve
for
people
like
don't
have
any
or
much
ui
experience
and
on.
D
On
the
other
hand,
the
react
is
more
like
friendly,
like
people
can
pick
up
the
ui
development
really
fast,
using
the
react,
and
so
we
kind
of
for
one
of
our
internal
tools.
We
decided
to
just
get
rid
of
amber
and
the
u
and
then
use
the
grafana
to
show
our
data
and,
of
course,
we're
gonna
use
the
majority
like
the
most
of
the
built-in
visualizations
from
from
grafana,
but
for
other,
like
other
ui
that
needs
the
like
user
to
that
does
more
complicated
stuff.
D
We're
gonna
just
use
the
react,
ui
kit
to
to
build
one
and
oh,
I
think
it's
really
awesome,
because
I
can
share
a
like
a
comparison.
D
So
for
the
amber
version
of
like
of
our
old
version,
we
kind
of
spend,
so
we
are
like
a
four
team
or
four
people
team
and
us
like
is
like
ui
guy,
and
we
spend
like
a
year
to
maintain
that
a
single
page
and
once
we
switched
grafana,
we
only
like
to
spend
10
days
to
implement
all
the
like.
Pretty
much
has
the
feature
parity
there.
A
A
No,
I
was
just
trying
to
get
a.
A
D
Yeah
so
so
within
linkedin,
there
are
like
tons
of
like
hundreds
of
like
tooling
right
so
individual
project
and
I'm
working
on
one
of
them
and
originally
built
on
top
of
amber
and
now
it's
built
on
top
of
grafana.
And
so
not
everyone
like
not.
Everyone
is
using
the
performance
right
now
and
right,
I'm
trying
to
promoting
it
and
using
my
case
as
a
success,
successful
story
and.
A
D
I
would
say
more
dark
on
the
ui
kit.
I
know
it's
new
and
and
when
I
see
the
ui
kit
dock,
it's
kind
of
it's
not
as
rich
as
the
like
grafana
dock,
so
we
I
think
we
just
need
more
examples
and
documentation
on
the
ui
kit.
That
would
be
really
helpful,
but
I
I
understand
it's
new
and
you
guys
need
more
time
too.
E
So
what
can
I
just
ask
when
you,
when
you,
when
you
refer
to
uikit,
do
you
are
you
referring
to
the
plugins
documentation
since
you
mentioned,
react.
D
Yes,
you
know
you
have
a
yes,
the
plugins,
the
do
you
like
it
to
build.
The
panel
plugins.
E
Yeah,
so
are
you
referring
to
the
developers
dot
grafana,
the
the
you.
E
B
Yeah
on
the
subject
of
examples
in
general,
some
of
the
feedback
we
get
about
the
documentation
is
that
they
people
would
like
more
examples
and
the
tough
part
about
that.
For
me,
as
a
writer,
is
I'm
not
an
expert
in
most
of
the
fauna
usages
and
I
don't
have
a
whole
lot
of
real
world
examples.
So
if
you
guys
are
looking
through
or
you
have
good
examples,
you
know
all
of
our
open
source
documentation
has
an
edit
this
page
button,
so
we'd
love
to
have
community
community
contributions
of
examples
of
things.
It's.
D
D
B
So
the
best
place
to
put
feedback
for
storybook
is
in
the
hashtag
grafana
fails
channel
in
the
public
slack.
I
did
not
name
that
channel
the
ux
folk
did
and
they
monitor
that
channel
quite
fairly
closely.
So
if
you
want
to
give
them
feedback
about
that,
that's
the
place.
To
put
it
so.
B
Yeah
they
they
own
the
storybook
and
and
manage
that,
but
we'll
we'll
help
them
as
best
we
can,
but
we
but
telling
us
what
your
pain
points
are
there
and
what
would
help
you
would
really
help
us
to
help
them
to
help
you.
A
Yeah,
that's
a
really
good
point.
Diana
and
it
kind
of
brings
me
to
this
other
bullet
that
somebody
before
the
meeting
had
made
some
contributions
to
the
notes
in
the
docs
and
one
of
the
things
about
about
using
grafana
like
what
did
they
want
to
see.
You
know
what
kind
of
content
would
you
like
to
have
and
they
wrote
something
about
performance
tuning,
a
performance,
tuning
guide
or
configuration
recipes
recipes
for
scaling
out,
which
made
me
kind
of
think
about
a
lot
of
things
that
could
maybe
be
useful
for
the
community.
A
You
know,
I'm
not
sure
what
this
person
was
thinking
about,
like
some
sort
of
like
kind
of
cookbook
type
format,
or
if
the
community
is
interested
kind
of
like
what
maybe
what
you
was
talking
about
like
quick,
starts
or
or
tutorials.
I
think
the
quick
starts
for
the
for
the
exporters
are
like
going
to
be
super
fantastic.
I'm
really
excited
to
poke
around
in
all
of
those.
A
Actually,
so
is
that
the
kind
of
content
that
we
should
have
more
of,
I
think
I
can't
say
for
sure
I
mean
I
would
love
it,
but
that's
that
I
just
mean
that
so
you
know
like
what
would
you
like
to
see?
I
mean
I'm
very
curious
and
especially
like
in
this
performance
to
an
email.
They
could
have
a
much
larger.
A
We
could
have
a
whole
community
call
about
that,
I'm
sure
and
what
that
could
entail,
but
yeah
as
far
as
like
content,
I
think
the
quick
start
and
the
tutorial
or
glossary
you
know
things
like
that
are
all
very
interesting
things.
So
anybody
have
any
feedback
on
that
or
or
the
person
or
the
ops
question
about
performance
tutoring
and
configuration
recipes
like.
Where
would
you
go
to
find
that
stuff?
A
I
would
go
to
the
docks.
I
would
go
to
the
docks
as
well
and.
B
Go
ahead,
speaking
of
so,
we
made
a
change
not
too
long
ago
and
here
in
getting
started,
come
on
you.
So
what
the
hell?
Okay,
that's
fun.
B
So
we've
got
the
these
getting
started
with
grafana,
getting
started
with
graffiti
fun
and
prometheus
and
getting
started
with
grafana
and
mssql
server
that
have
been
that
we
have
we're.
Gonna
have
more
of
those
coming,
and
so
that's
kind
of
your.
You
know
just
getting
started
from
zero
to
something
and
then
for
the
more
advanced
people.
B
That
would
be
great
and
we've
got
both
some
just
general
best
practices
for
dashboard
for
creating
and
managing
dashboards,
but
also
observability
strategies
like
the
use
method
and
the
red
method
and
some
links
to
other
useful
items
and
some
information
about
the
dashboard
maturity
model
so
kind
of
like
to
help
you
figure
out
where
you
are
in
your
progression
of
dashboards
and
where
you
might
want
to
be.
B
Oh
and
one
other
update
that
I
forgot
to
mention
our
gtm
folks
decide
to
help
out
by
adding
links
to
getting
started
stuff
at
the
bottom
of
all
of
our
documentation
pages.
So
you
get
to
see.
Marcus's
smiling
face
every
time.
A
By
the
way
that
is
a
great
video,
I
will.
C
It
is
absolutely
it's
a
really
great.
A
Video
that
marcus
did
with
a
really
great
companion
tutorial,
that's
also
in
our
docs,
but
following
the
video
and
the
tutorial.
Well,
I
I
had
a
great
experience
doing
that.
So,
if
you're
looking
for
like
spin
up
a
spin
up
a
grafana
setup
and
just
stand
it
up
and
play
around
with
it
and
see
how
it
works
like
in
real
time,
it's
a
great
it's
a
great
little
tutorial.
So
that's
why
it's
on
the
bottom
of
every
page!
A
Yeah!
That's
great!
That's
really
really
interesting
diana
does
anybody
else?
Have
any
feedback,
yeah.
E
I
was
just
gonna.
Add
the
you
know
to
the
the
discussion
of
how
do
you
learn
grafana?
Obviously,
we,
if
you
search
for
grafana
on
youtube,
for
example,
there's
not
a
ton
of
videos
from
the
grafana
team.
Is
that
something
that
you
would
like
to
see
more
of,
or
do
you
feel
like
you're,
getting
more
value
from
a
better
documentation,
or
would
you
like
to
see
more
something
more
visual
in
the
form
of
video
content?
I
know
that
there
are
some
screencasts
that
were
recorded
a
while
ago,
but
I'm
not
sure
daniel.
E
Is
it
4.0
or
5.0
they're
they're
demoing
either
way
it's
it's
yeah,
it's
pretty
dated
by
now.
So.
A
It's
a
really
good
point,
though
marcus,
because
I
remember
my
my
last
company.
I
worked
on
the
community
platform,
which
was
very
robust
and
we
were
always
getting
feedback
from
all
these
consultancies
about
like
what
developers,
what
kind
of
educational
content
developers
wanted
like
do
they
want
video
content?
A
Do
they
want
written
content
and
video
content
is
a,
I
think,
a
really
hard
thing,
but
very
dynamic,
and
might
work
really
well
with
might
work,
especially
well
with
grafana,
actually,
because
it's
such
a
visually
oriented
tool,
it
lends
itself
really
well
to
a
visually
oriented
like
medium
like
like
video,
so
I
think
that
could
be
super
interesting.
I.
E
E
You
know
you
can
put
a
a
page
out
there
and
then,
if
someone
finds
a
typo
or
something
that's
wrong
or
want
to
improve
it,
they
can
just
update
it,
whereas
in
video
you
need
to
record
another
video
and
then
republish
it
do
you
take
down
the
previous
one
or
you
know
it's
a
lot
of
work
and
creating
video
content.
That
is,
you
know,
with
nice
cuts
with
audio,
and
you
know
making
sure
that
you
have
a
good
recording
set
up
it
it.
E
It
is
a
lot
of
effort
and
I
think
that
we
want
to
make
sure
that
we're
we're
doing
it
well
and
we're
doing
it.
You
know
it's
providing
us
with
value.
E
C
Torkle
did
he
recorded
them
in
our
bathroom,
so
he
basically
filled
up
with
pillows
and
soft
things
and
like
in
our
like
tiny
old
office
that
we
had
and
he
was
sitting
in
there,
recording
them.
So.
E
A
B
A
fun
little
teaser
here,
actually,
our
cx
folk
are
getting
started
on,
are
working
on
some
videos
and
they
have
a
really
interesting
idea
for
how
to
put
them
together
in
ways
that
will
make
them
not
a
total
nightmare
to
update
basically
they're
going
to
record
small
segments
so
that,
hopefully,
they'll
only
need
to.
You
know,
update
a
small
if
they
a
small
segment
rather
than
an
entire
video.
If
something
changes
so
not
sure
what
the
timeline
on
those
are.
But
I
know
that
that
is
in
the
pipeline.
E
So
I
actually
have
a
question
for
if
there's
you
know,
maybe
more
experienced
grafana
users
out
there.
You
know
how
I'm
kind
of
curious
how
you
learn
grafana
today,
yeah,
obviously
you've
been
using
grafana,
maybe
for
years.
How
do
you
stay
updated
with
you
know,
new
features.
How
do
you
make
sure
that
you're,
you
know
you
you're
still
learning
rafana
and
how
do
you?
You
know
how,
if
you
want
to
take
it
to
the
next
level?
Where
do
you.
A
Go
yeah,
that's
a
really
really
good
question
marcus.
Does
anybody?
Does
anybody
in
the
audience
have
any
feelings
about
that.
G
Hi
everyone,
I
think
we
discussed
it
last
time,
actually
that
I
would
love
to
see,
updates
and
documentation
which
happens
recently
because
documentation
always
involving-
and
you
don't
know
what
changed
actually.
In
that
I
mean
this
kind
of
calls
helps.
But
as
talking
about
this
video
presentation
of
small
videos,
it
will
be
great
actually
to
have
some
updates
video.
I
mean
you,
don't
need
to
change
it
right.
G
It
just
updates
which
happens
last
last
month
and
will
be
great
to
learn
like
five
minutes,
video
great
to
learn
for
everyone
and
regarding
the
updates,
what
I
do
recently.
I
just
do
look
for
the
pull
requests
like
every
pull
request,
which
is
happening.
You
actually
can
see
the
updates
and
documentation
the
way
when
they
happen
right.
You
see
all
the
new
functionality.
B
Yeah
quick
thing
about
that-
I
wasn't
necessarily
going
to
mention
this
because
it
will
ideally
be
mostly
transparent
to
you
folks,
but
we
made
a
change
recently
so
that
we
can
actually
so
previous
state
is
that
every
time
we
made
a
merge
from
into
the
docs
folder
in
the
master
branch,
it
would
go
straight
into
the
website,
and
now
we
made
a
change
so
that
by
default
it
will
go
into
a
different
folder
in
the
website.
B
B
B
Maybe
just
there
we
go
so
latest
is
the
current
and
next
is
and
latest
was
where
everything
was
going.
Next
is
where
it
will
be
sent
by
default
now,
but
we
can
also
put
it
in
latest
like
if
we've
got
a
typo
or
something
that's
not
really
specific.
A
That's
yeah.
That's
a
really
really
good
point:
diana
for
surfacing
things
that
new
changes
to
the
docs
which
I've
been
using
too
and
so
mikhail.
If
I
could
just
ask
like,
would
you
be?
Are
you
saying
that
you
would
be
interested
in
seeing
like
a
short
snappy
videos
that
tour
or
demo
new
features
as
they're
coming
out.
F
B
Yeah
and
and
the
nice
things
about
that
I've
done
what's
new
videos
before
the
nice
thing
about
those.
Is
they
never
go?
Stale,
because,
what's
new
in
say,
grafana
7.5
will
always
be
what
happened
in
grafana's
7.5.
You
don't
need
to
go
back
and
update
that
ever
yeah.
B
You
know
tons
of
small
things
every
day
so
yeah
I
hear
you
what
you're
saying
rick
hill
and
we'll
try
to
at
least
be
aware
that
aware
of
the
the
bigger
changes
and
ensuring
them
so
yeah
keep
an
eye
on
the
hashtag
hashtag
docs
channel
in
public
slack
for
that
sort
of
thing,
because
that's
where
we're
likely
to
announce
stuff
related
to
docs
anyway,.
G
G
C
G
Different
things
I
mean
it's
great
because
when
I
explain
someone
something
or
try
to
answer
the
question,
I
learn
something
myself
and
experiment
with
different
things.
It
takes
too
much
time.
I
would.
I
would
love
someone
from
grafana
actually
take
responsibility
and
start
disappointing.
A
The
plug-in
ecosystem
is,
is
a
lot,
no
doubt.
No
doubt
what
was
I
gonna
say.
A
Not
quite
it's
too
early
for
that
yeah.
That's
really
really
really
interesting,
though,
like
twitter
short
for
one
more
point:
yeah,
please.
G
Also,
what
I
would
love
to
see
more,
it's
a
life
cycle
for
plugins
or
dashboards,
because
I
mean
you
have
now
a
history
from
version
7
now
version
8
right
and
I
mean
as
a
as
a
plugin
developer,
I'm
really
interested
how
you
do
this
lifecycle
management.
Should
you
upgrade
your
plugin?
This
is
the
latest
I
mean
every.
I
I
think
I
talked
about
it
before.
G
C
G
E
Yeah,
it's
it's
a
it's
a
really
tough
problem
to
keep.
You
know
if
you're
developing
a
plug-in
to
make
sure
that
it's
you
know
it
supports
even
pre
7.0
and
if
even
if
you're
developing
a
plug-in
for
a
7.0
to
keep
it
running
for
7.5
and
all
the
way
back
it
is.
It
is
a
tricky
thing
and
you
know
apis
change,
and
you
know,
one
option
is,
of
course,
to
you
know,
create
a
release
for
every
minor
version
of
grafana.
But
of
course
that
comes
with
maintenance.
E
Cost
of
you
know
maintaining
every
all
of
those
versions
and
every
time
you
want
to
fix
something,
you
need
to
create
a
hotfix
for
our
all
the
the
the
previous
versions
as
well.
So,
of
course,
the
the
nicer
thing
would
be
to
if
you
have
one
plug-in
that
is
backwards
compatible
with
previous
versions
and
there
we.
E
I
will
say
that
we
are
discussing
this
heavily
internally.
This
is
something
that
we
are
very
aware
of,
and
even
you
know
our
own
enterprise
plug-in
developers
are.
Are
you
know
experienced
in
this?
So
we
hope
that
we,
you
know,
we
obviously
need
to
write
some
form
of
documentation
for
this
and
provide
some
guidance.
E
I
don't
think
there's
a
clear-cut
answer.
I
you
know
one
one.
One
thing
you
could
do
is
you
know
check
if
the
actual
feature
is
is
available.
You
know,
that's
that's
what
I
do
for
my
plugins,
where
I
actually
have
a
little.
You
know
if
statement
to
see
if
the
the
feature
is
undefined.
Basically,
but
you
know
that
means
that
you
have
a
ton
of
conditionals
in
your
code
to
check
like
if
it's,
if
is
it
more
than
7.3,
is
it
7.4?
Is
it
7
point
and
a
half?
E
B
H
In
for
a
little
bit
just
to
go
back
to
what
mikhail
said
about
kind
of
slack
versus
discourse,
you
know,
I
think,
a
lot
of
the
reasons
that
diana
mentioned
up
front
about
why
we
focus
a
lot
of
our
attention
on
on
discourse.
Being
this
community-built
knowledge
base
is
like
that
findability
aspect
that
isn't
to
say,
like
we
completely
ignore
we,
as
in
grafana
labs,
ignore
our
slack.
H
You
know
we
we
try
to
answer
when
we
can,
but
as
a
team,
we
commit
most
of
our
time
answering
questions
on
the
forums
just
because
we
know
that
has
more
long-term
value
to
the
community.
So
I
mean
we
do
know.
There
are
some
people
who
prefer
that
real-time
engagement
aspect,
but
you
know
our
community
is
global
grafana
as
a
team
is
global,
and
so
sometimes
people.
H
You
know
things
move
quickly
when
there's
a
3
000
person,
slack
channel
and
you're
trying
to
get
help,
and
so
sometimes
we
just
miss
things
because
of
a
bandwidth
or
how
quickly
things
go.
But
you
know
one
of
the
things
marcus
and
and
matt,
and
a
lot
of
other
folks
on
the
community
team.
Do
we
have
dedicated
times
every
week
to
answer
forum's
questions
just
because
we
know
that's
going
to
have
value,
and
so
we
don't
want
to
discourage
people
from
like
we.
H
We
want
people
to
one-to-one
help
each
other
on
slack,
but
it
it's
hard.
When
we
know
somebody
has
a
great
response
to
a
question,
especially
questions
that
come
up
a
lot
and
it
just
goes
into
the
ether.
So
that's
something
we're
trying
to
figure
out
like
how
can
we
integrate
slack
and
discourse
a
little
bit
better
just
so
we
don't
lose
things
because,
like
richie
mentioned,
like
hey,
it's
against
slack's
use
policy
for
us
to
extract
that
information
in
a
more
programmatic
way.
So
just
some
things
we're
thinking
of.
B
Just
a
quick
thing:
sam
is
our
community
manager,
so
she
knows
of
what
she
she
speaks
and
richie
is
both
the
prometheus
guy
and
our
director
of
community.
So
that's
where
he's
come
from,
and
I
don't
know
if
marcus
olsen
introduced
himself
this
time,
but
usually
he
runs
the
call.
So
a
lot
of
you
should
know
him
he's
our
developer
advocate.
So
sorry,
belated
introductions
all
around
for
the
graphinistas
on
the
call
that.
H
A
H
Before
the
pandemic,
did
you
did
you
go
to
meetups
and
things
were
you
where
you
saw
somebody
presenting
something
on
grafana
or
conferences,
not
not
hosted
by
grafana,
but
like
other
meetups,
I'm
just
kind
of
curious
because
we're
trying
to
wrap
our
head
around?
How
can
we
have
more
beyond
just
community
calls
opportunities
for
community
members
to
show
and
tell
and
grafana
labs,
to
show
demos
of
new
features
and
teach
little
things
so
we're
trying
to
figure
out?
G
G
Something
you
can
learn
from
everyone,
and
I
mean
in
radius
labs.
We
had
different
sessions
from
time
to
time
when
we
actually
explained
the
technology
so,
and
I
mean
now
with
the
pandemic,
you
can
actually
invite
someone
who
will
do
the
showcase
for
the
community
and
save
it
to
youtube.
It
should
be
great.
G
My
my
talk
about
radius
plugins
for
grafana
on
monday
at
radius
corner.
So
if
you.
H
A
A
That's
a
very
I
mean
that's
a
question
that
I'm
very
curious
about
too,
because
some
of
the
best
pieces
of
learning
that
I've
encountered
are
recordings
from
in-person
conferences
about
prometheus
or
about
grafana
like
some
of
the
best
content
that
I've
engaged
in
are
these
video
resources,
but
those
video
resources
were
made
from
like
people
coming
together
and
congregating
at
a
conference
or
a
meetup,
and
I
don't
know
if
it's
just
the
magic
of
getting
people
together,
but
some
of
those
talks
are
really
really
really
valuable.
A
So
it's
curious
to
me
to
see
how
that's
going
to
kind
of
play
out
in
the
future.
In
this
like
covet
and
maybe
post
covet
moment
yeah,
this
has
been
super
valuable
for
me.
Does
anybody
have
anything
else
on
their
mind?
Otherwise
I
think
this
has
been
like
a
really
valuable
call.
We
can
maybe
cut
it
a
few
minutes
early,
any
burning
desires,
anything
any
feedback.
B
G
E
I
mean
we
will
we
will
I
mean
we
are
working
on
app
plugins
right
now,
but
mostly
it's
figuring
out
what
we
want
to
focus
on
I
mean
we,
we
developed
several
enterprise
plug-ins
and
a
lot
of
the
the
stuff
that
we
do
for
commercial
purposes.
At
grafana
labs
is
relying
heavily
on
app
plugins,
so
applicants
are
here
to
stay,
but
we're
kind
of
in
a
in
a
position.
Now
where
we
are
thinking
hard
about
where
we
do,
we
want
to
take
app
plugins.
E
There
are
several
things
that
we
can
improve.
For
example,
routing
is
one
of
those
things
that
we
we
really
want
to
improve,
and
I
think
that
is
going
to
have
a
big
impact
on
on
how
you
can
write
your
app,
but
there
are
other
aspects
to
applicants
as
well
right
now
there
is
no,
you
know
official.
E
You
know
documentation
on
what
we're
planning
to
do.
I
think
it's
scattered
on
github.
For
now
there
are
a
few
checklists
on
and
github
issues.
I
can
try
to
find
them
for
you
just
to
give
you
a
heads
up
what's
coming,
but
as
soon
as
we
feel
more
comfortable
about
where
we're
going
without
plugins,
we
will
have
documentation.
I'm
standing
ready
at
my
keyboard
to
start
spitting
out
documentation
as
soon
as
we
know
more.
B
Yeah
another
question
in
the
chat
from
divya:
are
there
any
breaking
changes?
We
should
be
aware
of
in
8.0
and
I
don't
recall
any,
but
I'm
also
not
an
engineer,
matt
and
marcus.
So
I
might
not
have
recognized
one
if
I
saw
it.
A
E
Not
that
I
can,
I
can
think
of
most
of
the
stuff
is
just
new
features,
and
you
know
more
basically
not
changing
things
that
much.
B
Yeah,
the
the
closest
thing
I
can
think
of
is
that
we're
really
we've
made
a
lot
of
progress
in
becoming
a
react
rather
than
an
angular
thing.
So
how
did
they
describe
it?
But
basically
we're
going
to
be
grafton
is
going
to
be
more
of
a
react
app
with
a
few
angular
legacy
things
rather
than
an
angular
kind
of
a
weird
mix.
B
So
I,
like
I
say
no
one-
has
told
me
to
put
anything
in
the
docs
yet
about
hey.
This
is
going
to
horribly
break
stuff
and
nothing
that
I
recall
from
the
feature
set.
Has
that
either
another
question?
Are
you
able
to
expand
a
bit
on
the
panel
library
functionality
that
was
mentioned
on
hashtag
fauna
earlier
today?
Yes,
that
is
an
8.0
feature.
One
of
the
big
themes
for
rafana
8
is
dashboard
management
and
one
of
those
things
is
being
able
to
reuse
panels
in
more
than
one
dashboard.
B
So
I
kind
of
think
of
them
like
variables,
but
basically
because
basically
you'd
have
a
panel
in
one
place
and
be
able
to
stick
it
into
multiple
dashboards.
But
have
it
centrally
managed
from
one
place
and
I'm
not
quite
sure
what
it's
going
to
look
like
yet
and
they're
still
debating
what
it
exactly
should
be
called.
But
that's
the
general
idea.
A
Yeah
and
marcus
quickly,
if
I'm
wrong
here,
but
I
think
this
is
use
implementing
that
method
is
a
more
performant
way
than
just
duplicating
entire
dashboards
or
panels.
E
Yeah
it
so
currently,
if
you,
if
you
want
to
reuse
panels,
I
mean
right
now:
it's
just
you
know
copying
and
pasting
unless
you're
using
provisioning,
for
example-
and
you
know
if,
if
you're,
storing
your
dashboard
definitions
in
github,
for
example,
then
you
can,
you
know
automate
that
a
little
easier,
but
hopefully
with
8.0.
We
can
make
it.
You
know
as
a
first-class
citizen,
where
we
can
have
a
whole
library
of
of
panels
that
you've
you've,
developed
and
you're
you're
you're
very
happy
with,
because
you
know
in
larger
organizations.
E
You
typically
have
teams
that
come
up
with
the
same
kind
of
dashboards,
and
so
this
is
a
way
of
reusing
that
and
letting
teams
discover
already
existing
panels.
B
B
B
So
I
hope
that
answers
the
question
and
then
jamie
says
we
have
a
few
sets
of
dashboards
where
panels
are
duplicated
yep.
That
is
exactly
the
use
case
and
right
now
we
have
to
make
any
changes
multiple
times
and
it's
prone
to
human
error.
We're
probably
a
candidate
for
provisioning
but
haven't
made
that
leap
yet,
so
that
would
be
a
really
useful
future
future
cool
jamie.
B
G
C
A
Yeah,
that's
a
good
question
mikhail.
We
need
you
to
bang
on
this
thing
and
see
if
you
can
break
it,
it
sounds
like
sure
so
yeah
I
don't
have
an
answer
for
you
right
now.
All
right.
B
Jamie
says
that
they
put
the
beta
date
on
the
calendar
to
try
it
out.
Awesome
and
divya
asks
so
will
that
allow
data
source
authors
to
ship
predefined
panels,
along
with
their
data
source,.
E
B
B
Marcus
a
lot
more
basically
like
kind
of
like
apis
was
how
it
was
explained
to
me,
and
they
might
have
just
been
dumbing,
that
down
for
the
technical
writer
but
a
lot
so
that
you
could
treat
them
more
directly
as
repeatable
code.
B
E
So
the
the
challenge
with
dashboard
definitions
today
is
that
they're
huge
it's
a
it's
a
massive
json
blob
that
if
you
were
to
fully
embrace
git
ops
and
editing
this
dashboard
in
github,
it
would
be
you
know
very
difficult,
I'm
sure
people
are
doing
it.
I
wouldn't
wanna.
E
Instead,
there
are
ways
to
generate
those
dashboard
definitions
from,
for
example,
using
jsonnet
and
similar
tools,
but
coming
up
in
the
future,
we
will
provide.
You
know
explicit
schemas
for
dashboards,
and
you
know
we
will
also
make
a
lot
of
these
settings
settings
in
the
dashboard
definition
defaults.
So
you
don't
have
to
define
everything
yourself.
You
only
define
the
the
stuff
that
you
care
about
and
having
formal
schemas
for
dashboards
will
also
enable
tooling,
like
you
know,
linting
dashboard,
formatting
dashboards.
E
You
know
is
this:
is
this
a
accessible
dashboard
and
you
can
write
a
linter
that
lists?
Oh,
you
can't
use
these
colors
because
they're
not
accessible,
for
example.
So
we
we
see
a
ton
of
cool
features.
Coming
from,
you
know
having
a
well-defined
schema
for
dashboards.
A
Yeah,
I
I
have
to
say
this
is
something
I
really
like
about.
Grafana
labs
in
general
is
like
this
will
towards
automation,
and
this
will
towards
treating
as
much
as
possible
in
a
sort
of
code
like
fashion,
whether
it's
infrastructure
as
code
and
this
interest
in
like
terraform
providers
and
and
the
kind
of
locking
down
these
kind
of
configuration
issues
to
just
remove
complexity
and
just
make
things
work
and
treating
docs's
code,
as
I'm
sure
we'll
have
another
call
about
that,
because
there's
a
lot
of
interesting
things
going
on
there.
A
So
I
just
really
love
the
that
kind
of
like
spirit
that
is
pervasive
across
grafana
labs
and
I
think
it's
gonna,
I
think
exactly
marx
is
talking
about.
It's
gonna,
make
like
a
sort
of
quantum
leap
and
taking
care
of
these
things
that
are
becoming
sort
of
unwieldy,
yeah.
That's
a
great
question
and
a
great
idea
for
feature.
A
E
Yeah
massive
thanks
to
everyone
who
joined
and
massive
thanks
to
matt
for
hosting
this
call.
Thank.
F
F
More
attendees
are
welcome
to
speak
up,
we
don't
bite.
I
know
it
takes
some
time
to
warm
up
and
everything,
but
it's
also
super
rewarding
when
you
allow
yourself
to
to
speak
up
and
actually
participate
more
actively,
no
pressure
or
anything
but
feel
emboldened,
like
you,
don't
have
to
raise
your
hand
through
the
feature
or
anything
unmute
and
talk.
This
is
not
us
having
a
monologue
with
each
other.
This
is
us
actively
trying
to
talk
with
you
and
to
listen
exactly.
B
H
H
A
Want
a
special
t-shirt:
okay,
I.
B
Oh
oh
you're,
talking.
F
B
A
Yeah
all
right,
very
cool,
looking
forward
to
my
t-shirt
thanks
everyone
for
hopping
on
the
call-
and
we
will
see
you
next
time
and
have
a
great
day-
have
a
great
rest
of
your
day
wherever
you
are.