Configuration
Remote Logs configuration
Remote control - allow control via Token
For proper connector functionality, enabling Remote Control in the company settings for Token
capability is essential.
Minimum Log Level
Trace Debug Info Warning Error Fatal
default: Info
Input & Output Schema
Input
Data schema is mandatory
The connector requires mandatory input or output data schema, which must be selected by the user from the existing data schema repository or a new one must be created. The connector will fail without structured data.
Output
Remote get logs (ver. 1.0.0)
Column | Data type | Allow null | Description |
---|---|---|---|
Date | string | No | Log date and time (timestamp) |
Level | integer | No | Log level (Info, Warning, Error...) |
Message | string | Yes | Log message |
TaskID | integer | No | Log related Task ID |
TaskRunID | integer | No | Log related Task run ID |
TaskStepID | integer | Yes | Log related Task step ID |
TaskStepRunID | integer | Yes | Log related Task step run ID |
Keys | JSON | Yes |
Release notes
3.0.6
- Fixed input process type.
3.0.5
- Fixed remote endpoint.