HWPSupervisor should record its decisions

Open
#944 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
observability

Research direction

The issue names HWPSupervisor and its session.data variables but no files or tests; start by locating that component and reviewing how its state is currently exposed and logged. Define the required feed breadcrumbs and critical state changes with maintainers, then verify that shutdown behavior produces the intended feed data and log entries.

Written by the indexing model from the issue text.

Description

It seems that HWPSupervisor internal variables are available in session.data, but not published to a feed (for grafana etc) and there is very limited logging. This has complicated forensic understanding of behavior in shutdown situations so we should add some better breadcrumbs.

So request here is for:

  • some basic state and conclusions published to a feed
  • logging on critical state changes
Dominant language
Python
Stars
17
Forks
20
Avg merge
1h 22m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from simonsobs/socs

All issues in simonsobs/socs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.