IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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.

Add a new idea Subscribe
Status Under review
Workspace IBM Z Observability Connect
Created by Guest
Created on Jan 22, 2026

RELATED IDEAS

A utility to analyze SMF & syslog volume, and then suggest sizes for components

Since IBM has the zPET env., it should be reasonable to create workload to drive CICS, IMS, Db2, MQ, etc., and see at what point ZAPM Connect + CDP croaks.
The sizing exercise should be data driven, i.e., based on SMF/log data from each customer env. where they run this utility (the utility is the ask), and it'll report out - "for x million records/day, you'd need x RAM, x millicores, etc.".

I know there's S/M/L sizing recommendations already but S can mean 1-5 LPAR, L can mean 20-50 LPARs, CICS regions, etc.
Within the L range, there's high variability, and it would be good from a capacity planning perspective to know that with 'x' I can cover 5% of CICS/IMS/etc., with 'y' capacity, I can go to 100%, so that I can look to turn on more data sources/flows piece by piece, knowing the infra can handle it.
I also see that there's HPA and VPA for Telemetry Controller etc., but as I said, it'll be good to know what's needed before we go on the compute/resource acquisition journeys internally.
 

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.