Identification simulation provides run logs which are generated by Identification and
Reconciliation Engine (IRE). You can access these run logs for payload runs, to examine
results and for debugging purposes. IRE payload output logs appear in a user friendly format
on a central page.
Also, internal applications that use IRE (such as Discovery) can call
an internal API to provide a URL to viewing IRE run logs.
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
Note: IRE performs an initial verification of a payload before processing
identification rules. If IRE detects any duplicate CIs based on any class
identifiers, the payload is rejected and processing stops.