dsh-logger-channels
cordis ctx.logger 服务的可见日志接收器：注册命名的 stderr/stdout/file 通道（按大小轮换的文件），使框架和插件的日志输出能够到达操作员；dsh 主机仅提供内存接收器
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:xuan25/dsh-logger-channels#916f2da67308519ce58212542adfb966ead2c2c3Logger Channels 以 dsh-logger-channels 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
dsh-logger-channels gives a DSH profile a visible log sink: named channels that receive every ctx.logger record from the framework and all plugins, so runtime log output reaches the operator instead of ending only in the host's in-memory buffers.
dsh-logger-channels is an out-of-tree plugin for a dsh profile. Install it with the dsh plugin command:
dsh plugin --profile <name> add dsh-logger-channels
Configuration is layered: built-in defaults, the LOGGER_CHANNELS_* process-env block, and a cordis config layer (see below).
One variable per channel declares it (TYPE); the rest attach to the declared channel and are optional:
| Variable | Required | Meaning |
|---|---|---|
LOGGER_CHANNELS_<NAME>_TYPE | yes | declares channel <name> = the lowercased <NAME>; the value is stderr, stdout, or file |
LOGGER_CHANNELS_<NAME>_PATH | file only | output file path (parent directories are created) |
LOGGER_CHANNELS_<NAME>_MINLEVEL | no | numeric level threshold: 0 = error only, 1 = +info, 2 = +warn, 3 = +debug (default 2) |
LOGGER_CHANNELS_<NAME>_COLORS | no | ANSI color level: false or 1-3 (default false) |
LOGGER_CHANNELS_<NAME>_MAXLENGTH | no | per-line truncation in characters (default 10240) |
LOGGER_CHANNELS_<NAME>_MAXBYTES | no (file) | size that triggers rotation, in bytes (default 10485760) |
LOGGER_CHANNELS_<NAME>_KEEP | no (file) | number of rotated generations to keep (default 5) |
Example:
LOGGER_CHANNELS_APP_TYPE=file
LOGGER_CHANNELS_APP_PATH=/<path>
LOGGER_CHANNELS_APP_MINLEVEL=3
The <NAME> segment of the variable name is uppercase letters and digits only, and the channel name is its lowercased form; the channel name must match ^[a-z][a-z0-9-]{0,31}$, so e.g. LOGGER_CHANNELS_1APP_TYPE declares no channel, and a lowercase segment such as LOGGER_CHANNELS_app_TYPE matches nothing at all. A key other than TYPE on a name that no TYPE variable declares is ignored, as are unknown keys in the namespace.
The level numbers follow cordis's verbosity ladder, not a severity ladder: ERROR=0, INFO=1, WARN=2, DEBUG=3. Note that INFO sorts numerically before WARN, the opposite of the log4j/Python severity convention. The config layer's minLevel uses the same numbering.
An optional config layer sits on top of the env block: a patch entry targeting the plugin id dsh-logger-channels (the profile's cordis.patch.yml, the user-global ~/.dsh/cordis.patch.yml, or a --patch overlay) carries a config object with one key, channels (a map of channel name to channel, minLevel, colors, maxLength, path, maxBytes, keep). Every key is optional.
- id: dsh-logger-channels
config:
channels:
app:
channel: file
path: /<path>
minLevel: 3
config: {} (or no entry) is exactly the env-only behavior.--patch overlay).path, an out-of-range value) fail the plugin entry at apply time with a labeled error, and the profile does not start.[2026-10-11T08:01:02.123Z] #42 INFO app Processing: scope=c2c peerId=1
Fields, in order: wall-clock timestamp (UTC), #sn (per-boot sequence number; resets on restart), level, logger name, body. In the body, an Error as the first argument renders its stack; the body is subject to the channel's maxLength.
maxBytes, the live file is renamed to .1 (the newest generation), older generations shift to .2 ... .keep, and the oldest generation is dropped. Files are appended to, and the size counter is seeded from the existing file on open, so rotation continues across restarts.stdout is a shared stream: in profiles where stdout carries a structured protocol, do not configure a stdout channel; stream ownership is the operator's to coordinate.