1b6dcabd6c
* migrate reporting top nav to sharing menu * pass share extensions to visualize share menu * start creating the reporting panel component * add buttons * generate report generatation URL * require save if url changes * add print layout UI * putting it all together - generate reports from share context menu * ensure copy button fills entire menu width * inject job params functionallity * refactor print layout out of ReportingContentPanel * CSV report generation * disable report generation when app is dirty * update URL when window is resized * remove all the old stuff * clean up CSV report register provider * fix typescript errors * fix functional retests * remove failure_debug folder * close popover when generate button clicked, more work on functional tests * set size on button and text, do not use EuiFormRow * use ReactElement type * move ShareContextMenuExtensionsRegistryProvider to ui/share and create interfaces for registy * strictor typing, do not use hard coded object type name * move registry files to typescript * remove destructuring in the interface * convert createReportingJob to async function, remove unneeded comment |
||
|---|---|---|
| .. | ||
| common | ||
| export_types | ||
| public | ||
| server | ||
| webpackShims | ||
| index.js | ||
| log_configuration.js | ||
| README.md | ||
| types.d.ts | ||
Kibana Reporting
An awesome Kibana reporting plugin
Development
Assuming you've checked out x-plugins next to kibana...
- Run
yarn kbn bootstrap - Run
yarn startto watch for and sync files on change - Open a new terminal to run Kibana - use
yarn startto launch it in dev mode- Kibana will automatically restart as files are synced
- If you need debugging output, run
DEBUG=reporting yarn startinstead
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.