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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Hi @SRIDHAR Venkatesh
We had a look into this and it looks like what customer is expecting are the below,
1. Details of long running / hung threads
2. Provision to kill those threads.
Incase of #1, This is not supported by the Sensor the way we are collecting data as of now.
But before making a conclusion, would like to get more details on the requirement. Had seen the following in the 'Field Feedback' tab.
"This is part of an ITCAM to Instana conversion. They are running ITCAM for Diagnostics and see Gaps in Instana which are causing them to stop the conversion".
So will it be possible to get some details around what all details as mentioned in the requirement are they seeing in ITCAM.
Incase of #2, we don't have a provision to kill specific threads of the JVM we are monitoring and not sure if it is even achievable by an agent that attaches to JVM.
Although generating thread dumps is something we already have the capability for. Please see the screenshot below.