Collector Logs

1. Overview

The Collector Logs module in Sumo Ledger tracks the execution history of data collection pipelines (collectors). It records when each collector run started, its progress, whether it succeeded or failed, and how many files were processed. This is the monitoring counterpart to the Collector module.

Navigation: Logs > Collector logs

URL: https://las.ledger.raralabs.dev/collector/log/list

---

2. Collector Logs Page

The page has two tabs: Fetcher Logs and Fetcher Response.

2.1 Fetcher Logs Tab

Displays the execution log for each collector run.

Table Columns:

Column	Description
ID	The unique identifier for this log entry.
Source ID	The ID of the source collector that was executed.
Status	The execution status (e.g., Success, Failed, Running).
Progress	The progress of the collector run (e.g., percentage or step indicator).
File Count	The number of files processed during this run.
File Pattern	The file pattern used to match files from the source (e.g., *.csv, report_*.xlsx).
Message	A status message or error description.
Started At	The timestamp when the collector run started.
Completed At	The timestamp when the collector run finished.

2.2 Fetcher Response Tab

Displays the response data from collector runs, providing details about what was fetched or processed.

Controls

• Filter: Dropdown filter for narrowing results.
• Search: Free-text search across log entries.
• View: Toggle table layout.
• Pagination with configurable items per page.

---

3. Best Practices

1. Check Fetcher Logs after scheduled collector runs. Verify that each run completed successfully and processed the expected number of files.
2. Investigate failed runs immediately. Check the Message column for error details and verify the source connectivity.
3. Monitor File Count values. A sudden drop to zero may indicate the source system stopped producing files or the file pattern no longer matches.
4. Use the Fetcher Response tab to inspect the actual data that was collected during each run.