Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Examine identification engine run logs

Log in to subscribe to topics and get notified when content changes.

Examine identification engine run logs

Applications that use the identification engine (such as Discovery) can provide a URL to viewing identification engine run logs. To view results and for debugging purposes, you can use these links to examine the details of logs generated by the identification engine for payload runs.

Before you begin

Role required: admin

About this task

These URLs link to a central page where the identification engine payload output logs appear in a user friendly format. Logging is in the context of a specific run of the identification engine, and you can filter the log list by a specific data source and time range. Up to 1000 run logs that are up to 2 months old are listed, grouped by Context IDs, and run times. You can use the glide.identification_logs.max_run_ids property to modify the 1000 limit.

You can control the logging level by using the glide.discovery.identification.log_level Discovery system property and setting the value to one of the following:
  • Info
  • Warn
  • Error
  • Debug
  • DebugVerbose
  • DebugObnoxious


  1. Navigate to Configuration > Identification/Reconciliation > Identification Logs.
  2. Filter the runs list as follows:
    1. Source: Select the data source for which to display run logs.
    2. Time Range: Specify a time range for which to display run logs.
    The Runs list displays all runs for the specified data source, during the specified time range.
  3. In the Runs list, click a Run # to display its Context ID and Run ID.
    A unique Context ID is associated with each specific payload that is run. Each run of that payload, is associated with a unique Run ID. A single Context ID for a payload that is run multiple times is associated with multiple Run IDs.
  4. Click the drop down arrow for a Run # to display additional details.
    • Input: Displays the payload for the run.
    • Logs: Displays all the logged messages that the identification engine generated while running the payload, according to the specified logging level.
    • Output: Displays the output payload returned by the identification engine.