nemo_gym.telemetry.spans

A CLIENT-kind span, which nemo-lens cannot currently produce.

nemo.lens.helpers.managed_span calls tracer.start_span(name) with no kind argument and exposes no way to pass one, so every span it creates is SpanKind.INTERNAL. For spans inside a service that is right. For Gym’s outbound calls it is not: an INTERNAL span on a cross-service hop means a backend cannot tell that the agent server called the model server, so Jaeger/Tempo/Honeycomb service maps lose the edge and client-vs-server latency attribution stops working.

Gym is pinned to nemo-lens b85578fc, so rather than change lens this module creates that one span directly against the OTel API. Adding a kind parameter to managed_span is the proper fix and is raised as a decision in the PR body; when it lands, delete this module and pass kind= instead.

Everything else is deliberately identical to managed_span: context attach/detach, exception recording, and an unconditional end() in finally.

Callers must gate on the span group themselves. Nothing here checks it, so that a disabled site does not pay for entering a context manager at all (kb/knowledge/conventions/hot-path-overhead.md).

Module Contents

Functions

API

nemo_gym.telemetry.spans.client_span(
    name: str,
    tracer: typing.Any = None,
    attributes: typing.Any = {}
)