Copybara import of the project: - #1768
Open
copybara-service[bot] wants to merge 1 commit into
Open
Conversation
copybara-service
Bot
requested review from
abheesht17,
hgao327,
jiangyangmu,
lc5211,
s-noghabi,
sizhit2,
tianshub and
wang2yn84
as code owners
July 27, 2026 19:42
|
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
copybara-service
Bot
force-pushed
the
test_954772841
branch
from
July 27, 2026 23:37
c15e291 to
a33458c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.