Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-1011

Improving Kibana UX for ES6+

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • Log Storage
    • Kibana UX Improvement
    • False
    • False
    • NEW
    • Done
    • NEW
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      Goals

      We are looking for ways to improve the UX for Kibana 6+ so that it is a better experience for customers like they had on Kibana 5.

      • Automated creation of index patterns for user tenants based on their access
      • Smart/automated handling of failed tenant migrations

      Non-Goals

      • This does not guarantee we will be providing Kibana 7, just that improvements we can make in 6 will also be available in 7 given these changes will be taking place in the OpenDistro plugin.

      Motivation

      With Kibana 5 there were more things we could do automatically for the user because of Kibana's structure and how we implemented multitenancy using our own elasticsearch plugin which allowed us to automate much more of the user experience. Things are much more manual in Kibana 6 currently.

      Alternatives

      • Continue to keep things as manual interactions for users

      Acceptance Criteria

      • Verify that as a Kibana user my index patterns will be automatically created for me upon logging in
      • Verify that admin tenants have the correct index patterns made available to them
      • Verify that non-admin tenants have the correct index patterns made available to them
      • Verify that if we were to run into tenant migration issues the plugin handles it for us instead of just wrapping an error

      Risk and Assumptions

      With contributing into the opendistro repos, there is a chance these changes will not be accepted by the community. In that case, we may be carrying manual patches of the Kibana security plugin in our repo.

      Documentation Considerations

      Our current documentation describes how to perform these steps manually, we will be able to update that language to remove it.

      Open Questions

      N/A

      Additional Notes

      • The intention is not to backport this, it would just be available from its release onward.

              Unassigned Unassigned
              ewolinet@redhat.com Eric Wolinetz (Inactive)
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: