This section explains the settings necessary to monitor errors in applications and operations, and to make discovering the causes easier.
Make error log settings only when instances are created with the initdb command.
When creating instances with WebAdmin, these settings are already made and hence do not need to be set. Furthermore, some parameters are used by WebAdmin, and if changed, may cause WebAdmin to no longer work properly. Refer to "Appendix F Configuring Parameters" for details.
Edit the following parameters in postgresql.conf:
Parameter name | Parameter description | How to enable the settings |
|---|---|---|
event_source | Specify the event source name to be attached to messages, for identifying messages output to the event log when using multiple instances. |
|
logging_collector | Specify "on" to ensure that messages are output by Symfoware Server to the server log file. The server log file is created in the pg_log directory in the database cluster. |
|
log_destination | Specify " stderr, eventlog" to output messages from Symfoware Server to the screen and either the system log or the event log. | reload option of the pg_ctl mode |
log_line_prefix | Specify information to be added at the start of messages output by an instance. This information is useful for automatic monitoring of messages. You can output the SQLSTATE value, output time, executing host, application name, and user ID. Refer to "What To Log" in the PostgreSQL Documentation for details. Example: log_line_prefix = '%e: %t [%p]: [%l-1] user = %u,db = %d,remote = %r app = %a ' | reload option of the pg_ctl mode |
Point
If you want fewer application errors being output to the eventlog, refer to "When To Log" and "What To Log" in the PostgreSQL Documentation for information on how to reduce the output messages.
If you want to separate errors output from other software, refer to "Where To Log" in the PostgreSQL Documentation to change the output destination to the server log file rather than the system log.
