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.
Specific links you will want to bookmark for future use
Configuration option for Tracing of SQL query parameters (PostgresQL)
In certain cases, it would be helpful for us to see the query parameters of a query. We would like to have a configuration option to switch tracing on for specific services or even only database entities. E.g. we are having a concurrent access on ...
It would be great to have some kind of source information always visible for traces/calls.
However it is not always feasible to have the source application instrumented, or even to have an Instana-agent installed on the source host/node.
Our implementation of tracking flows into Db2 for z/OS via JDBC , the Db2 for z/OS and Z Common Data Provider are required. Once installed and configured, we provide metrics (such as cpu_time, smf_id, io_wait, subsystem_id, elapsed_time, lock_wait...
I want to add custom instrumentation to a COBOL/C/C++ process to hook into the call and instrumentations pipeline in Instana enabling end-to-end traceability from our front-end through all the tiers and including the SQL queries in SQL server. In ...
In the tracing view, Instana does not collect any Request Body data/payload on a POST request. Header and Parameters are collected, but not the Body. it would be nice to add the request body so traces become more efficient
The URI of the service called from the screen in the package used by the customer is /cc/claimcenter.do. Currently we cannot check that "which function to call is written in the parameters in the POST".So it will be great to see POST parameters in...
Agent configuration file should support more alternative solutions to hide clear text passwords than HashiCorp Vault.
Security teams in enterprise customers are not approving passwords to be stored in clear text format in agent configuration yaml file. According to the current documentation of Instana, only solution provided to this issue is HashiCorp Vault (http...
Do not place IBM confidential, company confidential, or personal information into any field.