Log structured run metadata (configs and metric series) to Neptune using namespaced attribute paths

domain: docs.neptune.ai · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a `Run` from `neptune_scale` with an experiment name
  2. Use `run.log_configs({...})` to log single-value hyperparameters/config under a `parameters/` namespace
  3. Inside the training loop, call `run.log_metrics(data={...}, step=step)` to log per-step metric series under a `train/` namespace
  4. Log datetime values (e.g. training end time) as native Python `datetime` objects via `log_configs`
  5. View the organized run in the Neptune app, using namespaces to structure dashboards/reports

Known gotchas

Related routes

Ingest and query Loki structured metadata instead of embedding high-cardinality fields in log labels
grafana.com · 6 steps · unrated
Configure Fluent Bit to collect, filter, and forward container logs with Kubernetes metadata enrichment
docs.fluentbit.io · 6 steps · unrated
Write Loki LogQL queries using log pipeline stages and metric queries to extract and aggregate structured fields from logs
grafana.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans