ohmr
For generating, encoding and managing runtime trace ids. These are typically used to link side-effects:
db records
search documents
log entries
…
for things like debugging, auditing, isolation, etc.
Get it like:
$ pip install ohmrFirst create a tracer e.g. like:
import coid
import ohmr
trace = ohmr.Tracer(coid.Id(prefix='OHM-'))Then use it, most likely at session begin/resume points, e.g. like:
import flask
app = flask.Flask('krazy_eyez_killah')
@app.before_request
def set_trace_id()
trace.reset()1 maintainer
Metadata
1 maintainer
Release files for ohmr 0.1.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 | |
|---|---|---|---|---|
| ohmr-0.1.0.tar.gz | 1.9 kB | Without provenance | Details |
Release files / ohmr-0.1.0.tar.gz
| Download URL | ohmr-0.1.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8d7c78b15edcd17e1a8e8f52aa67d03fdbe7841481928ba87be004b324c33b3
|
|
BLAKE2b-256 checksum How to use checksums |
bc88df97c45e84f0788cb61c35ce005b304b83ea3490dc1ec5162a9769e83a8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ohmr 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.
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.
