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>


    • Related Articles

    • HL7 NON-verbose logging

      If PasasgePoint's HL7 logger is set to verbose, to remove verbose logging, replace log4j2.xml on your server with attached log4j2.xml, then restart the passagepoint service.

    • HL7 verbose logging (prior to 6432)

      To turn on Verbose logging for HL7 Rename your current log settings to log4j_old.xml Replace with attached log4j, then restart the passagepoint service.

    • HL7 verbose logging (6432 and higher)

      To turn on Verbose logging for HL7 Rename your current log settings to log4j2_old.xml Replace with attached log4j2.xml, then restart the passagepoint service. Once restarted, all HL7 messages are then logged to the "services.log" file ***NOTE*** ...

    • PassagePoint's web Module

      PassagePoint web Module allows a user to pre-register visitors ahead of time. The authentication method can be 1) SSO through IIS NTLM (single sign on) When using SSO, a user clicks on the passagepoint website links and is logged on to the web module ...

    • Acuant scanner IDscan logging

      Create cssnlogdir older at the root of the c drive once created, do a normal scan in passagepoint and when a failur happens, send support the cssnlogdir. ***NOTE*** folder can get quite large, so only do this for a short amount of time