I'm probably okay with marking it as deprecated in two releases (after
moving to 5.x, thus not really helping with the migration), but it depends
a lot on increased functionality for the metron alerts UI IMO.

Jon

On Wed, Nov 1, 2017 at 12:51 PM Otto Fowler <ottobackwa...@gmail.com> wrote:

> I don’t think we should remove it until there is a viable alternative for
> the capabilities we rely on it for.
> Also, the ‘story’ around metron integration with kibana needs to be solid
> and well supported at that time.
>
>
>
> On November 1, 2017 at 12:13:18, 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
>
-- 

Jon

Reply via email to