Monitoring the Lookup Manager and ITE applications
SPL standard and specialized toolkits > com.ibm.streams.teda 1.0.2 > Operating applications > Monitoring the Lookup Manager and ITE applications
Your Telecommunications Event Data Analytics applications usally work on huge data sets of streaming data. As an operator you must ensure that the system resources do not deplete and you will have to monitor the system state to ensure your application works properly.
The main resources to watch for are the file system and the system’s RAM.
Before you begin
You set up your system properly, started and initialized your applications. You checked that the applications read your input files and produces the expected output files.
Now input files continuously arrive at your landing zone and your application produces a continuous stream of output data.
Procedure
- Use the Monitoring GUI sample application to continuously check the current state of your application.
- Use the Streams Console to continuously monitor if the file processing is working correctly and to react to congestion states immediately.
- Use system and command line tools, for example, free, vmstat, or top to track memory consumption and react to RAM resource depletion.
- Use system and command line tools, for example, df or du to track file system usage and react to resource depletion.
- Lookup Manager statistics
- For each externally triggered action, the Lookup Manager application writes one or more log entries that include statistics and debug information.
- Lookup Manager error statistics
- The Lookup Manager application writes one or more error log entries if any fault occurs in the separate statistic file <date>_LookupManagerErrorStatistics.txt. These entries are written to a new file every day, and each reported error is a text line in the file.