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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Alerts need to have the option to set a consecutive number of ocurrences for a check before it alerts. This is an option present in other monitoring tools and prevents a lot of false alerts.
Example being number of connections, we have an threshold set for 900, but occassionally the application will spike on connections and it will go above 900 for a few minutes. That does not reflect any real issue that needs an alert/notification. If we could set it so that number of ocurrences was something like three, it would take three consecutive checks (which would combine with the "Collect data every (minutes)" setting) to alert. So only trigger an alert if the number of connections is high for fifteen minutes (or more).
Without this feature, the alerts from the Db2 Data Management Console are almost worthless as they are too sensitive. A short-lived spike in a metric is not an issue, and can be completely depenent on exactly when a person checks the data. CPU is another good eample, it can easily spike high if you check and exact right moment, and then immediately go back down. Having a number of occurences option makes alerts usable and actionable.
Do not place IBM confidential, company confidential, or personal information into any field.