Show TOC

Procedure documentationTriggering Traces


As a level 2 user, you can trigger traces to identify the causes of errors. To do so, temporarily change the granularity of the recorded trace data.


  • You have authorization as a level 2 user.

  • You have set a special value for the trace level. For more information, see Changing Parameters Temporarily for Error Analysis.

  • If the EEMon script in question is relevant for reporting, you have ensured that reporting is deactivated.

    Caution Caution

    Executing a script with a higher trace level distorts performance values. You therefore deactivate reporting during these analysis runs. This results in gaps in reporting.

    End of the caution.


  1. Select an EEMon robot and script combination, for example, an EEMon script in the Robot Tile view or a robot in the Script Tile view.

  2. Choose Run Script with Trace in the context menu.

    When the EEMon script is executed, server-side data is collected. Executions with expected server-side data are displayed in italic print in the script tree or robot tree. As soon as the server-side data is collected, the execution in the script tree or robot tree is displayed in bold print.

    Note Note

    Executions are always displayed in bold print when server-side information at levels below steps and requests is available.

    End of the note.
  3. In the execution that contains the server-side data, select the step that you want to analyze.

  4. Choose Go to E2E Trace Analysis in the context menu.


The end-to-end trace analysis in diagnostics in SAP Solution Manager is displayed.