runspec-logops
Log-condensing and code-mapping runnables for
runspec — cheap application-support triage
from a log file. The runnables do the heavy lifting on the host where the log
lives and return small structured JSON, so the runspec-console agent reads
condensed conclusions, not raw logs or code. pip install it into a venv and the
runnables are discoverable by runspec local, runspec serve (MCP), and
runspec-console.
Install
pip install runspec-logops
Runnables
| Runnable | Autonomy | What it does |
|---|---|---|
summarize-log |
autonomous | Streams a log and clusters repeated errors by a normalised signature, returning a bounded top-N digest (counts, first/last timestamp, one sample each) whose size is independent of input size. Supports a --level floor and a --since/--until window. |
map-trace |
autonomous | Resolves a stack trace — or a summarize-log signature like NullPointerException@com.acme.OrderSvc.price — to just the source snippets around each frame in a checkout (--repo). |
bundle-digest |
confirm | Zips a digest + snippets + manifest for transfer (e.g. via runspec-console's download_file). |
The operator's flow: use the console's filtered fetch to colocate the log with the code (remote or local), then run these over it.
summarize-log --path /var/log/app/app.log --level error --top 20
map-trace --repo /srv/checkouts/orders --trace "NullPointerException@com.acme.OrderSvc.price"
Public Python API
The pure logic is in runspec-logops-core — no
runspec dependency, no runspec.toml, no entry points, so installing it
exposes the helpers for import without surfacing any runnables:
from runspec_logops_core import summarize_log, map_trace_to_sources, build_bundle
digest = summarize_log("/var/log/app/app.log", level="error", top=20)
All params are plain (summarize_log(path, *, level, since, until, top, max_sample_lines, max_bytes), etc.), so a private (e.g. Nexus-hosted) wrapper
can bake in corporate defaults / paths / redaction and publish only its own
runnables.
Development
python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
ruff check . && ruff format --check .
pytest
Metadata
Release files for runspec-logops 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| runspec_logops-0.1.4.tar.gz | 6.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runspec_logops-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 kB
Release files / runspec_logops-0.1.4.tar.gz
| Download URL | runspec_logops-0.1.4.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34119974b2678a0462d1914d3d536b8d3f3d6fb50b78fc4a8e085e325c69a4c7
|
|
BLAKE2b-256 checksum How to use checksums |
4031923d1b246da722df58ae5629ea13e07b5dd15fc5cfe5df84b93b2692d1f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.
Transparency logRelease files / runspec_logops-0.1.4-py3-none-any.whl
| Download URL | runspec_logops-0.1.4-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d35cf4036557cea02d374b3dce25b0dc3add5305a7f683f66afaeae7957e852
|
|
BLAKE2b-256 checksum How to use checksums |
54438396697b43dda8b8b8d844ea2467f01b79db974d3053466f55bf34841a94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.
Transparency log