Sponsored Content
Full Discussion: Central Logging
Special Forums UNIX and Linux Applications Central Logging Post 302284418 by otheus on Thursday 5th of February 2009 12:39:48 PM
Old 02-05-2009
Is this still an active question?

My main thoughts were that your choices are to either make it partially relational, fully relational, or do no relations. Partially relational would have relations for:
  • hostname
  • log facility
  • log level
  • date/time
and the text of each log message is stored. Fully relational would have all messages stored in a unique table.

Doing this in perl would be easy, but probably a better way would be to take the syslog code and just modify it to interact directly with Oracle.

A great OSF project would be to do this and for max flexibility, allow the configuration to specify the SQL statements for all the inserts.
 

8 More Discussions You Might Find Interesting

1. Red Hat

Central Syslog

Hello, Does anyone have any suggestions for a central logging solution? We have several different environments. (dev, fit, prod) I think I've settled on using rsyslog but I'm not sure on best practice. Should I tier the logging? Is a database required? etc... Any suggestions? :confused: (1 Reply)
Discussion started by: dwells
1 Replies

2. Filesystems, Disks and Memory

Central Backup Server

Hi , I have several Linux Servers , and now i want to run a Central backup server. . I'm looking forward finding an enterprise solution for this affair . there are different types of data on this servers, like : Mysql databases , mail server, web server , Cacti and MRTG graphs , ... I find some... (1 Reply)
Discussion started by: nasser
1 Replies

3. AIX

How to create - Central access printer..

Guys, Totally new to this... I have asked to create a Central access printer to an AIX Server.. Spoolserver : SapErpDev_DEV_00 Host : SapErpDev IP : 172.30.1.17 Device type : HPLJ4 Printer model - HPLJ 4 : HP laserjet 4 series PCL - 5 Question.. From my understanding, I... (3 Replies)
Discussion started by: mushr00m
3 Replies

4. UNIX for Dummies Questions & Answers

Help with central syslog

Hi, I want to collect all syslog messages from thses servers to a central syslog server and store them in seperate files. I created new Redhat server to collect all the system logs, from Linux, Windows and Cisco to this new server. For example: syslog messages from server NY01 >... (4 Replies)
Discussion started by: samnyc
4 Replies

5. AIX

Fix central firmware download

Hello, i'm a french IT student, not very fluent in English. I'm trying to download firmware updates on IBM website but they asking a serial number of a server under warrenty or maintenance. But i have a personnel server for learning, training, etc... and its not under IBM warrenty or maintenance... (4 Replies)
Discussion started by: Tharsan
4 Replies

6. Red Hat

Central authentication server

Hi guys In the firm we are running Windows and Linux server. Currently all servers are using the same usernames and password and from my opinion is we are running bad and non secure practice. I was looking some documentation and I think best solution is to use SAMBA/LDAP/Kerberos to act as... (5 Replies)
Discussion started by: solaris_user
5 Replies

7. Linux

Syslog not logging successful logging while unlocking server's console

When unlocking a Linux server's console there's no event indicating successful logging Is there a way I can fix this ? I have the following in my rsyslog.conf auth.info /var/log/secure authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies

8. Solaris

Configuring central logging server for network devices

Hi I am very well aware of configuring central logging (syslog)server on solaris to capture logs of other solaris servers. But don't know how to capture the logs of network devices like Juniper , cisco etc on solaris server. Is this possible through syslog server of solaris. Is there any way we... (1 Reply)
Discussion started by: amity
1 Replies
syslog.conf(4)						     Kernel Interfaces Manual						    syslog.conf(4)

NAME
syslog.conf - syslogd configuration file SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h. See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See /usr/include/sys/syslog_pri.h. The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An asterisk (*) causes a message to be sent to all users who are currently logged in. DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify more than one facility and its severity level by separating them with semicolons. You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section. The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab characters. If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com- mand: # syslogd -f config_file Daily Log Files You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax: /var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre- ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory. To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory. EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary # priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys- log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug /var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg * FILES
/etc/syslog.conf /etc/syslog.auth - Authorization file for remote logging. /usr/include/sys/syslog_pri.h - Common components of a syslog event log record. RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8) System Administration delim off syslog.conf(4)
All times are GMT -4. The time now is 04:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy