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.
Thank you for the suggest to use the agent API to push metrics in, and yes, if we either had or defined a custom shell script that would stay in a while loop, with a timer, to publish the metrics every second/minute/hour then yes, we could basically run the free command, parse the output, format to the api metric publish method, then repeat.
The idea is that the agent, since it already has a timer, process and communication context, it must since it is running the process to use sigar, is to open that interface so that we can inject a custom shell/batch file. This has several relative reason, getting the free metrics in the same time slices as the CPU or other OS level methods, when the agent starts/stops/installed/uninstall the logic goes with it and won't run with the agent present. Lastly communication management, on reading it appears that the suggestion is to open the connection and leave it open and also do the recovery on the connection. If the logic/process was the agent itself, that would already be present and durable.
Would this work to achieve the goals
https://www.ibm.com/docs/en/instana-observability/current?topic=apis-host-agent-rest-api