Observability & Logs
Inspect every request, stream logs to external tools, and control PII masking
Last updated
Every request through NemoRouter is logged. The Logs page is your request-by-request view, and Log Settings lets you forward those events to the observability tools you already use.
The request log
The Logs page (/logs) lists individual requests. Each row shows:
- Model and provider
- Token counts and total cost
- Latency and status (success / error)
- Cache-hit status
- Start/end timestamps and a request ID
Search by request ID to jump straight to a specific call, and export the current view to CSV. Click into a row for the full request/response detail.
Logs apply PII masking both in your browser (email/phone/card patterns) and on the server when org-level redaction is enabled — see Data Policy below.
Logging callbacks (stream logs out)
Under Log Settings → Callbacks, forward request logs to external platforms. Each callback can fire on success only, failure only, or both:
| Destination | Typical use |
|---|---|
| Langfuse | LLM tracing and evals |
| Datadog | Metrics and APM |
| Amazon S3 / Google Cloud Storage | Long-term raw log archive |
| Slack | Push notable events to a channel |
| Athina | LLM monitoring and evaluation |
| OpenMeter | Usage metering |
| Custom Callback | POST logs to your own HTTP endpoint |
Each destination has its own credentials (for example, Langfuse needs its public/secret keys and host). Sensitive fields are masked in the UI with a show/hide toggle.
Data policy & PII masking
Your organization controls how much request data is retained and whether PII is redacted before it's stored. Configure logging level and PII masking in Privacy Settings. Cost headers (x-nemo-request-cost) always pass through so spend stays accurate regardless of logging level.
Alert channels
Log Settings → Alert Channels defines where notifications go — Email, Slack, Microsoft Teams, Jira, or a generic Webhook. You then bind these channels to specific alerts; see Alerts & Notifications.
Next steps
- Alerts & Notifications — Get notified on errors, slow calls, and budget thresholds
- Analytics & Reports — Aggregate the same data into spend and usage reports
- Guardrails — Correlate guardrail decisions with request logs by request ID