Logs
Logs
The Logs section is the central place to understand what DeDuplica is doing and to diagnose any issues. Every significant operation is recorded here — from agent activity and job executions to individual duplicates found and webhook calls fired.
What Is Logged
| Event type | Description |
|---|---|
| Job executions | Each job run: when it started, how long it took, how many records were scanned, and whether it completed successfully |
| Duplicates found | Every duplicate pair identified, including the match probability and which job produced it |
| Webhook calls | Each outbound webhook delivery — the target URL, response code, and any retry attempts |
| Agent activity | Connection events, queue picks, and errors from Local Agents running in your infrastructure |
| User actions | Agent restarts, manual runs, and other user-initiated operations |
Using Logs to Diagnose Issues
Logs are the first place to check when something isn’t working as expected:
- Job not producing results? Check the job execution log entry for error messages or unexpected record counts.
- Webhook not reaching your endpoint? The webhook log shows the HTTP response code returned by your endpoint and whether DeDuplica retried after a failure.
- Local Agent not picking up work? Agent log entries will show whether the agent is connecting to the queue and whether it encountered errors reaching your database.
- Unexpected duplicates or missed matches? Log entries for individual duplicate pairs include the fields that matched and the probability score, helping you tune Find Duplicates configuration.
Filtering
Logs can be filtered by date range, event type, job, and status (success / warning / error). For environments running many jobs, filtering by job and date is the fastest way to isolate the relevant entries.