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.
Hi Ryan,
Our /v3/devices/list endpoint is capable of filtering down to 1 or more devices and can return the IPS information. This API is how we surface IPS info for devices in the DI Device manager, but as you point out, we can't view that data over time or even as a table in reports.
We could consider storing this information as timeseries for recall in graphs, etc., but there are some concerns doing so for very small devices like ICMP only devices. Adding this single metric would be jarring because we'd need to create an additional object type under a different plugin, making it no longer ICMP only. There are additional implications that we would then need to address with automation of device type license classification, which would also affect CoC (Cross object Calculation) devices too. We could consider adding this to our roadmap, but if we did it would likely require a user to turn it on so that edge cases like this can be avoided when not desired. Another consideration is that we might only update these metrics every 2 hours during data rollup, as doing so every polling cycle might be overkill.
I would like your feedback on this before I close the idea to ensure that's the type of outcome you're looking for, whether you have any thoughts of the potential impact this could cause in object/indicator bloat to smaller devices, as well as whether you have strong need for this information being updated every poll cycle vs every 2 hours when shortterm data is aggregated.
In the meantime, one workaround might be to use automation to periodically query the /v3/devices/list endpoint to populate a new object/indicator using the xStats/deferred ingestion pipeline, or export it wherever you'd like
Overall, I think this is a good idea if we can figure out a way that minimizes undesired object/indicator bloat for smaller devices.
Regards,
Ryan Wilson, Senior Product Manager