Skip to main content

CI PyPI Python License

e-track

Run tracking for agent systems. A source turns a framework's run into one event model; the model travels on a structlog channel of its own; a bus fans it out to parallel sinks, each reading the partial view it declares.

framework hooks ─► source ─► fold ─► channel (validate → publish → forward to host logger)
                                                 │
                                                 └─► bus ─┬─► otlp   spans + logs → Langfuse · LangSmith · Tempo · Phoenix
                                                          ├─► live   per-thread replay + push → a canvas, a chat
                                                          └─► yours  any SinkPort, any EventView

Part of the EDamLabs eager series: EDamLabs' own e- products (EDamLabs families).

Install

uv add "e-track[langgraph,otel]"    # or: pip install "e-track[langgraph,otel]"

Extras: langgraph (LangGraph/deepagents source and topology), otel (OTLP driver), topology (layout), all. Python 3.14+, typed (py.typed).

Usage

from contextlib import AsyncExitStack

from etrack.logic.api import Tracker
from etrack.logic.channel import EventChannel
from etrack.models.event import EventKind
from etrack.providers.adapters.bus.anyio import AnyioAdapter
from etrack.providers.adapters.sink.live import LiveAdapter
from etrack.providers.adapters.source.langgraph import LanggraphSourceAdapter
from etrack.providers.drivers.sink.otlp import OtlpDriver

async with AsyncExitStack() as stack:                       # the host's composition root
    live = await stack.enter_async_context(LiveAdapter())
    otlp = await stack.enter_async_context(OtlpDriver())
    bus = AnyioAdapter()
    bus.subscribe(live)
    bus.subscribe(otlp, select=lambda event: event if event.part is None else None)  # policy per sink
    await stack.enter_async_context(bus)                   # opened last: closed first, drains into the sinks
    tracker = Tracker(EventChannel(bus), LanggraphSourceAdapter(mcp=frozenset({"onto_query"})))

    with tracker.track(thread="t1", config={"configurable": {"thread_id": "t1"}}) as run:
        await graph.ainvoke({"messages": [("user", "hola")]}, run.config)
        with run.fold.span("gate", kind=EventKind.EVALUATION):
            ...                                             # the project's own code, same tree

With the house renderer (ELogger) on the host:

2026-11-03T12:00:00Z | INFO | run.event || run_id: 019a… || kind: node || phase: start || name: agent || step: 1

Every frame is also a line on the host's etrack logger, rendered by the host's own structlog setup; e-track never configures logging.

The record

Field What
run_id, thread_id the run (32 hex, also the W3C trace id) and the conversation
seq, id, parent order within the run; the span and its visible parent
kind run agent subagent node llm embedding retrieval tool mcp interrupt state evaluation custom
phase start delta end error instant
part on deltas: text reasoning tool_call image audio video file custom
node, ns, step, visit graph coordinates: node, subgraph path, superstep, times the run entered the node
message_id, call_id the chat message and the tool call a client renders
model, usage, error typed sections: provider/name/params, tokens/cost, failure
payload, attributes what the span carried (redacted); the open, namespaced extension bag

Grow it by subclassing RunEvent and passing the subclass to EventChannel(model=…); read it through an EventView.

The full guide lives at edamlabs.github.io/e-track.

Development

make install        # sync deps + prek hooks
make check          # lint + type + arch + validate + test
make cov            # coverage gate: 100 % lines and branches, every outbound service faked in process
make integration    # real services: the session fixtures bring sandbox/compose.yml up and down (collector + Phoenix)
make ci             # every gate CI runs, in one command

Stack: uv · ruff · ty · tach · pytest (xdist, randomly, pytest-docker) · prek · zizmor · Zensical · Renovate. Released from a v* tag through PyPI trusted publishing; maintained by the EDamLabs fleet.

Metadata

Release files for e-track 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for e-track 0.1.0
File Size Uploaded Provenance Actions
e_track-0.1.0.tar.gz 61.4 kB With provenance Details for e_track-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for e-track 0.1.0
File Interpreter ABI Platform Actions
e_track-0.1.0-py3-none-any.whl Python 3 none any Details for e_track-0.1.0-py3-none-any.whl

Total release size: 107.1 kB

Release files / e_track-0.1.0.tar.gz

Download URL e_track-0.1.0.tar.gz
Size 61.4 kB
Tags Source
SHA-256 checksum
How to use checksums
026c2b5404fcb880fa53eaad5bc4380dea6d5cb9c185ae5635f2d5fd23cde742
BLAKE2b-256 checksum
How to use checksums
2c5ca35200824c9b2fac11486b826716d96fb14dd91b652cc6d4822b440f7789
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Release files / e_track-0.1.0-py3-none-any.whl

Download URL e_track-0.1.0-py3-none-any.whl
Size 45.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4b8bfb55c2e5d5c7a9e5c70052f2d88eabb47c04c94fb95b619d15bccd6e69b2
BLAKE2b-256 checksum
How to use checksums
234d056139e969193b3e54bdc7104c4c51a604ffc5cf30d3ff015901f00d67fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 3, 2026.

Transparency log

Security for e-track 0.1.0

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for e_track-0.1.0.tar.gz

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 Nov 3, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page