1. Overview

• Definition: Monitor Log (Sync Log) tracks every recorded system record in detail, along with each record’s processing status during sync.
• Benefits/Value: Helps operators quickly pinpoint failed records, error groups, and error timing — cutting down troubleshooting time.
• Target users: System Admin, Data Engineer/IT Ops, Implementation/Support team.

2. Terminology & Specifications

• Session — A sync run’s data-processing lifecycle, created per execution.
• Message ID — A unique identifier that the system generates for each record.
• Trace Key — Matches against source data to look up the right record; capped at 64 characters on screen.
• Record status — Successful, Syncing, Failed.
• Error Category — Prepare, Ingest, Process, Unclassified.

3. Prerequisites

• Permissions: Your Mobio account must have the INTEGRATION RBAC permission. See the RBAC permissions guide.
• Access Path: Go to Settings → Data Integration → Data Flow/Data Source → select a connector → Monitor Log tab. Or: Settings → Data Integration → Data Flow/Data Source → select a connector → Report → select a sync session → open Monitor Log.
• Input data: The system has recorded at least one record within a sync session.

4. Implementation steps

4.1. Open Sync Log and pick a view

• Go to the Sync Log for the connector you want to monitor.
• For Snapshot connectors: view a single session, or roll up across all sessions.
• For Streaming connectors: view every record within the filter range.

4.2. Set filters and refresh

• Filter by record status.
• Filter by start/end time: today, yesterday, 7 days ago, or custom.
• Data refreshes automatically every minute — click Reload to refresh manually.

4.3. Read the record list

• Check the key fields: Message ID, processing status, Trace Key, sync session, start time and end time.
• Check each record’s remaining storage time (within 7 days).
• Prioritize failed records or records that have been stuck in Syncing for an unusually long time.

4.4. View a record’s details

• Click a record to open its detail screen.
• Compare data across three stages: source data (extract), transformed data (transform), and the destination result (load).
• Compare the JSON at each stage to pinpoint where the error occurred.

4.5. Identify and handle transform errors

• Check the record’s data conversion status: Yes, No, or No conversion.
• For a transform error, identify the source field, target field, transform rule, and whether that rule executed.
• Prioritize fixing format or data-type errors in the source data before rerunning.

5. Operational Rules & Use Cases

• Use Monitor Log to quickly tell system-level errors (by session) apart from data-level errors (by record).
• When a session fails, read the error category in order — Prepare → Ingest → Process — to find the right layer to fix.
• To reconcile source and destination data, combine Trace Key with Message ID for precise tracing.
• If record counts don’t match, first compare against the previous session, then drill into that session’s failed records.

6. Frequently Asked Questions (FAQ)

• Q: Why can’t I find an old record in Sync Log? 
  • A: Records have a limited retention period set by system policy. Check the time filter and how much storage time the record has left.
• Q: Is it a problem if a record stays in Syncing for a long time? 
  • A: Not necessarily — the system may have ingested it but is still waiting to process it. If it takes unusually long, check the error category and the detailed log for the related session.
• Q: Where should I start troubleshooting when data is missing? 
  • A: Start from the sync session with the largest gap, open Sync Log, filter for failed records, then compare data across the three stages to find the root cause.

7. Next Steps

Monitor & Manage Profile & Company Data