Logging
AMPS supports several different types of log formats, and multiple targets can be defined simultaneously.
For details on logging, including a cross reference to the types of message and a breakdown of the format AMPS uses in log messages, see the Logging section of the AMPS User Guide.
The following table lists the configuration elements that apply to all logging protocols:
Element | Description |
| Define the logging target protocol Valid values: |
| Defines a lower bound (inclusive) log level for logging. All log messages at the specified level and up are logged. A production server should be configured to log at Valid values: |
| A comma separated list of specific log levels. Only log messages at the specified levels will be logged.
This element can be used with the Valid values: |
| Additional errors that should be included when logging. If an error appears in this element, it will be logged regardless of the level of the error. There is no default for this option. This element accepts a comma-delimited list of error numbers. You can also provide a regular expression that matches a set of errors, such as |
| Errors that should be excluded when logging. If an error appears in this element, it will not be logged regardless of the level of the error. There is no default for this option. If the same error appears in both This element accepts a comma-delimited list of error numbers. You can also provide a regular expression that matches a set of errors, such as |
AMPS logging is always opt-in. That is, no messages are logged to a target by default. Logging must be explicitly requested using the configuration elements above.
The following tabs list information that is only relevant for specific protocols.
Element | Description |
| File to log to. If the protocol is gzip, then Required for Default: |
| Log size at which log rotation will occur. See Byte Units for details on specifying file size. |
Last updated