Skip to main content

​
Daily 5-Minute Check

1

Gateway baseline

argent gateway status
argent logs --follow --plain | rg --line-buffered "health: ok|ollama=|auth="
2

MemU extraction activity

argent logs --follow --plain | rg --line-buffered "memu|Extraction complete|memu-extract|fallback episode stored"
3

Contemplation + SIS parse health

argent logs --follow --plain | rg --line-buffered "contemplation|sis:|consolidation returned no patterns|no parseable JSON"
4

Auth routing sanity (memory providers)

argent logs --follow --plain | rg --line-buffered "model-router|auth-failover|provider=ollama|selected profile"
5

RAG ingestion/retrieval health

argent logs --follow --plain | rg --line-buffered "knowledge|library|ingest|collection|ACL|denied"

​
Escalate Incident If

  • No successful MemU extraction for 30+ minutes during active chat.
  • SIS parse failures persist for 3+ consolidation windows.

​
Common Critical Signatures

Check that Ollama is running and accessible. Verify MemU LLM provider configuration in argent.json.
Verify the selected provider/model for the SIS path. Check that the model supports structured output. Validate JSON contract and fallback parser behavior.
During active use, MemU should be extracting regularly. Check gateway logs for errors in the memory extraction pipeline.

​
Compatibility Warnings (Usually Non-Blocking)

These indicate compatibility mode, not immediate outage:
  • Legacy dashboard SQLite modules are quarantined...
  • Using PostgreSQL compatibility mode for memory inspector.