Kibana: [Security] Persist user preferences

Created on 15 Jun 2020  路  4Comments  路  Source: elastic/kibana

There are several configuration points within the Security UI that are not persisted. If the user's preference doesn't match the default, the user must perform the same action on every page load.

This issue is meant to inventory, discuss, and address as many of these as possible.

A few to get the ball rolling:

  • Detections Page

    • Alerts Histogram



      • stack order



    • Alerts Table



      • Open/Closed filter


      • Row Count (Page Size)



    • Rules Table



      • Row Count (Page Size)



  • Overview Page

    • All Histograms

    • stack order

Meta SecuritySolution SIEM enhancement

All 4 comments

Pinging @elastic/siem (Team:SIEM)

Thanks @rylnd! We should get row count persistence on the Alerts Table (both on the Detections and Rule Details pages) as part of https://github.com/elastic/kibana/pull/67156, but will still need to handle our custom status filter.

Thanks @rylnd! As @spong said in #67156 the following actions are persisted for every timeline table and specifically for Host Page (Events, External Alerts), Network (External Alerts), and Detections Page (Alerts list for all rules and detailed rule view):

  1. Column removal
  2. Column addition
  3. Column reorder
  4. Column resize
  5. Sorting
  6. Row count (Page Size)
  7. Resetting to default fields

Fixed by https://github.com/elastic/kibana/pull/67156. Persistence of Open/Closed filter is not supported at the moment.

Was this page helpful?
0 / 5 - 0 ratings