Is there a way to pull logs for websites hosted in a WAMP system using LEM?

We recently migrated some of our sites to a system running WAMP from a Linux box. We were getting desired logs through LEM before and would like to keep doing it in the new configuration.

Is there a way to get this done?

We are running the most recent version of LEM 6.2.

Thanks in advance.

Vicky Barraza

Find more posts tagged with

wamp

lem 6.2

Logs

apache

Accepted answers

FormerMember

Ah!

The paths of the logs will change so the systems can't really coexist on the same configuration cleanly, but you should be able to do the same monitoring on both Windows and Linux.

One way to do this would be:

Create a connector profile for a Linux webserver that has a good monitoring config
Clone the connector profile and put your Windows webserver in it
Go edit all the configurations to point to the right log files, remove irrelevant ones, and add the Windows-specific connectors

Pro: you do get some of the stuff from the Linux config carried over; Con: you can't actually use it so you still have to go manually change everything.

Another way, more manual:

Make a list of the connectors on the linux config (you can double click on the agent or go to connectors to see what's configured)
Go to the Windows agent and manually configure the missing connectors to the new config

Pro: you don't have to delete/add so much stuff that's different across platforms; Con: you still have do manual config.

Not many great ways to avoid manual config. The big part is that you'll have to chase down the actual paths of the logs you want to monitor on the Windows system, which will most importantly be the Apache logs (possibly in C:\Program Files\Apache Software Foundation\Apache2.2\logs, but you'll have to check).

Covering the Apache logs should cover the A-P part of (W|L)AMP. For the W or L parts, you need to configure Windows or Linux-specific connectors. On WIndows the agent will install with the System/Security/Application Log connectors by default, which should cover most of your bases on an application server. (On Linux you have a little more of an a la carte system, but probably want PAM and a few others) For the M part, I'm not sure what you're monitoring for the Linux side today, but LEM doesn't cover any database auditing for MySQL, but might catch errors in the System log regarding the service, and the Application log regarding critical and error level stuff.

Hope that helps

All comments

FormerMember

WAMP as in windows-apache-mysql-php(perl, etc) or WAMP as in web-application-messaging-protocol?

vbarra

WAMP as in Windows-Apache-MySQL-php.

Thanks.

FormerMember

Ah!

The paths of the logs will change so the systems can't really coexist on the same configuration cleanly, but you should be able to do the same monitoring on both Windows and Linux.

One way to do this would be:

Create a connector profile for a Linux webserver that has a good monitoring config
Clone the connector profile and put your Windows webserver in it
Go edit all the configurations to point to the right log files, remove irrelevant ones, and add the Windows-specific connectors

Pro: you do get some of the stuff from the Linux config carried over; Con: you can't actually use it so you still have to go manually change everything.

Another way, more manual:

Make a list of the connectors on the linux config (you can double click on the agent or go to connectors to see what's configured)
Go to the Windows agent and manually configure the missing connectors to the new config

Pro: you don't have to delete/add so much stuff that's different across platforms; Con: you still have do manual config.

Hope that helps

vbarra

Thanks Nicole, that is what I started trying but for some reason no events show up on the LEM console after the connector is started. I configured the same connector we had for the Linux box, and like you mentioned manually changed the path to the log file. Since there is a file for each day for the apache logs, I went and manually added one to the path in the connector for testing to see if the logs showed up, but they don't.

vbarra

Yes, thanks for the suggestions. I did open a support ticket about this, I will reply to this discussion with more information once I find out the results.