Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Not under consideration
Categories Command Server
Created by Guest
Created on Jan 9, 2018

Additional performance related timing data required in the audit log on a per-card basis

A change that I would love to see in audit logs is a start time and an end time for each card.  The current way of showing timings at the card level – with a “TimeStamp” at each card – is very confusing.  I get the idea that the TimeStamp means different things if it's an input card or an output card – on input cards, it seems that it's a start time (the TimeStamp of input 1 always matches the StartTime at the beginning of the log), but the TimeStamp for output cards is almost certainly the end time, as it jumps on cards that process more data.

For example, a map that has a large amount of input, and where Target 3 does a lot of work on that input, seems to look like this:

          StartTime = 12:00:00
          Source 1      TimeStamp = 12:00:00
          Target 1       TimeStamp = 12:00:10
          Target 2       TimeStamp = 12:00:10
          Target 3       TimeStamp = 12:00:30

That's really confusing.  Did the 10 seconds elapse while processing Source 1 or Target 1? Or was it spread out between the two? Was the 20 seconds spent in Target 2 or Target 3? It would be much easier if it looked like this:

          StartTime = 12:00:00
          Source 1      StartTimeStamp = 12:00:00 EndTimeStamp = 12:00:10
          Target 1       StartTimeStamp = 12:00:10 EndTimeStamp = 12:00:10
          Target 2       StartTimeStamp = 12:00:10 EndTimeStamp = 12:00:10
          Target 3       StartTimeStamp = 12:00:10 EndTimeStamp = 12:00:30

…or this:

          StartTime = 12:00:00
          Source 1      StartTimeStamp = 12:00:00 ElapsedSec = 10
          Target 1       StartTimeStamp = 12:00:10 ElapsedSec = 0
          Target 2       StartTimeStamp = 12:00:10 ElapsedSec = 0
          Target 3       StartTimeStamp = 12:00:10 ElapsedSec = 30
DeveloperWorks ID DW_ID56852
Link to original RFE
  • Guest
    Jun 4, 2019

    Concept: We are contemplating a new audit log via JSON format