Skip to Main Content
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
  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 (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.

Status Future consideration
Workspace SevOne
Created by Guest
Created on Feb 24, 2026

There should be a v3 API endpoint to run a ping command from any peer to a device

The ability to specify a specific peer to ping an arbitrary device by id, name or management address would be helpful for process automation, particularly for very large scale SevOne clusters.

It's not clear what part of the API schema it should be under - /api/v3/devices seems to deal with reading or editing device data, so it probably is not that. The client that requested this feature uses /api/v3/metadata/devices/snmpwalk to run a SNMP walk from peers to a specific device - perhaps there could be a /api/v3/metadata/devices/ping endpoint.

The payload should include the ability to specify which peer, by ID, to run the ping command from, so that the specific peer to run the ICMP ping request from is preserved when sending the API call to the cluster leader, or through a load balancer.

Idea priority Low