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.
Specific links you will want to bookmark for future use
The minimum evaluation granularity for a smart alert is limited at 5 mins, We need to change it so that we get alerts related to slow calls etc which may not persist for more than 5 minutes. Below is a real time scenario.
When will a person be alerted if a sql running for more than 2 seconds like for example 10 seconds etc. will persist for 5 minutes interval. In a real world scenario, there can't be a sql running for 10 or 15 seconds persist for a 5 minute interval. Which in case, we will never be alerted. Sql runs for 30 to 40 seconds, users will have problem as application don't get a timely response on its sql's from the databases and DBA's will never be alerted on sql's running for a long time. Because the condition for persistence granularity is 5 minutes. And there should be a way to change this number to a smaller one so that we get alerted as soon as there is a sql running for 25 seconds or 40 seconds, we get alerted and we can take timely action on troubleshooting.
Hope you understand the scenario. Question is on the time threshold on when we want to be alerted as evaluation granularity needs to be custom number like 1 min or 30 seconds or something. No sql in the database that is running will persist for more than 5 mins, And with thousands of sql's running, application will crash if this ever happens.
Do not place IBM confidential, company confidential, or personal information into any field.