Skip to main content

Syvain Metrics Collector

Use this Python package to send metrics and annotations from a training, evaluation, or benchmark job to Syvain Metrics. Use syvain-metrics-api-client or syvain-metrics cli (available in npm) to read stored metrics.

Install

uv add syvain-metrics-collector

Collect an experiment

from syvain_metrics_collector import Collector

collector = Collector(api_key="ak_org_...")
experiment = collector.experiment(
	slug="mamba-run-001",
	description="Baseline mamba training run",
	folder_id="00000000-0000-0000-0000-000000000000",
	meta={
		"model": "mamba",
		"dataset": "internal-v1",
		"seed": 7,
		"config": {"batch_size": 32, "learning_rate": 0.0003},
	},
)

with experiment.run():
	for step in range(1, 1_001):
	  # run actual training
		loss = 1.0 / step

		if step == 1 or step % 10 == 0:
			experiment.metric(
				"loss",
				loss,
				step=step,
				metadata={"split": "train"},
			)

	experiment.annotation(
		"Checkpoint saved",
		metadata={"path": "checkpoints/mamba-run-001/step-999.pt"},
	)

experiment.flush_or_raise()

metric() and annotation() enqueue data. The collector sends queued batches in the background. experiment.run() records the lifecycle and attempts a best-effort flush when the block exits. The final flush_or_raise() fails the job if queued data cannot be delivered.

Use exactly one flush_or_raise() after the run() block. Do not call flush() or flush_or_raise() from the training loop, evaluation loop, reporting branch, or checkpoint branch.

Collect only measurements the experiment needs

Define the evidence before adding metrics. Each metric must be required to answer the experiment's question or to interpret training health. Do not emit every intermediate, tensor statistic, layer value, or runtime diagnostic.

Report training metrics at a planned cadence. Aggregate device tensors first, then convert them to Python numbers only when reporting. This avoids a device synchronization on every microbatch.

Put values in the right field

Value Field
Stable run identity and configuration Experiment meta
Numeric measurement Metric value
Training or evaluation progress Metric step
Bounded category used to group a series Metric metadata
Unique event details, paths, hashes, IDs, and text Annotation metadata

Use one stable metric name for one quantity and unit. Keep the same name across splits, datasets, stages, devices, and ranks:

experiment.metric("loss", train_loss, step=step, metadata={"split": "train"})
experiment.metric("loss", valid_loss, step=step, metadata={"split": "valid"})

Do not encode dimensions in the name:

# Wrong
experiment.metric(f"{stage}/{split}/loss", loss, step=step)

# Correct
experiment.metric(
	"loss",
	loss,
	step=step,
	metadata={"stage": stage, "split": split},
)

Keep metric metadata low-cardinality

Metric metadata is a flat str -> str mapping. Use it only for bounded categories needed to compare series, such as split, dataset, training_stage, device, rank, or optimizer parameter group.

Every distinct metadata mapping creates a separate series. The product of all dimension values, including missing-key variants, must stay at or below 4,096 series per metric in one experiment. For example, 8 stages, 3 splits, and 16 ranks produce 384 series.

Never put steps, epochs, timestamps, paths, sample or request IDs, hashes, free text, numeric measurements, or serialized objects in metric metadata. Put progress in step, stable configuration in experiment meta, and unique details in annotations.

The client accepts at most 32 metadata keys, 128 UTF-8 bytes per key, 512 UTF-8 bytes per value, and 4,096 UTF-8 bytes in the canonical JSON mapping. It validates these limits before enqueueing the metric. Metric values must be finite numbers; the client logs and drops non-finite values.

Use test collectors

Use NoopCollector when a test only needs the collector interface. Use JsonlCollector(path=...) when a local run needs inspectable JSONL output. Both collectors use the same experiment, metric, annotation, and lifecycle calls as Collector.

Release files for syvain-metrics-collector 0.0.322

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for syvain-metrics-collector 0.0.322
File Size Uploaded
syvain_metrics_collector-0.0.322.tar.gz 16.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for syvain-metrics-collector 0.0.322
File Interpreter ABI Platform
syvain_metrics_collector-0.0.322-py3-none-any.whl Python 3 none any Details

Total release size: 33.5 kB

Release files / syvain_metrics_collector-0.0.322.tar.gz

Download URL syvain_metrics_collector-0.0.322.tar.gz
Size 16.0 kB
Tags Source
SHA-256 checksum
How to use checksums
149d1e4155405202d414aac5a6d1123de8da9b61f05329334fbea7dd6fb29762
BLAKE2b-256 checksum
How to use checksums
805720e1508e82ccc2d64305d1105d87dd74c42db1765204b799e139c0fe3f18
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.10 {"installer":{"name":"uv","version":"0.12.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / syvain_metrics_collector-0.0.322-py3-none-any.whl

Download URL syvain_metrics_collector-0.0.322-py3-none-any.whl
Size 17.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aec20eebe64eb7bddda76998c60215ca26b7a9458cc631f052cb5899c3510e05
BLAKE2b-256 checksum
How to use checksums
915f840077e48c65c98a7abdd8124f54de2ce4fdf8f1422b72515e268dfd5ed8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.10 {"installer":{"name":"uv","version":"0.12.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page