Extra verbose logging in passagepoint

Extra verbose logging in passagepoint

We do not recommend customers enabling the logs unless required.


See attached for log4j2.xml which has all verbose enabled. You can simply remove yours and replace with the attached, then restart.

We have 5 different logging for a different purposes:

  1. Enabling “lime” logs gives extra information for Access Control System (ACS) related activities.

  2. Enabling “zinc” logs gives extra information for hardware-related activities.

  3. Enabling “iodine” logs gives extra information for HL7-related activities.

  4. Enabling “mercury” logs gives extra information for UI-related activities.

  5. Enabling “slate” logs gives extra information for overall features.

  6. Enabling “ruby” logs gives information on schedule task.


“Lime” logs need to be enabled from the Server machine:

Navigate to the “PPGlobal\Tomcat\webapps\pp\WEB-INF\classes” folder.

Open the ‘log4j.xml’ file in any text editor, for example, WordPad.

Add the following text above “<!-- For debugging -->” line and save, and then restart the PassagePoint service:

      <Logger name="lime" level="debug" additivity="false">

         <AppenderRef ref="async"/>

      </Logger>






“zinc” logs need to be enabled on the PassagePoint client machine:

Navigate to the “PPGlobal\Client” folder.

Open the ‘log4j.xml’ file in any text editor, for example, WordPad.

Add the following text above “<!-- For debugging -->” line and save, and then restart the PassagePoint service:

<logger name="zinc" additivity="false">

<level value="debug"/>

<appender-ref ref="async"/>

</logger>


“iodine” logs need to be enabled from the Server machine:

Navigate to the “PPGlobal\Tomcat\webapps\pp\WEB-INF\classes” folder.

Open the ‘log4j.xml’ file in any text editor, for example, WordPad.

Add the following text above “<!-- For debugging -->” line and save, and then restart the PassagePoint service:

<logger name="iodine" additivity="false">

<level value="debug"/>

<appender-ref ref="async"/>

</logger>


“slate” logs can be enabled on both Server as well as a Client machine, depending upon the issue the user is facing:

For Server machine: Navigate to the “PPGlobal\Tomcat\webapps\pp\WEB-INF\classes” folder.

OR

For Client machine: Navigate to the “PPGlobal\Client” folder.

Open the ‘log4j.xml’ file in any text editor, for example, WordPad.

Add the following text above “<!-- For debugging -->” line and save, and then restart the PassagePoint service:

<logger name="slate" additivity="false">

<level value="debug"/>

<appender-ref ref="async"/>

</logger>





“mercury” logs need to be enabled on the client machine:

Navigate to the “PPGlobal\Client” folder.

Open the ‘log4j.xml’ file in any text editor, for example, WordPad.

Add the following text above “<!-- For debugging -->” line and save, and then restart the PassagePoint service:

<logger name="mercury" additivity="false">

<level value="debug"/>

<appender-ref ref="async"/>

</logger>


“ruby” logs can be enabled on both Server as well as a Client machine, depending upon the issue the user is facing:

For Server machine: Navigate to the “PPGlobal\Tomcat\webapps\pp\WEB-INF\classes” folder.

OR

For Client machine: Navigate to the “PPGlobal\Client” folder.

Open the ‘log4j.xml’ file in any text editor, for example, WordPad.

Add the following text above “<!-- For debugging -->” line and save, and then restart the PassagePoint service:

<logger name="ruby" additivity="false">

<level value="info"/>

<appender-ref ref="async"/>

</logger>