Run Logs

RuleGo-Server provides persistent storage and querying capabilities for rule chain execution logs, supporting multiple storage backends.

# Configuration

# Whether to persist execution logs
save_run_log = true
# Storage backend type: bbolt (default), file, nop
run_log_store_type = bbolt

1
2
3
4

# Storage Backends

Type	Description	Use Case
`bbolt`	Embedded key-value database (default)	Production, good performance
`file`	JSONL file storage	Debugging, log export
`nop`	No storage	No log recording needed

# Query Execution History

GET /api/v1/logs/runs?chainId={chainId}&page=1&size=20&startTime=&endTime=
Authorization: Bearer {token}

1
2

Query parameters:

Parameter	Type	Description
`chainId`	string	Rule chain ID filter
`id`	string	Specific run record ID
`page`	int	Page number
`size`	int	Items per page
`startTime`	string	Start time filter
`endTime`	string	End time filter

# Get a Single Record

GET /api/v1/logs/runs?id={runId}
Authorization: Bearer {token}

1
2

# Delete Records

# Delete by rule chain
DELETE /api/v1/logs/runs?chainId={chainId}

# Delete by record ID
DELETE /api/v1/logs/runs?id={runId}
Authorization: Bearer {token}

1
2
3
4
5
6

# Node Debug Data

Get debug logs for rule chain nodes:

GET /api/v1/logs/debug?chainId={chainId}&nodeId={nodeId}
Authorization: Bearer {token}

1
2

Node debug logging is controlled by the debug and max_node_log_size configuration:

# Whether to record node debug data
debug = true
# Maximum log entries per node
max_node_log_size = 40

1
2
3
4

# Viewing in the Editor

Debug Console: Bottom panel displays node IN/OUT data in real time
Node Debug Panel: Click a node to view historical debug logs
Execution History: View historical execution records in the run dialog

# WebSocket Real-time Debugging

See REST API Reference - Real-time Debugging.

Edit this page on GitHub

Last Updated: 2026/05/30, 11:18:53

← Component Marketplace Internationalization→