Kibana: Break up core Kibana tabs into separate plugins

[tbragin]

Today Discover, Visualize, Dashboard, and Settings are implemented as one plugin.

Breaking them up into separate plugins will allow users to disable them at startup, satisfying requests such as this: https://github.com/elastic/kibana/issues/6496

[epixa]

I bumped this to P2 because while the feature at face-value is a P3, it would be a huge technical gain to move these to individual plugins, and that would help us iterate on future features faster.

[sagh0900]

We have kibana version 4.5.2. We are looking for possibility to disable settings app (either by removing it from menu) or redirect it is discover app. how can I do it?

[mgoritzk]

+1

[shaanen]

+1

[abdalians]

any word on this?

[epixa]

@abdalians This is an important change, but it's a significant project with a lot of risks. There's no target date or release for it.

There are two efforts that will make this easier:

• Remove loading screen
• New platform

[cjcenizal]

I've seen this request come up quite a few times in the forums:

• https://discuss.elastic.co/t/how-to-disable-kibana-5-0-0-plugins-like-management-dev-tools/64536
• https://discuss.elastic.co/t/disable-kibana-management-section-for-users/76443
• https://discuss.elastic.co/t/disable-hide-management-plugin-kibana-5/72763
• https://discuss.elastic.co/t/user-management-on-kibana/82808

[nfx]

+1

[Shini31]

+1

[Payback159]

+1

[varunsharma27]

+1

[MattBorowiec]

+1

[xorpaul]

+1

[dovefi]

+1

[natebunton]

+1

[piotrkochan]

+1

[Hariharan-Gandhi]

+1

[basilrormose]

+1

[suckowbiz]

+1

[widhalmt]

+1 I would definitely like to see this for Dev-Tools as well.

Update: I realized too late, that this should be possible via console.enabled: false

[dianazv]

+1

[keshara]

+1

This will be very helpful when it comes to mange with end uses, giving them less access.

[havidarou]

+1

[gergely-ujvari]

+1

[piotrkochan]

+1

[ikrauchanka]

+1

[f0xtek]

+1

[glira]

+1

[uwrob]

+1

[emanzaman]

+1

[guanghaofan]

+1

[coleshores]

Any word on this? This is a pretty big deal for our organization's needs.
Thanks

[heyarb]

+1

[pinkielll]

+1

[larriaga]

+1

[victor-mendes-eduardo]

+1

[rajesnal]

+1

[naveenkumart28]

+1

[lanerjo]

+1
I would like to know when this is planning to be implemented, and can a back port be made available to all 6.x versions?

[epixa]

@lanerjo There's supportive work related to this happening in every version, but we don't have a target version for actually breaking up the apps into separate plugins. I do know that it won't be done in 6.x, though.

[lanerjo]

Blocking the use of a section as powerful and potentially breaking of a product such as the management section, seems like it would be a fairly high priority. Especially considering how many users are requesting that feature.

[baracudda]

Having had to tackle this very subject, I figured out how to do it in a way that works for my clients so I thought I'd share it here in case others are still looking for a workaround until this gets handled internally: https://stackoverflow.com/a/54263016/429728

[elasticmachine]

Pinging @elastic/kibana-app-arch

[flash1293]

During 7.6, 7.7 and the upcoming 7.8 we incrementally refactored this code and moved it into separate plugins - in 7.9 the catch-all "kibana" plugin will be removed completely.