Skip to content

Monitor coordinator-mode (fire-and-forget) workflows via a remote event stream #79

Description

@nh13

The AWS Batch executor is growing a coordinator mode (fulcrumgenomics/snakemake-executor-plugin-aws-batch — "coordinator mode" PR): snakemake itself runs as a Batch job and the local terminal disconnects. That moves .snakemake/ and the snakesee logger plugin's .snakesee_events.jsonl into the coordinator container, so snakesee's passive local monitoring sees nothing.

Sketch:

  • snakemake-logger-plugin-snakesee: optional sink that ships the event stream to a reachable location — the natural choice is the workflow's S3 prefix (the executor already requires S3 storage), e.g. append/rotate JSONL objects under <prefix>/.snakesee/. Needs batching to avoid per-event PUTs.
  • snakesee: an S3-aware EventReader (poll the object(s), track offset/etag) selected when the workflow dir argument is an s3:// URL.
  • Auth/perms: reuse the ambient AWS credentials; document s3:GetObject/ListBucket needs.

This is the missing piece for monitoring fire-and-forget remote workflows end-to-end, and extends the remote-job-state contract work (the snakesee_remote events would travel the same stream).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions