I completely see the advantages that you point out, Mike. But I would be against removing support at this time.
With a project like Metron, it is hard for new users to get their head around what it is and what it can do. The Kibana dashboard gives new users an understanding of how they can leverage the normalized, enriched, and triaged data that Metron produces. It is the only interface we currently have that shows-off plots, maps and the like. On Wed, Nov 1, 2017 at 12:13 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > As part of the ES upgrade, I got to thinking that it makes sense to remove > Kibana and the dashboards we're currently bundling in the MPack. To be > clear, this would not remove the ability to independently install and use > Kibana if the user so chooses, it would only remove the dashboards, and > potentially, the Ambari/MPack management support that we ship. > > *pros* > Removes need to support tooling outside our wheelhouse > Smaller testing effort for ongoing support and future upgrades > Simplifies our base Metron install via Ambari. Also simplifies full dev > setup. > > *cons* > User would need to install and setup their own Kibana instance and > dashboards. > If any existing users are using this, they'd need to backup and manage > their own Kibana dashboards going forward. They would also need to handle > any upgrade issues with Kibana post-Metron ES 5.x upgrade. > > Any concerns? > > Mike >
