The available logging parameters can be accessed and updated in ArcGIS GeoEvent Manager on the Logs page. However, there may be times when you need more control over the logging capabilities in ArcGIS GeoEvent Server.
The configuration file for managing GeoEvent Server logging capabilities (org.ops4j.pax.logging.cfg) can be found in one of the following locations depending on your operating system.
- Windows—<ArcGIS Server installation directory>\GeoEvent\etc\org.ops4j.pax.logging.cfg
- Linux—<ArcGIS Server installation directory>/GeoEvent/etc/org.ops4j.pax.logging.cfg
Logging properties
Several logging properties for the global log system are in the file as well as each of the configured individual loggers. One general setting to be aware of is ${karaf.data}, which points to the GeoEvent Server data directory, which can be found at <ArcGIS Server installation directory>\data\.
Rolling file appender
The rolling file appender is responsible for creating a log file every time an old one exceeds a certain size. The following properties affect the size and the number of log files stored by GeoEvent Server:
- log4j2.appender.rolling.policies.size.size = 16MB
- log4j2.appender.rolling.strategy.max=10
Individual logger configuration
In GeoEvent Manager, the ROOT logger or individual loggers can have their level configured. Those settings are written to this file. The current settings are presented toward the bottom of the file and have the following format:
- log4j2.logger.<LoggerName>.name=
- log4j2.logger.<LoggerName>.level=
In general, the value for the logger name property will be the same as the <LoggerName> with the underscore replaced by a period. See the following example:
log4j2.logger.com_esri_ges_httpclient_httpclientservice.name = com.esri.ges.httpclient.HttpClientService
The value for the level property can be any one of the available logging levels: Trace, Debug, Info, Warn, Error, Off.
Nota:
The logging level Off is special and is only available in the configuration file. If you set a logger’s level to Off, all messages from that logger will be ignored. This can be useful if you have one or more loggers in your configuration that are writing too many logs, making your logs hard to manage.
For more information on configuring the application logger, see the Debug Techniques - Configuring the application logger blog on the Comunidad de Esri.