Dear team,
Current Behavior
The Planning Analytics Workspace Server Logs interface currently provides basic filtering capabilities, such as Log Level and time range.
Logger Name filtering has also been requested separately in PAOC-I-2074.
However, the Server Logs interface currently does not provide a full-text search across the available log entries.
This makes troubleshooting difficult, particularly in environments with high log volumes. Even when the relevant log data is available, administrators may need to manually inspect large numbers of unrelated entries to find a specific process, cube, user, REST API call, error message, or other relevant information.
For example, an administrator may want to find all log entries containing:
ExecuteProcess
or:
insufficient memory
or:
/api/v1/ExecuteProcess
Currently, there is no convenient search functionality for this within the Server Logs interface.
Requested Enhancement
Add a full-text search capability to the Planning Analytics Server Logs interface.
The search should operate across the available server log data and should be combinable with the existing and planned filters.
For example:
Time range:
24.08.2026 09:00–09:30
Log Level:
ERROR
Logger Name:
TM1.API
Search:
ExecuteProcess
→ Show only matching log entries.
The search should ideally support arbitrary text contained in the log entry, including error messages, process names, cube names, REST API endpoints, usernames, error codes, and other relevant information.
Server-Side Search
For large log volumes, the search and filtering should preferably be performed server-side.
The complete log history should not need to be transferred to the browser before the search is performed.
The PAW UI could use pagination, virtual scrolling, or another suitable mechanism to display the matching results efficiently.
This would allow the functionality to remain usable even when searching across large log files or longer time periods.
Filtered Download
The search results should also be downloadable.
For example, after applying:
Logger Name = TM1.API
Log Level = ERROR
Search = ExecuteProcess
the user should be able to download the resulting entries rather than having to download and manually process the complete log.
CSV would be a useful primary export format, with JSON and/or plain-text as optional formats.
Logger Name Integration
The full-text search should work together with the requested Logger Name filter from PAOC-I-2074.
This would allow administrators to combine structured filtering with free-text search.
For example:
Logger Name = TM1.Process
Log Level = ERROR
Search = Z_0004_Quality_Check
This would provide a much more targeted troubleshooting experience than reviewing the complete Server Log manually.
Relationship to Existing Ideas
This request complements existing enhancement requests for the Server Logs functionality:
CPDIDEAS-I-3031 – Server Logs: Increase number of lines to display and download
Addresses the current limitation on the number of log lines that can be displayed and downloaded.
PAOC-I-2074 – Add Logger Name Filter to Planning Analytics Server Logs
Addresses the missing Logger Name filter.
This request addresses a further limitation: the lack of full-text search and advanced, combined log analysis capabilities.
These enhancements together would provide a much more powerful troubleshooting experience for Planning Analytics administrators.
Benefits
Faster identification of relevant log entries
Significantly more efficient troubleshooting
No need to manually inspect large volumes of unrelated log entries
Easier investigation of REST/API activity
Easier troubleshooting of specific processes, cubes, users, and errors
More effective use of the existing Logger Name information
Reduced need to manually download and process complete log files
Reduced dependency on IBM Support or manual log-file analysis
Reduced mean time to resolution (MTTR) for production issues
The goal is to evolve the current Server Logs interface from primarily a log viewer into a more effective search and troubleshooting tool, while continuing to respect the existing security and administrative permissions.
Thanks in advance.
With best regards,
Vitalij
With a text search it would also be possible to look for minor errors, which are only handled as "Info". There is no way to find them easy in PAW today. Perspectives offered that possibilty.
+1 from me. This is exactly the kind of functionality we found was needed for practical troubleshooting.
In SPACE we already support full-text search, structured filtering, nested AND/OR conditions, IN filters, saved searches, and filtered downloads across Server, Audit, and Transaction logs. SPACE also parses additional log fields, so users can filter directly by things like cube, process, user, or even element name.
And using SPACE AI, you can ask any questions about logs.
The attached screenshot shows an example of the filtering interface. Search remains fast even across very large historical log volumes.
+1
This is a very useful enhancement, especially for environments with a high volume of Server Log entries.
Increasing the number of displayed and downloadable lines would solve an important limitation. However, from our experience, it would be even more useful if this could be combined with more advanced filtering and search capabilities.
In particular, being able to filter by Logger Name and perform a full-text search within the available log entries would make troubleshooting significantly more efficient.
For example:
Logger Name = TM1.APILog Level = ERRORTime Range = 09:00–09:30Search = ExecuteProcessThis would allow administrators to isolate the relevant entries without manually reviewing thousands of unrelated log messages.
We have submitted a separate enhancement request for the Logger Name filter (PAOC-I-2074), as this addresses a related but distinct limitation.
Ideally, the long-term solution would provide server-side search and filtering across the available log data, with the PAW UI displaying the matching results using pagination or virtual scrolling. The filtered result set could then also be downloaded.
This would turn the current Server Log viewer into a much more powerful troubleshooting tool without requiring administrators to manually download and process large log files.
We strongly support this enhancement and believe that combining increased log access with advanced search and filtering would provide significant value for Planning Analytics administrators.