Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management and AIOps 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
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.
Peter,
I think we should pivot this to 1 or more support tickets, depending on the number of issues occurring. We need to determine:
Are there performance issues with the API itself, like a poorly optimized query?
Keep in mind testing should be done vs API v3, as v2 will be deprecated soon and v3 already has better performance than v2; this isn't guaranteed to address the reported issue but it might.
If JPMC would like to discuss REST v2 > v3 migration I'm happy to meet for a call
Is the API being evoked sub-optimally? E.g., metadata CRUD functions before devices are fully created & replicated.
Are there issues in the cluster that are interfering with the API being performant?
If so, if there are opportunities to address these issues more proactively next time, we can open Stories and prioritize them in my backlog.
If there are specific errors occurring, what are they? Are those error messages helpful/actionable? If not, we can open one or more defects to address this.
On the issue of device creation and subsequent metadata CRUD for those devices (bullet 2), that's a known nuance that our engineers run into. This item definitely deserves its own Support ticket, asking for a set of best practices (since SevOne knows how to do this). I think a Support ticket will get our customer the enablement they need must faster than jockeying for roadmap priority. Any guidance they receive can be published to documentation.