Feature #24571
mgr/dashboard: Move Cluster/Audit logs from front page to dedicated "Logs" page
0%
Description
The Manager Dashboard currently shows the Cluster Log and Audit Log on the front Dashboard page. To unclutter the front page, I suggest to move this part into a dedicated "Logs" page, located in the "Cluster" menu. If possible, that page should provide some additional functionality to work with the logs, e.g. to search for keywords or to show a certain time range of the logs.
Related issues
History
#2 Updated by Lenz Grimmer 8 months ago
- Assignee deleted (
Lenz Grimmer)
#3 Updated by Jos Collin 8 months ago
- Assignee set to Diksha Godbole
- Source set to Community (dev)
#4 Updated by Lenz Grimmer 6 months ago
- Blocked by Feature #24573: mgr/dashboard: Provide more "native" dashboard widgets to display live performance data added
#5 Updated by Lenz Grimmer 6 months ago
Please note that work is underway to improve the dashboard landing page (see #24573 for details). This PR will keep the logs on the landing page, please rebase and adapt your PR once this one has been merged.
#6 Updated by Alfonso MH 6 months ago
- Related to Feature #27050: mgr/dashboard: Landing Page Enhancements added
#7 Updated by Jos Collin 6 months ago
- File dashdoard-logs.png View added
Please see the screenshot of the new logs page attached. As we have a dedicated page for the logs now, do we still need the tabs?
#8 Updated by Jos Collin 6 months ago
- Status changed from New to In Progress
#9 Updated by Diksha Godbole 6 months ago
#10 Updated by Lenz Grimmer 5 months ago
- Status changed from In Progress to Need Review
#11 Updated by Lenz Grimmer 3 months ago
- Pull request ID set to 23834
#12 Updated by Lenz Grimmer 3 months ago
- Precedes Feature #37387: mgr/dashboard: Add date range and log search functionality added
#13 Updated by Lenz Grimmer 3 months ago
- Status changed from Need Review to Resolved
- Target version set to v14.0.0
The logs have now been moved to a dedicated page on the dashboard. The additional functionality described in this issue have now been moved to a separate tracker issue: #37387