aws-cnug-o11y/dsh-trajectory-persistence
Persists every DSH session trajectory to S3, OTel/GenAI or CloudWatch sinks, observe-only, with all sinks off by default.
Answers the question a durable session log cannot: what actually went over the wire, and can it be replayed somewhere else. Because ship mode copies the jsonl backend's artifact byte-faithfully with a manifest watermark rather than re-encoding events, a bucket becomes a restorable archive of sessions and machine switching becomes a sync-down instead of a lost history. The other sinks serve different questions — OTel/GenAI events map to spans for Jaeger, Collector or Langfuse, and CloudWatch/AgentCore delivery uses SigV4 with Transaction Search. The documentation is published as a site with a getting-started walkthrough against a local Jaeger, a configuration reference covering every field, default and validation rule, and a maintainer page on adding a sink.
Install
dsh plugin --profile web add dsh-trajectory-persistenceThe npm line, then configure in $DSH_HOME/settings.yaml — the README states that sink changes apply live with no restart. Every sink defaults to disabled, so installing this changes nothing until you enable one. For the S3 sink the minimum is a bucket plus region, with credentials coming from the AWS default provider chain. There is also a restore CLI: dsh-trajectory-persistence sync-down --bucket <bucket> --region <region> runs on the destination machine with dsh not running and restores sessions from the bucket into the local root.
Compatibility
An S3-compatible target (S3, OSS or MinIO) for the object sink, AWS credentials through the default provider chain, and for the OTel side a collector such as Jaeger, an OpenTelemetry Collector or Langfuse. The two sinks toggle independently, and the S3 sink has two modes with different guarantees: ship tails the official jsonl backend's on-disk artifact read-only and uploads byte-faithful zstd frame segments plus a manifest, restorable on another machine; push is the legacy default that writes part files with buffering, retry and a dead-letter path. The plugin never writes to a session — it is observe-only.
Details
- Repo: aws-cnug-o11y/dsh-trajectory-persistence
- Category: Infrastructure & Deployment
- Stars: 1
- Version: 0.1.0 (npm)
Alternatives
januory/dsh-remote-workspaces · ChenLuoi/dsh-auth-remote · Edge-Echo/dsh-netassist