Jul 4, 2013

Java Application Monitoring with Tivoli

Tivoli Management Framework (TMF) is a CORBA-based network management framework from IBM. BM Tivoli Monitoring helps you optimize IT infrastructure performance and availability. here is a high level overview of using Tivoli to monitor Java log files for presence of some text like errors and then raise support tickets at different levels like p1,p2,p3, and p4. The "P" is for prodyction environment and 1-4 are level of importance. Any p1 and p2 level issues need to be attended immediately. The SCIM is used to identify the source of the ticket, and it stands for System, Component, Item, and Module.

Firstly, you need to out put special text in the log to be picked up by the Tivoli.

Step 1: Use log4j to output text like "Monitoring|MyApp|TRADEFORECAST some exception followed ......". Say the exceptions are logged to a log file named myapp.log.

Step 2: The Tivoli config file needs to be configured as shown below with  log file name, regex pattern of the text to search, the SCIM name, queue name, and the ticket level as shown below.

[/local/myapp/applogs/myapp.log;(.*)Monitoring\|MyApp\|TRADEFORECAST(.*);Likely trade Feed Generation Failure]

[/local/myapp/applogs/myapp.log;(.*)Monitoring\|MyApp\|TRADE_LINK(.*);Likely trade Feed Generation Failure.]

"(.*)Monitoring\|MyApp\|TRADE_LINK(.*)" is the regex to look for in the myapp.log file, and "Likely trade feed generation failure" will be highlighted in the p4 ticket raised via the Peregrine ITSM system. Peregrine system is an ITSM (i.e IT Service Management) software. The SCIM is  "APPLICATION/MYAPP/TRADE/ERROR" to identify which system is raising a ticket, and QUEUE1 is the Peregrine system queue name.

Note: Nagios is a very popular monitoring tool and it is an open source tool. It is a network monitoring tool to test availability of servers, applications, etc.



Post a Comment

Subscribe to Post Comments [Atom]

<< Home