A Standalone Data Collector for WebSphere Liberty Monitoring

Beginning with IBM Cloud Application Performance Management, Advanced Private 8.1.4, you can use a standalone data collector to monitor your Liberty profiles running on xLinux, on Bluemix, or both. If you choose the standalone data collector, you can simply skip the installation procedure of WebSphere Applications agent and directly deploy the data collector in Liberty. This data collector provides similar capabilities (resource monitoring, deep-dive diagnostics, and transaction tracking) as the agent embedded data collector.

To deploy a standalone data collector for Liberty monitoring, you will need to download and extract the data collector package that contains all the required data collector files to your local machine and then edit several local files of your Liberty server. Restart the server or re-push it to Bluemix for monitoring to take effect. The next step would be checking the monitoring data on Cloud APM console. The following screenshot shows an overview of the standalone data collector instance within in the Application Performance Dashboard. There is a note-worthy difference when you are browsing data on the dashboards. Data collected by the agent embedded data collector is categorized into the WebSphere Application Server component. While data collected by the standalone data collector is categorized into the Liberty Runtime component.

You can also customize data collection with various properties files. For example, you can enable heap snapshot collection so that the data collector can take snapshot of heap dump at the specified interval. The collected data is displayed in the Heap Dump dashboard, which can be accessed by clicking View Heap Dump on the JVM GC (history) widget. You can also enable memory allocation collection so that the data collector can collect memory allocation information at the specified interval. Then you can check the data in the Memory Analysis dashboard, which can be accessed by clicking View Memory Analysis on the JVM GC (history) widget. Method tracing can also be enabled and you can even set different thresholds for different types of requests. So collection of different levels of monitoring data can be triggered based on your settings.

For more information about using Cloud APM to monitor WebSphere Applications, see Configuring WebSphere Applications monitoring in the Knowledge Center.

1 Like
Recent Stories
Anthem Inc.'s Journey to WebSphere Liberty

Containers and Docker: Why Do We Need POD?

IBM Cloud Private Behind the Scene Blog Series: Kubernetes Architecture