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 Submitted
Workspace Cloud Pak for Data
Created by Guest
Created on Apr 2, 2024

Capture individual transactions across the different capabilities/services within CP4D

We would like to capture individual transactions across the different capabilities/services within CP4D. This will provide visibility on what customer transactions are running on the platform. The key fields that we are interested in are as follows.

  1. User Name - We would like to capture the user name alias this way we can join that to our employee dimension to do further analytics
  2. Start Time
  3. End Time - This field in combination of with the start time would help us determine the duration and we could build a notification around long running transactions
  4. Command – Examples would be the Job Name, SQL  statement, Cognos report name, workbook name etc.
  5. Status - Indicates the status of the request/job run etc.
  6. Node/Container – Where the command/request is running from
  7. Service (i.e. Watson Query, Cognos etc.)

Other notable requirements
• We want the data on scheduled job runs, user-invoked transactions, and any other transactions that occur on the platform. We have an API for assets that are part of jobs (i.e. /v2/jobs/{job_id}/runs)  however, we do not have an API method for assets not part of jobs.
• The option to retrieve this data through an API, a database, or alternative methods (not yet considered).
• Ultimately we want the ability to store the collected data in a database, so that it can be joined with our Employee Dimension table and used for further analysis, such as identifying the user with the most requests, departments with the most requests, average duration by user or department etc.

Needed By Month