kibana/x-pack/plugins/reporting
Stacey Gammon 2c1fcf9604
Typescript-ify screenshot stitcher code in reporting (#20061)
* typescript screenshot stitcher

* Throw an error if the data captured is not of the expected width and height.

* Import babel-core types

* Add babel-core types to x-pack package.json

* Dimensions => Rectangle
2018-06-22 09:18:29 -04:00
..
common [Monitoring/Reporting Stats] Move hardcoded Reporting stats type collection out of monitoring plugin (#18894) 2018-05-24 11:14:27 -07:00
export_types Replace spy panels by Inspector (#16387) 2018-06-20 11:07:44 +02:00
public updateUrl is on scope, not this. (#19687) 2018-06-05 18:40:40 -04:00
server Typescript-ify screenshot stitcher code in reporting (#20061) 2018-06-22 09:18:29 -04:00
webpackShims
index.js [X-Pack Usage API] use authentication from request headers (#19613) 2018-06-05 10:38:02 -07:00
log_configuration.js
README.md

Kibana Reporting

An awesome Kibana reporting plugin

Development

Assuming you've checked out x-plugins next to kibana...

  • Run yarn kbn bootstrap
  • Run yarn start to watch for and sync files on change
  • Open a new terminal to run Kibana - use yarn start to launch it in dev mode
    • Kibana will automatically restart as files are synced
    • If you need debugging output, run DEBUG=reporting yarn start instead

If you have installed this somewhere other than via x-plugins, and next to the kibana repo, you'll need to change the pathToKibana setting in gulpfile.js

Conventions

This plugins adopts some conventions in addition to or in place of conventions in Kibana (at the time of the plugin's creation):

Folder structure

export_types/ (contains public and server aspects of the different export types) 
  printable_pdf/ 
    public/
    server/
  csv/
    public/
    server/
public/ (shared public code for all export types)
server/ (shared server code for all export types)

This folder structure treats the different export_types like Plugins, with their public/server code being separate in a folder.