Legacy log format
Learn about the
VIP Enterprise Gateway
legacy log format.The legacy format for
VIP Enterprise Gateway
log files is tab-delimited and can be customized. The
vipegconsole
and the server logs use the following format for their entries:LogLevel DateTime ClientIP Component [SessionID] TransactionID ErrorCode \ Message [ThreadID] [SourceClassName]
The message component has the following format:
"[actor=who,][text=some message,][op=x,][tid=y,] [user=user1,]\[nameX=valueX]"
Component | Meaning |
|---|---|
LogLevel | One of DEBUG, INFO, ERROR, AUDIT, WARN |
DateTime | Double-quoted string in the following format: "yyyy-MM-dd HH:mm:ss.SSS ‘GMT’Z" |
ClientIP | Numeric client IP address (in IPv4 format) of the original request. This value should not be a host name. If no client is involved for logging, the application should set the value to 0.0.0.0. |
Component | The name of the software module that creates the logging. For example: ValidationServer. |
Session ID | A numerical string that uniquely represents the session at which the log is created. The component is optional and applies only to the vipegconsole log. |
TransactionID | An identifier for an operation that may involve multiple logging events. This value is optional. If the value does not apply to the application, the application should set the value to ‘0’. |
ErrorCode | Decimal error code. |
Message | Comma-delimited name-value pairs with predefined names. Each name-value pair is optional, but there must be at least one name-value pair. |
See the following topics for details about working with the log file components: