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 (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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
What you desire is achievable now, in the supported 6.1 and 6.2 releases of IBM Sterling Control Center. :-)
Let me explain.
Control Center emits
- CCTR135I Event insert took too long,
- CCTR137I Event update took too long, and
- CCTR138I Time Event Monitor took to retrieve EVENTS data took too long
events when certain engine property values are exceeded. Settings you are able to change!
So if you'd like to have a CCTR135I event generated if an insert takes more than a minute, you would just need to set an engine property accordingly.
One caveat you should know is Control Center will emit at most one of these events per hour (per thread used to do database I/O).
To affect CCTR135I events, specify the engine property INSERT_EVENT_DB_WARN_TIME and override the default value of 2000.
To affect CCTR137I events, specify the engine property UPDATE_EVENT_DB_WARN_TIME and override the default value of 1000.
To affect CCTR138I events, specify the engine property EVENT_MONITOR_SELECT_EVENT_TIME_WARNING and override the default value of 2000.
The unit for all of these values is milliseconds, so to specify 1 minute you would use 60000.
Note for changes to these engine properties to take effect, you must restart your system.
Thanks for submitting an ehancement request. We need to review this further.