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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com


Status Not under consideration
Workspace DataStage
Created by Guest
Created on Aug 22, 2018

Operational Console Report generator tab.

The DSODB database which sits behind the Operational Console is a treasure trove of information.  It would be very handy if the webpage allowed for some standardized reports to be generated.  Such reports could be a PDF or Excel format.  Data in the reports should be selectable by project and date range. 

 

Report #1:  It would be great if we could get the history behind failed jobs. 

 

Project name, job name, invocation id, Start time, end time, all "fatal" messages for that job.

 

Report #2:  Bar chart with average runtime for jobs.

 

Each job exaction (failed entries in red) would have a bar in a horizontal line.  Their execution date as X axis and duration is Y axis.  "Average execution duration"  as a super imposed line graph.

 

Report #3:  Gant chart for jobs in a project.

 

Have the start and end time for all jobs in a project listed in GANT CHART format.  Sequencers contain nested jobs.  Default timeframe would be a day of the calendar month.  Selectable date range as well.  But a 24hrs view would be nice.

 

Report #4:  Hogs and Dogs report.

 

project; jobname; invocation id, start time, end time, duration, CPU, completion status.

 

The HOGS are the ones taking a lot of CPU.

The DOGS are the ones taking a long duration.

 

Seeing the complete list of jobs in an excel format allows us to do trend analysis and plan for grown needs of our infrastructure or to address upcoming issues before they happen.

 

 

These report (other than the GANT Chart) can be obtained from SQL queries, but the TOOL should create these simple reports and allow the user to email the results to their desktop.  Simply provided a GUI view is not enough as often times in a large org, we need to submit the information for analysis by others.  Hence the excel, csv or pdf file format.  JSON or XML is also a good idea.

 

Externalizing the data behind the DSODB is very important.  The Dashboard should have a report tab and creativity applied to the reports that are "canned" and maybe allow for an adhoc ability as well.  Selectable date range is a must.

 

  • Guest
    Reply
    |
    Oct 18, 2020

    While I'm marking this as not under consideration for Operations Console, we recognize this requirement as an important use case and will be thinking about this as we progress forward in our roadmap.