Crawl Logs
Track crawl status, page outcomes, failures, retries, and coverage.
Browse docs
Crawl Logs show what Ceisium found, indexed, skipped, or failed during a crawl.
Run states
| State | Meaning |
|---|---|
| Queued | Crawl is waiting to start. |
| Running | Ceisium is fetching and indexing pages. |
| Completed | Crawl finished and page counts are ready. |
| Failed | Crawl stopped before completing. Check the error and source settings. |
Page counts
| Count | Meaning |
|---|---|
| Discovered | URLs found during crawl. |
| Indexed | Pages added to search. |
| Skipped | Pages ignored because of scope, duplicate URLs, or unsupported content. |
| Failed | Pages Ceisium tried but could not fetch or index. |
SigNoz example
For https://signoz.io/docs/, a healthy crawl should discover docs paths such as:
TXT
/docs/install//docs/install/docker//docs/instrumentation//docs/instrumentation/python//docs/userguide/logs/If /docs/instrumentation/python/ is missing, check include and exclude paths before rerunning the crawl.
Debug flow
- Open the latest crawl.
- Filter URL events to
FailedandSkipped. - Check whether the missing page is outside the source path.
- Adjust source scope.
- Run crawl again.