Skip to Main Content
Cloud Platform
Hide about this portal


This is an IBM Automation portal for Cloud Platform products. 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
  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 (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.


Capturing the response time of every hit that stub responds and present the graphical reporting

See this idea on ideas.ibm.com

We store the following three stub metrics and display the appropriate plotted graphs on KiarosDB UI.

• rtvs.stub.evt_in – total hits

• rtvs.stub.evt_match – hits that got processed

• rtvs.stub.evt_passthrough – hits that got passed to the real system

But this does not provide a performance response time of  every hit that stub responds to and plot graphs. 

 

The only alternate way is that we can get the engine logs capture the execution time details by tweaking the "agent-logging.properties" file

Ie; After you configure for logging of the stub metrics, you can view the log for each event as follows:

FINE: addNumbers/addition/additionStub: Instance 1: Execution Complete. Timings: Queue To Run=0, Run to Execute=3, Execution=138, Finalization=0, Total=143

 

As an alternate solution, we proposed Splunk Universal Forwarder to read these engine logs and craft a graph out of it.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 6, 2025

    We need to determine if there are any performance issues.