Levanta doesn't do much monitoring. It's more of a deployment tool. We use on VM CA's VM:Operator for some automation and message filtering. While this is nice to look at on a 3270 screen, the ops don't look at it - they've got something like 30 LPARs to watch so you can't blame them :). So we're in the process of setting up an interface from VM:Operator into Command Post/Patrol (BMC I believe - if you need the details I can go ask the automation guys here) and the ops will see important things there. We've also got some home grown checking of things like service machines that puts things up on VM:Operator.
For Linux itself, we don't have anything installed on it for that purpose. We do have the Velocity tools set up and it can tell us when file systems get full, linux processes are not running, instances have gone dead, and (I'm hoping) instances are looping. When ops are ready to start monitoring our Linuxes, I will have them pick those messages up and display them on their command post too. There is a group here tasked with standardizing tools, so I suspect some of this might change if they decide to go off and buy something else. That brings up a another question, is anyone using something to monitor DB2 Connect end-to-end? Marcy Cortes Wells Fargo Services -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gene Walters Sent: Tuesday, April 06, 2004 11:27 To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Linux Administration tools Well, Actually, both monitoring and maintenance of the instances. I am trying to figure out where is the best place to spend the money. Is it better to monitor in VM, or linux or both. We basically arent monitoring anthing, and I need to figure out where to start. Thanks Gene > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
