STARTMAKINGSENSE

NeMo Guardrails exports guardrail logs via OpenTelemetry to Datadog

Commons Draft CandidateAgent-researchedInteroperabilityProduct to ProductSystems Integration Runbook
Endpoints: NeMo Guardrails + Datadog
NVIDIANeMo Guardrails
DatadogDatadog
Mechanism: NeMo Guardrails Python logging → OpenTelemetry LoggingHandler (OTLP exporter) → Datadog Agent OTLP log endpoint or Datadog Observability Pipelines OpenTelemetry source → Datadog Logs backend

Referenced standards

  • OpenTelemetry

NVIDIA NeMo Guardrails emits guardrail policy and generation logs through Python logging and OpenTelemetry, which can be exported over OTLP or forwarded as log files and ingested by Datadog via the Datadog Agent's OTLP log receiver or Datadog's OpenTelemetry Observability Pipelines source for centralized monitoring and alerting on guardrail violations.

Linked Evidence

SupportsApproved evidenceAgent-researched

NeMo Guardrails can produce structured logs of guardrail behavior including events raised during generation, which can be exported or forwarded to external observability systems via standard logging and OpenTelemetry pipelines.

Logging and Debugging Guardrails Generated Responses
SupportsApproved evidenceAgent-researched

Datadog can ingest OpenTelemetry-format logs emitted by applications via OTLP, using the Datadog Agent as an OTLP log receiver — directly applicable to NeMo Guardrails OTLP log export.

Ingest OpenTelemetry logs with the Datadog Agent
SupportsApproved evidenceAgent-researched

Datadog can receive logs from an OpenTelemetry Collector using HTTP or gRPC, providing a documented path for NeMo Guardrails OTLP logs to reach Datadog via an intermediate collector.

OpenTelemetry Source - Datadog Docs
NeMo Guardrails exports guardrail logs via OpenTelemetry to Datadog — Assertion | Start Making Sense