nv-one-logger-core
Extensions to onelogger library to use Open telemetry (OTEL) as a backend.
Decision gist · record as of 2026-08-14
Yes, if you need a lightweight, vendor-agnostic telemetry foundation for applications or jobs. The core is intentionally minimal to avoid dependency conflicts. However, the aging maintenance status (289 days since last release) suggests limited active development—verify whether it fits your stability and support expectations before committing to it as a long-term instrumentation backbone.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.8 or later (supports up to 3.13).
- Runtime dependencies (pydantic, overrides, StrEnum, toml, typing-extensions) must be available.
- Low install friction with a pure-Python wheel distribution.
License · maintenance · safety
Apache-2.0 (permissive) — Licensed under Apache-2.0 (permissive), allowing use in most commercial and open-source projects with minimal restrictions.
last release 2025-10-29 (289 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 231,034 downloads/mo, #9,099 on PyPI
Alternatives
Verify before relying
pip install nv-one-logger-core
from nv_one_logger.api.timed_span import configure_one_logger, get_recorder, timed_span
from nv_one_logger.core import Attributes
with timed_span(name="operation", span_attributes=Attributes({"tag": "value"})):
# business logic here
pass- Whether the package is actively maintained or in stable/maintenance-only mode despite the aging status
- Real-world performance characteristics when handling high-volume telemetry from large-scale jobs
What it is and what it does
nv-one-logger-core is a telemetry collection library that provides the foundational abstractions for instrumenting applications—particularly long-running jobs like ML training. It defines core concepts (spans representing units of work, events representing singular points in time, and attributes as properties) modeled on OpenTelemetry standards. The library intentionally keeps its core lightweight by minimizing third-party dependencies, allowing it to be adopted without conflicting with existing application dependencies.
The package provides a Recorder interface that applications use to start and stop spans, record events, and report errors. It also includes a flexible exporter configuration system supporting direct code configuration, YAML/JSON files, and Python entry points, with clear priority rules. Applications can use it via higher-level domain-specific libraries, the Recorder interface directly, a context manager (timed_span), or by instantiating exporters manually—though the Recorder approach is recommended to reduce instrumentation mistakes.
Use it for
- Instrument ML training jobs to track checkpointing, model evaluation, and other domain-specific events with automatic timing
- Collect distributed traces from microservices by creating spans for operations and exporting them to a collector pipeline
- Add telemetry to long-running batch jobs with configurable exporters (Kafka, Weights & Biases, OTEL collector) without tight coupling
- Build domain-specific observability libraries on top of the core abstractions for specialized application types
- Aggregate and filter telemetry events at the recorder level (e.g., computing checkpoint statistics across multiple events)
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need a lightweight, vendor-agnostic telemetry foundation for applications or jobs.
The core is intentionally minimal to avoid dependency conflicts. However, the aging maintenance status (289 days since last release) suggests limited active development—verify whether it fits your stability and support expectations before committing to it as a long-term instrumentation backbone.
Install
nv-one-logger-core on PyPI
Before you install
Low install friction with a pure-Python wheel distribution. Maintenance status is aging (289 days since last release), which may indicate the package is stable but not actively developed.
Requires Python 3.8 or later (supports up to 3.13). Runtime dependencies (pydantic, overrides, StrEnum, toml, typing-extensions) must be available.
License in practice
Licensed under Apache-2.0 (permissive), allowing use in most commercial and open-source projects with minimal restrictions.
Quickstart
pip install nv-one-logger-core
from nv_one_logger.api.timed_span import configure_one_logger, get_recorder, timed_span
from nv_one_logger.core import Attributes
with timed_span(name="operation", span_attributes=Attributes({"tag": "value"})):
# business logic here
passVerify before relying
- Whether the package is actively maintained or in stable/maintenance-only mode despite the aging status
- Real-world performance characteristics when handling high-volume telemetry from large-scale jobs
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release <4.0,>=3.8 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 5 packagespydanticoverridesStrEnumtomltyping-extensions |
| Maintenance | Aging 289 days since the last release |
| First released | |
| Downloads | 231,034 / month, #9,099 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | License :: OSI Approved :: Apache Software LicenseProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: nv_one_logger_core-2.3.1-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “job telemetry logging”
- nv-one-logger-coreProvides core telemetry abstractions (spans, events, attributes) and…
- cronitorA Python client library for Cronitor that monitors background jobs,…
- nv-one-logger-pytorch-lightning-integrationAdds training telemetry collection to Lightning applications via…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also uipath-core · nv-one-logger-pytorch-lightning-integration · azure-core-tracing-opentelemetry · azure-monitor-opentelemetry-exporter · opentelemetry-exporter-gcp-trace · opentelemetry-exporter-jaeger · opentelemetry-exporter-otlp-proto-grpc · opentelemetry-exporter-otlp · buildkite-test-collector