'Time Slicing Sync' job debugging
search cancel

'Time Slicing Sync' job debugging


Article ID: 208108


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


How do you enable debugging for the 'Time Slicing Sync' job used for per-period metrics and Group by Aggregation in the Modern User Experience (UX) for SQLCurves?

How do you detect if a sql curve is out of sync with the corresponding nkcurve?


Component: Clarity Time Slicing Sync job (renamed from Time Slicing Group By job starting in 15.9.2)

Release: 15.9.1 and higher


Step 1: Enable debugging

  1. Log in to Clarity as an Administrator
  2. Replace everything after 'action:' in the URL with 'Security.Logs'
  3. Click on the Logs drop-down and select 'Edit Configuration'
  4. Click Add Category
  5. Scroll down to the new category created and add the following
    1. Other Name = com.niku.blobcrack.SqlCurveCrack
    2. Appender = STDOUT
    3. Priority = Debug
  6. Click Save

Step 2: Ensure 'Debug Logging' is checked 

This should be checked in job parameters. 

This was named 'Log debug output' in 15.9.1:

Step 3: Review the details in the bg-ca.log.

Search for 'blobcrack.SqlCurveCrack' to find output related to the job

Step 4: Disable debugging

Once debugging is captured, make sure to disable debugging. This will prevent the logs from filling up with debug information in case the job is checked to run with the parameter 'Log debug output'.

Options to disable below:

  • Delete the blobcrack.SqlCurveCrack category


  • Change the Priority of the category from Debug to Fatal.

Additional Information

See: Time Slicing Group By for more information on this job