Applications Systems

Enable and collect WPM Player Debug logs

This article provides steps on how to enable and collect WPM Player logs on DEBUG level when the issue is related to failing playback of a transaction. Depending on where the problem with playback occurs (Orion Server, Additional Polling Engine or WPM Player machine) collected diagnostics should be always on DEBUG log level and should contain logs from the moment when the transaction failed or the issue with transaction occurred.

First published date

11/12/2018 12:09 PM

Last published date

1/6/2022 12:52 PM

Overview

This article provides steps on how to enable and collect WPM Player logs on DEBUG level when the issue is related to failing playback of a transaction. Depending on where the problem with playback occurs (on the Orion Server, an  Additional Polling Engine, or WPM Player machine) collected diagnostics should be always on DEBUG log level and should contain logs from the moment when the transaction failed or the issue with transaction occurred.

To learn more about WPM logs, see Troubleshoot WPM.

Product section

Web Performance Monitor

Resolution

  1. (Recommended) Unmanage all other transactions from that WPM location or move the transaction you are troubleshooting to a new location that has no transactions.
  2. Clear the WPM log directory: C:\ProgramData\Solarwinds\Logs\SEUM\.
    Remove all log files and subdirectories. Diagnostics will be smaller and simple to investigate.

    NOTE: Skip any files currently in use by WPM, if prompted.
     
  3. If the transaction is assigned to Orion Server or an Additional Polling Engine which was assigned as a WPM location:
    1. Run the LogAdjuster application from the player location by right-clicking on it and selecting Run as administrator.
    2. Set under WPM section the DEBUG logger level for:
      • Agent Worker
      • Agent Worker – Browser
      • Agent Worker – Player
    3. Set for above loggers:
      • File size: 50MB
      • # of files: 50
    4. Click Apply.
  4. If the transaction is assigned to a WPM Player machine:
    1. Run the C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\LogAdjuster.exe application from the player location by right-clicking on it and selecting Run as administrator.
    2. Set under WPM section the DEBUG logger level for:
      • Agent Worker
      • Agent Worker – Browser
      • Agent Worker – Player
    3. Click Apply. 
    4. Run as administrator Notepad.exe process and open the following .config file:
      C:\Program Files(x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Worker.exe.config

      NOTE: Create a backup of the .config file outside the SolarWinds directory.
       
    5. Edit logger attributes:
      • maxSizeRollBackups and set it to 50
      • maximumFileSize and set it to 50MB

        The edited attributes should look like this: 
        <maxSizeRollBackups value="50" /> <!-- Default value is 10 -->
<maximumFileSize value="50MB" /> <!-- Default value is 5MB -->


        NOTE: Use CTRL+F to find them.
    6. Save the .config file.
  5. Wait an hour (be sure that the transaction failed during that time).
  6. Verify the following logs are in DEBUG:
    C:\ProgramData\Solarwinds\Logs\SEUM\AgentWorker.logs
  7. Run WPM Diagnostics from OS Start Menu or from C:\Program Files (x86)\SolarWinds\Orion\SEUM\ SolarwindsDiagnostics.exe, and collect diagnostic to send to us.
  8. Turn off DEBUG in LogAdjuster.exe for WPM (use "Reset to default" button and then Apply).
  9. Export the recording with which you have an issue to a file. You can use WPM Recorder for it (File->Export).

    NOTE: If you encrypted a transaction with a password, provide the password to Support.
     
  10. Capture the Transaction Details view in Orion Web Console by printing it to a PDF. Click Ctrl+P and then select Save as PDF as the Destination.

    NOTE: If you cannot save to a PDF, capture a screenshot of the entire Transaction Details view in the Orion Web Console with another method.
     
  11. Create a single zip that includes:
  12. How to gather and send a diagnostics file to SolarWinds Support