livepeer / livepeer/livepeer-python-gateway
Operator-visible logging for the live runner lifecycle
Open
@rickstaa is already working on this.
Since Jun 15, 2026.
- Dominant language
- Python
- Stars
- 1
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
What
Add operator-visible logging for the live runner lifecycle, so "is my runner connected, and at what price?" can be read from logs instead of inferred from /discovery.
Lifecycle events to surface:
Dynamic runners
live runner registered— new-runner branch ofHeartbeatlive runner deregistered— with areason(heartbeat timeouton crash/OOM/network loss/hard kill,unregisteron graceful SDK shutdown)
Static runners
static live runner registered— first registration onlystatic live runner health changed— onready <-> unavailabletransitions
Pricing
live runner price set— debug level, on first set and on actual change
Why
Better logging makes the runner lifecycle observable for developers and operators running the live runner via the Python SDK.
Implementation
The go-livepeer side is implemented in livepeer/go-livepeer#3943.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.