Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Functionality already exists
Workspace Spectrum Symphony
Components Future Version
Created by Guest
Created on Dec 5, 2022

Symphony jobs log retrieval enhanced mechanism

Whereas Symphony provides an easy way to retrieve its own cluster logs through its System Logs web interface, the same is not true for user jobs submitted to the cluster. Today, a given job’s log is generated and stored on the filesystem. A user must log onto the filesystem in order to retrieve that job’s log. This is a bit of a hassle when you think that an end user is submitting its job to a portal, which in turns submits the job to the Symphony cluster, then the user must initiate an SSH session to the Symphony cluster to retrieve the job.

Conductor handles this is a nicer way where it allows a user to retrieve stderr and stdout of a given job driver and its executors through the GUI itself and via APIs. The request for enhancement here is to have Symphony jobs operate in a similar fashion, by allowing users to retrieve jobs’ logs throug the GUI or, more importantly, via API.

Needed By Quarter
  • Admin
    Dennis Xiao
    Dec 14, 2022
  • Guest
    Dec 12, 2022

    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.