92697edb7c
Venice's API doesn't support certain OpenAI-compatible parameters that Clawdbot sends by default: - `store`: Venice returns HTTP 400 with no body when this is present - `developer` role: Not supported by Venice's API This adds VENICE_COMPAT settings (supportsStore: false, supportsDeveloperRole: false) to all Venice model definitions, both from the static catalog and dynamically discovered models. Fixes issues reported in PR #1666 where users experienced silent failures (HTTP 400, no body) when using Venice models. Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com> Co-authored-by: Clawdbot <bot@clawd.bot>
90 lines
1.9 KiB
Markdown
90 lines
1.9 KiB
Markdown
---
|
|
summary: "Diagnostics flags for targeted debug logs"
|
|
read_when:
|
|
- You need targeted debug logs without raising global logging levels
|
|
- You need to capture subsystem-specific logs for support
|
|
---
|
|
# Diagnostics Flags
|
|
|
|
Diagnostics flags let you enable targeted debug logs without turning on verbose logging everywhere. Flags are opt-in and have no effect unless a subsystem checks them.
|
|
|
|
## How it works
|
|
|
|
- Flags are strings (case-insensitive).
|
|
- You can enable flags in config or via an env override.
|
|
- Wildcards are supported:
|
|
- `telegram.*` matches `telegram.http`
|
|
- `*` enables all flags
|
|
|
|
## Enable via config
|
|
|
|
```json
|
|
{
|
|
"diagnostics": {
|
|
"flags": ["telegram.http"]
|
|
}
|
|
}
|
|
```
|
|
|
|
Multiple flags:
|
|
|
|
```json
|
|
{
|
|
"diagnostics": {
|
|
"flags": ["telegram.http", "gateway.*"]
|
|
}
|
|
}
|
|
```
|
|
|
|
Restart the gateway after changing flags.
|
|
|
|
## Env override (one-off)
|
|
|
|
```bash
|
|
CLAWDBOT_DIAGNOSTICS=telegram.http,telegram.payload
|
|
```
|
|
|
|
Disable all flags:
|
|
|
|
```bash
|
|
CLAWDBOT_DIAGNOSTICS=0
|
|
```
|
|
|
|
## Where logs go
|
|
|
|
Flags emit logs into the standard diagnostics log file. By default:
|
|
|
|
```
|
|
/tmp/clawdbot/clawdbot-YYYY-MM-DD.log
|
|
```
|
|
|
|
If you set `logging.file`, use that path instead. Logs are JSONL (one JSON object per line). Redaction still applies based on `logging.redactSensitive`.
|
|
|
|
## Extract logs
|
|
|
|
Pick the latest log file:
|
|
|
|
```bash
|
|
ls -t /tmp/clawdbot/clawdbot-*.log | head -n 1
|
|
```
|
|
|
|
Filter for Telegram HTTP diagnostics:
|
|
|
|
```bash
|
|
rg "telegram http error" /tmp/clawdbot/clawdbot-*.log
|
|
```
|
|
|
|
Or tail while reproducing:
|
|
|
|
```bash
|
|
tail -f /tmp/clawdbot/clawdbot-$(date +%F).log | rg "telegram http error"
|
|
```
|
|
|
|
For remote gateways, you can also use `clawdbot logs --follow` (see [/cli/logs](/cli/logs)).
|
|
|
|
## Notes
|
|
|
|
- If `logging.level` is set higher than `warn`, these logs may be suppressed. Default `info` is fine.
|
|
- Flags are safe to leave enabled; they only affect log volume for the specific subsystem.
|
|
- Use [/logging](/logging) to change log destinations, levels, and redaction.
|