pytracer-gateway
Layer 2 of pyTracer: a stateless FastAPI service that receives batched spans from deployed SDKs, validates them against the span schema, authenticates each project by API key, and writes them through to the ClickHouse trace store via an internal queue so a traffic spike never blocks ingestion.
# Run it (writes to ClickHouse from docker-compose):
PYTRACER_GATEWAY_API_KEYS="devkey:my-app" uvicorn pytracer_gateway.app:build_default_app --factory --port 8080
POST /v1/spans body: {"spans": [ <span>, ... ]} header: X-API-Key: <key>
GET /healthz liveness
GET /readyz readiness (ingest worker running)
GET /v1/stats ingest counters
Compatibility
The gateway ignores span fields it does not recognise instead of rejecting the span, so a newer SDK that adds an optional field still ingests against an older gateway. When upgrading a release that adds a span field, upgrade the gateway before the SDKs that send to it, so the field is understood wherever it lands.
1 maintainer
Metadata
1 maintainer
Release files for pytracer-gateway 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pytracer_gateway-0.1.3.tar.gz | 35.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytracer_gateway-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.1 kB
Release files / pytracer_gateway-0.1.3.tar.gz
| Download URL | pytracer_gateway-0.1.3.tar.gz |
|---|---|
| Size | 35.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d81b8cd5cb383a77dd6091bc86ac6637b0afed6252b76b97b8709f9d3515537
|
|
BLAKE2b-256 checksum How to use checksums |
edb7ea3eabf9c7170e747924cbb3c6628181af404abcfaddaf4bdaa1e8eefb8c
|
| 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 Oct 24, 2026.
Transparency logRelease files / pytracer_gateway-0.1.3-py3-none-any.whl
| Download URL | pytracer_gateway-0.1.3-py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c398f55ae8f6f892ba184b78dec4033de06a7d3fee50a1399b1746be0b085cc3
|
|
BLAKE2b-256 checksum How to use checksums |
b4d03acde48b0b853ffe14ce0241b6adb44d94b829fe6852ce006d94497a8ee0
|
| 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 Oct 24, 2026.
Transparency logSecurity for pytracer-gateway 0.1.3
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pytracer_gateway-0.1.3.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 Oct 24, 2026.
Transparency logA 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.
