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 updateson 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
Monitoring, Alerting and Reporting capabilities not available
Monitoring: The only way to investigate the status/traffic of a specific connection is accessing the Event and Audit log files located in the SSP server. This has a deep impact on the usability of the product making the operation activities of Support team extremely hard.
Alerting: No Alerting capability is available. it should be possible to setup Alerts on errors happening in SSP (i.e. Authentication Errors, Network Connectivity, etc... ) to allow a proactive monitoring/support.
Reporting: It is not possible to run any KPI report (standard or custom) on SSP traffic (i.e. number of connection per hour/day/week at user/adapter/engine level)
These functionalities should be available in Configuration Manager or SSP should be integrated with Sterling Control Center.
Control Center Monitor can monitor SSP (Secure Proxy) server as well as configurations. This is true but what i am actually looking for is CCM does not have the ability to monitor the actual logs that we see on proxy servers "/opt/SSP/logs/secureproxy.log and perimeter.log
Do not place IBM confidential, company confidential, or personal information into any field.