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)
Option to add multiple Humio repositories for log monitoring
There are many use cases where there is no single repository for an entire cluster in Humio. Each application/team have their own repository in Humio but the application is running on the same kubernetes cluster (e.g., Production). Instana, right ...
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...
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.
Hello, A few details about this feature.It would be interesting to explore the possibility to connect from our Kinesis Data stream. We currently push logs with Json format via Kinesis to elasticsearch.The idea would be to be able to push these Jso...
Hello, Here is some infos about the request. We highly use custom headers to get contextual informations about HTTP calls . For instance device type, application version etc ..Currently we can filter these informations on the view Application> ...
Hello, Today the feature 'Logs' provide only warning and error log levels.We would find it valuable to also have a log level info because it provides a lot of contextual infos. One thing to point out is that if log levels info would be tracked in ...
"support for multiple ELK instances associated with a technology or Application".The customer is trying to envision what would be the granularity ABSA is looking for (in terms of the mapping: X -> Elk instance).
Do not place IBM confidential, company confidential, or personal information into any field.