I have a Magento website setup on a Linux machine that is based on a Bitnami ready-made image.
The main goal is to be notified by email whenever there might be a potential attack on the site.
My setup:
Ubuntu is also a free OS that is availble to download, making this IDS a totally free appliance for you, except the cost of the computer. There are two ways to install Snort onto a Ubuntu Distrobution and the easiest is to do it through a command line. Snort is a popular open source intrusion detection system (IDS). Learn how to install this security tool and configure it with MySQL on Red Hat Enterprise Linux 5. This is also applicable to Red Hat Enterprise Linux 4, CentOS 4 and 5 and Fedora Core 5 and 6.
To achieve that I decided to install Snort IDS and email the alerts coming to the syslog using Swatch.
I’ve installed snort by following this tutorial from Snort’s official website.
I've just finished section 9 of that tutorial which means:
Next to allow Snort to log alerts to syslog I've uncommented this line in the snort.conf file:
Hands Of The Ripper Soundtrack (by Christopher Gunning) Dracula: Classic Scores From Hammer Horror (by James Bernard, Christopher Gunning, David Whitaker) Agatha Christie’s Poirot Soundtrack (by Christopher Gunning). View credits, reviews, tracks and shop for the 1992 CD release of Agatha Christie's Poirot on Discogs. Christopher gunning hercule poirot downloads.
I’ve tested the installation by running this command:
While Snort is running I’ve made a ping request from another system.I can see alerts registering in Snort’s log file but nothing was added to the syslog.

Trail and errors:
Run snort as user root.
Set syslog to bounce logs to another server (remote syslog).
I don't have great deal of experience with Linux so any help to point me to the right direction will be very much appreciated.
JakeGouldI've posted this question on linuxquestions.org aswell and got an answer.
Following unSpawn reply I've reviewed the rsyslog conf files and found that auth logs are sent to the auto.log file.Which led to a quick fix of adding an additional .conf file to /etc/rsyslog.d with the content:
Also as suggested I've made some changes to the snort execution command (omitting the -q -A console):
after restarting the rsyslog service I found the missing Snort alerts in syslog.
I don't have great deal of experience with linux so any help to point me to the right direction will be very much appreciated.