[syslog-ng] no compatibility between syslog and mysql log priority more

gatfi sami pfegatfi.sami at gmail.com
Thu Jun 4 16:33:32 CEST 2009

Hi i a successfully configured a centralised syslog server using syslog-ng
2.09 here is the structure:

syslog-client(read mysql error log) -------> *send* to a syslog-relay
--------->* forword* to a syslog server ----> centralise in a mysql tabe

CREATE TABLE  `syslogtopnet`.`log` (
  `seq` int(10) unsigned NOT NULL auto_increment,
  `host` varchar(60) NOT NULL,
  `facility` varchar(40) NOT NULL,
  `*priority*` varchar(40) NOT NULL,
  `*level*` varchar(40) NOT NULL,
  `date_log` date NOT NULL,
  `time_log` time NOT NULL,
  `program` varchar(40) NOT NULL,
  `*message*` text NOT NULL,
  PRIMARY KEY  (`seq`),
  KEY `index_log` (`host`)

my problème is : i find for exemple priority ='*Notice*' and level='*Notic*e'
but in the message i find *[warn]*

here is an exemple:
INSERT INTO `syslogtopnet`.`log` VALUES  (320,'','user',*
'notice'*,*'notice'*,'2009-05-19','19:33:24','','[Tue May 19 19:33:24 2009]
*[warn]* Init: Session Cache is not configured [hint: SSLSessionCache]');
INSERT INTO `syslogtopnet`.`log` VALUES
17:21:02  mysqld started'),
17:21:02  mysqld started'),
Unable to lock ./ibdata1, *error: 11*'),

i discovered that apache log level are different then syslog's so !!!!!

1 wired isnt it lease is there a solution to keep the same level in the
original priority?

2 beside in more than 20589 line in my table priority and level have the
same values. is it normal that the level and priority are the same how can
this be?

thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20090604/6bc1ff2f/attachment.htm 

More information about the syslog-ng mailing list