LogoLogo
  • Overview
    • Introduction
    • Getting Started
    • Nimbus Hub
    • Log Optimization
      • Reduce Optimizations
      • Lint Optimizations
    • Working with NTL
      • Working with Transforms
    • Working with Aggregated Logs
    • Examples
    • Concepts
    • FAQ
    • Architecture
  • Additional Features
    • Configuration Overrides
    • Pause All
    • Error Detection
    • Private Link
  • Integrations
    • Datadog
      • AWS Lambda Extension
      • AWS Lambda Forwarder
      • DD Agent
      • DD Log Forwarding Destination
      • Heroku
      • Journald
      • OpenTelemetry
  • Resources
    • Nimbus Attributes
    • Changelog
    • SLA
    • Bug Bounty
    • Support
  • Preview Features
    • Metric Optimization
    • Datadog CLI
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Integrations
  2. Datadog

DD Agent

1. Add Nimbus as a log endpoint

Add the following configuration to your datadog config

observability_pipelines_worker:
  logs:
    enabled: true
    url: "https://YOUR_NIMBUS_ENDPOINT"

NOTE: YOUR_NIMBUS_ENDPOINT is an URL that is generated for you when you first create an account

Optionally, you can configure the endpoint using the following environmental variables. This is useful when you're running the datadog agent in kubernetes like environments and don't have easy access to the raw configuration.

DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_ENABLED=true 
DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_URL="https://YOUR_NIMBUS_ENDPOINT"

Update your datadog agent to run with the new configuration. Congratulations - you're now forwarding log traffic with Nimbus!

Last updated 1 year ago

Was this helpful?