Skip to Main Content
Cloud Management and AIOps

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace SevOne
Categories Data Insight (DI)
Created by Guest
Created on Mar 28, 2024

Traceroute Path Tool in LiveMaps | Point-to-Point discovery

We already have a traceroute tool in NMS, which is hardly used. If using the tool in DI Live Maps, you could create logical devices in a path and see which hops between sevone and the device are part of your monitoring.

The concept is you would have "DEVICE-A" where this device is the one you want to traceroute. And then (similar to hop generation) you would generate the path traveled to reach the device.

For each IP and name found you create an unassigned node with the name and IP. (or if the IP exists, fill it with the sevone information!) then proceed to the next IP in the path. If a path fails, you can create a grey logical link at the device node that failed.

This is useful for a troubleshooting standpoint for admins to generate a map of their network, but more importantly, see what devices response looks like to sevone via PING stats.


Another concept is that if you had to SevOne nodes existing in the map, you highlight both of them and generate the shortest path between each item, a way this could be done is in a backend run hops out from both devices until they match the name of their pairs then use that generation to create the link in the map. This wouldnt be traceroute focused more than it would be a procedure that already exists in LiveMaps, just simplified to a point-to-point generation.

Idea priority Low