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.

ADD A NEW IDEA

Clear

Ideas

Showing 96 of 6110

Provide level WARN for Docker version of Instana agent

In https://www.ibm.com/docs/en/instana-observability/current?topic=requirements-installing-host-agent-docker#installation INSTANA_LOG_LEVEL does not provide the level WARN. I guess this is an issue and should be added. Esp. for consistency.
over 2 years ago in Instana / Logging 1 Planned for future release

Provide enhancements for Splunk Integration

It’s nice to see we can navigate to Splunk directly from Instana however I still see some enhancements can be made like below, Support of custom names for field names for PODs E.g: As per Instana the POD name key will be kubernetes.pod_name howeve...
over 2 years ago in Instana / Logging 0 Future consideration

Support for jboss logging version 3.4.1 without programmatic API

For making the JBoss deployment lighter, and for reducing downtime while deployments, we consider that using jboss logging is more convenient than log4j. Unfortunately, this logging framework is not supported by instana (see case #30712). So then,...
almost 3 years ago in Instana / Java / Logging / Tracing 3 Functionality already exists

Resource state at node start time

The original state of a resource (when a node first comes online or a domain comes online) is treated differently to a monitor command returning 0 (unknown) or a monitor timing out.With this running resources are stopped, whenthere is a dependency...
about 12 years ago in Tivoli System Automation 2 Not under consideration

SA-MP Support of concurrent LVM on AIX

We urgently needs the support of concurrent LVM on AIX
over 12 years ago in Tivoli System Automation 2 Not under consideration

Add (java) context to logs

We're currently writing java logs with logback/slf4j. Using the logstash ArgumentsJsonProvider in our logback.xml this allows us to extend the log message with context information like stack_traces, logger_name, log level but also custom informati...
about 3 years ago in Instana / Logging / Tracing 3 Functionality already exists

Custom keyword for ELK

I would like to have the possibility of changing the keyword that Instana uses when redirecting to Kibana The problem is that Instana uses keyword that Kibana does not find, so when redirecting no machine is found.
over 3 years ago in Instana / Logging 1 Not under consideration

Improvements for state "Stuck Online"

Today, we have very limited possibilities to operate a resource with state "stuck online". There are two functions that should be improved:1. a resource stays in "stuck online" if the stop request is canceled and the desired state isn't "offline" ...
almost 14 years ago in Tivoli System Automation 3 Not under consideration

enhancements in DASH tables/tree-tables

Part #1:Provide the ability to set the default domain entry of a system automation table to empty/not_set/no_domain or something like this.The table should then display no data until a subscribed NodeClickedOn event from another table occurs.Part ...
over 10 years ago in Tivoli System Automation 3 Not under consideration

creating a Domain should not automatically switch on ip_forwarding

creating a TSAMP-Domain causes unasked ip_forwarding to "on" even though it is not necessary if CG(s) are all in the same subnet. RSCT needs the function "Loose Source Routing":A simple answer for now is that RSCT uses LSR to deal with communicati...
about 11 years ago in Tivoli System Automation 2 Not under consideration