Observability Pipeline Status

[huaxel]

Question

Why does the observability history.jsonl have only 10 entries despite extensive pi usage? Investigate:

1. Is the dynamic-footer observability pipeline working correctly? Check the segment configuration in ~/.pi/agent/observability/settings.json.
2. Is the history.jsonl being truncated, rotated, or not written to?
3. Is there a gap between sessions having footer display data and sessions being recorded to history?
4. What would need to change to get reliable cost and session tracking?

Deliverable: Root cause assessment of the sparse history and a recommendation for fixing or replacing the observability pipeline.

[huaxel]

Resolution: Observability Pipeline Status

Branch: research/observability-pipeline
Investigator: Worker subagent

Root Cause

The history.jsonl has only 10 entries by design. The pi-dynamic-footer extension calls trim({ keepLast: 10 }) in its session_shutdown handler, which intentionally caps the persisted history to the last 10 sessions. The 10 entries that exist cover only ~3 hours because the extension (or its history write path) was recently activated.

The run-history.jsonl is a completely separate system written by the pi core binary (not an extension) and is unaffected.

Recommendation

• Increase keepLast to 200+ and make it configurable via settings.json
• Currently the limit is hardcoded in the dynamic-footer extension source

Full findings: research/observability-pipeline/findings.md

[huaxel]

Resolved via wayfinder research subagent. Findings posted in resolution comment above.