SQL trace for troubleshooting XOG actions (Clarity)
search cancel

SQL trace for troubleshooting XOG actions (Clarity)


Article ID: 206148


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


In some situations for troubleshooting, you may need to see what queries are executed at the time you perform XOG actions. How can you enable SQL Trace / Action Trace for XOG?


Release : Any


  1. Identify which user you will use for the trace, and set the trace in the User Properties to Trace without Statements, save
  2. Go to CSA - Logs - Edit Configuration
  3. Set trace.server.selective.user category to “Trace”.
  4. Set Trace XOG to enabled
  5. Set Default Trace Threshold (Seconds) to 0 in CSA and make sure it updates properties.xml traceAlarmThresholdSeconds field as well.
  6. If it doesn't manually set “traceAlarmThresholdSeconds” to 0 in properties.xml
  7. If Detect Changes Automatically on Edit Configuration page is enabled and you didn't have to manually update the properties.xml file then you do not need a restart
  8. Restart the app services if you updated the properties.xml manually. 
  9. Perform XOG and app-trace.xml should be enabled with the results, collect your trace and provide to Support as requested

After the trace, reset everything back in Edit Configuration

    • Set trace.server.selective.user category back to INFO
    • Uncheck Trace XOG
    • Set Default Trace Threshold (Seconds)  to -1, if it doesn't update properties.xml, then update properties.xml traceAlarmThresholdSeconds field 
    • Restart services if you updated properties.xml manually

Note: You must reset the trace on XOG back as described above. Leaving the trace on will lead to performance overhead