# The ColdFusion Logging Page

ColdFusion generates log files you can use to help monitor ColdFusion server activity as well as activity in your ColdFusion applications. ColdFusion generates several different log files, most of which are written to `\Cfusion\Log` on Windows and `/opt/coldfusion/log` directory on Solaris. The Administrator mail error log is written to `\cfusion\Mail\Log` (Windows) and `/opt/coldfusion/mail/log` (Solaris). All log files are written in comma delimited format.

In addition to logging options, the Logging page contains a few other administrative options.

## Administrator email address

When you enter an administrator's e-mail address in the Administrator Logging page, this e-mail address appears with any error messages generated by ColdFusion. This facility can help users report errors. Note that this e-mail address can be overridden in the application framework page, `Application.cfm`.

## Log directory

The default location for ColdFusion log files in Windows is `cfusion\log`. For Solaris, the default location is `opt/coldfusion/log`. You can specify a new location for ColdFusion log files by entering a new value in the Log Directory list box.

## Log slow pages

ColdFusion allows you to track pages in your applications that take longer than a specified length of time to process. You can specify the amount of time ColdFusion allows before writing an entry to the `server.log` file.

## Logging email messages

In addition to system logs, ColdFusion writes a log of errors generated by SMTP mail server used to post mail from ColdFusion applications. You can choose to log warning messages, information messages, or error messages.

In Windows, the mail log file is stored by default in `cfusion\mail\log`. On Solaris, the mail log file is stored by default in `/opt/coldfusion/mail/log`.

| To enable email logging:

1. Open the ColdFusion Administrator to the Mail Logging page.
2. Select the error severity you want and click to enable the Log all email messages checkbox.
3. Click Apply to complete the operation.

## Log files created by ColdFusion

ColdFusion creates nine different log files.

ColdFusion Log Files
Log Filename | Description
--- | ---
    exec.log
| Logs problems with the ColdFusion Server service. If the ColdFusion service hangs or if the service was unable to access the system registry, that information is written to `cfexec.log`.
    rdseservice.log
| Logs errors occurring in the ColdFusion RDS service, which provides file, debugging, directory, and database browsing services for ColdFusion Studio.
    application.log
| Logs every ColdFusion error reported back to a user. All application page errors, including ColdFusion syntax errors, ODBC errors, and SQL errors, are written to this log file. Every error message that is displayed on a user's browser is logged here, along with the visitor's IP address and browser information, if possible.
    webserver.log
| Logs errors occurring in the Web server and the ColdFusion stub.
    schedule.log
| Logs scheduled events that have been submitted for execution. Indicates whether the task submission was initiated and if it succeeded. Provides the scheduled page URL, the date and time executed, and a task ID.
    server.log
| Logs errors that occurred in the communication between ColdFusion and your Web server. This file is meant primarily to help Allaire Technical Support personnel.
    customtag.log
| Logs errors generated in custom tag processing.
    remote.log
| The Network Listener Module (NLM) writes various messages to the `remote.log` file relating to a distributed ColdFusion configuration.
    errors.log
| Logs errors generated in attempts to send mail from ColdFusion applications. Stored in `cfusion\mail\log` (Windows) or `/opt/coldfusion/mail/log` (Solaris).

## Log file format

All ColdFusion log files share the same comma-delimited format consisting of five separate fields as follows:

ColdFusion Log File Format
Field | Field | Description
--- | --- | ---
1 | Severity | "Information," "Warning," or "Error."
2 | Thread ID | Service Thread ID. This information is only useful to Allaire Technical Support personnel.
3 | Date | Date that the error occurred.
4 | Time | Time that the error occurred.
5 | Details | Description of the error (with error number, if appropriate).