This is the public portal for all IBM Z Hardware and Operating System related offerings. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
As a development shop we have a number of users testing Web Services APIs on the HMC. Some of these APIs are known to cause lockouts of the SE (such as those in Perform Model Conversion) - both changes and queries.
We need a central place to audit who is doing what and when. The HMC provides "Manage Web Services API Logs" but that is limited to the Web Services user who issued the API call. This becomes a problem with multiple userids and passwords. We want ACSADMIN or some other userid to have access to all API logs.
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.
z14 and later SEs and z15 and later HMCs have the ability to forward a variety of log data to any centralized log server that supports the syslog protocol (RFC 5424), such as QRadar, Splunk, etc. One type of data that can be forwarded is the web service API log data. When this is done all web service log data is forwarded to the log server where it can be analyzed and viewed for all systems in the enterprise rather than just a single system. With this support in place we do not see a need to provide a way to view the same type of data scoped to a single HMC or SE. Other types of logs can also be forwarded to a central server, so that a more complete picture of what was happening where can be seen, which can help provide insight into what things might be interacting (favorable or unfavorably) with each other.
Thank you for your input.