Logging Section - trillium_geolocation - 15.21

Trillium Geolocation Reference

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Geolocation
Version
15.21
Language
English
Product name
Trillium Geolocation
Title
Trillium Geolocation Reference
Copyright
2023
First publish date
2017
Last updated
2024-07-17
Published on
2024-07-17T14:48:30.219520

The Logging section is not required, but if it is included it must have the name [Logging]. Only one Logging section can be specified in the configuration file.

The Logging section specifies how much information is logged during processing and where it is logged to. It also allows the format of the logging output to be customized.

The table given below describes the keys available in the Logging section of the configuration file

Table 1. Logging Section

Key

Description

File name

The name of the file to which information is logged. The default is gaserver.log.

Level

 

Denotes the level of logging to report. Available levels are:

  • Critical - Records all events that cause critical server failures, such as memory failure or data file inconsistency.
  • Error - Records all events that cause a command process to cease but do not cause a server failure.
  • Warning - Records all events that cause no errors but are outside normal working parameters, such as a command receiving invalid data from a client.
  • Info - Records general server information.
  • Session - Records all command information relating to client sessions, including the command performed and the client’s IP address.
  • Descriptors - Records all textual description requests.
  • Options - Records all option retrieval and setting activity.
  • Data - Records input and output contact information for all name and address processing functions. This should only be used for debugging purposes, as a log file can quickly become extremely large when this level is activated.
  • Debug - Records full debugging information, including function calls and parameters. This should only be used in response to a request from the Precisely customer support team.
  • All - Includes all of the above options.

LogToScreen

A yes/no value that specifies whether or not to write information to the command line.

LogToFile

A yes/no value specifying whether or not to write information to a log file.

MaxSize

The log file’s maximum byte size. Once this limit is reached, logging continues at the beginning of the file, overwriting important versioning information at the top of the file. During testing, set the MaxSize to the largest practical size, up to a maximum of 2Gb. The default is 10Mb.

TimeStamp

Specifies the format of the timestamp to use within the log file. The default format is '%X %x' (date representation for current locale followed by time representation for current locale). Possible values are:

%a - abbreviated weekday name

%A - full weekday name

%b - abbreviated month name

%B - full month name

%c - date and time representation appropriate for locale

%d - day of month as decimal number (01 – 31)

%H - hour in 24-hour format (00 – 23)

%I - hour in 12-hour format (01 – 12)

%j - day of year as decimal number (001 – 366)

%m - month as decimal number (01 – 12)

%M - minute as decimal number (00 – 59)

%p - current locale’s a.m./p.m. indicator for 12-hour clock

%S - second as decimal number (00 – 59)

%U - week of year as decimal number, with Sunday as first day of week (00 – 53)

%w - weekday as decimal number (0 - 6; Sunday is 0)

%W - week of year as decimal number, with Monday as first day of week (00 – 53)

%x - date representation for current locale

%X - time representation for current locale

%y - year without century, as decimal number (00 – 99)

%Y - year with century, as decimal number

%z, %Z - time-zone name or abbreviation; no characters if time is unknown

.