Skip to content

Copybara import of the project: - #1768

Open
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_954772841
Open

Copybara import of the project:#1768
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_954772841

Conversation

@copybara-service

Copy link
Copy Markdown

Copybara import of the project:

--
23ee67c by Yu Yi yiyu@google.com:

Add opt-in OpenTelemetry double-write to MetricsLogger

Add an experimental, off-by-default enable_opentelemetry flag to
MetricsLoggerOptions. When set, every scalar logged through
MetricsLogger.log() is emitted both through the existing
Metrax/jax.monitoring backends (unchanged, still the default) and as
OpenTelemetry gauges with stable tunix.* instrument names,
low-cardinality prefix/mode attributes, and a separate
tunix.training.step gauge.

Because Weights & Biases has no OTLP endpoint for run metrics (its
native OTLP ingestion is traces-only via Weave), also add
tunix.sft.otel_wandb.WandbMetricsExporter, an OpenTelemetry SDK metric
exporter that forwards the gauges to wandb.log using the legacy
{prefix}/{mode}/{name} chart keys so both pipelines can be compared in
the same W&B project. An offline end-to-end test exercises the real
wandb client (wandb.init(mode="offline"), no account or network
needed) and verifies the per-step history written to the run.

OpenTelemetry is a new optional [otel] extra, not a core dependency;
providers and exporters remain application-owned.

@google-cla

google-cla Bot commented Jul 27, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

--
23ee67c by Yu Yi <yiyu@google.com>:

Add opt-in OpenTelemetry double-write to MetricsLogger

Add an experimental, off-by-default enable_opentelemetry flag to
MetricsLoggerOptions. When set, every scalar logged through
MetricsLogger.log() is emitted both through the existing
Metrax/jax.monitoring backends (unchanged, still the default) and as
OpenTelemetry gauges with stable tunix.* instrument names,
low-cardinality prefix/mode attributes, and a separate
tunix.training.step gauge.

Because Weights & Biases has no OTLP endpoint for run metrics (its
native OTLP ingestion is traces-only via Weave), also add
tunix.sft.otel_wandb.WandbMetricsExporter, an OpenTelemetry SDK metric
exporter that forwards the gauges to wandb.log using the legacy
{prefix}/{mode}/{name} chart keys so both pipelines can be compared in
the same W&B project. An offline end-to-end test exercises the real
wandb client (wandb.init(mode="offline"), no account or network
needed) and verifies the per-step history written to the run.

OpenTelemetry is a new optional [otel] extra, not a core dependency;
providers and exporters remain application-owned.

PiperOrigin-RevId: 954772841
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant