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 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Turbonomic uses APIs. We can contribute to Azure API throttling. How do we manage and minimize this impact.
Many clients have multiple applications using API calls in Azure Subscriptions. Security Apps, Compliance Apps, APMS (like Dynatrace) , Terraform, and our IBM apps - Turbonomic ARM and parkmycloud (PMC). Whilst Turbonomic may not be the main consuming of API Calls the current limit per sub per hour according to Microsoft is 28000. Only they can run queries determining which applications are consuming this 28000. After the 28000 is consumed, no more API calls for that Subscription is allowed.
This can have a negative impact in 2 ways
1) turbonomic has incomplete data to make recommendations. Clients are tracking our recommendations and don't like inconsistency. It reduces trust.
2) other applications start getting errors - and they'll ask for other competing apps to be removed. e.g. a Client asked us to remove Turbonomic from SAP Prod Subs.
Turbonomic API calls to Microsoft should follow Microsoft's recommendations for efficiency - found here -> https://docs.microsoft.com/en-us/partner-center/develop/api-throttling-guidance. Which I'm sure we're already doing.
Are there ways to synchronize Turbonomic's API calls to particular times of the day? Terraform can do their deployments in the morning, and Turbo runs the storage probe in the afternoon?
Can Engineering reduce the number of API calls per hour for certain targets (depending on business value). Can you make this adjustable by the customer in Targets.
Can we actually count the number of API calls we're making so that we can self police - if for instance we're adding a lot of API calls like adding PMC to the mix.
Can we analyze and find out which of our probes or targets are causing lots of API calls and prioritize them by business value? And show that in the tool
I'm not a developer but the process is ALREADY murky because only Microsoft can see the limits and API usage. This is an interesting business problem. What are Microsoft working on to better fix or manage this issue?
I've scoped this to Azure right now - but I'm sure similar things apply to AWS.
Do not place IBM confidential, company confidential, or personal information into any field.