Now you can pull OS Metrics history with BiWhy from your hosts with the SAP Host Agent installed and zoom in on problematic areas.
By default, the SAP Host Agent keeps history for 31 days.
OS Metrics include about 50 metrics for CPU, memory, network, disk, files, and VM.
Problem:
The customer does not provide OS-level access and lacks OS monitoring solutions, yet you still need to conduct due diligence to gather as much information as possible to add value.
Solution:
We monitored BOBJ hosts with BiWhy:
CPU: While the customer planned a 20% CPU upgrade following the system upgrade, we demonstrated that the current CPU usage is minimal, with almost no load on the Tomcat servers.
Memory: Although there were no reported issues regarding memory or any other system malfunctions, we identified that the free memory on the hosts drops to nearly zero due to scheduled AO workbook executions.
BiPrecalculation.exe consumes memory and almost never releases it, leading to high memory usage.
3274298 - High memory consumption of BiPrecalculation.exe
Problem:
Occasionally, we need to run scripts at the OS level to monitor the number of open connections, errors, the presence of certain classes in a Java process, etc.
Of course, you can write a script, run it in a loop, output the results to a file, collect the file, and import it into another tool...
Solution:
Run commands directly in BiWhy, immediately analyze the output in tables and charts, and save it for future analysis.
