Inwire Observe User Guide

Monitor model, agent, and platform behavior through traces, metrics, alerts, costs, drift, errors, events, topology, and runbooks.

Who This Guide Is For

Where To Go

Page Use It For
/inwire-observe Observe dashboard.
/inwire-observe/metrics Metrics exploration.
/inwire-observe/traces Trace inspection.
/inwire-observe/alerts Alert rules and incidents.
/inwire-observe/errors Error analysis.
/inwire-observe/drift Drift monitoring.
/inwire-observe/costs Cost analysis.
/inwire-observe/topology Service topology.
/inwire-observe/runbooks Operational runbooks.
/inwire-observe/live-tail Live log tailing.

Core Concepts

Concept Meaning
Trace A request-level timeline across services and model calls.
Metric A numeric signal such as latency, throughput, error rate, token cost, or GPU usage.
Drift A change in inputs, embeddings, outputs, or behavior over time.
Alert A rule that triggers when a signal crosses a threshold.
Runbook A documented response procedure for known incidents.

Common Workflows

Investigate an incident

  1. Open Alerts or Errors.
  2. Identify impacted deployment, agent, or service.
  3. Open traces and metrics for the same time window.
  4. Check topology and dependency status.
  5. Run the relevant runbook.
  6. Record outcome and follow-up.

Monitor drift

  1. Open Drift.
  2. Select model, pipeline, or embedding source.
  3. Review drift metric and sample changes.
  4. Compare with recent releases or data changes.
  5. Trigger evaluation, retraining, or rollback if needed.

Best Practices