How to visualize new install plugin in kibana


(sarbjeet kaur) #1

i copied kbn_circles_vis into src/plugins/.
when i start kibana. it runs in browser properly. when i see its status it display:-
plugin kbn_circles_vis=ready

but how to use that plugin in visualization.because in visualization we could not find any option for installed plugin.


(Jon Budzenski) #2

If the plugin installed correctly and it's compatible with your version of Kibana it would most likely be added to the list of visualizations on the visualize page at app/kibana#/visualize/step/1. Can you share a link to the plugin and your Kibana version?


(sarbjeet kaur) #3

kibana version is 4.4.2.
plugin:- kbn_circles_vis.
plugin installation steps:-

  1. git clone https://github.com/JuanCarniglia/kbn_circles_vis.git
    it creates kbn_circles_vis directory
  2. then just copy the kbn_circles_vis folder into /src/plugins.
  3. service kibana restart.
  4. kibana started. its status shows that plugin ready with green signal.

(Jon Budzenski) #4

It should be adding "Cirlces Diagram" to your list of visualizations, is that not the case?


(sarbjeet kaur) #5

circles diagram not display in my case.
what should i do?


(sarbjeet kaur) #6

please tell me complete steps for installation.


(sarbjeet kaur) #7

Now i installed kibana 4.5 . its running.but when i
cp -R kbn_circles_vis /opt/kibana/src/plugins/
and remove kibana.* files from bundle directory.
kibana is not running.
i checked
cat /var/log/kibana/kibana.stderr.
file contains:-
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL [Error: Config schema already has key: kbn_circles_vis]
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/kibana.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/kibana.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/statusPage.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/statusPage.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/statusPage.entry.js' },
isOperational: true,
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/statusPage.entry.js' }
FATAL { [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/statusPage.entry.js']
cause:
{ [Error: EACCES: permission denied, open '/opt/kibana/optimize/bundles/statusPage.entry.js']
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/opt/kibana/optimize/bundles/statusPage.entry.js' },

where is the problem?


(Jon Budzenski) #8

That's caused by a current bug in kibana (https://github.com/elastic/kibana/issues/6730). Recursively setting the user and group on the optimize folder to kibana:kibana will fix that issue.


(sarbjeet kaur) #9

how can i resolve this issue?
please explain.


(sarbjeet kaur) #10

please reply .how can i resolve this issue?


(Jon Budzenski) #11

Something like chown -R kibana:kibana /opt/kibana/optimize will make sure the package user kibana can use the files in /opt/kibana/optimize.


(system) #12