Skip to content

Management - Cluster vs Global Kibana vs Space #37283

@kobelb

Description

@kobelb

Currently, the management application in Kibana has a number of different management sections.

Screen Shot 2019-05-28 at 2 24 09 PM

They're currently all in a flat list; however, each of them has a different "scope".

  1. Cluster: these sections apply to the entire Elasticsearch cluster
  2. Global Kibana: these sections apply to the entire tenant/instance of Kibana. Most users only use a single tenant/instance of Kibana, but it's possible to create a different tenant/instance by changing the kibana.index in the kibana.yml to create separate tenants
  3. Space specific: these sections only apply to the currently selected space

I'm not certain whether it'd be beneficial to differentiate as much between cluster and global-kibana, as much as it is beneficial to differentiate between space specific and cluster/global-kibana.

We'd like to find a way to expose this "scope" on the management screen. The following sections have the specified scope:

Cluster

  • Elasticsearch
    • Index Management
    • Index Lifecycle Policies
    • Rollup Jobs
    • Cross-Cluster Replication
    • Remote Clusters
    • Watcher
    • Snapshot Repositories
    • License Management
    • 9.0 Upgrade Assistant
  • Logstash
    • Pipelines
  • Beats
    • Central Management
  • Security
    • Users
    • Roles

Global Kibana

  • Kibana
    • Spaces
    • Reporting

Space specific

  • Kibana
    • Index Patterns
    • Saved Objects
    • Advanced Settings

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature:Kibana ManagementFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature:Security/SpacesPlatform Security - Spaces featureTeam:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//enhancementNew value added to drive a business resultunified-security-painpointHighlights issues that are painpoints as a result of the lack of a unified security model

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions