otel-metrics

Reusable OpenTelemetry library: simplified wrappers around OTel metric instruments, plus an OTLP tracing pipeline.

Install

pip install otel-metrics

Or from a built wheel:

pip install dist/otel_metrics-0.1.0-py3-none-any.whl

Usage

from enum import auto

from otel_metrics import MetricName, OtelConfig, setup_metrics

# Define your metric names
class MyMetrics(MetricName):
    REQUEST_COUNT = auto()
    REQUEST_DURATION_MS = auto()

# Configure and initialize
config = OtelConfig(endpoint="http://localhost:4317", service_name="my-service")
metrics = setup_metrics(config)

# Create instruments
counter = metrics.counter(MyMetrics.REQUEST_COUNT, description="Total requests")
timer = metrics.timer(MyMetrics.REQUEST_DURATION_MS, description="Request latency")

# Record
counter.inc()

Timing operations

from otel_metrics import TimestampNS

start = TimestampNS.now()
# ... do work ...
timer.record(start)

Configuration

OtelConfig is a pydantic-settings model. Values resolve from constructor args or environment variables:

Supported protocols: grpc, http/protobuf.

headers accepts either a mapping or the OTLP key=value,key2=value2 string form, and is forwarded to both the metrics and traces exporters. Values may be URL-encoded per the OTLP spec, but plain values are accepted too.

Tracing

from otel_metrics import OtelConfig, setup_telemetry

config = OtelConfig(
    endpoint="https://api.braintrust.dev/otel",
    service_name="my-service",
    protocol="http/protobuf",
    headers={"Authorization": "Bearer <key>", "x-bt-parent": "project_id:<id>"},
)
tracer = setup_telemetry(config)

with tracer.start_as_current_span("my-operation"):
    ...

setup_telemetry sets the process-global tracer provider, so call it once at startup and before importing anything that captures a tracer. Use build_test_tracer() for a non-exporting tracer in unit tests.

Testing

Use build_test_metrics() to get a no-op Metrics instance for unit tests:

from otel_metrics import build_test_metrics

metrics = build_test_metrics()

Development

uv sync
uv run pytest
uv run ruff check .

Build

uv build

Produces a wheel and an sdist in dist/.

Releasing

Publishing happens on merge to main. The workflow runs the tests and builds on every merge, but only uploads when the version in pyproject.toml is one PyPI has not seen — so bumping the version is what cuts a release. Merging anything else is a no-op for the index.

To release: bump version, open a PR, merge it.

Uploads use PyPI Trusted Publishing, so no API token lives in this repo. It needs a one-time setup on each index:

1. On PyPI, go to Your projects → Publishing (or Account → Publishing for a name that has never been published) and add a GitHub publisher:

   Field	Value
   Owner	venkateshvasuki
   Repository	reusable_otel_metric
   Workflow	publish.yml
   Environment	pypi

2. In this repo's Settings → Environments, create an environment named pypi. Add required reviewers there if releases should need a human approval.

Repeat with an environment named testpypi on test.pypi.org to use the manual Run workflow button, which defaults to TestPyPI.