Page History
Logging
All Aspire Logs are now stored in the aspire-log NoSQL Database. This provides a centralized log that will contain information from all components loaded on all nodes.
These are the fields stored on each log entry:
| Field | Description |
|---|---|
| timestamp | Long valued representing the date and time the log was generated. |
| severity | Severity of the log entry. Possible values: DEBUG, INFO, WARN, ERROR.1 |
| component | The Aspire component this log entry comes from. |
| message | Log message. |
| stack | In case the log is an ERROR, the stack trace of the exception causing the error is stored here. |
| server | Json object containing all information related to the server this log comes from. |
| server.ip | The server ip address. |
| server.port | The server port. |
| server.name | Hostname of the server. |
| server.start | Long representing the Aspire node start time. |
| server.id | Unique id assigned to the server when the Aspire node is started. |
Error Log
The Connector Framework provides an extra NoSQL database that will store all crawl related errors. This error entry will contain the corresponding log as well as information related to the error.
| Field | Description |
|---|---|
| seedId | Seed that logged the error. |
| crawlId | Crawl where this error was generated. |
| type | Error type. Possible types: process, scan, connector or identity. |
| timestamp | Long valued representing the date and time the error was generated. |
| message | Error log message. It can contain the exception and a stack trace. |
Error Types
| Error Type | Description |
|---|---|
| process | Any error that comes from processing an item. |
| scan | Any error generated while scanning a container. |
| identity | Any error created when extracting an identity. |
| connector | Any error generated while processing a connector control item. See Crawl Control to learn more about control items. |
Log Monitoring
See How to Enable Aspire Logs in Kibana guide.
Overview
Content Tools