ERROR

The platform encountered an error, but is expected to recover.

Error events of considerable importance prevent normal execution of a program, but still allow the application to continue running.

For example, a temporary failure to lookup a database.

For example, All critical exceptions such as:

ERR-RST 05 Nov 2019 05:34:50.634 [JobStatisticsEventHandlerDataPullerThread|RestClient.makeRestRequest:860] - Failed to get response. Response Code=500

WARN

Potentially harmful situations for end users or system managers. The situations indicate potential problems.

For example, the platform detected an unusual condition.

For example, an excessive number of clients registered with the server.

Any ignorable Exception

• WRN 05 Nov 2019 05:35:00.009 [PMonitorScheduleTimer|AbstractDBHelper.getTotalDoneCount:1712] - SQL exception : org.postgresql.util.PSQLException: ERROR: relation "pim_12" does not exist

• WRN 05 Nov 2019 05:34:58.393 [PimServerMonitor|ServerMonitorThread.processJobsForNuisanceAlarm:235] - Failed to fetch job nuisance info.

INFO

This is the default logging level.

Messages that provide information about the progress of the application to end users and system administrators.

This level of logging is used for one-time events, such as initialization.

For example,

• IFO 05 Nov 2019 05:04:00.134 [CampaignDirector|CampaignDirector.main:718] - Campaign Director Server IPAddress=10.133.84.49

• IFO 05 Nov 2019 02:18:27.926 [ImportWorker_9|ImportDsJob.processImportJob] - ImportDsJob.processImportJob:2252 - Starting Import with jobId=9

• IFO 05 Nov 2019 02:01:47.763 [ImportWorker_8|ImportDsJob.createHistory2445] - ImportDsJob.createHistory:2445 - Completed Import with jobId=9

FINE

FINE

Only top level methods log at this level.

This level provides generic information to developers who do not have a specialized interest in the specific subsystem.

Includes failures and issues indicating potential performance problems.

For example, doRequest() and doResponse() in a servlet are the main entry points.

Thus, if deemed needed, they can log at this level.

For the service or component, the top level methods handle the application registration and cancellation callbacks from the container.

For example,

• FNE 05 Nov 2019 05:35:08.619 [EventPublisherTask|JobStatisticsEventPublisherManager.EventPublisherTask.run:133] - EventPublisherTask started

FINER

FINER

All public functions of classes log at this level.

These messages provide detailed information about tracing.

For example,

• FNR-RST 05 Nov 2019 05:42:01.988 [Cleanup-Thread|RestClient.getPOMALMServiceStatus:2986] - Sending request to pom alm service for status for IPAddress=10.133.84.49 on Port=8,091

• FNR 05 Nov 2019 05:42:01.347 [PimServerMonitor|ContactAttemptsBO.getPerJobNuisanceCallsCount:2481] - No running job found.

FINEST

FINEST

All classes log at this level.

Classes with private methods that are important for debugging log ENTER/EXIT logs to the private methods with this level.

Classes with public methods that are important for debugging log ENTER/EXIT logs to the public methods with this level.

For example,

• FST-ZNE 05 Nov 2019 05:46:49.552 [ZoneManagementThread|PimZoneDirectorBO.getOrphanedPimDirectorZoneList:357] - UpdateSinceInSeconds=0, CurrentMode=0

• FST-ZNE 05 Nov 2019 05:46:44.548 [ZoneManagementThread|ZoneManagementThread.getMyAllocatedZonesReleasedNow:183] - Entering getMyAllocatedZonesReleasedNow

• FST-ZNE 05 Nov 2019 05:46:44.549 [ZoneManagementThread|ZoneManagementThread.getMyAllocatedZonesReleasedNow:204] - Exiting getMyAllocatedZonesReleasedNow