About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
App user can also get various app info(logs) from GUI with these: https://www.ibm.com/docs/en/spectrum-symphony/7.3.2?topic=files-retrieving-logs/ https://www.ibm.com/docs/en/spectrum-symphony/7.3.2?topic=service-retrieving-application-logs-from-cluster-management-console including task logs that are created by application service.
Application logs and structure are external to Symphony. Applications generate 1000's of log files and searching these logs through the Symphony GUI is not practical. Customers typically use ELK for this purpose.
Symphony has GUI support to retrieve application logs, but the location of these logs are assumed to be on the local disk of the compute host. Symphony can only download a small number of logs at one time before running into timeouts. For most common use cases, downloading a small number of files is sufficient, if the application developer is looking for something specific.
If all logs are located in one location, then using "ssh" to access the log location is a far better approach. If the application developer is looking for a specific message or job log on a large set of hosts, then using a tool like grep to search will be much more efficient than downloading around 10 logs at a time, checking them and moving on to the next set.