Once the Asset Optimization plugin is installed and configured, SysTrack's system identification and configuration data is automatically imported into your ServiceNow CMDB, eliminating the need to manually create records that identify each system.
CMDB Data Integrity
CMDB data integrity is preserved by creating new computer records when a SysTrack system does not already exist in CMDB, updating existing SysTrack-managed computer records with the latest data, and leaving non-SysTrack CMDB systems unchanged (not modified or deleted). The integration also prevents duplicate records by correctly handling the same device across different domains, such as when a system moves from one SysTrack domain to another.
Import Job Run History
Each data import can be reviewed as an entry in the Import Job Run History table. All new imports generate new entries in the table, regardless of whether they were scheduled runs or manual runs.
.png?sv=2026-02-06&spr=https&st=2026-09-07T04%3A59%3A12Z&se=2026-09-07T05%3A12%3A12Z&sr=c&sp=r&sig=mG%2FrUNR3Wb6FWbBsh2LhMyOz5%2BkZPUo4u0xww3z2wZc%3D)
Number - Sequence number of the history record.
State - Current state of the import job.
Finished - The import job completed successfully.
Loading - The import job is loading raw data for the current chunk into the staging tables.
Transforming - The import job is transforming data for the current chunk from the staging tables into the target tables (cmdb_ci_computer and cmdb_ci_disk).
Stopped - The import process was stopped by the user.
Error - The import job stopped because of an error.
Paused - Import paused due to chunking boundary.
Last chunk size - Last page index of the data fetched from SysTrack.
System per chunk - Number of data rows per page.
Stopped by user - Indicates whether the import job was stopped by the user.
Loaded Systems - Total number of systems imported in the job.
Created Systems - New systems - IRE found no existing match.
Updated Systems - Existing systems updated - IRE matched an existing record.
No Change Systems - IRE matched an existing system but data was identical.
Domain - Domain for which the import job was run.
Execute Now
Only ServiceNow admins can press the Execute Now button to import data manually. In such scenarios, the import will be run as the currently logged-in user.
Stop Import
If an import job is in the Transforming or Loading state, you can press the Stop Import button to cancel the import. Only users with the x_laso_systrack_sy.user role can perform this action.
Performance Tuning
Use the recommended chunk sizes in the following table as a starting point for performance tuning. Adjust the chunk size gradually based on the number of endpoints in your environment.
Scenario | Recommended Chunk Size |
|---|---|
Initial load / first run | Start with 1,000, increase gradually |
Small environment (< 5,000 endpoints) | 1,000–2,000 |
Medium environment (5,000–50,000) | 2,000–5,000 |
Large environment (50,000+) | 5,000–10,000 |
NOTE: Very large import jobs, such as 300,000+ systems with the maximum chunk size of 50,000, can take several hours to complete.
Troubleshooting
If a run fails or completes with errors, use the following steps to identify the cause.
Where to check logs:
System Logs > Outbound HTTP Logs: review outbound requests to SysTrack and HTTP response status codes.
System Logs > System Log > All: review application and platform errors not shown in outbound logs.
Example 1: Invalid API key (Cloud)
Symptom: The run shows an error in Import Job Run History.
.png?sv=2026-02-06&spr=https&st=2026-09-07T04%3A59%3A12Z&se=2026-09-07T05%3A12%3A12Z&sr=c&sp=r&sig=mG%2FrUNR3Wb6FWbBsh2LhMyOz5%2BkZPUo4u0xww3z2wZc%3D)
Check: Open System Logs > Outbound HTTP Logs and locate the request from the failed run.
Expected evidence: HTTP 401 response
.png?sv=2026-02-06&spr=https&st=2026-09-07T04%3A59%3A12Z&se=2026-09-07T05%3A12%3A12Z&sr=c&sp=r&sig=mG%2FrUNR3Wb6FWbBsh2LhMyOz5%2BkZPUo4u0xww3z2wZc%3D)
Action: Update the SysTrack API key in Properties and run the job again.
.png?sv=2026-02-06&spr=https&st=2026-09-07T04%3A59%3A12Z&se=2026-09-07T05%3A12%3A12Z&sr=c&sp=r&sig=mG%2FrUNR3Wb6FWbBsh2LhMyOz5%2BkZPUo4u0xww3z2wZc%3D)
Example 2: MID Server not provided (On-Premises)
Symptom: The run shows an error in Import Job Run History.
Check: Open System Logs > System Log > All.
.png?sv=2026-02-06&spr=https&st=2026-09-07T04%3A59%3A12Z&se=2026-09-07T05%3A12%3A12Z&sr=c&sp=r&sig=mG%2FrUNR3Wb6FWbBsh2LhMyOz5%2BkZPUo4u0xww3z2wZc%3D)
Expected evidence: Error entries related to missing or invalid MID Server configuration.
Action: Set a valid MID Server in Properties and run the job again.
TIP: Filter logs by prefix [SysTrack Asset Optimization] to quickly find application-specific entries.
.png?sv=2026-02-06&spr=https&st=2026-09-07T04%3A59%3A12Z&se=2026-09-07T05%3A12%3A12Z&sr=c&sp=r&sig=mG%2FrUNR3Wb6FWbBsh2LhMyOz5%2BkZPUo4u0xww3z2wZc%3D)
Common Errors and Fixes
Symptom | Likely Cause | Fix |
|---|---|---|
Import fails with Access denied on staging tables | Run As user missing | Add |
Import fails on transform/import set operations | Run As user missing | Add |
Many duplicate systems created | IRE identification rules not matching | Tune identification rules (see IRE section) |
Import stuck in Loading state | Network/timeout issue to SysTrack API | Check connectivity, reduce chunk size |
Stopped state unexpectedly | Another admin clicked Stop Import | Check |
No data imported but state is Finished | API returning empty results | Verify SysTrack master name and API key/credentials |
Chunk size property won't save | Value outside 1–50,000 range or not integer | Enter a whole number between 1 and 50,000 |
MID Server errors (On-Premises) | MID Server down or cannot reach SysTrack | Verify MID Server is Up and has network access |
Users not mapped | Email/name mismatch between SysTrack and ServiceNow | Ensure user records exist in |