Aleph
Gateway RPCMethods Reference

logs.*

System logs and diagnostics RPC methods

logs.* exposes three methods for log-level control and log-directory lookup. All methods work on RUST_LOG-style filter strings (error / warn / info / debug / trace); the underlying primitives live in src/logging/.

Methods

MethodDescription
logs.getLevelRead the current global log level
logs.setLevelSet the global log level
logs.getDirectoryReturn the absolute path of the log directory

Historical aliases such as logs.list / logs.get / logs.tail / logs.levels / logs.set_level are not RPCs; only the three endpoints above are exposed at runtime.

logs.getLevel

Read the current process-wide log level (via crate::logging::get_log_level()).

Request:

{ "jsonrpc": "2.0", "id": 1, "method": "logs.getLevel" }

Response:

{ "jsonrpc": "2.0", "id": 1, "result": { "level": "info" } }

The level field is LogLevel::to_filter_string() output and accepts error / warn / info / debug / trace.

logs.setLevel

Set the global log level. Takes effect immediately.

Request:

{ "jsonrpc": "2.0", "id": 2, "method": "logs.setLevel", "params": { "level": "debug" } }

Response:

{ "jsonrpc": "2.0", "id": 2, "result": { "ok": true, "level": "debug" } }

Parameters:

ParameterTypeRequiredDescription
levelstringYeserror / warn / info / debug / trace

An invalid value returns -32602 Invalid params with the valid set listed in the message.

logs.getDirectory

Return the absolute path of the log directory. The directory is resolved by crate::logging::get_log_directory(); files are named aleph-<service>.log.<date> and rotate on day boundaries (an ALEPH-BOOT marker is written on startup).

Request:

{ "jsonrpc": "2.0", "id": 3, "method": "logs.getDirectory" }

Response:

{ "jsonrpc": "2.0", "id": 3, "result": { "directory": "/home/user/.aleph/logs" } }

For filtered reads of the files inside the directory, use daemon.logs.

See Also

On this page