3tears-observe
Structured logging, tracing, and OpenTelemetry setup for 3tears applications.
Modules
threetears.observe.logging-- Structured logging with context correlation and automatic call-site capture.threetears.observe.tracing--@traceddecorator (zero-cost without OpenTelemetry).threetears.observe.metrics--counter/histogram/gaugeget-or-create accessors plus the@metereddecorator built on them, records prometheus metrics (zero-cost without prometheus_client).threetears.observe.setup-- OpenTelemetry SDK bootstrap (TracerProvider, LoggerProvider, OTLP exporters).
Installation
pip install 3tears-observe
# With OpenTelemetry SDK support, traces over OTLP/gRPC:
pip install 3tears-observe[otel]
# The same over OTLP/HTTP, with no gRPC installed (about 10 MB against about 49):
pip install 3tears-observe[otel-http]
With otel-http, set TelemetryConfig(protocol="http/protobuf", endpoint="http://collector:4318");
spans go to <endpoint>/v1/traces. protocol defaults to "grpc", which needs the otel extra.
Log export is OTLP/HTTP under either extra.
1 maintainer
Metadata
1 maintainer
Release files for 3tears-observe 0.73.0
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 | |
|---|---|---|---|---|
| 3tears_observe-0.73.0.tar.gz | 94.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_observe-0.73.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 156.4 kB
Release files / 3tears_observe-0.73.0.tar.gz
| Download URL | 3tears_observe-0.73.0.tar.gz |
|---|---|
| Size | 94.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0a4e1e151dfcff968ae4cffd46da513300bed8d8e8be818f08f78a582725161
|
|
BLAKE2b-256 checksum How to use checksums |
27f8f5bea0fa635acc315ea5451fdca52760a68a30621f778c6c400ae9941ca3
|
| 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 20, 2026.
Transparency logRelease files / 3tears_observe-0.73.0-py3-none-any.whl
| Download URL | 3tears_observe-0.73.0-py3-none-any.whl |
|---|---|
| Size | 61.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ba134b4b7e0be7fa52fee9134e74f6eb854e9f8ac26bc73fa82f99abc0a34ba
|
|
BLAKE2b-256 checksum How to use checksums |
370cfad1321ddeb5891aca800d61d4979c6f19141c90a1666897f35170ae61cf
|
| 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 20, 2026.
Transparency logSecurity for 3tears-observe 0.73.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for 3tears_observe-0.73.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 Oct 20, 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.
