►
From YouTube: Grafana Community Call 2021-07-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
To
the
to
the
va
use
case,
it's
still
really
early
stages,
but
we're
trying
to
figure
out
what
our
longer
term
goals
are
there
and
all
these
kind
of
things,
and
we
have
the
user
essentials
squad,
which
their
focus
is
the
end
user
profile.
So
they
work
on
all
these
flows
like
navigation
logging,
theming,
dashboard
management,
all
those
kind
of
things,
and
then
we
have
the
third
one
that
is
one
that
will
develop
more
intuitive,
probably
which
is
the
plugins
platform.
A
I'm
not
gonna
spoil
the
surprise.
I
think
marcus
and
jack
can
can
tell
you
more
about
it,
but
maybe
we
can
do
a
quick
intro
for
each
of
the
people
meeting
here
I
don't
know,
maybe
object.
Do
you
want
to
start
holiness
well
already
name
but
which
team
you're
in
and
what
you're
up
to.
B
Yeah
sure
so
hi
everyone,
my
name
is
you
can
call
me
for
sure,
I'm
a
software
engineer
at
grafana,
I'm
part
of
like
the
front-end
platform
squad,
formerly
as
it's
called,
but
now
I'm
part
of,
like
the
user,
essential
squad
which
you
would
still
discuss
in
a
bit
and
yeah.
I
live
and
work
from
a
country
called
nigeria
in
africa
and
yeah.
I'm
super
excited
to
be
here.
I'm
a
huge
community
fan
and
yeah
I'm
happy
to
like
get
to
learn
more
about
each
and
every
one
of
you
yeah.
C
Yes,
I'm
you
that
sorry
yeah,
so
my
name
is
marcus.
I'm
used
to
being
working
in
the
frontend
platform
squad
that,
as
natalia
said,
where
you
split
so
I'm
working
in
the
plugins
platform
squad
and
I'm
based
in
falcon
street
in
europe.
C
D
Yeah
sure
hi,
my
name
is
jack.
I've
been
happily
working
in
the
front
end
platform
squad
for
nine
months
now
recently
moved
over
to
the
plugins
platform
with
marcus
and
yeah.
I'm
I'm
based
out
in
italy,
near
milan,
alexa.
E
F
Yes,
yes,
I'm
antobias,
I'm
based
in
sweden
a
little
bit
here
and
there
you
never
know
where
I
end
up.
This
is
my
fourth
time
being
an
intern
at
grafana,
so
I'm
gonna
spend
the
summer
mainly
focusing
on
accessibility
issues,
I'm
also
in
the
user
essentials
squad.
F
A
That's
nice.
We
have
quite
a
bit
yeah,
I
I
did
I'm
in
berlin.
I
didn't
say
that
berlin,
germany
yeah,
but
so
the
idea
was
to
introduce
a
little
bit
about
what
the
plans
platform
is
up
to
because
yeah
also,
we
have
some
packing
developers
here
and
maybe
you
can
give
us
some
input
and
you
can
discuss
some
things
but
I'll
leave
that
that's
for
martin's,
facebook
who
knows
better.
C
Yeah
I
actually
gonna
share
on
an
issue
with
you
guys.
I
don't
know
if
you
marcus
olson,
can
bring
that
up
or
share
that.
So
we
are
kind
of
we're.
Gonna
have
had
like
a
couple
of
weeks
as
a
squad
together,
but
our
main
focus
is
basically
focusing
on
the
developer
experience
when
it
comes
to
extending
and
building
plugins
for
rafana.
C
Which
is
an
an
area
where
we
have
lots
of
potential
and
lots
of
great
ideas
on
how
we're
going
to
be
making
the
death
experience
even
better
and
hopefully
adding
more
cool
apis
and
possibilities
to
in
the
future,
to
let
people
like
you
mikael
extend
rafana.
C
So
if
you
have
a
look
at
this,
so
we
have
published
a
roadmap
issue
containing
some
of
the
things
that
we
are
planning
to
focus
on
both
short
term
and
long
term,
so
short
term
for
grafana
8.1
9.2.
C
We
are
actually
taking
one
of
the
projects
that
marcus
olson
introduced,
which
was
called
the
plugins
catalog
or
the
plugins
marketplace,
and
we
are
bringing
that
one
into
grafana
core
with
the
goal
to
replace
some
of
the
grafana
core
plugin
management
features,
and
one
of
the
pretty
cool
new
features
is
that
you
can
install
upgrade
and
uninstall
plugins
directly
in
grafana,
without
needing
to
restart
or
without
using
any
cli,
which
is
a
pretty
cool
new
feature.
C
C
There
is
yeah
there,
basically
is
a
need
for
for
get
a
guide
with
some
easy
steps
on
how
you
can
make
your
plug-in
profana
8
compatible,
and
so
that's
also
something
that
we
are
aiming
to
release
pretty
soon
and
I
think
for
8.2.
C
C
And
if
we
talk
a
little
bit
long
term,
we
so
historically
we
have
been
kind
of
bad
when
it
comes
to
introduce
breaking
changes
in
the
plugins
apis.
C
That's
something
that
we
gonna
focus
on
want
to
change.
We
want
to
have
much
more
stable
apis
and
we
want
to
make
it
easier
to
go
between
different
kupana
versions
and
support
multiple
final
versions
when
you
develop
a
plugin
and
we
also
have
ideas
around
providing
way,
much
better
documentation,
especially
for
developers.
C
So
it's
going
to
be
easier
to
know
what
parts
of
the
api
you
can
use
for
what
kind
of
plugins,
and
hopefully
we
can
provide
a
bunch
of
starter
templates
that
can
help
developers
us
like
a
starting
point
or
as
as
examples
for
how
we
can
build
different
things.
I
know
that
we
we
have
a
couple
of
things
like
that,
but
we're
we're
looking
into
improving
those
we're
also
talking
about,
have
talked
about
making
it
easier
for
plug-in
developers
to
wire
up
their
plug-in
to
our
ci.
C
So
we
haven't
really
decided
how
we're
going
to
do
that.
But
there's
been
talk
about
maybe
publish
github
actions,
so
you
easily
can
set
up
like
building
testing
signing
and
publishing
plugins
internet
internationalization
is
one
thing
that
we
are.
C
Bringing
to
grafana
as
a
product
and
such
also
to
the
to
the
plugins.
So
if
you
want
to
have
a
plugin
that
supports
multiple
languages,
that
should
be
easy
to
do
what
else
jack
have
I
missed
anything.
D
C
Yeah
and
one
thing
that
we
that
I
haven't
mentioned,
that
we
are
also
going
to
look
into
is
the
the
current
group
on
a
toolkit.
We
know
that
it
can't
be
a
challenge
to
to
to
use
the
toolkit
in
between
grafana
versions.
So
that's
also
something
that
we
we
want
to
improve
and
make
it
easier
to
use.
G
So
I
have
a
question,
or
you
mentioned,
that
there
you're
working
on
publishing
a
plug-in
migration
guide
right
from
upgrading
plugins
from
seven
to
eight.
Is
there
any
major
things
that
you
can
think
of
right
now
that
you
know
you
can
share?
If
someone
is
built,
they
have
published
a
plugin
for
7.5
and
they're
looking
to
migrate
it
to
8.0.
Is
there
like
a
a
big
thing?
They
need
to
take
into
account
or
something
they
should
be
aware
of
already
before
the
migration
guide
is
already
here.
C
So
the
tricky
thing
that
it
depends
so
yeah
it
depends
on
the
state
of
your
plugin.
So
in
grafana
8
we
dropped
the
support
for
the
a
deprecated
backend
api
for
plugins.
C
So
if
you
have
a
plugin
that
you
have
built
on
the
apis
prior
to
not
really
sure
when
doing
to
do
it,
but
seven
something
and
then
you
potentially
need
to
upgrade
the
whole
backend
structure
and
use
the
the
new
go
sdk,
we
are
still
supporting
angler
when
it
comes
to
the
front
end
and
player
editors
and
those
things.
So
that
should
be
fine.
You
can
like
bare
minimum
would
basically
be
to
upgrade
the
back-end
code
and
we'll
also
have
introduced
a
new,
a
new
data
format
called
data
frames.
C
G
I
guess
the
the
first
thing
to
do
is
just
to
try
to
install
it
on
grafana
8
and
see
if
it
still
runs
and
take
it
from
there.
C
Yeah
yeah
exactly
and
if
you
run
into
any
troubles,
I
think
there
are
a
couple
of
issues
open
on
github,
where
people
have
the
that
people
have
found
in
running
two
different
problems.
So
I
think
there's
plenty
of
help
to
to
to
find
on
github.
G
So
I
know
that
there's
a
lot
of
people
that
are
are
really
excited
about
app
plugins
out
there.
Is
there
anything
that
we're
scheduling
or
or
planning
to
do
for
app
plugins
at
all
right
now
where
we
we
we,
for
example,
don't
have
a
tutorial
for
how
to
write
applicants,
so
many
people
struggle
when
they
want
to
write
their
first
one.
Is
there
something
that
we
can
say
to
them,
or
is
there
something
that's
happening
right
now?
Any
big
changes
coming.
D
I'm
not
aware
of
any
major
changes
that
are
coming.
One
thing
that
we
are
planning
that
marcus
mentioned
is
to
create
example,
like
more
examples
like
get
that
can
showcase
the
various
like
features
that
plug-in
developers
can
tap
into.
D
For
example,
in
in
grafana
8,
we
released
the
react
routing,
which
makes
it
a
much
easier
task
for
you
to
actually
to
implement
routing
within
your
app
plugin,
but
right
now
we
need
to
give
that
more
exposure.
So
these
these
ideas
around
the
examples
starters
is
probably
our
first
step
towards
answering
your
question.
Markus.
C
C
But
apart
from
that,
I
don't
think
we
have
anything
planned.
We
have
a
bunch
of
requests
regarding
app
plugins
things
like
being
able
to
extend
the
different
menus
in
grafana,
like
from
everything
like
the
main
navigation
to
be
able
to
add
menu
items
in
like,
for
example,
in
a
in
the
panel
menu.
C
C
Also
one
of
the
like
you
asked
about
the
tutorials
or
or
something
for
apple,
and
so
today
we
have.
We
have
the
storybook.
We
have
an
audio
narrated
api
like
reference
guide,
we
have
a
bunch
of
tutorials
and
we
have
a
lot
of
documentation
or
not-
maybe
not
a
lot,
but
we
have
documentation
that
is
more
focused
against
the
developer
community
and
how
you
can
develop
plugins
and
extend
grafana,
and
we
have
had
some
discussions
about.
G
Awesome,
I
I
remembers
as
well
that
I
don't
know
if
you,
if
you
mentioned
it,
but
when
you
talked
about
the
plug-in
catalog,
you
mentioned
that
we're
gonna
make
a
lot
of
you
know,
changes
to
you
know
installing
and
uninstalling
and
managing
plugins
from
within
grafana,
but
I
believe
that
it's
already
available
right.
So
it's
not
enabled
by
default.
G
C
But
there's
there's
a
you
just
need
to
enable
it
in
your
in
your
configuration,
and
you
can
play
around
with
this
feature
today.
D
D
So
I
think
I
I
think
eventually
it
will
probably
become
the
default,
but
we
we've
got
it
behind
a
feature
flag,
because
we
have
a
lot
of
ux
improvements
that
we
want
to
make.
G
I
think
something
that
also
needs
to
be
mentioned
is
that
it's
a
you
know
a
security
aspect
to
it
as
well,
because
you
know
you're
allowing
people
to
install
plugins
with
you
know
through
the
ui,
rather
than
install
being,
you
know,
logging
into
the
server
installing
them
from
there,
so
we
we
also
want
to
make
sure
that
we
feel
confident
about
that,
and
you
know
before
we
enable
it
by
default.
H
H
My
example
I
saw
that
there
are
a
couple
of
people
who
is
actually
doing
that
they
totally
change
the
grafana,
so
you
don't
have
explore
you,
don't
have
plus
buttons
on
your
left
side
menu.
You
have
your
own
application
buttons,
your
site
menus.
So
it's
totally
so
it
looks
totally
different
right.
So
it's
not
it's.
This
is
the
idea
to
use
a
grafana
as
a
platform,
not
just
as
what
it
is
right
now.
So
what
is
what
is
on
your
roadmap.
C
C
Yeah,
I
I
understand
we
haven't
talked
about
something
like
that,
but
we
like
we
would
like
feedback
feedback
like
that.
So
if
you,
if
that's
something
that
you
want
like,
please
jump
into
the
to
the
issue
that
marcus
is
presenting
and
like
write
a
comment
about
it.
C
A
C
A
Sorry,
like
in
terms
of
navigation,
that
you
were
mentioning
like
showing
certain
icons
or
showing
those
so
deciding
which
ones
show
there.
That's
actually
something
that
we
because
we're
starting
a
new
navigational
project
and
it's
something
that
we
may
explore.
Like
the
possibility
of
rearranging
what
shows
in
your
navbar
and
what
you
know.
I
mean
still
like
super
early
stage,
and
this
is
just
one
of
the
multiple
hypothesis
of
the
weekend
that
we
have.
But
it
could.
H
G
Are
you
saying
something
like
you
know,
embedding
certain
just
a
few
panels,
or
so
it's
not
just
a
theming
issue
right
based
on
what
you're
saying
it's
not
about
just
changing
a
css
you're
asking
for
something
more.
You
know
I
only
want
to
you
know,
show
two
panels
and
no
menus.
No
nothing
right
is
that
what
you're
saying
yeah
so.
H
We
can
go
as
a
like
a
bootstrap
or
you
like
and
react
itself
right.
You
can
have
you,
you
can
start
from
scratch
and
then
you
can
add
what
you
need
right
for
your
application,
because
right
now,
what
if
you
create
something
on
grafana?
It's
still
going
to
look
like
grafana
like
a
base
in
grafana,
but
you
want.
But
if
you
want
to
have
it
as
a
platform
you
can,
you
should
be
able
to
remove
everything
which
is
grafana
and
just
keep
what
you
need.
F
F
H
I
mean
you
still
can
have
a
plugin
right
which
is
registered
on
your
left
side
with
your
dashboard.
So
I
mean
you
can
still
use
everything.
What
graphana
provides.
You
know,
authentication
all
kind
of
panels,
components
everything,
but
it's,
but
it
should
look
different
than
grafana
itself
and
we
still
some
community
members
already
did.
I
can
provide
a
couple
of
links
later
on
to
show
actually
how
what
they
created.
G
So
I'm
thinking,
couldn't
you
do
that
already,
if
you,
if
you
built
a
app
plugin
for
example,
and
it
just
enabled
like
a
kiosk
mode,
so
then
you
have
total
control
over
the
the
you
know
the
the
whole
area.
Basically,
and
then
you
can
theme
it.
However,
you
want
in
your
your
app
plugin
and
then
you
could
use
the
the
components
from
you
know
the
storybook
and
the
ui
packages,
but
that
would
you
know
that
would
mean
that
you
would
have
to
write
your
own
app
plug-in
in
order
to
do
that.
H
Right,
but
how
are
you
going
to
deploy
it?
I
mean
my
idea
is
that
I
have
this
application
right.
I
want
to
be
easily
deployed
by
end
users
and
when
they
start
the
application.
This
is
what
they
will
see.
Only
my
application,
only
my
app
plugin
right
right
now
they
see
the
grafana
with
everything
grafana
provides.
They
have
to
install
my
application,
for
example,
and
then
they
go
from
there,
but
I
mean
I
just
want
this
simulator
experience.
They
install
it
and
they're
already
in
this
special
plug-in
application.
G
H
Yeah,
I
see
what
you
mean.
This
is
what
ryan
mckinley
talked
some
time
ago.
We
discussed
that,
and
this
is
what
I
think
some
of
the
platform
team
was
doing,
but
I
think
ux
have
to
be
involved
in
that
and
I
think
it's
a
great
idea
that
you
can
actually
have
your
publication
plugins
and
if
you
are
doing
iot
different
use
cases.
This
is
what
you
need
right.
You
just
install
it
and
you
see
what
it
is.
H
C
We
we
did
a
hacked
project
that
maybe
would
enable
this
somewhat,
but
then
you
would
need
to
embed
rafana
in
another
application,
but.
C
We
basically
did
something
that
we
called
display
profiles.
I
think
we
call
it
write
your
chin,
so
that
basically
gives
the
user
the
possibility
to
set
up
a
profile
where
you
can
hide
like
menu
the
time
controls
and
like
you
can
basically
customize
what
part
of
the
grafana
interface
that
you
want
to
be
on
to
show
for
the
user
and
what
not.
C
C
But
this
this
would
probably
this
in
combination
with
impending
your
fauna
in
an
application,
would
basically
end
up
with
what
your
what
you
were
asking
for
in
the
pr
we.
Basically,
we
implemented
something
that
we
we
use
the
display
profile
to
implement
something
that
we
called
like
we
custom
kiosk
mode,
so
we
re-implemented
the
whole
kiosk
mode
with
the
display
profiles
and
also
added
something
that
we
called
a
just
mode
that
basically
left
the
user
to
control.
What.
C
So
exactly
so
that
was
something
that
we
did
during
a
hackathon.
I
think
it's
two
weeks
ago
or
something.
H
C
G
Well,
I
I
think
it's
up
to
each
team.
You
know
if
the
team
wants
to
to
to
tell
the
world
about
it,
it's
a
it's
totally
up
to
them.
A
lot
of
you
know,
projects
done
during
the
hackathon
are
just
you
know,
fun
stuff.
They
just
want
to
experiment
and
don't
intend
to
share
it.
Some
some
projects
will
end
up
in
the
public
sphere,
but
might
not
end
up
in
grafana,
so
it's
totally
up
to
the
developers
whether
they
want
to
share
it
or
not.
G
It's
not
like
you
know,
there's
no
nda
on
this.
You
know
they're
they're,
very
free
to
share
their
projects
with
the.
H
H
C
H
A
H
I
just
updated
one
of
the
data
sources
to
the
latest
version
and
the
rxjs
was
updated
as
a
part
of
it,
and
there
was
a
couple
of
things
we
cannot
fix
without
graffana
updating
to
it.
So
I
have
to
use
a
older
version,
but
I
mean
there
are
like
different
changes.
Different
things
will
change.
There
is
no
two
promise
anymore
and
you
have
to
get
the
first,
the
last
value,
and
there
are
some
types,
but
I
mean
not
nothing.
For
me.
C
That,
hopefully
soon
do
you
have
any
other
feedback
or
or
thoughts
regarding
building
plugins.
C
H
Marcus
already
mentioned
that
I
was
looking
for
application
plugins,
because
I
was
the
first
one
who
actually
developed
it
to
the
state
state
when
it's
working
state
and
it's
really
hard
to
find
and
are
helping
the
community
as
much
they
can,
because
it's
really
hard
to
find
good
examples.
Synthetic
monitoring
up.
It's
not
it's,
not
a
good
example,
actually
to
look
for,
but
still
I
haven't
done
this
routing,
which
was
implemented
recently.
H
So
I
I
can
look
into
that
and
do
back
back
and
back
engineering,
but
it
will
be
great
to
see
the
tutorial
how
to
do
it
properly
and
it
will
be
great
to
actually,
as
you
said,
the
immigration.
It's
it's
a
big
thing,
so
the
radius
data
source,
plugins
and
applications
they
supported
grafana
7..
Now
when
we
moved
to
grafana
8,
I
just
said
that:
okay,
everything
is
based
on
graphon
8.
H
Now,
because
we
don't
support
the
latest
version
won't
support
graphana
7,
because
there
are
so
many
things
was
changed
with
the
graph
panels.
If
you're
working
with
a
not
specific,
this
is
general
things,
it
all
works.
If
you
started
to
do
more
specific
components,
your
custom
panels,
this
is
what
breaking
really
hard,
so
I
hope
it
won't
break
in
the
future
versions,
like
that,
it's
same
with
the
data
source
as
the
with
the
dashboards.
H
The
problem
is
that
when
you
introduce
new
panels
like
time
series
panel
replace
graph
panel,
there
is
no
life
cycle
for
the
dashboards
right,
so
you
kind
of
have
to
include
dashboards
for
graphs
and
time
set
at
the
same
time,
but
it
will
be
great
actually
to
introduce
to
display
different
dashboards
based
on
the
version
in
as
a
part
of
the
left
side
menu.
For
example,.
H
And
enterprise
customers
are
not
that
fast
as
open
source
customers.
So
if
there
are
multiple
enterprise
customers
who
use
radius
applications
who
are
still
using
version,
seven,
two
or
seven
three,
and
I
have
no
idea-
when's
upgraded
to
version
eight,
but
still
I
kind
of
have
to
break
it
and
start
to
work
on
graph
support.
Grafana
eight.
Only
because
you
cannot
support
both
version
because
of
the
theme
increase,
changed
time
series
panels.
As
I
said,
and
different
different
things.
C
D
I
think
I
mean
we've
discussed
ideas
around
building
out
these
examples
for
separate,
like
various
features
that
you
can,
you
can
like
easily
focus
on
how
to
achieve
that.
One
thing,
rather
than
being
given
like
a
huge
starter,
app
that
you
just
can't
you've
got
to
like
wade
through
one
one.
Other
idea
we
have
around
this
is
that
we
can
also
use
them
for
testing.
D
We
can
use
these
examples
to
help
us
prevent
those
breaking
changes
which,
like
your
example,
the
theming
that
that
that
can
be
really
problematic
if
you're
trying
to
support
multiple
versions
in
a
single
plugin,
so
yeah
that
that's
that's
our
thinking
behind
it,
but
if
you've
got
any
input
or
ideas,
we
would
love
to
have
them
as
well.
H
Also
before
I
recently
found
the
problem
with
the
versioning
itself,
if
I
have
a
application
plugin
and
my
application
plugin
depends
on
the
data
source
and
I
said
that
I
want
to
have
the
latest
version
of
the
data
source
by
my
application.
Plugin,
it
doesn't
work,
so
it's
kind
of
this
very
even
versioning
broke.
So
I
have
we
have
to
release
a
new
version
of
application
plug-in,
so
it
can
install
latest
version
of
data
source.
H
If,
if
somebody
can
take
a
look
into
this,
versioning
in
package.json
will
be
great,
and
I
don't
remember
if
I
opened
the
issue
actually,
maybe
I
have
to.
G
H
Right
and
less
breaking
changes,
because
I
remember
there
was
a
latest
beta
which
introduced
breaking
change
that
you
have.
You
should
have,
I
think,
ref
id
as
a
part
of
your
query,
which
was
not
required
anymore
and
then,
when
grafana
8
was
released,
the
three
of
ideas
became
mandatory
right.
There
is
a
I
mean
there
is
a
kind
of
one
week
was
before
the
last
batter,
which
includes
breaking
change
and
the
general
availability
release,
which
I
think
it's
not
enough
for
any
developers.
G
So,
from
your
perspective,
how
how
much
time
in
advance
would
you
be
expecting
if
we're
to
deprecate
an
an
api
or
or
a
function,
some
form
of
functionality?
How
many?
How
how
much
ahead
of
time
would
you
want
to
know
that,
and
how
would
you
want
to
know
that?
Are
you
reading
the
change
logs,
for
example,
for
for
grafana
versions,
or
is
there
any
other
place
your
you
would
be
looking
for?
G
You
know
upcoming
breaking
changes
so
say
because
we're
deprecating
things
you
know
we
we
realize
there
is
better
things
to
better
ways
to
do
things
on,
and
so
we
we
kind
of
need
to
deprecate
things
eventually.
But
how
would
you
want
to
be
notified
of
of
those
changes
and
how
much
time
would
you
need
to
to
make
that
change.
H
G
That's
impressive,
but
I
don't
think
that
we
should
expect
that
every
plug-in
author
does
that
I
think
you're
exceptional.
That
way.
H
Right,
every
plugin.
What
I
have
I
test
on
the
master
release
all
the
time
when
I
finish
something
on
the
current
latest,
I
do
it
on
master
domain,
but
at
the
same
time
I
mean,
I
think
one
month
is
good
enough
from
one
to
three
months
at
least
or
a
couple
of
releases
will
be
good,
but
still
I
mean
not
all
the
changes
kind
of
developer
can
see
as
a
breaking
change,
for
example,
this
ref
id,
which
is
required
lately
right.
H
So
it
was
changed,
probably
because
it's
not
required,
but
the
problem
is
the
way
how
it
works.
It's
kind
of
it's
required
and
this
query
was
not
executed
anymore,
so
you
kind
of
have
to
troubleshoot
why
it's
not
working,
and
it
was
changed
last
minute,
so
kind
of
duplication
of
api.
It
will
take
a
version
or
two
right
and
there
was
cases
for
that.
It's
totally
understandable,
but
still
the
changes
in
the
code.
They
have
to
be
properly
validated.
Who
is
using
that?
How
and
what
can
be?
What
happened
with
it?
G
Yeah
we
I
I
know
we
have
discussed.
You
know
whether
we
want
to
have
a
set
of
plugins
that
we
we
actually
build
for
every
version
to
make
sure
that
they're
still
working.
You
know
obviously
there's
a
few
plugins
that
a
lot
of
people
use
and
they
I
think
that
they're
great
examples
for
how
plugins
should
be
built.
So
we
we
kind
of
want
to
start
testing
them
even
more
than
we
have
in
the
past.
Of
course,
we
we
can't.
We
can't
test
every
plug-in,
that's
out
there.
G
Of
course
we
would
want
to,
but
you
know
that
would
require
us
to
to.
You
know
continuously
build
every
version
of
that
plug-in,
and
you
know
I.
I
don't
think
that's
realistic
at
this
point,
but
you
know
it's
a
very
good
point
of
you
know
actually
trying
to
build
some
of
our
community
plugins
as
well.
G
We
we
have,
since
the
I
believe,
the
the
last
two
versions.
We,
we
are
running
now
test
environments
with
the
most
popular
plug-ins
and
for
every
new
release.
We
go
through
them
and
make
sure
they
are
still
working.
G
H
G
So
I'm
kind
of
curious
about
the
developer
portal.
Is
there
anything
more?
You
can
say
that?
Is
there
any
you
know
anything
more
you
can
share
in
terms
of
how
will
how
would
it
look
like
what
kind
of
documentation
would
be
expect
to
see
there
and
you
know,
is
there
a
time
frame?
D
I'm
not
sure
about
a
time
frame.
I
know
it's
pretty.
I
know
it's
a
pretty
early
stages
right
now.
I
think
it
comes
from
and
it's
come
from
internal
conversations
around,
like
discoverability
of
certain
things
in
our
in
our
current
docs,
particularly,
I
think
a
lot
of
developers
struggle
a
bit
with
the
way
our
types
are
documented
and
searching
or
trying
to
find
those.
It's
quite
problematic
right
now,
I
believe
so
yeah.
D
C
No
I'll
hop
on
the
only
thing
that
I
know
for
sure
marcus
is
that
you
will
be
included.
C
Thank
you.
So
when
we
start
to
look
into
this
a
little
more
details,
you
will
definitely
be
involved
and
probably
a
bunch
of
other
people,
but
I
I
think
the
idea,
I'm
not
sure
it
was
you
or
ryan
or
someone
else
who
you
know
mentioned
it,
but
current
documentations.
C
C
So
when
they
search-
and
they
end
up
in
like
code
definition
documentation,
it's
kind
of
it,
it
will
bring
a
bad
experience
to
them,
but
the
other
it
also
basically
can
be
done
around
like
people
that
want
to
develop
a
plugin,
I'm
looking
for,
like
really
technical
stuff,
you
end
up
in
a
more.
C
G
G
It's
just
not
discoverable
from
one
single
place,
and
I
think
that's
that
sounds
like
what
we're
trying
to
improve
with
the
developer
portal.
Yep.
H
D
H
Right
and
if
you're
going
to
create
this
kind
of
project
with
documentation
for
developers,
it
will
be
great
to
have
like
a
change
log.
What
actually
was
changed
and
to
notify
if
you
can
have
like
a
developer
mail
list
and
notify
everyone?
Oh
it's
what
we
changed
recently,
for
example,
because
I
mean
I
looked
in
documentation
a
year
ago
almost
a
year
ago,
and
now,
when
I
look
for
it
against
something,
I'm
kind
of
writing
an
article,
I'm
looking
at
your
documentation.
H
D
G
I
think
me
personally,
I
I
go
to
the
storybook
to
see
what's
what's
available,
but
in
order
for
me
to
realize
how
to
use
it,
I
go
to
the
repository
because
a
lot
of
the
components
in
the
storybook
they're
they're
meant
to
to
to
demonstrate
how
it
looks
like.
But
when
you
look
at
how
you
know,
I
don't
know
what
the
term
is.
Is
it
the
action
now
the
the
story?
G
Then
it's
like
encapsulated,
so
you
don't
actually
see
how
you
use
that
component,
and
so
so,
usually
you'd
have
to
go
to
the
repository
and
find
that
specific
component
to
see
what
properties
it
supports.
H
G
So
I
mean
you're
maintaining
now
what
is
it
four,
five
plugins?
How
do
you
you
know?
How
do
you,
how
do
you
version
them
when
you
like,
when
a
new
version
of
grafana
comes
out?
How
do
you
make
sure
to
keep
compatibility?
You
mentioned
that
you're
you're.
Now
you
need
to
release
a
new
version
of
the
the
plugin
and
that
won't
work
on
previous
versions
of
grafana
right.
H
If
you're
talking
about
radius
plugins
three
of
them,
so
what
I
did,
I
released
the
reverse
version,
one
of
plugins,
which
supports
grafana
7,
and
when
I
realized
that
application
plug-ins
there
was
so
many
things
was
changed.
I
just
moved
them
to
graphana
8
called
the
version
2..
Then
they
support
only
version
8..
If
you
want
to
version
graphana
7
right
go
to
previous
version
for
the
data
source,
there
is
not
a
lot
of
things
was
changing
the
data
source,
so
it's
still
compatible.
H
H
H
H
H
I
think
so,
and
the
dashboards
itself
you
have
to
change
dashboards,
but
eventually
everybody
will
go
there
and
I
think,
and
my
plans
is
I'm
going
to
use
more
custom
panels
and
time
series
panels
was
very
crucial
for
me
to
use
it
so
because
the
graph
panel
I
used
before
it's
not
totally
not
supported
anymore.
There
is
no
tooltips.
There
is
nothing.
So
it's
why
I
just
migrated.
F1
8
variables
changed.
H
There
are
so
many
things
actually
changed
between
seven
and
eight
and
it's
really
hard
to
spot
with
issues
until
you
kind
of
do
it
manually
I
mean
even
I
have
a
ci
which
works
all
the
time.
Is
there
still
many
things
you
cannot
see?
I
properly
have
to
kind
of
do
it
manually
and
I
have
three
three
or
four
projects
actually
based
on
radius
plugins,
which
basic
different
technologies,
and
they
have
to
be
great
as
well
with
them
dashboards.
G
Well,
thank
you
so
much
for
sharing
all
that.
It's
it's
really
great
to
to
hear
that
from
you
know
in
the
grafana
team,
even
though
we're
building
the
the
the
plug-in
platform
there,
you
know.
Obviously
you
know
the
community
is
writing
and
building
so
many
plugins
that
you
know
in
a
way
you're.
You
know
there's
more
than
we
do
or
or
you
have
more
experience
about
what
the
the
challenges
are,
and
you
know,
as
we've
heard
now,
just
just
now,
there's
a
ton
of
things
we
can
learn
from
this.
G
So
thank
you
very
much
we're
coming
up
on
the
you
know
the
hour
here.
So
we're
about
to
end
this
community
call.
Is
there
any
final
questions
or
comments
you
should
make
to
anyone.
G
G
So
if
you're
interested
in
that,
please
join
us
and
thank
you
again
see
you
next
time.
Thank
you
very.
G
So
you
just
joined
at
the
end
of
the
the
community
call,
so
everyone
just
left.
Unfortunately,
did
you
get
the
hour
wrong?
Maybe.
G
That's
that's!
Okay,
if
not
so
the
the
the
the
community
call
was
recorded.
So
we
will
upload
this
to
youtube
as
soon
as
we
can
so
you'll
be
able
to
watch
the
recording
over
there.