New features
Managing logs across multiple nodes in an enterprise environment just got a whole lot easier. With Last Log, you can now monitor and troubleshoot log files across all your nodes directly from the Jira Admin UI. No more jumping between servers or dealing with complex server access issues!
Improvements
- The user filter is now a dropdown menu with available options, replacing the previous text field.
- Added support for Jira 10.
- Rotated log files are now automatically displayed—no more manual selection.
- Replaced the max results picker with lazy loading, enabling unlimited log file search.
- You can now enable or disable specific log files for better performance and a cleaner view.
- Introduced anonymized app metrics.
Bug fixes
- Resolved an issue where log entries were not correctly generated when reading log files in reverse order.
Further notes
Version 2.1.0 introduces some changes in usage, primarily due to a complete revision of the backend. Last Log no longer directly accesses the local log files but a database into which the logs are synchronized.
Multi-node support
Last Log can now display all log files from all nodes, “All nodes” being the default view option.
Log view and search
The maximum results picker has been removed since the search is now working across all log entries, and the view now supports lazy loading.
Log selection
By default, only the standard log file, atlassian-jira.log / atlassian-confluence.log, is activated with a sync interval of “Auto” and a retention period of “7 days” so that the latest log entries within the last 7 days are always available.
To investigate further log files, they must be activated on the Log settings page. By switching the “Status” toggle, the default config will be enabled with a sync interval of “Auto” and a retention period of “7 days”.
