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
Under Log Settings → Callbacks, configure external observability platforms as log destinations. Each callback can be set to 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.
Beta — coming soon. You can add destinations and verify their credentials with Test connection today. Automatic streaming of your request logs to these services is not yet active; we'll enable delivery soon.
Data policy & PII masking
Your organization controls how much request metadata is retained and whether PII is redacted. Request/response content is not stored today (a privacy-safe default) — the logging level governs metadata retention, and Full Logging (capturing request/response content for debugging) is coming soon. 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
Observability → Alerts → Channels defines where notifications go — Email, Slack, Microsoft Teams, Jira, or a generic Webhook. To route a budget alert to one of these channels with a custom threshold, bind it on the Budget Controls page; see also 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
FAQ
What does each row in the request log show me?
The Logs page lists every request individually, with the model and provider, token counts and total cost, latency and status (success or error), cache-hit status, start/end timestamps, and a request ID. Click into any row to see the full request and response detail.
Can I look up a single request or export my logs?
Yes. Search by request ID to jump straight to a specific call, and use the CSV export to download the current filtered view. You can also filter by model, status, and time range before exporting.
Do I need to change my application code to get request logging?
No. Every request through NemoRouter is logged automatically — there's no SDK change, header, or flag to enable. Logs appear on the Logs page as soon as calls run.
Who can change the logging level and data policy?
Viewing logs is available to your whole organization, but changing the logging level (zero, metadata, full, or PII-redacted) is an owner/admin action — members see the Privacy Settings controls as read-only. This is a documented permission boundary, not a temporary limitation.
If I reduce logging or redact PII, will my spend numbers still be accurate?
Yes. The cost header (x-nemo-request-cost) always passes through regardless of your logging level, so spend, budgets, and analytics stay accurate. Request/response content is not stored today (a privacy-safe default); the logging level controls how much request metadata is retained, never billing.
Which external tools can I stream my logs to?
Under Log Settings → Callbacks you can configure Langfuse, Datadog, Amazon S3, Google Cloud Storage, Slack, Athina, OpenMeter, or your own HTTP endpoint via a Custom Callback as log destinations. Each has its own credentials, entered once and masked in the UI with a show/hide toggle. Adding destinations and verifying them with Test connection works now; automatic streaming of your request logs to these services is in Beta and coming soon.
Can I forward only failed requests to an external tool?
Yes. Each callback can be set to fire on success only, failure only, or both — so you can, for example, push only errors to a Slack channel while archiving everything to S3.
How is PII protected in my logs, and where do I control it?
Logs apply PII masking in two places: pattern-based masking (email, phone, card) in your browser, and server-side redaction when org-level redaction is enabled. You configure the logging level and PII masking in Privacy Settings.
What's the difference between a logging callback and an alert channel?
A logging callback is a destination for your request logs on an observability or storage platform (Langfuse, Datadog, S3, and so on) — you can configure destinations and verify them today, and automatic streaming is coming soon (Beta). An alert channel (Email, Slack, Microsoft Teams, Jira, or a generic Webhook) is where notifications go when an alert fires — you bind a channel to a budget's thresholds on the Budget Controls page.
Who can set up logging callbacks and alert channels?
Creating or editing callbacks and alert channels is an admin/owner action; members can view the configuration but not change it. This keeps log-forwarding destinations and their credentials under your organization's administrators.