Log detail can be configured on a per-service basis using the LogsDetail parameter in the general properties section of serverconfig.ini:
[GeneralProperties]
LogsDetail = MappingService:3,FeatureService:3,RenderingService:3,
ResourceService:3
The allowable service entries are:
- MappingService
- RenderingService
- FeatureService
- ResourceService
- SiteService
The detail level is defined as follows:
- Level 0 - Errors without parameters
- This is the default level of detail.
- Errors (exceptions) are logged without method parameters for the specified service.
- Warnings are not logged for this service.
- Traces are not logged for this service.
- Call parameter generation is disabled at this level to improve performance.
- Level 1 - Warnings and Errors with parameters
- Errors (exceptions) are logged with method parameters for the specified service.
- Warnings are logged with parameters for this service.
- Traces are not logged for this service.
- Level 2 - Trace, Warnings, and Errors
- All Level 1 detail, plus traces with parameters are logged for published Service API calls.
- Level 3 - Internal Trace, Trace, Warnings, and Errors
- All Level 2 detail, plus traces with parameters are logged for internal API calls.
Turning on a level 2 or level 3 trace log for all services in a production environment can generate more than 100MB of log information per hour. Disk space should be continuously monitored when the Infrastructure Map Server is run under these conditions.
Nota:
Since the detail level is configurable for each service, the logs can be tailored to debug specific error conditions. For example, tracing the execution of the Resource service is not very useful when you are debugging a database connectivity problem.