Search Results for "memory monitor"

Log4db2 is a logging utility for DB2 LUW that uses SQL instructions with SQL PL code. Its purpose is to provide an easy way to write messages from a SQL routine, with the possibility to query these messages directly from the database, allowing to monitor the progression of a process. This utility aims to reduce the time used for developing, testing, debugging and monitoring SQL routines, by centralizing the messages produced by the code. The idea and architecture of this utility...

gcRadar is not a static code anayser but it is a library using which is ment to beused in your source code and it will monitor and report the lifetime events of yuor objects. gcRadar can provide this information by using callbacks, log4j & polling. gcRadar can monitor entities ranging from individula objects to full object trees comprising of is-a & has-a relationships. By using gcRadar you can monitor the lifetime of the objects that are created by your application in runtime, gcRadar enables the application to be aware of the memory constaraints that arise at runtime. ...

The software program (SarBox) parses and analyzes SAR data in charts or text formats. SAR is cumulative activity counters in the operating system. It is the most comprehensive command which helps to monitor performance of various Linux / Solaris subsystems (CPU, Memory, I/O, Disk, Network, etc) all in same log. This makes it difficult to analyze since every counter data is dumped into the log file. SarBox helps to analyze this log file and present data in graphical charts or text format. To collect sar statistics from an environment, use below syntax [user@host ~]# sar -A 30 2 > sar_linux.log “30 2” reports for every 30 seconds and total of 2 times, written in sar_linux.log.

jLlama is a desktop application to monitor servers over SSH. Any figure retrieved from the command line can be polled and graphed in real time. Out of the box, jLlama can graph CPU and Memory usage for Linux and Solaris servers.