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)
ITNM SNMP poll definition should allow setting specific index
When trying to snmp poll for e.g. a routing engine teperature index it resulted that it is not possible to query directly from the basic threshold policy on an indexed OID like 18.104.22.168.4.1.2622.214.171.124.126.96.36.199.0.0. It is only possible to poll for the whole OID 188.8.131.52.4.1.26184.108.40.206.1.7 (&SNMP.VALUE.jnxOperatingTemp) and then try to filter. However this is only possible in advanced definition in General Threshold and not in Basic Threshold. This makes it impossible to store the historical data for specific components monitored as only Basic Threshold enables it. Even then Basic Threshold would force us to store all data from all indexes under main OID which is not scalable and difficult to maintain. It also generates a problem when displaying alerts (there is just an index ID) as we don't want to monitor all objects but a selected ones. It should be possible to configure the indexed OIDs with both Thresholds so enable selcting specific data.
Do not place IBM confidential, company confidential, or personal information into any field.