►
From YouTube: Grafana Community Call 2020-11-19
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
A
And,
of
course,
that
is
not
obvious
what
that
means.
So
I
would
like
to
spend
this
call
to
you
know,
walk
through
what
what
that
means
and
how
to
do
it.
Basically,
so
let's
see
if
I
can
open
up
the
tabs
again
so
to
start
off
with,
there
is
some
documentation
on
this.
A
So
if
you
go
to
grafana
I'll
post,
these
links
in
the
in
the
chat
as
soon
as
I
I
get
them.
So
we
do
have
a
documentation
page
here.
A
I
I
posted
it
in
the
chat.
So
that's
how
you
sign
a
plugin
and
we're
also
going
to
look
at
how
to
package
a
plugin
that
you
can
find
here
as
well.
So
I
was
thinking
that
we
could
walk
through
how
to
do
these
two
tasks
and
I'm
going
to
use
a
a
plug-in
of
mine.
A
So,
let's
see
if
I
can
share
my
screen,
I
hope
you
can
all
see
my
my
my
chrome,
tab
or
chrome
browser
right
now.
So
I
have.
A
If
you
go
to
github.com
marcus
olsen,
I
have
a
few
plugins
on
my
account
that
are
all
signed
and
packaged
according
to
the
documentation.
So
if
you
have,
you
know,
if
you
want
to
look
at
examples
of
of
what
it
looks
like
when
you're
done
feel
free
to
check
them
out,
I'm
going
to
make
a
signed
and
packaged
plugin
out
of
this
json
api
data
source.
A
A
So
you
should
be
seeing
my
vs
code
window
here.
If
not,
then
let
me
know
so.
I
have
my
plugins
here.
Let's
remove
this
one
for
now.
A
You
don't
have
to
to
do
this,
but
if
you
want
to
publish
on
grafana.com,
you
will
have
to
have
a
a
public
repository
with
this,
and
the
first
thing
we'll
need
to
do
is
that
we
need
to
build
our
plugin.
So
first
thing
is:
you
know,
yarn
build.
A
What
happens
is
when
you
run
this
command
yarn
build
is
that
it
starts
building
your
front
end
assets
and
when
we
do
that,
eventually
it's
going
to
create
a
little
directory
in
our
plugin
directory,
which
is
called
dist
and
to
those
of
you
who
have
been
developing
plugins
in
the
past.
You
know
that
this
is
something
you
would
have
to
check
into
github
and
we
would
need
that
the
commit
of
that
dist.
You
know
the
the
commit
shaw
of
that
dist
folder.
This
is
not.
A
This
is
something
that
you
don't
need
to
do
anymore,
so
you
won't
ever
need
to
check
in
your
disk
directory
again.
I
know
there's
a
lot
of
you
who
are
excited
about
that,
because
it's
something
that
has
been
error
prone
in
the
past.
A
So
when
you
build
your
plugin,
you
end
up
with
this
disk
directory
with
all
the
build
front,
end
assets
with
a
bunch
of
other
things
like
your
readme
and
your
images
and
your
plugin.json
file.
So
when
you
want
to
sign
your
plugin,
then
you
need
to
go
through
a
few
steps.
A
So
if
you
look
in
the
the
sign
a
plugin
documentation,
you
see
that
they
differ
a
little
bit
between
whether
you
want
to
sign
a
public
plugin
or
you
want
to
sign
a
private
plugin.
So
today,
we'll
walk
through
how
to
sign
a
public
plugin,
but
hopefully
the
the
documentation
for
private
plug-ins
shouldn't
be
too
difficult.
A
A
So
if
you
have
a
subscription
a
plug-in
subscription
with
grafana
labs,
then
that
should
already
be
fixed
for
you.
But
if
you
are
interested
in
getting
one
of
those,
then
please,
you
know,
send
an
email
to
the
address
in
the
in
the
documentation.
I
believe
it's
plugins
grafana.com,
if
you
wish
to
start
developing
a
community
plugin,
send
an
email
to
plugins.grafana.com
telling
us
what
what
plugin
id
you
want
to
start
signing-
and
you
know
that
is
the
community
signature
level.
If
you
wish
to
publish
this
on
graphana.com.
A
A
So
the
next
step
is
that
I
want
to
you
know
log
in
to
grafana.com,
and
I
want
to
create
an
api
key
and
if
you
log
in
to
grafana.com
and
to
the
left
in
the
sidebar,
you
will
see
a
section
that
says
api
keys
and
if
you
click
that
it
will
pop
up
a
little
button
to
the
right
that
says,
add
api
key
and
once
you
do
that
you
will
have
a
little
a
window
pop
up.
A
That
will
ask
you
to
name
it,
and
it's
important
that
in
that
little
drop
down
that
you
will
see
there
not
sure
if
you're
all
logging
in
and
trying
this
yourself
right
now,
but
then
you
will
have
a
little
drop
down
that
says,
roll
and
make
sure
to
select
plug-in
publisher
from
that
drop
down
and
create
a
new
api
key.
A
So,
let's
see,
if
we
can
did,
I
think
we
can
do
that
right
now.
A
A
So
let's
see
if
I
can
go
back
to
just
here
to
code
here-
and
I
will
export
this
like
that-
and
I
will
run
a
command
that
is
plugin
colon
sign
and
when
I
do
this
should
say
sign
successfully.
A
I
want
you
to
know
that
I'm
deleting
the
api
key
right
now,
so
if
we
do
this
again
or
so,
you're
not
yeah,
so
so
this
won't
work
again,
but
so,
when
you're
watching
this
in
the
recording
of
this,
this
api
key
will
not
be
no
more
but
yeah.
So
it's
signed
successfully.
What
happened
now
is
that
we
now
see
another
file
in
our
disk
directory,
which
is
manifest.txt,
and
it
contains
a
bunch
of
information
here.
A
So
this
is
basically
a
list
of
all
the
the
the
files
that
you've
you've
confirmed
is
part
of
your
plugin.
So
if
someone
tries
to
load
your
plugin,
but
while
it
contains
anything
else
in
this
or
if
the
file
differs
from
what
is
currently
in
the
the
manifest,
then
grafana
will
complain
and
says
that
this
signature
is
has
been
modified
and
we
won't
load
it.
A
So
so
that's
basically
the
manifest.
Ideally
you
don't
have
to
really
care
about
this.
That
much
you
should
just
run
the
plug-in
sign
command,
and
so
that's
really
all
there
is
to
signing.
A
The
next
step
is
to
package
this
plugin,
which
is
basically
taking
this
disk
directory
and
moving
it
to
a
directory
or
renaming
the
directory
to
the
the
id
of
that
plugin.
So
in
my
case,
that's
marcus,
olsen
json
data
source.
If
I
do
that,
I
can
then
archive
this
by
creating
a
zip
file.
A
It's
called
062,
dot,
zip
and
then
we're
going
to
take
the
directory
that
we
just
created
or
renamed
and
then
minus
r
to
start
doing
this
recursively.
A
So
that
has
created
now
a
zip
archive
containing
the
contents
of
the
disk
directory,
and
that
is
your
package
plugin.
A
So
what
what
I've
done
here
is
that
I've
created
a
my
pass
release:
zero
six
one
has
a
zip
file
here
that
was
created
just
the
way
I
showed
you.
It
also
has
a
md
file
checksum
for
for
so
when,
when
you
submit
your
plugin
to
the
plugin
repository
for
publishing
into
graphone.com,
we
also
are
gonna
need
your
the
checksum
of
that
zip
archive.
A
So
we
know
that
we're
we're
uploading
the
right
one
and
that's
really
it
when
you
have
that
you
can
go
to,
and
some
of
you
are
already
are
familiar
with
this
process,
but
you
can
go
to
the
grafana
plugin
repository
and
in
this
repository
there
is
a
file
called
repo.json
and
to
that
file
you
should
add.
If
this
is
a
new
plugin,
you
should
add
this
file
called
or
sorry.
You
should
add
a
new
entry
to
the
file.
That
looks
something
like
this
and
so
in
this
url
field.
A
Here
you
paste
the
url
to
your
zip
file
and
then
the
md5
checksum
that
I
mentioned
earlier,
and
then
you
create
a
pull
request
and
what
happens
is
that
one
of
us
is
going
to
start
looking
and
reviewing
your
plugin.
We
will
install
it.
We
will
do
some
smoke
testing.
We
will
see
that
the
readme
works,
the
the
logos
are
showing
the
way
they
are.
A
You
know
nothing
is
breaking
so
see
if
yeah,
so
that's,
basically
what
we're
doing
when
we,
when
you
submit
a
a
plug-in
to
the
plug-in
repository
and
one
other
thing
that
I
wanted
to
mention,
is
that
once
you
have
that
this
zip
file,
this
hosted
zip
file,
then
you
can
go
to
this
plugin
validator
and
you
can
find
the
link
in
the
the
the
readme
for
the
github
repository
the
the
plugin
repository
on
github.
A
A
And
it
will
also
make
sure
that
the
the
the
structure
of
the
package
package
plug-in
is
correct,
that
it
has
a
correct
signature
and
a
few
other
things
so
make
sure
that
this
is
showing
green,
because
otherwise
we
won't
be
able
to
publish
it.
A
C
A
D
Hey
to
depends
on
what
type
of
plug-in
it
is.
If
it's
like
a
panel
plug-in,
then
it'll
be
on
sign,
I
think,
and
if
it's
a
back-end
plug-in,
then
it
won't
run.
D
Yeah,
the
developer
mode,
then
it'll
work
yeah.
If
it's,
if
it's
a
a
a
data
source
with
a
back-end
component,
then
yeah
you,
you
know
your
phone
won't
start
it'll,
say
it's
an
unsigned
plugin
and
if
it's
a
front-end
plug-in,
then
you'll
get
like
an
unsigned
flag
on
it.
In
nicaragua,
ui.
C
A
So
by
accept
you
mean
load
in
grafana
right.
Yes,
yes,
because
we
had
a
question
earlier
on
whether
you're
still
whether
we're
still
open
to
reviewing
and
publishing
unsigned
plugins,
and
to
to
that
the
question
is
no
we're
not
going
to
review
any
unsigned
plugins
at
this
point,
but
we
will
still
load
unsigned
plugins
until
what
did
you
say
january.
D
All
right,
zero
that
that's
not
set
in
stone,
maybe
we'll
push
out
even
further.
A
A
So
there's
a
question
on
virta
media
brown
eugene.
I
published
airplane
money,
so
I
have
on
my
so
it
looks
like.
E
Yes,
no,
I
log
it
in
my
personal
account,
but
previously
I
published
our
plugin
via
pull
request
only
and
I
don't
think
I
have
account
which
which
was
a
signet
with
readme
page
on
grafana.com
plugins.
So
I
I
need
more
information
about
how
I
can
assign
my
account
to
current
virta
media.
A
Plugin
so
yeah,
I
I
I
don't
know
about
inverted
media
specifically,
but
if
you're
you
want
to,
you
know,
use
your
personal
account.
I
believe
you
have
to
be
part
of
the
the
virta
media
organization.
E
Currently,
currently,
currently,
click
house
grafana
that
source
plugin,
it's
open
source,
community
maintenance-
and
I
just
currently
personal
maintainer
of
this
plugin
yeah,
and
so
it's
just
publisher,
yeah,
there's.
B
E
We
can
do
that:
okay,
daniel
okay,
how
I
can
communicate
with
you.
We
are
maybe
via
github
issues.
D
Yes,
you
could
do
that.
I
think
you
just
need
to
know
your
grafana
username
that
you
have
like
a
a.
E
Username,
do
you
do.
A
So
we
have
another
question:
when
requesting
a
signature
level
from
plugins
should
I
also
include
a
plugin
id
yes,
so
we
need
the
the
id
of
the
plugin
that
you
intend
to
sign,
as
well
as
the
level
that
you
intend
to
sign
it
under.
So
that
are
the
two
things
we
need.
A
We
also
need
you
to
have
a
graffana.com
account
so
and
the
the
the
account
you
know
so
so,
if
you've
published
plugins
in
the
past,
you
know
that
the
the
first
part
of
your
plugin
id
is
the
organization
that
owns
the
plugin,
so
that
plugin
needs
to
to
be
and
to
exist
as
well.
A
Can
a
single
api
key
be
used
to
assign
multiple
plugins?
I
believe
yes,
I
I
believe
that
if
you
have
a
single
organization,
you
can
create
one
api
key
and
sign
the
plugins
in
that
organization.
A
A
I'm
not
sure
exactly
what
information
that
gets
sent,
but
I
I
could
look
that
up
for
you.
D
A
That
that
sounds
reasonable,
so
yeah.
So
so
there's
going
to
be
information
about
you
know
the
files
in
your
plugin,
the
file
names
rather,
for
example,.
A
So
the
time
version
plugin
id
stuff
like
that.
A
D
A
Are
there
any
rate
limits
for
the
signing
api?
It's
a
good
question.
I
assume
there
is,
but
I
think
it's
probably
more
than
you
need.
Is
there
a
reason
you're
asking
do
you
intend
to
sign
a
lot.
A
Yes,
you,
you
can
totally.
Oh
good
point,
I
think
I
I
I
missed
showing
you
that
earlier
you
can
totally
sign
your
your
every
build.
If
you
want
to
pop,
I
can
show
you
something
that
I'm
using
for
my
own
plugins,
so
I
am
working
on
a
github
action.
So
if
you
go
to
one
of
my
my
plugins
here,
there
is
a
directory
called
github
workflows.
A
If
you
look
at
that,
there's
a
main.yaml
file
in
there.
That
is
basically
doing
all
the
things
that
I
showed
you
earlier.
So
yarn
build
your
plug-in
sign.
You
know
it's
using
the
grafana
api
from
as
a
secret
in
the
repository
it's
extracting
some
information,
it's
creating
a
zip
archive
just
the
way
I
showed
you
creating
the
md5
sum,
and
then
it
creates
a
github
release
and
uploads
the
zip
archive
as
a
res
release
asset
to
that.
A
So
the
only
thing
I
have
to
do
to
package
sign
and
package
is
to
push
a
tag
to
this
repository,
and
what
you
will
have,
then,
is
something
like
this.
A
If
we
check
this
out,
then
you
see
that
you
have
a
bunch
of
steps
here
and
in
the
end,
there's
a
step
right
now
where,
if
you
expand
this
publish
to
grafana.com,
you
can
get
the
the
entry
that
you
should
add
to
the
repo
dot
json
file.
A
So
it's
just
handy
that
way.
I
I
will
work
on
improving
this,
and
hopefully
we
can
get
this
published
to
the
github
marketplace.
At
some
point
I
know
mikhail
you,
you've
done
some
improvements
to
this
for
for
back-end
plug-ins
that
I
hope
that
we
can
start
incorporating
as
well.
Yes,
it's
important.
A
C
A
Yes,
I
yeah-
I
I
don't
yet
have
any
personal
back-end
plug-ins,
so
I
haven't
integrated
that
for
myself
yet,
but
we
will
definitely
look
at
that
for
an
official
github
action.
So
if,
if
you're,
maintaining
a
community
plug-in
on
github,
you
definitely
want
to
look
into
this.
You
can
use
this
github
workflow,
as
is,
if
you're
not
maintaining,
maintaining
a
back-end
plug-in.
I
believe
the
redis
repository
has
an
example
of.
E
E
C
Yeah,
it's
pretty
easy,
but
it's
very
convenient.
Actually
you
can
do
it
as
a
ci
pipeline.
So
when
you're
ready
to
release
right,
you
just
publish
it.
It's
great,
the
only
problem
that
when
you
actually
publish
the
release
with
it
it's
published,
there
is
no
description,
proper
description,
so
everybody
who
signed
to
your
repository
get
notified.
There
is
new
release,
but
the
description
is
empty
kind
of
it's
new
release.
You
don't
know
what
the
features
are.
Yeah,
it's
something.
Maybe
we
can
improve.
A
C
A
Yeah
good
point
yeah,
but
yeah
keep
working
on
that
yeah
go
on.
Okay,.
C
Just
let
us
know
when
you're
ready,
so
we
can
test
it.
I
have
actually
another
question
about
grafana
roadmap.
Is
it
something
you
can
share
with
the
community
because
there
is
releases
coming?
Some
of
them
was
not
stable,
like
recent
one,
seven,
three
one,
seven
thirty
two
with
this
issue
with
the
starts
so
because
we
started
to
use
it
in
production
already
as
data
source
and
grafana
in
in
different
instances.
D
Yeah
yeah
take
that
marcus
yeah,
please
yeah
so
yeah,
so
we're
working
on
the
roadmap
right
now
for
griffon8,
so
yeah,
hopefully
publishing
that
in
the
next
week
or
two,
but
I
think
you're
looking
for
something
more
specific
just
around
the
the
plug-ins
not
like
generally
for
all
of
grafana.
Is
that
right,
I'm.
C
I'm
looking
for
the
graph-
yes
like
grafana
roadmap,
that
in
a
month
we'll
have
this
version,
seven
three
right
733
after
that
we'll
do
seven
four
or
seven
five
and
then
we'll
do
like
version
eight.
So
we
can.
We
will
know
what
to
expect.
D
Yeah,
so
I
think
we
won't
be
doing
it
on
that
level.
So
seven,
three
three
is
a
patch
release,
so
that
is
much
more
like
depends
on
which
bugs
show
up
and
that
get
reported.
So
it's
it's
very
ad
hoc
and
the
process
there
is
that
once
we
have
enough
books
and
or
we
have
enough
serious
books,
if
you
have
one
serious
book
then
then
we
do
a
patch
release
and
we
try
to
do
as
few
batteries
as
possible
and
then
I
think
yeah.
D
We
will
do
it
at
a
higher
level
for
for
the
seven
or
four
days
which
is
going
to
be
in
start
of
february,
and
then
there
might
not
be
any
more
more
release
for
8.0,
so
that
would
be
like
in
may
june.
We'll
see
there
might
there
might
be
a
7.5
but
yeah
yeah,
the
the
there
it's
it's
almost
decided,
but
it
won't
be
super
detailed,
it's
more
like
it'll,
be
about
you
know,
20
or
30
or
headline
features
that
we're
working
on.
D
So
I
suppose
we
have
a
an
official
roadmap
if
you
look
at
ours,
so
there
are
products
as
well
for
open
source
grafana.
We
try
and
keep
it
sort
of
general
because
because
it's
open
source,
so
things
turn
up
so
having
sprints
and
things
is
really
hard
to
keep
if
you're
thinking
like
who
knows
like
which
external
pr
will
come
in
so
at
the
high
level.
D
Yes,
we
we,
we
do
know
what's
going
to
go
into
seven
or
four
and
what's
going
to
go
into
8.0,
but
at
the
low
level
it's
it
changes
a
lot
over
a
few
months.
C
Okay,
well,
I
mean
we
kind
of
have
the
same
strategy
for
radius.
I
mean
you,
never
know
what
is
going
to
be
there,
but
still
because
we
as
a
developers,
we
invest
a
lot
of
time
and
with
plugins
and
they
already
started
to
use.
So
I
just
want
to
know
what
reasons
have
to
test
and
kind
of
adjust.
My
time
right
with
your
new
releases.
D
C
D
There
there
is
like
the
very
low
level
planning.
Is
there?
If
you
look
at
the
milestones
in
github,
we
are
we
live
in
github.
That's
where
everything
is.
I
think
the
problem
is.
That
is
not
that
useful
to
someone
who's,
not
working
on
grafana,
it's
so
low
level.
It's
hard
to
see
the
the
the
forest
for
the
trees,
which
is
why
I'd
like
to
provide
something.
That's
a
bit
more
high
level.
A
Yeah,
I
it's
it's
still
in
process.
It's
been
paused
in
favor
of
a
plug-in
signing.
Unfortunately,
I
hope
to
continue
working
on
it
in
the
coming
couple
of
weeks.
I
hope
we
do
have
some
pros
progress
on
the
starter
repository,
so
we
I
know
that
the
one
of
our
teams
have
been
working
on
improving
that
a
bit,
so
you
should
have
seen
some
some
changes
to
that
repository.
I
think
that
you
have
the
link
to
it
already.
If
not,
I
can
just
add
it
to
the
chat.
A
So
there
are
some
changes
being
made
there
as
well,
but
yeah
no
real
progress.
Since
last
time
we
talked
unfortunately,.
C
A
Yeah
yeah
yeah
for
sure
well,
we'll
we'll
see.
If
we
can,
we
can
add
something
to
the
the
migration
guide
that
we
have
already.
G
I
have
a
question
about
signing.
Last
week
I
tried
to
sign
a
plugin
which
I
already
published
to
grafana,
which
worked
quite
easily.
I
got
signed
successful,
but
the
thing
is
a
couple
of
days
ago
I
tried
infinity
panel
signing,
but
it's
failing.
I
was
thinking
it's
a
private
plug-in.
So
what
should
be.
F
A
Is
the
infiniti
it's
not
yet
published
right?
It's
unusual.
A
Yeah,
so
you
will
have
to,
I
can
actually
do
it
for
you
right
after
this
call.
I
can
so
whenever
you,
whenever
you
create
a
new
plugin,
that
you
want
to
publish
you
need
to
request
the
signature
level
that
I
mentioned
earlier,
so
we
need
to
set
whether
it's
a
private
is
a
community
or
a
commercial
plug-in.
In
your
case,
it's
a
community
plug-in
and
the
reason
why
your
previous
plugin
is
working
is
because
we've
we've
already
set
all
already
published
plugins
to
have
the
community
level
all
right
yeah.
A
But
I
I
can,
I
know
the
plugin
that
you're
referring
to.
So
I
can
just
add
that,
right
after
this
call,
it
should
be.
G
A
That's
much
appreciated
thanks,
yeah
sure
question
from
yvonne
a
question
about
compatibility.
Should
I
keep
this
folder
in
repo
for
new
releases
so
that
version
6.7
and
earlier
may
can
install
plug-in
by
so
you
should
be
able
to
so
I
think
it
should
work
as
if,
if
you
start
packaging,
the
your
plugin
just
the
way
it
was,
it
should
work.
If
not,
then
let
me
know
because
I
would
want
to
know
that,
but
I
don't
think
it's
going
to
be
any
issue
with
backward
combat
compatibility
there.
D
D
I
mean
about
compatibility,
no,
I
think
I
think.
E
A
I
think
yeah,
so
you
should
never
have
to
keep
the
dist
folder
going
forward.
B
There
was
a
practice
to
keep
this
folder
in
separate
branches.
Yes,
so
I
can.
I
can.
I
can
use
this
practice.
A
So
we
going
forward,
we
don't
actually
care
because
to
publish
a
plugin,
we
only
need
the
packaged
sip
archive.
That's
the
only
thing
that
we
need
from
you.
So
if
you
want
to
keep
the
disk
directory
by
all
means,
do
so,
but
yeah
not
for
our
sake.
A
A
So
earlier
versions,
so
when
when
you
submitted
a
plug-in
before
then
when
we
accepted
and
published
it,
we
actually
packaged
this
and
we're
storing
your
package
plug-in
on
in
the
cloud
in
a
bucket.
A
So
if
you
change
to
not
contain
your
dist,
that's
not
going
to
be
an
issue
for
people
that
already
are
installing
through
profana.com.
A
Yeah
but
again,
if
you're
encountering
issues
with
this,
let
me
know
and
I'll
get
right
on
it.
A
A
We
are
working
on
a
script
to
you
know
to
to
sign
plugins
in
from
there.
That
has
already
been.
You
know,
plugins
that
have
already
been
published
in
the
past,
because
there's
a
lot
of
publics
that
plug-ins
that
have
been
used.
You
know
by
for
for
people
for
many
years,
but
they're
not
being
actively
maintained
and
the
the
plug-in
author
has.
You
know
not
touched
that
plug-in
in
many
years
and
we,
of
course
we
want
to
make
sure
that
people
can
still
use.
You
know
their
their
favorite
plugins.
A
So
for
for
those
plugins
we
are
going
to,
you
know,
sign
and
publish
a
new
version.
If
you
don't
want
us
to
do
that
for
your
plugin,
then
I
mean,
let
me
know
I
think
most
of
you
are
in
here
are
going
to.
You
know,
be
publishing
plugins
going
forward.
I
mean
you're
actively,
maintaining
a
plug-in.
I
I
assume
so
you
want
to
be
able
to
handle
that
yourself,
but
for
a
lot
of
plugins
they're,
you
know
they're,
they
don't
have
an
active
maintainer.
G
G
Okay,
so
if,
if
someone
built
a
plug-in
that
direct
competition
to
the
grafana
enterprise,
plugin
or
grafana
stock
plugins,
will
that
be
signed
by
grafana.
A
So
if
a
community
member
wants
to
publish
a
plug-in
that
competes
with
a
grafana
plug-in,
will
grafana
lab
still
sign
that
plug-in?
Yes,.
D
Yeah,
definitely
so
if
you
want
to
do
like
a
version
of
either
one
of
our
open
source
or
commercial
plugins,
that
was
really
similar.
Yes,
as
long
as
long
as
it's
open
source,
okay,
I.
D
Oh,
that
is
something
we
would
have
to
discuss.
So
I
suppose
azure
is
not
it's
not
an
open
source
service,
it's
a
commercial
service,
but
so
that's
it
in
the
gray
zone.
Maybe
it
depends
on
the
program.
I
think
something.
G
Is
yeah
and
I
I
developed
a
plugin
for
azure
but
native
data
source
doesn't
have
those
features.
So
what
should
be
there.
D
Yeah
so
it'd
be
great
to
collaborate
as
well
on
making
the
azure
monitor
data
source
better,
and
I
know
we
will
be
dedicating
more
time
to
in
in
the
very
near
future
and
work
together
with
microsoft
on
it.
D
But
I
think,
like
azure
is
huge,
so
you
know
if
we
never
intend
to
you
know
if
the
features
you
want
to
add
we're
like
okay,
we're,
never
gonna,
add
those
and
then
maybe
we
we
would
publish
it,
but
looking
at
the
the
the
terms
that
we
have
for
for
publishing
like
we
are
going
to
be
a
bit
stricter
on
data
sources
for
close
source
services.
C
A
That's
a
that's
a
awesome
idea.
I
I'm
not
aware
of
any
efforts
like
that
unless
daniel
knows
more
than
I
do,
but
if
you're
curious
then
have
a
go.
D
I
don't
think
so,
not
that
I've
heard
of
I
know
we
do
have
plans
for
some
commercial
plugins.
I
think
for
the
grafana
team.
We
have
enough
things
going
on.
I
think
we
have
things
like
you
know,
converting
world
map
to
react,
and
I
don't
know
lots
of
other
things
that
I
think
we
would
work
on.
First
before
we
branch
out
into
even
more
plugins.
C
Okay,
okay,
because
I
mean
I
started
working
with
radius
plugins
and
then
many
different
use
cases
actually,
instead
of
creating
an
application
using
angular
or
other
frameworks,
you
can
actually
create
it
using
dashboards.
So
we
thought
we
tried
to
do
right
now
we
put
everything
in
the
databases
and
then
create
the
dashboards
actually,
which
show
us
this
information
collecting
the
data
from
different
theorems
from
different
systems
and
have
one
stop
like
360
view
for
that.
C
C
C
Okay,
it's
good!
What
about
world
map?
Are
you
going
to
world
map
right
now,
it's
kind
of
very
limited.
What
it
can
show
it
can
show
with
different
dots
with
different
colors
right.
Are
you
have
any
plans
to
create
like
connections
between
them.
D
Yes,
so
I
think
the
world
map
was
originally
built
for,
like
a
a
cloud
service,
we
had
called
world
ping,
so
it
wasn't,
as
was
originally
built
as
some
sort
of
general
purpose.
Like
does
everything,
and
then
we
added
some
features
but
yeah
we
never
had
the
capacity
to
actually
do
it
properly.
So,
yes,
there
are
plans
but
not
like
in
the
very
near
future.
D
So
sometime
next
year,
I
think
we
like
to
do
a
lot
more,
not
just
on
the
ui,
but
also
like
a
proper
child
map
server,
and
we,
I
think
we
move
into
core
griffon
as
well
rather
than
having
as
an
external
plugin.
So
I
don't
know
eight
eight
dot
something
8.182,
maybe.
C
C
I
mean
the
world
map
right
now.
It's
great
is
that
you
can
show
what
happened
in
different
dots
of
the
world
right
different
parts
of
the
world,
but
if
you
want
to
see
the
like
one,
different
servers
on
the
world
map
right
and
they're
communicating
with
each
other,
and
they
have
like
replicating
the
data,
for
example,
so
it
will
be.
A
world
map
will
be
great
plug
into
service
information
instead
of
using
maybe
flow
chart
and
other
plugins
yeah.
D
D
So
that's
also
on
the
the
backlog
is
a
proper
weather
map
panel.
So
this
was
for
the
last
two
years.
The
quantity
has
been
very
focused
on,
like
the
the
angular.
Migration
has
taken
a
lot
of
our
resources.
D
So
now
we're
nearing
the
end
of
that
and-
and
you
see
that
we're
starting
to,
for
example,
break
up
the
the
graph
panel
into
lots
of
smaller
panels
so
you'll
see
already
in
7.4.
I
think
there
will
be
a
new
pie
chart.
Hopefully
a
new
bar
chart
panel
as
well
a
new
graph
panel
and
like
8.0.
There
should
be
a
whole
bunch
more
so
over
the
next
couple
of
say,
six
six
to
eight
months,
we
should
be
putting
out
like
a
lot
more.
D
It's
a
core
visualizations
in
grafana
and
lots
of
them
are
I've
always
been
there
they're
sort
of
hidden
away
in
the
graph
panel.
So
we're
going
to
try
and
break
the
craft
bundle
out
into
multiple
visualizations,
and
we
made
that
change.
Where
you
know
now,
you
can
pick
a
visualization
type.
You
can
easily
switch
between
them,
which
means
that
there
isn't
really
any
point
in
having
tons
of
features.
In
one
panel
like
we
used
to
have
before.
C
D
Yes,
they
will,
and
that's
also
on
the
ground,
a
road
map
actually
which
we're
publishing
soon
is
lots
of.
So
it's
actually
multiple
problems
like
that.
So
we
also
have
a
problem
with
you
know
if
you
without
plugins,
if
you
have
too
many
applicants
installed
and
they
all
have
an
icon,
then
it
gets
very
weird
and
funky
on
the
the
ground
navigation
on
the
navbar.
So
we
have
a
ton
of
small
things
without
the
fix.
C
D
D
More
on
that
on
just
apps,
I
think
we
like
it
turning
the
company.
We
have
like
other
teams,
not
the
crown
team
that
are
building
apps
now
and
and
yeah.
We
have
lots
of
lots
of
features
that
we
want
to
add.
So,
as
we've
done,
a
fair
amount
of
work
on
data
source
and
panel
plugins,
but
app
plugins
are
still
mostly
the
same
as
they
were.
You
know
three
or
four
years
ago,
so
there's
lots
to
do
there.
A
So
I
see
andreas
you
had
a
question
about
the
graph
components.
I'm
not
sure
if
you
feel
like
you
had
a
answer
to
your
question,
but
to
summarize
yes,
we're
we're
going
to
move
to
the
next
next-gen
graph,
but
we're
also
going
to
break
it
apart
into
multiple
visualizations,
based
on
what
daniel
just
said,.
D
Yeah,
I
think
it's
gonna
take
a
while,
so
I
think
the
old
graph
panel
I
mean
it's
on
every
single
dashboard.
I
think
that
exists
for
grafana.
It
is
gonna,
be
super
hard
to
migrate
it
to
new
records.
I
think
we'll
have
to
keep
it
around
as
a
legacy
panel
for
for
a
long
time
and
then
maybe
have
some
migration
paths
for
the
obvious
cases
and
then
the
other
ones
you'd
have
to
manually
migrate,
but
I
think
yeah
it
will.
D
It
will
live
on
for
a
long
time,
I'm
afraid,
but
hopefully
the
the
newer
more
focused
panels
will
will
be
better.
D
A
G
D
G
Okay,
let
me
let
me
do
that:
okay,
apart
from
data
source
and
panel
plug-in,
is
there
any
other
plug-in
roadmap
like
transformation
themes.
D
So
the
next
one
will
be,
for,
I
think,
alert
notifiers,
but
yes,
there
will
be
new
plugin
types,
I
think
not
not
for
8.0.
I
think
we're
trying
to
focus
on
on
improving
what
we
have,
but
after
after
8.0,
then
then
then
yes
would
be
new
plugin
types
be
on
the
roadmap.
D
A
Another
comment
in
the
in
the
chat
about
the
world
map
plugin
and
you
know,
publishing
a
a
mapbox
panel,
plug-in
it
kind
of
feels.
I
I
assume
the
the
the
gaps
that
the
world
map
has
right
now,
but
I'm
not
sure
I
mean
I.
I
don't
think
I
I
know
exactly
what
mapbox
you
know
what
it
improves
on
for
the
for
the
world
map,
but
I
don't
see
any
issues
with
having
like
multiple
map
plugins
as
well.
So
I
happen
to
see
that
you're.
D
D
There
are
already
multiple
map,
plugins,
so
yeah.
I
think
we
look
at
some
of
them.
They
are
very
like
totally
different
from
world
map
and
have
a
totally
different
angle
on
it.
So
yeah,
that's.
What
we
will
hopefully
do
is
in
the
future,
have
more
map
components
in
the
chrono
ui
library,
so
that
it'll
be
easier
to
build
them.
C
My
box,
actually
it's
an
interesting
product,
they
use
their
own
api
and
their
own
data.
So
it's
a
little
bit
diff
different
kind
of
than
than
world
map
itself,
which
is
a
really
interesting
company
to
work
with.
I
have
a
question
about
the
stats
starts
panel.
Is
any
plans
to
support
strings
there
properly
like
right?
Now,
it's
allow
you
to
if
it's
an
it's
not
work,
mostly
with
numbers
right.
C
D
Yeah,
I'm
not
sure
I
know
I
know,
there's
lots
of
feature
requests
for.
I
think
I
have
to
ask
the
front-end
platform
team
or
if
they
have
any
plans
I
know
they
are.
They
are
working
visually
visualizations
generally.
So
so
maybe
I
can't
say
yes.
C
Or
no
to
that,
so
should
I
require
look
for
such
issue,
because
this
is
something
I
I'm
looking
for.
I
need
it
for
my
own
work,
yeah,
look
for
it
and.
A
Cool,
I
think
that
we're
pretty
much
done
here.
If
you
have
any
questions
about
plug-in
signing
or
you
know,
plug-in
development
and
publishing
plug-ins.
Let
me
know
you
can
send
me
an
email
to
marcus.olson
grafana.com.
A
If
you
have
any
more
questions,
you
can
also
I'm
I'm
active
in
the
slack
channel
hashtag
plugins,
I'm
I'm
sure
that
some
of
you
are
already
there,
but
if
you're,
not
that
you
can
ask
me
questions
there
as
well,
so
I
will
say
goodbye
for
now
and
I
I'm
not
sure
if
there's
gonna
be
a
community
call
in
december,
I
think
it
might
coincide
with
the
holidays,
so
keep
keep
st
stay,
updated
and
yeah.
Otherwise
I'll
see
you
next
time.