Skip to main content

Trazio Telemetry SDK for Python

Version 0.3.0 renames the package from hyperlake-telemetry; the API is unchanged. See SDK integration and release status.

trazio-telemetry sends standards-compatible OTLP/HTTP JSON, attaches events and immutable artifacts, manages tenant-editable settings, and performs scoped event, artifact, video, Run, and evidence-graph investigations. It does not replace the OpenTelemetry SDK: applications with existing instrumentation should continue using their normal exporter and use this package only for run context, stable event identity, evaluations, and artifact attachment.

pip install trazio-telemetry
from trazio_telemetry import Client, Privacy

client = Client(
    base_url="https://us.hyperlake.cloud",
    protocol_token="write-only-protocol-token",
    tenant_jwt="short-lived-jwks-jwt",
    privacy=Privacy(capture_content=False),
)

with client.run("invoice-agent", goal_id="goal-42") as run:
    with run.span("lookup-account", kind="RETRIEVER"):
        pass
    run.evaluate("groundedness", score=0.97, label="pass")

client.flush()

result = client.semantic_query(
    "Show critical robot video and related faults from the last 2 hours"
)

detection = client.analyze_live_frame(
    "./frame.jpg",
    stream_session_id="camera-session-17",
    frame_id="frame-42",
    device_id="robot-17",
)

analyze_live_frame() uses the immutable model profile pinned to the JWT's pipeline. It requires a short-lived JWT with live:analyze and event:ingest. The response is a factual object-detection result; the attached live Rule Packs determine whether it becomes an alert or notification.

The JWT determines tenant and pipeline routing. Explicit routing IDs are optional with a JWT and are rejected when they conflict with its claims. Local claim decoding is not signature verification; the regional service verifies signature, issuer, audience, expiry, permissions, tenant, and pipeline for every request. Prompt, response, tool argument, and tool result content is suppressed by default. Set capture_content=True only after applying an approved data policy.

See the repository integration guides for Temporal, Langflow, OpenInference, Collector, and Alloy examples.

Reliable semantic queries

semantic_query() creates and validates a versioned, bounded query plan before calling any endpoint. Plans may target event retrieval, artifact/vector search, and evidence-graph traversal, but cannot contain tenant, pipeline, URL, token, SQL, or authorization fields. Every response includes the plan hash and scope provenance.

DeterministicSemanticPlanner works without an LLM. ModelSemanticPlanner accepts any callable that returns a JSON-like object; unsafe or invalid model output falls back to the deterministic plan. A model therefore interprets user intent but cannot expand authorization or execute arbitrary queries.

Artifact and video retrieval uses configured vector embeddings. Event retrieval is bounded structured/lexical retrieval, while graph results come from recorded scoped evidence edges. These signals remain separate and similarity is not treated as causation.

The client also exposes event listing/search, artifact search/upload/download, typed telemetry, video playback/timeline, Runs, evidence graphs, tenant config, protocol-token rotation, and Rule Pack validate/dry-run/publish helpers.

Metadata

Release files for trazio-telemetry 0.3.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 trazio-telemetry 0.3.0
File Size Uploaded Provenance Actions
trazio_telemetry-0.3.0.tar.gz 20.5 kB Without provenance Details for trazio_telemetry-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for trazio-telemetry 0.3.0
File Interpreter ABI Platform Actions
trazio_telemetry-0.3.0-py3-none-any.whl Python 3 none any Details for trazio_telemetry-0.3.0-py3-none-any.whl

Total release size: 37.6 kB

Release files / trazio_telemetry-0.3.0.tar.gz

Download URL trazio_telemetry-0.3.0.tar.gz
Size 20.5 kB
Tags Source
SHA-256 checksum
How to use checksums
1b5d76ca5f4f5764bdd202ced8349d2dd51cb9df1df81072ec1b36f36dc80062
BLAKE2b-256 checksum
How to use checksums
3daa43b3bffcb79747894aaf4187e3f68ccd9b2154c66170ee42bc88c3a32170
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.15.0

Release files / trazio_telemetry-0.3.0-py3-none-any.whl

Download URL trazio_telemetry-0.3.0-py3-none-any.whl
Size 17.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bc3e25105722874ac04b3b04ac9b0be3ec9a467770f8a9cb1437e7500f70bd44
BLAKE2b-256 checksum
How to use checksums
d6b6546e2daae0c8181f49cef645df1820d0448a0d704983b562c44d363faa26
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.15.0

Security for trazio-telemetry 0.3.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files No provenance

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