Building and deploying Kibana plugins… And should I do it?
Developing Kibana plugins seems an appealing way to enhance the Elastic frontend. Even though tactical problems can be overcome, it might not be the best choice from a strategical point of view
12. From a list of localized tweets
Standalone
Aggregation
Field
formatter
kibana-howto-plugin-clock
kibana-howto-plugin-viz-data-country
kibana-howto-plugin-format-tweet-text
17. Format tweet text
#build the .zip archive
npm run build
git add build/xxx-5.2.2.zip
+ commit and push
#install the plugin
bin/kibana-plugin install
http://github…/xxx-5.2.2.zip
27. Upgrading the demo plugins
was a real pain (4.2 to 5.2.2)
• No documentation available
• Compared diff commit of working plugins
• Google Developper console to debug
• … That was the last update
28. A few reasons not to go
• User Experience is tied to Kibana paradigms
• Development is not a smooth experience
• Undocumented features (resize…)
• Versioning hell