Depending on your system’s data store, there are other ways to access your log data. The following sections review alternative methods to access your log data:
The File channel allows the logging server to log events directly to file in raw format or to translate those events to a human-readable log file.The advantage of using the File channel to log system events is that it can log a large number of events per second; however, it cannot be queried using iManager or Novell Audit Report.
LETrans is a command line utility that allows users to access data logged by the File Channel. Its primary function is to translate raw text log files into human-readable form. However, it also provides the ability to query an ODBC data source on your Windows machine, then translate and format the output.
The LEtrans utility takes no parameters; it is configured using the letrans.cfg file. The letrans.cfg file contains a description of each LETrans configuration option.
To Launch LETrans:
Open letrans.cfg in a text editor. LETrans and letrans.cfg are located in the following directories:
List the path and name of each untranslated log file in the source files section.
Add the path to the log schema file (*.lsc) for any additional instrumentations you are using in the schema section.
Save letrans.cfg, then execute LETrans from the server.
Because Novell Audit logs events to standard systems (MySQL, Oracle, Microsoft SQL Server, syslog, and delimited text files), you can directly access log data using any tool that is standardized to those systems. For example, you can access data in MySQL and Oracle systems using ODBC or JDBC tools. Text files can be opened with a standard text reader such as Windows Notepad or VIM (UNIX) or an application that supports delimited text files such as Microsoft Excel.
NOTE:You can reference the logging applications’ log schema (LSC) files to identify the log data event fields. For more information, see How LSC Files Are Used.