Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Operations Management
Product - Tivoli Application Dependency Discovery Mgmt (TADDM)
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Operations
Product - Tivoli Application Dependency Discovery Mgmt (TADDM)
#publish
Please confirm below understanding on the "Discovery Summary" details:
1. Number of Discovery Servers Used : We understand, this is the count of different TADDM discovery servers used for selected discoveries.
2. Number of Discovery Sessions Started : This is the total count of session sensors triggered for all the selected discoveries.
3. Number of Devices Discovered : Here, by devices do you mean the app servers, storage devices, database servers or component type ? If yes, then this count will give the total number of component types for all the selected discoveries.
4. Number of Profiles Used : This is the total count of discovery profiles used in selected discoveries. Here, Our assumption is that you are referring to the "distinct" profiles being used.
5. Number of Sensors Used : This is the count of all the sensors triggered in selected discoveries. Here, Our assumption is that you are refering to the "distinct" sensors being used.
6. Number of Sensors Discoveries Started : What is difference between this metric and point 5 metric (Number of Sensors Used)? Is only difference that here total count of sensors is being referred, i.e. repeated sensors also counted.
7. Number of Sensors Discoveries Succeed: This is the count of all the sensors which executed successfully for all the selected discoveries.
8. Number of Sensors Discoveries Fail : This is the count of all the sensors which are not successful, i.e. have reported errors. (warnings are not considered in this count)
9. Number of Sensors Discoveries Warnings : This is the count of all the sensors which have reported warnings.
10. Number of Events : What do you mean by events here ? Does it mean the different error types like Timeout Issue, Connect Issue or Storage Issue ?
Please confirm below understanding on the "Discovery Summary" details:
1. Number of Discovery Servers Used : We understand, this is the count of different TADDM discovery servers used for selected discoveries.
2. Number of Discovery Sessions Started : This is the total count of session sensors triggered for all the selected discoveries.
3. Number of Devices Discovered : Here, by devices do you mean the app servers, storage devices, database servers or component type ? If yes, then this count will give the total number of component types for all the selected discoveries.
4. Number of Profiles Used : This is the total count of discovery profiles used in selected discoveries. Please confirm, if you are referring to the "distinct" profiles Only being counted here in this metric.
5. Number of Sensors Used : This is the count of all the sensors triggered in selected discoveries. Please confirm, if you are referring to "distinct" sensors be only counted here in this metric.
6. Number of Sensors Discoveries Started : What is difference between this metric and point 5 metric (Number of Sensors Used)? Is only difference that here total count of sensors is being referred, i.e. repeated sensors also counted.
7. Number of Sensors Discoveries Succeed: This is the count of all the sensors which executed successfully for all the selected discoveries.
8. Number of Sensors Discoveries Fail : This is the count of all the sensors which are not successful, i.e. have reported errors. (warnings are not considered in this count)
9. Number of Sensors Discoveries Warnings : This is the count of all the sensors which have reported warnings.
10. Number of Events : What do you mean by events here ? Does it mean the different error types like Timeout Issue, Connect Issue or Storage Issue ?
Attachment (Description): Feedback
Adrian, so that we can get a better clarity on the needs you have, can you please tell us what types of errors you look for, and/or how a error is recognized? The initial thought is, if there is a way you needs could be addressed by a diagnostic utility that transverses the data looking for key indicators.
In addition, I have split the RFE into 3 new RFE's, dividing down your requirement into individuate requirements, to making reviewing and tracking the requirements easier. All 4 RFE's are associated to the same dW RFE ID, but you may not see the new internal numbers reflected. As a note, the new RFE numbers, in addition to this one, based upon your original order are as follows: (2) 87690, (3) 87691, and (4) 87692.
Attachment (Description): Screenshot with enhancements applied