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 (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 updateson 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Monitoring support for ETCD 3.3.x and 3.4.x using /v3 endpoints
As per documentation instana is still using the /v2 endpoint to monitor etcd. /v2-API is deprecated (https://github.com/etcd-io/etcd/issues/12913) Monitoring support for ETCD 3.3.x and newer using /v3 endpoints should be added.
we are running some of our applications in docker containers. We would like to see the name of the running container within the instana "breadcrumb" view. In the VM View we have the same Problem. We can see a number of Redis instances, but we can ...
Modern browsers support network error logging - which is basically the possibilty to sent network issues to a distinct system. The system is to be defined via a header. This allows gathering data about connectivity issues - which is otherwise not ...
When an unusual amount of issues have occured (for an entity) it would be good to assure this boils up somehow. I.e. if CPU usage or memory exhaustion happens more frequently than usual (on a host) the user should be able to be informed pro-active...
Currently it is not possible to add a custom event based on the connectionResets FPM metric. This would be important to us as the limits set by the default "Too many connections reset" FPM event are too low and we would like to customize it.
We're managing multiple instana backends via API configuration. This works for many configuration items. However it doesn't work for Smart Alerts with a daily or weakly seasonality. Seasonality differs per system. While it is possible to recalcula...
We're using redis-cluster to run redundant scaleable redis services. However calls traced by java instrumentation are not mapped to a redis-cluster but to a specific redis instance. This means that redis calls for a specific redis cluster are dist...
Using the Grafana data source for Instana does not allow creating alerts. It would be really useful to be able to manage alerts from Grafana where we already have dashboards with built-in metrics and custom metrics (ie: StatsD).
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...
In the Merge Cluster Plan the wizard does not take the user to the storage actions, desired state, or desired state diameter settings.
When running the the Merge Cluster Plan the wizard misses the options to configure the storage actions, desired sate, and the desired state diameter settings. In other plan configurations these configurations are present in the wizard. This can le...
Do not place IBM confidential, company confidential, or personal information into any field.