{"id":79426,"date":"2026-10-20T04:45:05","date_gmt":"2026-10-20T04:45:05","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=79426"},"modified":"2026-10-20T04:45:09","modified_gmt":"2026-10-20T04:45:09","slug":"how-to-install-datadog-cli-on-macos-windows-and-linux-complete-step-by-step-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-install-datadog-cli-on-macos-windows-and-linux-complete-step-by-step-guide\/","title":{"rendered":"How to Install Datadog CLI on macOS, Windows, and Linux: Complete Step-by-Step Guide"},"content":{"rendered":"\n

SEO Title:<\/strong> How to Install Datadog CLI on Mac, Windows & Linux \u2013 Complete 2026 Tutorial<\/p>\n\n\n\n

Meta Description:<\/strong> Learn how to install Datadog Pup CLI and Datadog CI CLI on macOS, Windows, Ubuntu, Debian, RHEL, and CentOS. Includes installation commands, authentication, verification, troubleshooting, and updates.<\/p>\n\n\n\n

Focus Keywords:<\/strong> install Datadog CLI, Datadog CLI macOS, Datadog CLI Windows, Datadog CLI Linux, Datadog Pup CLI, Datadog CI CLI, datadog-ci install, Datadog Homebrew, Datadog CLI Ubuntu<\/p>\n\n\n\n

\n\n\n\n

1. Introduction<\/h2>\n\n\n\n

Datadog is a cloud-based observability and monitoring platform that helps organizations monitor applications, infrastructure, logs, metrics, traces, security events, and cloud services.<\/p>\n\n\n\n

Although Datadog provides a comprehensive web interface, developers, DevOps engineers, SREs, and platform engineers often need command-line tools to manage monitoring resources and automate operations.<\/p>\n\n\n\n

Datadog provides CLI tools for these tasks.<\/p>\n\n\n\n

In this tutorial, we will learn how to install and configure Datadog command-line tools across macOS, Windows, and Linux.<\/p>\n\n\n\n

We will cover:<\/p>\n\n\n\n

    \n
  • Installing Datadog Pup CLI on Intel and Apple Silicon Macs.<\/li>\n\n\n\n
  • Installing Datadog CLI on Windows using PowerShell.<\/li>\n\n\n\n
  • Installing Datadog CLI on Ubuntu and Debian.<\/li>\n\n\n\n
  • Installing Datadog CLI on RHEL, CentOS, and Amazon Linux.<\/li>\n\n\n\n
  • Installing the Datadog CI CLI using npm.<\/li>\n\n\n\n
  • Authenticating with Datadog using OAuth2 or API keys.<\/li>\n\n\n\n
  • Managing monitors, logs, metrics, dashboards, and SLOs.<\/li>\n\n\n\n
  • Updating and uninstalling Datadog CLI.<\/li>\n\n\n\n
  • Troubleshooting installation and authentication problems.<\/li>\n<\/ul>\n\n\n\n

    2. Understanding Datadog’s Different CLI Tools<\/h2>\n\n\n\n

    Unlike GitHub, which provides a general-purpose executable named gh<\/code>, Datadog has several command-line tools designed for different purposes.<\/p>\n\n\n\n

    Tool<\/th>Executable<\/th>Primary purpose<\/th><\/tr>
    Datadog Pup CLI<\/td>pup<\/code><\/td>General-purpose Datadog API and resource management<\/td><\/tr>
    Datadog CI CLI<\/td>datadog-ci<\/code><\/td>CI\/CD automation and Continuous Testing<\/td><\/tr>
    Datadog Agent CLI<\/td>datadog-agent<\/code><\/td>Local monitoring Agent administration<\/td><\/tr>
    Datadog Sync CLI<\/td>datadog-sync<\/code><\/td>Synchronize supported resources between organizations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Which Datadog CLI Should You Install?<\/h3>\n\n\n\n

    If you want to work with monitors, dashboards, logs, metrics, SLOs, or other Datadog platform resources, use Datadog Pup CLI<\/strong>.<\/p>\n\n\n\n

    If you need to integrate Datadog with GitHub Actions, GitLab CI, Jenkins, Azure DevOps, or other CI\/CD systems, use Datadog CI CLI<\/strong>.<\/p>\n\n\n\n

    If you need to inspect or troubleshoot a locally installed Datadog monitoring Agent, use Datadog Agent CLI<\/strong>.<\/p>\n\n\n\n

    This guide focuses on Pup CLI for general platform administration and also explains how to install datadog-ci<\/code> for automation.<\/p>\n\n\n\n

    \n\n\n\n

    Part 1: Installing Datadog Pup CLI<\/h1>\n\n\n\n

    3. What Is Datadog Pup CLI?<\/h2>\n\n\n\n

    Pup is Datadog’s general-purpose, API-oriented command-line interface.<\/p>\n\n\n\n

    It provides commands for interacting with major Datadog products directly from a terminal.<\/p>\n\n\n\n

    Pup supports functionality across areas such as:<\/p>\n\n\n\n

      \n
    • Infrastructure monitoring<\/li>\n\n\n\n
    • Metrics<\/li>\n\n\n\n
    • Logs<\/li>\n\n\n\n
    • APM and traces<\/li>\n\n\n\n
    • Monitors and alerts<\/li>\n\n\n\n
    • Dashboards<\/li>\n\n\n\n
    • Service Level Objectives (SLOs)<\/li>\n\n\n\n
    • Incident management<\/li>\n\n\n\n
    • Real User Monitoring (RUM)<\/li>\n\n\n\n
    • Security monitoring<\/li>\n\n\n\n
    • Datadog API resources<\/li>\n<\/ul>\n\n\n\n

      Pup is also designed to support automation and AI-agent workflows.<\/p>\n\n\n\n

      The executable is:<\/p>\n\n\n

      pup<\/code><\/span><\/pre>\n\n\n
      Example commands:<\/p>\n\n\n
      pup --help\npup auth login\npup auth status\npup monitors list<\/span>\npup dashboards list<\/span>\npup slos list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Pup provides structured output, allowing results to be processed by scripts and automation tools.<\/p>\n\n\n\n
      4. Prerequisites<\/h2>\n\n\n\n
      Before installation, check the following requirements.<\/p>\n\n\n\n
      Requirement<\/th>Details<\/th><\/tr>
      Operating system<\/td>macOS, Windows, or supported Linux<\/td><\/tr>
      Processor<\/td>Compatible x86-64 or ARM64<\/td><\/tr>
      Internet<\/td>Required for installation and Datadog APIs<\/td><\/tr>
      Terminal<\/td>Terminal, Zsh, Bash, or PowerShell<\/td><\/tr>
      Datadog account<\/td>Required for authenticated platform operations<\/td><\/tr>
      Permissions<\/td>Permission to install software<\/td><\/tr>
      Homebrew<\/td>Recommended for macOS; optional on Linux<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      You can access Datadog from:<\/p>\n\n\n\n
      \nhttps:\/\/www.datadoghq.com\n<\/div><\/figure>\n\n\n\n
      Official CLI documentation:<\/p>\n\n\n\n
      \nhttps:\/\/docs.datadoghq.com\/cli\n<\/div><\/figure>\n\n\n\n
      Official GitHub repository:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/DataDog\/pup\n<\/div><\/figure>\n\n\n\n
      \n\n\n\n
      5. How to Install Datadog CLI on macOS<\/h1>\n\n\n\n
      The recommended method for installing Pup CLI on macOS is Homebrew.<\/p>\n\n\n\n
      This installation method works on both Intel-based and Apple Silicon Macs.<\/p>\n\n\n\n
      Step 1: Open Terminal<\/h2>\n\n\n\n
      Open Terminal from:<\/p>\n\n\n\n
      Applications \u2192 Utilities \u2192 Terminal<\/p>\n\n\n\n
      Alternatively, use Spotlight Search.<\/p>\n\n\n\n
      Step 2: Check the macOS Version<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      sw_vers<\/code><\/span><\/pre>\n\n\n
      Check the processor architecture:<\/p>\n\n\n
      uname -m<\/code><\/span><\/pre>\n\n\n
      For Apple Silicon:<\/p>\n\n\n
      arm64<\/code><\/span><\/pre>\n\n\n
      For Intel Macs:<\/p>\n\n\n
      x86_64<\/code><\/span><\/pre>\n\n\n
      Both architectures have official Pup CLI builds.<\/p>\n\n\n\n
      Step 3: Check Whether Homebrew Is Installed<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      brew --version<\/code><\/span><\/pre>\n\n\n
      If Homebrew is installed, its version will be displayed.<\/p>\n\n\n\n
      If you encounter:<\/p>\n\n\n
      zsh<\/span>: command not found: brew<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
      Install Homebrew using its official installation script:<\/p>\n\n\n
      \/bin\/bash -c \"$(curl -fsSL https:\/\/raw.githubusercontent.com\/Homebrew\/install\/HEAD\/install.sh)\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Review the installer before executing it and follow the setup instructions provided.<\/p>\n\n\n\n
      Verify:<\/p>\n\n\n
      brew --version<\/code><\/span><\/pre>\n\n\n
      Step 4: Update Homebrew<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      brew update<\/code><\/span><\/pre>\n\n\n
      This refreshes Homebrew’s package metadata.<\/p>\n\n\n\n
      Step 5: Add the Datadog Homebrew Tap<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      brew tap datadog-labs\/pack<\/code><\/span><\/pre>\n\n\n
      This configures the Homebrew tap containing Pup CLI.<\/p>\n\n\n\n
      Step 6: Install Datadog Pup CLI<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      brew install datadog-labs\/pack\/pup<\/code><\/span><\/pre>\n\n\n
      Homebrew downloads and installs the Pup CLI.<\/p>\n\n\n\n
      Step 7: Verify Installation<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n\n
      The command should display the installed Pup version.<\/p>\n\n\n\n
      Check the available commands:<\/p>\n\n\n
      pup --help<\/code><\/span><\/pre>\n\n\n
      Find the executable:<\/p>\n\n\n
      which pup<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      command -v pup<\/code><\/span><\/pre>\n\n\n
      On an Apple Silicon Mac, the command path may be under:<\/p>\n\n\n
      \/opt\/homebrew\/bin\/<\/code><\/span><\/pre>\n\n\n
      On an Intel Mac, it may be under:<\/p>\n\n\n
      \/usr\/local\/bin\/<\/code><\/span><\/pre>\n\n\n
      Step 8: Confirm the Homebrew Installation<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      brew list<\/span> --versions pup<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Display package details:<\/p>\n\n\n
      brew info pup<\/code><\/span><\/pre>\n\n\n
      Datadog Pup CLI is now installed on macOS.<\/strong><\/p>\n\n\n\n
      Alternative: Install Pup CLI on macOS Without Homebrew<\/h3>\n\n\n\n
      Datadog also provides a script-based installation method.<\/p>\n\n\n\n
      Download the installation script:<\/p>\n\n\n
      curl -fsSLo pup-install.sh \\\n  https<\/span>:\/\/raw.githubusercontent.com\/DataDog\/pup\/main\/install.sh<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Review its contents:<\/p>\n\n\n
      less<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Run the script:<\/p>\n\n\n
      sh<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      On macOS without Homebrew, the installer downloads the appropriate binary and normally installs it in:<\/p>\n\n\n
      ~\/.local\/<\/span>bin<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Ensure that this directory is on your PATH.<\/p>\n\n\n\n
      For example, for Zsh:<\/p>\n\n\n
      echo<\/span> 'export PATH=\"$HOME\/.local\/bin:$PATH\"'<\/span> >> ~\/.zshrc\nsource ~\/.zshrc<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Verify:<\/p>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n\n
      For most macOS users, Homebrew is the easier installation and upgrade method.<\/p>\n\n\n\n
      \n\n\n\n
      6. How to Install Datadog CLI on Windows 10\/11<\/h1>\n\n\n\n
      Datadog provides prebuilt Pup CLI binaries for 64-bit Windows.<\/p>\n\n\n\n
      You can install Pup using PowerShell without installing Node.js, Python, or Rust.<\/p>\n\n\n\n
      Step 1: Open PowerShell<\/h2>\n\n\n\n
      Open Windows PowerShell or PowerShell 7.<\/p>\n\n\n\n
      Step 2: Check Windows Architecture<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      [System.Runtime.InteropServices.RuntimeInformation]<\/span>::OSArchitecture<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      For a compatible x64 system, the result should be:<\/p>\n\n\n
      X64<\/code><\/span><\/pre>\n\n\n
      Step 3: Download the Pup CLI Package<\/h2>\n\n\n\n
      Visit the official releases page:<\/p>\n\n\n\n
      \nhttps:\/\/github.com\/DataDog\/pup\/releases\/latest\n<\/div><\/figure>\n\n\n\n
      Download the Windows x86-64 ZIP package.<\/p>\n\n\n\n
      For example, Pup v2.0.0 uses:<\/p>\n\n\n
      pup_2<\/span>.0<\/span>.0_Windows_x86_64<\/span>.zip<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Alternatively, download that release using PowerShell:<\/p>\n\n\n
      $version = \"2.0.0\"<\/span>\n\n$url = \"https:\/\/github.com\/DataDog\/pup\/releases\/download\/v$version\/pup_${version}_Windows_x86_64.zip\"<\/span>\n\n$zipFile = Join-Path $HOME \"Downloads\\pup.zip\"<\/span>\n\nInvoke-WebRequest -Uri $url -OutFile $zipFile<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      The example pins version 2.0.0 for reproducibility. To install a newer release, update the version variable after checking the official release assets.<\/p>\n\n\n\n
      Step 4: Create an Installation Directory<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      $installDir = Join-Path $HOME \"Tools\\PupCLI\"<\/span>\n\nNew<\/span>-Item -ItemType Directory -Path $installDir -Force<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This creates a dedicated installation directory in your user profile.<\/p>\n\n\n\n
      Step 5: Extract the ZIP File<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      Expand-Archive `\n  -Path $zipFile `\n  -DestinationPath $installDir `\n  -Force<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 6: Locate the Pup Executable<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      Get-ChildItem -Path $installDir -Recurse -Filter pup.exe<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      If the executable is inside a nested directory, copy it into the installation directory:<\/p>\n\n\n
      $pupExe = Get-ChildItem -Path $installDir -Recurse -Filter pup.exe |\n    Select-Object -First 1<\/span>\n\nif<\/span> (-not $pupExe) {\n    throw<\/span> \"pup.exe was not found in the downloaded package.\"<\/span>\n}\n\nif<\/span> ($pupExe.DirectoryName -ne $installDir) {\n    Copy-Item $pupExe.FullName (Join-Path $installDir \"pup.exe\"<\/span>) -Force\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 7: Verify the Executable<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      & \"$installDir\\pup.exe\"<\/span> --version<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      If the version is displayed, the executable is working.<\/p>\n\n\n\n
      Step 8: Add Pup CLI to Windows PATH<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      $userPath = [Environment]::GetEnvironmentVariable(\"Path\"<\/span>, \"User\"<\/span>)\n\nif<\/span> (($userPath -split \";\"<\/span>) -notcontains $installDir) {\n    $newPath = ($userPath.TrimEnd(\";\"<\/span>) + \";\"<\/span> + $installDir).TrimStart(\";\"<\/span>)\n\n    [Environment]::SetEnvironmentVariable(\n        \"Path\"<\/span>,\n        $newPath,\n        \"User\"<\/span>\n    )\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Update the current PowerShell session:<\/p>\n\n\n
      $env:Path += \";$installDir\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 9: Verify Installation Globally<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n\n
      Display help:<\/p>\n\n\n
      pup --help<\/code><\/span><\/pre>\n\n\n
      Find the executable:<\/p>\n\n\n
      Get-Command pup<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      where<\/span>.exe<\/span> pup<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      If the executable is not found after changing PATH, open a new PowerShell window.<\/p>\n\n\n\n
      Datadog Pup CLI is now installed on Windows.<\/strong><\/p>\n\n\n\n
      Alternative: Install Pup from Git Bash<\/h3>\n\n\n\n
      If Git Bash, MSYS2, or Cygwin is installed, you can use Datadog’s installer script:<\/p>\n\n\n
      curl -fsSL https:\/\/raw.githubusercontent.com\/DataDog\/pup\/main\/install.sh | sh<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      The installer downloads the appropriate release archive and verifies its SHA-256 checksum.<\/p>\n\n\n\n
      It normally installs the executable under the user’s ~\/.local\/bin<\/code> directory.<\/p>\n\n\n\n
      Make sure that directory is in your shell PATH.<\/p>\n\n\n\n
      \n\n\n\n
      7. How to Install Datadog CLI on Ubuntu and Debian<\/h1>\n\n\n\n
      For Ubuntu and Debian Linux, the Datadog-provided installation script is a convenient approach.<\/p>\n\n\n\n
      The same method also works on several other supported Linux distributions.<\/p>\n\n\n\n
      Step 1: Check Linux Distribution<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
      Check your architecture:<\/p>\n\n\n
      uname -m<\/code><\/span><\/pre>\n\n\n
      Possible results:<\/p>\n\n\n
      x86_64<\/code><\/span><\/pre>\n\n\n
      Or:<\/p>\n\n\n
      aarch64<\/code><\/span><\/pre>\n\n\n
      Pup has prebuilt Linux x86-64 and ARM64 release binaries.<\/p>\n\n\n\n
      Step 2: Update Linux Packages<\/h2>\n\n\n\n
      For Ubuntu or Debian:<\/p>\n\n\n
      sudo apt update<\/code><\/span><\/pre>\n\n\n
      Step 3: Install Required Utilities<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      sudo apt install -y curl ca-certificates tar<\/code><\/span><\/pre>\n\n\n
      Step 4: Download the Official Installation Script<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      curl -fsSLo pup-install.sh \\\n  https<\/span>:\/\/raw.githubusercontent.com\/DataDog\/pup\/main\/install.sh<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Review the downloaded script:<\/p>\n\n\n
      less<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      This is recommended before executing scripts retrieved from the internet.<\/p>\n\n\n\n
      Step 5: Install Datadog Pup CLI<\/h2>\n\n\n\n
      Execute:<\/p>\n\n\n
      sh<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      The installer determines the operating system and architecture, downloads the corresponding binary, and verifies its checksum.<\/p>\n\n\n\n
      By default, non-Homebrew installations use:<\/p>\n\n\n
      ~\/.local\/<\/span>bin<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 6: Add the Installation Directory to PATH<\/h2>\n\n\n\n
      Check whether the directory is already included:<\/p>\n\n\n
      echo<\/span> \"$PATH\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      If necessary, add it for Bash:<\/p>\n\n\n
      echo<\/span> 'export PATH=\"$HOME\/.local\/bin:$PATH\"'<\/span> >> ~\/.bashrc<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Reload:<\/p>\n\n\n
      source ~\/.bashrc<\/code><\/span><\/pre>\n\n\n
      If you use Zsh, update ~\/.zshrc<\/code> instead.<\/p>\n\n\n\n
      Step 7: Verify Installation<\/h2>\n\n\n\n
      Run:<\/p>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n\n
      And:<\/p>\n\n\n
      pup --help<\/code><\/span><\/pre>\n\n\n
      Find the executable:<\/p>\n\n\n
      command -v pup<\/code><\/span><\/pre>\n\n\n
      The installation is complete.<\/p>\n\n\n\n
      \n\n\n\n
      8. How to Install Datadog CLI on RHEL, CentOS, Rocky Linux, and Amazon Linux<\/h1>\n\n\n\n
      Pup’s official installation script can also install the CLI on compatible RPM-based Linux distributions.<\/p>\n\n\n\n
      Unlike the Datadog monitoring Agent, Pup does not require setting up a Datadog Agent YUM or DNF repository.<\/p>\n\n\n\n
      Step 1: Check the Operating System<\/h2>\n\n\n
      cat \/etc\/os-release<\/code><\/span><\/pre>\n\n\n
      Check architecture:<\/p>\n\n\n
      uname -m<\/code><\/span><\/pre>\n\n\n
      Step 2: Install Required Utilities<\/h2>\n\n\n\n
      On a DNF-based distribution:<\/p>\n\n\n
      sudo dnf install -y curl tar gzip ca-certificates<\/code><\/span><\/pre>\n\n\n
      On older systems using YUM:<\/p>\n\n\n
      sudo yum install -y curl tar gzip ca-certificates<\/code><\/span><\/pre>\n\n\n
      Step 3: Download and Review the Installer<\/h2>\n\n\n
      curl -fsSLo pup-install.sh \\\n  https<\/span>:\/\/raw.githubusercontent.com\/DataDog\/pup\/main\/install.sh<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Review:<\/p>\n\n\n
      less<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 4: Install Pup CLI<\/h2>\n\n\n
      sh<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 5: Configure PATH<\/h2>\n\n\n\n
      For Bash:<\/p>\n\n\n
      echo<\/span> 'export PATH=\"$HOME\/.local\/bin:$PATH\"'<\/span> >> ~\/.bashrc\nsource ~\/.bashrc<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 6: Verify Installation<\/h2>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n
      pup --help<\/code><\/span><\/pre>\n\n
      command -v pup<\/code><\/span><\/pre>\n\n\n
      Pup CLI is now available on your Linux workstation or server.<\/p>\n\n\n\n
      \n\n\n\n
      9. Alternative Linux Installation Using a Standalone Binary<\/h1>\n\n\n\n
      You can install Pup manually without running the installation script.<\/p>\n\n\n\n
      The following example uses the official Linux x86-64 v2.0.0 release archive.<\/p>\n\n\n\n
      Step 1: Download the Release<\/h2>\n\n\n
      curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/pup\/releases\/download\/v2.0.0\/pup_2.0.0_Linux_x86_64.tar.gz \\<\/span>\n  -o pup.tar.gz<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      For ARM64, use:<\/p>\n\n\n
      curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/pup\/releases\/download\/v2.0.0\/pup_2.0.0_Linux_arm64.tar.gz \\<\/span>\n  -o pup.tar.gz<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Download only the archive matching your system architecture.<\/p>\n\n\n\n
      Step 2: Verify the Download<\/h2>\n\n\n\n
      Download the published checksum file for the same release:<\/p>\n\n\n
      curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/pup\/releases\/download\/v2.0.0\/pup_2.0.0_checksums.txt \\<\/span>\n  -o pup_2.0<\/span>.0<\/span>_checksums.txt<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Check the downloaded archive’s hash:<\/p>\n\n\n
      sha256sum<\/span> pup<\/span>.tar<\/span>.gz<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Compare the hash against the official checksum for the corresponding release asset.<\/p>\n\n\n\n
      The filename in the checksum manifest refers to the original release archive name, so be sure to match the correct entry rather than just the locally renamed file.<\/p>\n\n\n\n
      For stronger supply-chain validation, Datadog also publishes signed checksum metadata that can be verified using Sigstore\/cosign.<\/p>\n\n\n\n
      Step 3: Extract the Archive<\/h2>\n\n\n
      tar<\/span> -xzf<\/span> pup<\/span>.tar<\/span>.gz<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 4: Find the Executable<\/h2>\n\n\n
      find . -type f -name pup<\/code><\/span><\/pre>\n\n\n
      Locate the extracted executable.<\/p>\n\n\n\n
      Step 5: Install the Executable<\/h2>\n\n\n\n
      If it was extracted in the current directory:<\/p>\n\n\n
      sudo install -m 0755 .\/pup \/usr\/local\/bin\/pup<\/code><\/span><\/pre>\n\n\n
      If it was extracted in a subdirectory, adjust the source path.<\/p>\n\n\n\n
      Step 6: Verify<\/h2>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n
      pup --help<\/code><\/span><\/pre>\n\n\n
      The standalone binary approach is useful for controlled servers and reproducible installation workflows.<\/p>\n\n\n\n
      \n\n\n\n
      10. How to Authenticate Datadog Pup CLI<\/h1>\n\n\n\n
      After installing Pup CLI, authenticate with your Datadog organization.<\/p>\n\n\n\n
      Pup supports OAuth2 authentication and API key authentication.<\/p>\n\n\n\n
      Method 1: OAuth2 Browser Login (Recommended)<\/h2>\n\n\n\n
      Step 1: Configure the Datadog Site<\/h3>\n\n\n\n
      Datadog operates regional sites.<\/p>\n\n\n\n
      Examples include:<\/p>\n\n\n\n
      Region<\/th>Datadog site<\/th><\/tr>
      US1<\/td>datadoghq.com<\/code><\/td><\/tr>
      US3<\/td>us3.datadoghq.com<\/code><\/td><\/tr>
      US5<\/td>us5.datadoghq.com<\/code><\/td><\/tr>
      EU<\/td>datadoghq.eu<\/code><\/td><\/tr>
      AP1<\/td>ap1.datadoghq.com<\/code><\/td><\/tr>
      AP2<\/td>ap2.datadoghq.com<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Select the site corresponding to your Datadog organization.<\/p>\n\n\n\n
      On macOS or Linux:<\/p>\n\n\n
      export<\/span> DD_SITE=\"datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      On Windows PowerShell:<\/p>\n\n\n
      $env:DD_SITE = \"datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 2: Log In<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      pup auth login<\/code><\/span><\/pre>\n\n\n
      The CLI initiates a browser-based OAuth2 authentication workflow.<\/p>\n\n\n\n
      Follow the prompts to complete authentication with your Datadog account.<\/p>\n\n\n\n
      OAuth2 uses scoped access rather than requiring you to manually supply long-lived application credentials.<\/p>\n\n\n\n
      Note:<\/strong> OAuth2 login requires the relevant functionality, including Dynamic Client Registration, to be available for your Datadog site. If it is unavailable, use API key authentication.<\/p>\n\n\n\n
      Step 3: Verify Authentication Status<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      pup auth status<\/code><\/span><\/pre>\n\n\n
      Step 4: Test Connectivity<\/h3>\n\n\n\n
      Execute:<\/p>\n\n\n
      pup auth test<\/code><\/span><\/pre>\n\n\n
      This checks the connection using your configured authentication.<\/p>\n\n\n\n
      Step 5: List Datadog Monitors<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      pup monitors list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      If the account has appropriate permissions, the CLI retrieves the organization’s accessible monitors.<\/p>\n\n\n\n
      Step 6: Log Out<\/h3>\n\n\n\n
      When required:<\/p>\n\n\n
      pup auth logout<\/code><\/span><\/pre>\n\n\n
      Method 2: Authenticate Using API and Application Keys<\/h2>\n\n\n\n
      For unattended automation, Pup also supports Datadog API and application keys.<\/p>\n\n\n\n
      Configure credentials in your Datadog organization.<\/p>\n\n\n\n
      Use appropriately scoped permissions.<\/p>\n\n\n\n
      macOS\/Linux<\/h3>\n\n\n\n
      Environment variable names for Pup are:<\/p>\n\n\n
      DD_API_KEY\nDD_APP_KEY\nDD_SITE<\/code><\/span><\/pre>\n\n\n
      Supply these securely through your terminal session, approved secret manager, or CI\/CD secret configuration.<\/p>\n\n\n\n
      For example, in a trusted interactive terminal:<\/p>\n\n\n
      read -r -s -p \"Datadog API key: \"<\/span> DD_API_KEY\necho\nread -r -s -p \"Datadog application key: \"<\/span> DD_APP_KEY\necho\n\nexport<\/span> DD_API_KEY DD_APP_KEY\nexport<\/span> DD_SITE=\"datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This avoids placing literal secret values in the command history.<\/p>\n\n\n\n
      Windows PowerShell<\/h3>\n\n\n\n
      Read the keys interactively:<\/p>\n\n\n
      $apiKey = Read-Host \"Datadog API key\"<\/span> -AsSecureString\n$appKey = Read-Host \"Datadog application key\"<\/span> -AsSecureString<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Convert the entered values into environment variables for the current process:<\/p>\n\n\n
      $env:DD_API_KEY = [System.Net.NetworkCredential]::new(\"\"<\/span>, $apiKey).Password\n$env:DD_APP_KEY = [System.Net.NetworkCredential]::new(\"\"<\/span>, $appKey).Password\n$env:DD_SITE = \"datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      These environment variables contain the key values as plaintext in process memory. Avoid displaying them, logging them, or persisting them insecurely.<\/p>\n\n\n\n
      Test API Key Authentication<\/h3>\n\n\n\n
      Run:<\/p>\n\n\n
      pup monitors list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Pup uses its configured authentication automatically.<\/p>\n\n\n\n
      If an existing OAuth session is active, it takes precedence over API key credentials unless authentication selection is changed.<\/p>\n\n\n\n
      \n\n\n\n
      11. Essential Datadog Pup CLI Commands<\/h1>\n\n\n\n
      After installation and authentication, you can perform many read-only Datadog operations.<\/p>\n\n\n\n
      Check Version<\/h2>\n\n\n
      pup --version<\/code><\/span><\/pre>\n\n\n
      Display Help<\/h2>\n\n\n
      pup --help<\/code><\/span><\/pre>\n\n\n
      Check Authentication<\/h2>\n\n\n
      pup auth status<\/code><\/span><\/pre>\n\n\n
      Test Connection<\/h2>\n\n\n
      pup auth test<\/code><\/span><\/pre>\n\n\n
      List Monitors<\/h2>\n\n\n
      pup monitors list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Filter Monitors by Tag<\/h2>\n\n\n
      pup monitors list<\/span> --tags=\"team:platform\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      List Dashboards<\/h2>\n\n\n
      pup dashboards list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Retrieve a Dashboard<\/h2>\n\n\n
      pup dashboards get<\/span> DASHBOARD_ID<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Replace DASHBOARD_ID<\/code> with an existing dashboard identifier.<\/p>\n\n\n\n
      List SLOs<\/h2>\n\n\n
      pup slos list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Retrieve an SLO<\/h2>\n\n\n
      pup slos get<\/span> SLO_ID<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Search Recent Error Logs<\/h2>\n\n\n
      pup logs search --query=\"status:error\"<\/span> --from<\/span>=\"1h\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      This searches logs with error status over the previous hour.<\/p>\n\n\n\n
      Results depend on your permissions, indexes, and retained data.<\/p>\n\n\n\n
      Query CPU Metrics<\/h2>\n\n\n
      pup metrics query --query=\"avg:system.cpu.user{*}\"<\/span> --from<\/span>=\"1h\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Search for Metrics<\/h2>\n\n\n
      pup metrics list<\/span> --filter=\"system.*\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      List Incidents<\/h2>\n\n\n
      pup incidents list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Use the command-specific help for supported filtering options:<\/p>\n\n\n
      pup monitors --help\npup logs --help\npup metrics --help<\/code><\/span><\/pre>\n\n\n
      Pup can also create, update, and delete supported resources. Confirm the target organization, permissions, and command behavior before executing write operations.<\/p>\n\n\n\n
      \n\n\n\n
      Part 2: Installing Datadog CI CLI<\/h1>\n\n\n\n
      12. What Is Datadog CI CLI?<\/h2>\n\n\n\n
      Datadog CI CLI is a separate command-line tool designed for CI\/CD integrations.<\/p>\n\n\n\n
      Its executable is:<\/p>\n\n\n
      datadog-ci<\/code><\/span><\/pre>\n\n\n
      It can support workflows such as:<\/p>\n\n\n\n
        \n
      • Running Datadog Synthetic tests from CI\/CD.<\/li>\n\n\n\n
      • Uploading JavaScript source maps.<\/li>\n\n\n\n
      • Sending supported CI events and metadata.<\/li>\n\n\n\n
      • Tracing custom CI pipeline commands.<\/li>\n\n\n\n
      • Automating Datadog-related development workflows.<\/li>\n<\/ul>\n\n\n\n
        The npm package is:<\/p>\n\n\n
        @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Official repository:<\/p>\n\n\n\n
        \nhttps:\/\/github.com\/DataDog\/datadog-ci\n<\/div><\/figure>\n\n\n\n
        13. Install Datadog CI CLI on macOS<\/h2>\n\n\n\n
        Step 1: Check Node.js<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        node --version<\/code><\/span><\/pre>\n\n\n
        Check npm:<\/p>\n\n\n
        npm --version<\/code><\/span><\/pre>\n\n\n
        If Node.js is unavailable and you use Homebrew:<\/p>\n\n\n
        brew install node<\/code><\/span><\/pre>\n\n\n
        For CI\/CD environments, choose an actively supported Node.js LTS release compatible with your selected datadog-ci<\/code> version.<\/p>\n\n\n\n
        Step 2: Install Datadog CI CLI Globally<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        npm<\/span> install<\/span> -g<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Step 3: Verify Installation<\/h3>\n\n\n\n
        Run:<\/p>\n\n\n
        datadog-ci version<\/code><\/span><\/pre>\n\n\n
        Display help:<\/p>\n\n\n
        datadog-ci --help<\/code><\/span><\/pre>\n\n\n
        Locate the executable:<\/p>\n\n\n
        command -v datadog-ci<\/code><\/span><\/pre>\n\n\n
        Step 4: Inspect Available Plugins<\/h3>\n\n\n
        datadog-ci plugin list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        For example, install the Synthetic testing plugin:<\/p>\n\n\n
        datadog-ci plugin install synthetics<\/code><\/span><\/pre>\n\n\n
        Datadog CI CLI is now installed on macOS.<\/strong><\/p>\n\n\n\n
        \n\n\n\n
        14. Install Datadog CI CLI on Windows<\/h1>\n\n\n\n
        Step 1: Open PowerShell<\/h2>\n\n\n\n
        Open PowerShell or Windows Terminal.<\/p>\n\n\n\n
        Step 2: Install Node.js<\/h2>\n\n\n\n
        Check:<\/p>\n\n\n
        node --version<\/code><\/span><\/pre>\n\n\n
        If Node.js is not installed, you can install Node.js LTS through WinGet:<\/p>\n\n\n
        winget<\/span> install<\/span> OpenJS<\/span>.NodeJS<\/span>.LTS<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        After installation, open a new PowerShell window.<\/p>\n\n\n\n
        Verify:<\/p>\n\n\n
        node --version\nnpm --version<\/code><\/span><\/pre>\n\n\n
        Step 3: Install Datadog CI CLI<\/h2>\n\n\n\n
        Execute:<\/p>\n\n\n
        npm<\/span> install<\/span> -g<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Step 4: Verify<\/h2>\n\n\n\n
        Run:<\/p>\n\n\n
        datadog-ci version<\/code><\/span><\/pre>\n\n\n
        Display help:<\/p>\n\n\n
        datadog-ci --help<\/code><\/span><\/pre>\n\n\n
        Find the executable:<\/p>\n\n\n
        Get-Command datadog-ci<\/code><\/span><\/pre>\n\n\n
        Step 5: Install a Plugin<\/h2>\n\n\n\n
        For Synthetic testing:<\/p>\n\n\n
        datadog-ci plugin install synthetics<\/code><\/span><\/pre>\n\n\n
        The installation is complete.<\/p>\n\n\n\n
        \n\n\n\n
        15. Install Datadog CI CLI on Ubuntu\/Debian Linux<\/h1>\n\n\n\n
        Step 1: Update Packages<\/h2>\n\n\n
        sudo apt update<\/code><\/span><\/pre>\n\n\n
        Step 2: Check Whether Node.js and npm Are Installed<\/h2>\n\n\n
        node --version\nnpm --version<\/code><\/span><\/pre>\n\n\n
        If both are already present and meet the CLI’s requirements, continue to Step 4.<\/p>\n\n\n\n
        Otherwise, install a supported Node.js LTS release using an approved Node.js distribution or version manager.<\/p>\n\n\n\n
        For a basic distribution-provided installation:<\/p>\n\n\n
        sudo apt install -y nodejs npm<\/code><\/span><\/pre>\n\n\n
        Important:<\/strong> The Ubuntu\/Debian repositories may provide older Node.js versions. Check compatibility with the selected Datadog CI CLI version rather than assuming every packaged Node.js version is supported.<\/p>\n\n\n\n
        Step 3: Verify Node.js<\/h2>\n\n\n
        node --version\nnpm --version<\/code><\/span><\/pre>\n\n\n
        Step 4: Install Datadog CI CLI<\/h2>\n\n\n
        npm<\/span> install<\/span> -g<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        If a permission error occurs, prefer a user-managed Node.js installation or an npm prefix configured for your user instead of automatically rerunning npm with sudo<\/code>.<\/p>\n\n\n\n
        Step 5: Verify Installation<\/h2>\n\n\n
        datadog-ci version<\/code><\/span><\/pre>\n\n
        datadog-ci --help<\/code><\/span><\/pre>\n\n\n
        Step 6: Install Synthetic Testing Plugin<\/h2>\n\n\n
        datadog-ci plugin install synthetics<\/code><\/span><\/pre>\n\n\n
        Datadog CI CLI is now available on Ubuntu or Debian.<\/p>\n\n\n\n
        \n\n\n\n
        16. Install Datadog CI CLI on RHEL, CentOS, and Amazon Linux<\/h1>\n\n\n\n
        The CLI installation is the same once a compatible Node.js runtime and npm are available.<\/p>\n\n\n\n
        Step 1: Check Node.js<\/h2>\n\n\n
        node --version\nnpm --version<\/code><\/span><\/pre>\n\n\n
        Step 2: Install Node.js if Missing<\/h2>\n\n\n\n
        On RPM-based distributions where compatible Node.js packages are available:<\/p>\n\n\n
        sudo dnf install -y nodejs npm<\/code><\/span><\/pre>\n\n\n
        On older YUM-based installations:<\/p>\n\n\n
        sudo yum install -y nodejs npm<\/code><\/span><\/pre>\n\n\n
        Verify the version and compatibility before continuing.<\/p>\n\n\n\n
        Step 3: Install Datadog CI CLI<\/h2>\n\n\n
        npm<\/span> install<\/span> -g<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Step 4: Verify<\/h2>\n\n\n
        datadog-ci version<\/code><\/span><\/pre>\n\n
        datadog-ci --help<\/code><\/span><\/pre>\n\n\n
        Step 5: Install Required Plugins<\/h2>\n\n\n\n
        For example:<\/p>\n\n\n
        datadog-ci plugin install synthetics<\/code><\/span><\/pre>\n\n\n
        For reproducible CI\/CD pipelines, install an exact, tested package version rather than relying on whichever version is latest at deployment time.<\/p>\n\n\n\n
        \n\n\n\n
        17. Install Datadog CI CLI Without Node.js<\/h1>\n\n\n\n
        Datadog provides standalone binaries for supported operating systems.<\/p>\n\n\n\n
        These binaries bundle the runtime needed to execute the CLI and include the Datadog CI plugins.<\/p>\n\n\n\n
        macOS \u2014 Apple Silicon<\/h2>\n\n\n
        curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/datadog-ci\/releases\/latest\/download\/datadog-ci_darwin-arm64 \\<\/span>\n  -o datadog-ci\n\nchmod +x datadog-ci\n\n.\/datadog-ci version<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        To install system-wide after verifying the binary:<\/p>\n\n\n
        sudo install -m 0755 datadog-ci \/usr\/local\/bin\/datadog-ci<\/code><\/span><\/pre>\n\n\n
        macOS \u2014 Intel<\/h2>\n\n\n
        curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/datadog-ci\/releases\/latest\/download\/datadog-ci_darwin-x64 \\<\/span>\n  -o datadog-ci\n\nchmod +x datadog-ci\n\n.\/datadog-ci version<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Linux \u2014 x86-64<\/h2>\n\n\n
        curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/datadog-ci\/releases\/latest\/download\/datadog-ci_linux-x64 \\<\/span>\n  -o datadog-ci\n\nchmod +x datadog-ci\n\nsudo install -m 0755<\/span> datadog-ci \/usr\/local\/bin\/datadog-ci<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Verify:<\/p>\n\n\n
        datadog-ci version<\/code><\/span><\/pre>\n\n\n
        Linux \u2014 ARM64<\/h2>\n\n\n
        curl -fL \\\n  https<\/span>:\/\/github.com\/DataDog\/datadog-ci\/releases\/latest\/download\/datadog-ci_linux-arm64 \\<\/span>\n  -o datadog-ci\n\nchmod +x datadog-ci\n\nsudo install -m 0755<\/span> datadog-ci \/usr\/local\/bin\/datadog-ci<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Windows \u2014 x64<\/h2>\n\n\n\n
        Open PowerShell:<\/p>\n\n\n
        $installDir = Join-Path $HOME \"Tools\\DatadogCI\"<\/span>\n\nNew<\/span>-Item -ItemType Directory -Force -Path $installDir\n\nInvoke-WebRequest `\n  -Uri \"https:\/\/github.com\/DataDog\/datadog-ci\/releases\/latest\/download\/datadog-ci_win-x64\"<\/span> `\n  -OutFile \"$installDir\\datadog-ci.exe\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Verify directly:<\/p>\n\n\n
        & \"$installDir\\datadog-ci.exe\"<\/span> version<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Add the directory to your Windows user PATH using the Windows Environment Variables settings or the PowerShell PATH configuration method described earlier.<\/p>\n\n\n\n
        When downloading standalone executables for production use, verify the release source and available artifact integrity information before executing them.<\/p>\n\n\n\n
        \n\n\n\n
        18. Authenticate Datadog CI CLI<\/h1>\n\n\n\n
        Unlike Pup’s interactive OAuth2 login, datadog-ci<\/code> commonly uses environment variables or configuration files for authorization.<\/p>\n\n\n\n
        The exact credentials required depend on the command.<\/p>\n\n\n\n
        For Synthetic testing, configure:<\/p>\n\n\n
        DATADOG_API_KEY\nDATADOG_APP_KEY\nDATADOG_SITE<\/code><\/span><\/pre>\n\n\n
        These variable names differ from Pup’s DD_API_KEY<\/code> and DD_APP_KEY<\/code> names.<\/p>\n\n\n\n
        macOS\/Linux<\/h3>\n\n\n\n
        Supply the keys securely:<\/p>\n\n\n
        read -r -s -p \"Datadog API key: \"<\/span> DATADOG_API_KEY\necho\nread -r -s -p \"Datadog application key: \"<\/span> DATADOG_APP_KEY\necho\n\nexport<\/span> DATADOG_API_KEY DATADOG_APP_KEY\nexport<\/span> DATADOG_SITE=\"datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Windows PowerShell<\/h3>\n\n\n
        $apiKey = Read-Host \"Datadog API key\"<\/span> -AsSecureString\n$appKey = Read-Host \"Datadog application key\"<\/span> -AsSecureString\n\n$env:DATADOG_API_KEY = [System.Net.NetworkCredential]::new(\"\"<\/span>, $apiKey).Password\n$env:DATADOG_APP_KEY = [System.Net.NetworkCredential]::new(\"\"<\/span>, $appKey).Password\n$env:DATADOG_SITE = \"datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        For CI\/CD automation, use your platform’s secret-management capabilities instead of placing credentials directly in source code.<\/p>\n\n\n\n
        \n\n\n\n
        19. Run Datadog Synthetic Tests from the CLI<\/h1>\n\n\n\n
        One of the most useful features of datadog-ci<\/code> is executing Datadog Synthetic tests from a command line or CI\/CD pipeline.<\/p>\n\n\n\n
        Step 1: Install the Plugin<\/h2>\n\n\n\n
        For an npm-installed CLI:<\/p>\n\n\n
        datadog-ci plugin install synthetics<\/code><\/span><\/pre>\n\n\n
        Standalone binaries already include plugins.<\/p>\n\n\n\n
        Step 2: Find Your Synthetic Test Public ID<\/h2>\n\n\n\n
        Open Datadog’s Synthetic Monitoring interface and select the test you want to execute.<\/p>\n\n\n\n
        Locate the test’s public ID.<\/p>\n\n\n\n
        Step 3: Run the Test<\/h2>\n\n\n\n
        Execute:<\/p>\n\n\n
        datadog-ci synthetics run-tests --public<\/span>-id YOUR_TEST_PUBLIC_ID<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Replace the placeholder with the actual test public ID.<\/p>\n\n\n\n
        The command starts the configured Synthetic test and reports the results.<\/p>\n\n\n\n
        The result depends on test settings, account permissions, available test locations, and authentication.<\/p>\n\n\n\n
        Note:<\/strong> Synthetic test executions may consume billable testing resources. Only run tests you are authorized to execute.<\/p>\n\n\n\n
        \n\n\n\n
        20. Install Datadog CI CLI Locally in a Project<\/h1>\n\n\n\n
        For production CI\/CD pipelines, a project-local installation is often preferable to a globally installed package.<\/p>\n\n\n\n
        Navigate to your project directory.<\/p>\n\n\n\n
        If you do not already have a Node.js project:<\/p>\n\n\n
        npm init -y<\/code><\/span><\/pre>\n\n\n
        Install the CLI as a development dependency:<\/p>\n\n\n
        npm<\/span> install<\/span> --save-dev<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Run it through npm:<\/p>\n\n\n
        npx datadog-ci version<\/code><\/span><\/pre>\n\n\n
        Or, once installed:<\/p>\n\n\n
        npx datadog-ci plugin install synthetics<\/code><\/span><\/pre>\n\n\n
        For automation, commit the package manifest and lockfile and use:<\/p>\n\n\n
        npm ci<\/code><\/span><\/pre>\n\n\n
        This installs dependencies according to the project’s lockfile.<\/p>\n\n\n\n
        Datadog recommends using an exact tested version to reduce unexpected major-version changes and software supply-chain risks.<\/p>\n\n\n\n
        \n\n\n\n
        21. Docker Installation Alternative<\/h1>\n\n\n\n
        If Docker is available, Datadog CI CLI can also run through its published container image.<\/p>\n\n\n\n
        Pull the container image:<\/p>\n\n\n
        docker pull datadog\/ci<\/code><\/span><\/pre>\n\n\n
        Display help:<\/p>\n\n\n
        docker run --rm datadog\/ci --help<\/code><\/span><\/pre>\n\n\n
        For commands requiring authentication, pass the necessary credentials through approved secrets handling.<\/p>\n\n\n\n
        For example, after configuring environment variables securely:<\/p>\n\n\n
        docker run --rm \\\n  -e DATADOG_API_KEY \\\n  -e DATADOG_APP_KEY \\\n  -e DATADOG_SITE \\\n  datadog\/ci synthetics --help<\/code><\/span><\/pre>\n\n\n
        This approach avoids installing the npm package directly on your host machine.<\/p>\n\n\n\n
        \n\n\n\n
        22. How to Update Datadog CLI<\/h1>\n\n\n\n
        Updates depend on which CLI and installation method you use.<\/p>\n\n\n\n
        Update Pup CLI on macOS<\/h2>\n\n\n
        brew update\nbrew upgrade datadog-labs\/pack\/pup<\/code><\/span><\/pre>\n\n\n
        Verify:<\/p>\n\n\n
        pup --version<\/code><\/span><\/pre>\n\n\n
        Update Pup CLI on Linux<\/h2>\n\n\n\n
        For a script-managed installation, download and review the current official installer again:<\/p>\n\n\n
        curl -fsSLo pup-install.sh \\\n  https<\/span>:\/\/raw.githubusercontent.com\/DataDog\/pup\/main\/install.sh<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        After review:<\/p>\n\n\n
        sh<\/span> pup-install<\/span>.sh<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        The installer can install the latest available release.<\/p>\n\n\n\n
        For version-pinned installations, specify the intended PUP_VERSION<\/code> or manually replace the binary with the approved release.<\/p>\n\n\n\n
        Update Pup CLI on Windows<\/h2>\n\n\n\n
        Download the newer official Windows release and replace the existing executable after validating the release artifact.<\/p>\n\n\n\n
        Check:<\/p>\n\n\n
        pup --version<\/code><\/span><\/pre>\n\n\n
        Update Datadog CI CLI Through npm<\/h2>\n\n\n
        npm<\/span> install<\/span> -g<\/span> @datadog<\/span>\/datadog-ci@latest<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Or upgrade the dependency within a project, review the changes, and update the lockfile.<\/p>\n\n\n\n
        Verify:<\/p>\n\n\n
        datadog-ci version<\/code><\/span><\/pre>\n\n\n
        Update Standalone Datadog CI CLI<\/h2>\n\n\n\n
        Download a newer release for the appropriate operating system and architecture, verify it, and replace the existing executable.<\/p>\n\n\n\n
        For CI\/CD systems, prefer a tested, pinned release over unreviewed automatic upgrades.<\/p>\n\n\n\n
        \n\n\n\n
        23. Troubleshooting Datadog CLI Installation Errors<\/h1>\n\n\n\n
        The following table summarizes common installation and authentication problems.<\/p>\n\n\n\n
        Error or symptom<\/th>Likely cause<\/th>Solution<\/th><\/tr>
        pup: command not found<\/code><\/td>Pup missing or directory not in PATH<\/td>Verify installation directory and PATH<\/td><\/tr>
        datadog-ci: command not found<\/code><\/td>npm executable not found in PATH<\/td>Inspect npm global prefix and shell PATH<\/td><\/tr>
        brew: command not found<\/code><\/td>Homebrew unavailable<\/td>Install\/configure Homebrew<\/td><\/tr>
        npm: command not found<\/code><\/td>Node.js\/npm missing<\/td>Install compatible Node.js<\/td><\/tr>
        EACCES: permission denied<\/code><\/td>npm installation permission issue<\/td>Use user-managed Node.js or npm prefix<\/td><\/tr>
        exec format error<\/code><\/td>Incorrect CPU architecture<\/td>Download the correct binary<\/td><\/tr>
        Windows command not recognized<\/td>Executable directory missing from PATH<\/td>Correct PATH and reopen PowerShell<\/td><\/tr>
        401 Unauthorized<\/code><\/td>Missing or invalid authentication<\/td>Check login or credentials<\/td><\/tr>
        403 Forbidden<\/code><\/td>Insufficient permissions<\/td>Review key scopes, OAuth scopes, and roles<\/td><\/tr>
        OAuth login fails<\/td>OAuth configuration, browser, or site issue<\/td>Verify site and use supported API-key authentication if necessary<\/td><\/tr>
        SSL certificate error<\/td>Certificate trust or proxy issue<\/td>Check trust store and approved proxy settings<\/td><\/tr>
        Unexpected or missing data<\/td>Wrong Datadog region or organization<\/td>Verify site, organization, and access rights<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        Troubleshooting 1: Pup Command Not Found<\/h3>\n\n\n\n
        On macOS\/Linux:<\/p>\n\n\n
        command -v pup<\/code><\/span><\/pre>\n\n\n
        Check:<\/p>\n\n\n
        echo<\/span> \"$PATH\"<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        If installed in the user-local directory, test:<\/p>\n\n\n
        \"$HOME\/.local\/bin\/pup\"<\/span> --version<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        If this works, ensure ~\/.local\/bin<\/code> is added to your PATH.<\/p>\n\n\n\n
        Troubleshooting 2: datadog-ci Command Not Found<\/h3>\n\n\n\n
        Check npm:<\/p>\n\n\n
        npm --version<\/code><\/span><\/pre>\n\n\n
        List globally installed packages:<\/p>\n\n\n
        npm list<\/span> -g --depth=0<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Inspect the global npm prefix:<\/p>\n\n\n
        npm prefix -g<\/code><\/span><\/pre>\n\n\n
        Confirm that the npm global executable directory is on PATH.<\/p>\n\n\n\n
        For a local project installation, use:<\/p>\n\n\n
        npx datadog-ci version<\/code><\/span><\/pre>\n\n\n
        Troubleshooting 3: Windows Does Not Recognize Pup<\/h3>\n\n\n\n
        Execute:<\/p>\n\n\n
        Get-Command pup<\/code><\/span><\/pre>\n\n\n
        If nothing is found, check the installation directory and PATH.<\/p>\n\n\n
        $env:Path<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Open a new PowerShell session after correcting the environment variable.<\/p>\n\n\n\n
        Troubleshooting 4: OAuth Login Fails<\/h3>\n\n\n\n
        Verify the intended Datadog site.<\/p>\n\n\n\n
        For example:<\/p>\n\n\n
        pup<\/span> auth<\/span> login<\/span> --site<\/span> datadoghq<\/span>.eu<\/span><\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        Check:<\/p>\n\n\n
        pup auth status<\/code><\/span><\/pre>\n\n\n
        The OAuth2 login flow requires site support for its authentication mechanisms, including Dynamic Client Registration.<\/p>\n\n\n\n
        If your site does not support the required OAuth2 flow, use appropriately scoped API and application keys.<\/p>\n\n\n\n
        Troubleshooting 5: Authentication Returns 403 Forbidden<\/h3>\n\n\n\n
        A valid identity may still lack permission for the requested resource.<\/p>\n\n\n\n
        For example:<\/p>\n\n\n
        pup monitors list<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        A permission error can indicate that the identity lacks the appropriate resource access.<\/p>\n\n\n\n
        Check user roles, OAuth scopes, API\/application key permissions, and organization selection.<\/p>\n\n\n\n
        Troubleshooting 6: Incorrect Datadog Region<\/h3>\n\n\n\n
        Datadog API requests must target the correct site.<\/p>\n\n\n\n
        For Pup on macOS\/Linux:<\/p>\n\n\n
        export<\/span> DD_SITE=\"ap1.datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        For Datadog CI Synthetic testing:<\/p>\n\n\n
        export<\/span> DATADOG_SITE=\"ap1.datadoghq.com\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Change the hostname to the actual region where your organization is hosted.<\/p>\n\n\n\n
        Troubleshooting 7: Linux Binary Architecture Mismatch<\/h3>\n\n\n\n
        Check architecture:<\/p>\n\n\n
        uname -m<\/code><\/span><\/pre>\n\n\n
        For x86_64<\/code>, use the x86-64 Linux binary.<\/p>\n\n\n\n
        For aarch64<\/code>, use the ARM64 binary.<\/p>\n\n\n\n
        Do not assume that binaries compiled for different operating systems or CPU architectures are interchangeable.<\/p>\n\n\n\n
        \n\n\n\n
        24. How to Uninstall Datadog CLI<\/h1>\n\n\n\n
        Uninstall Pup CLI on macOS<\/h2>\n\n\n\n
        If installed through Homebrew:<\/p>\n\n\n
        brew uninstall datadog-labs\/pack\/pup<\/code><\/span><\/pre>\n\n\n
        Uninstall Pup CLI on Linux<\/h2>\n\n\n\n
        For a user-local script installation:<\/p>\n\n\n
        rm -f \"$HOME\/.local\/bin\/pup\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        For a manually installed system-wide binary:<\/p>\n\n\n
        sudo rm -f \/usr\/local\/bin\/pup<\/code><\/span><\/pre>\n\n\n
        Remove only the executable created by the corresponding installation method.<\/p>\n\n\n\n
        Uninstall Pup CLI on Windows<\/h2>\n\n\n\n
        Delete the pup.exe<\/code> executable from the chosen installation directory.<\/p>\n\n\n\n
        Remove the directory from your Windows user PATH if it is no longer needed.<\/p>\n\n\n\n
        Uninstall Datadog CI CLI<\/h2>\n\n\n\n
        For a global npm installation:<\/p>\n\n\n
        npm<\/span> uninstall<\/span> -g<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        For a project-local dependency:<\/p>\n\n\n
        npm<\/span> uninstall<\/span> --save-dev<\/span> @datadog<\/span>\/datadog-ci<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        For standalone binaries, remove the installed executable.<\/p>\n\n\n\n
        Important:<\/strong> Removing these binaries does not automatically delete all stored credentials, authentication sessions, or configuration files. Review them separately if the goal is a complete security-sensitive removal.<\/p>\n\n\n\n
        \n\n\n\n
        25. Datadog CLI Installation Command Cheat Sheet<\/h1>\n\n\n\n
        Platform<\/th>Pup CLI installation<\/th>Datadog CI CLI installation<\/th><\/tr>
        macOS Intel<\/td>brew install datadog-labs\/pack\/pup<\/code><\/td>npm install -g @datadog\/datadog-ci<\/code><\/td><\/tr>
        macOS Apple Silicon<\/td>Same Homebrew command<\/td>Same npm command<\/td><\/tr>
        Windows 10\/11<\/td>Official Pup Windows ZIP<\/td>npm or standalone Windows executable<\/td><\/tr>
        Ubuntu<\/td>Official Pup installation script<\/td>npm or standalone Linux executable<\/td><\/tr>
        Debian<\/td>Official Pup installation script<\/td>npm or standalone Linux executable<\/td><\/tr>
        RHEL\/CentOS<\/td>Official Pup installation script<\/td>npm or standalone Linux executable<\/td><\/tr>
        Amazon Linux<\/td>Official Pup installation script<\/td>npm or standalone Linux executable<\/td><\/tr>
        Linux with Homebrew<\/td>brew install datadog-labs\/pack\/pup<\/code><\/td>npm or standalone executable<\/td><\/tr>
        Verify installation<\/td>pup --version<\/code><\/td>datadog-ci version<\/code><\/td><\/tr>
        Display help<\/td>pup --help<\/code><\/td>datadog-ci --help<\/code><\/td><\/tr>
        Authenticate<\/td>pup auth login<\/code><\/td>Command-specific API\/application key configuration<\/td><\/tr>
        List monitors<\/td>pup monitors list<\/code><\/td>Not the primary purpose<\/td><\/tr>
        Run Synthetic tests<\/td>Use supported Pup Synthetic API operations<\/td>datadog-ci synthetics run-tests<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n
        26. Frequently Asked Questions<\/h1>\n\n\n\n
        Q1. Does Datadog have an official CLI?<\/h3>\n\n\n\n
        Yes. Datadog provides Pup CLI for general Datadog API operations and Datadog CI CLI for CI\/CD workflows.<\/p>\n\n\n\n
        The Datadog Agent also includes its own administrative commands.<\/p>\n\n\n\n
        Q2. What is the executable name for Datadog CLI?<\/h3>\n\n\n\n
        For general platform operations:<\/p>\n\n\n
        pup<\/code><\/span><\/pre>\n\n\n
        For CI\/CD operations:<\/p>\n\n\n
        datadog-ci<\/code><\/span><\/pre>\n\n\n
        For local Agent administration:<\/p>\n\n\n
        datadog-agent<\/code><\/span><\/pre>\n\n\n
        There is no universal requirement to install a command simply named datadog<\/code>.<\/p>\n\n\n\n
        Q3. Can I install Datadog CLI on an Apple Silicon Mac?<\/h3>\n\n\n\n
        Yes. Datadog provides native ARM64-compatible builds of Pup and Datadog CI CLI.<\/p>\n\n\n\n
        Q4. Does Datadog CLI work on Windows?<\/h3>\n\n\n\n
        Yes. Pup and Datadog CI CLI provide Windows-compatible standalone binaries.<\/p>\n\n\n\n
        Q5. Do I need Node.js to install Datadog CLI?<\/h3>\n\n\n\n
        For Pup CLI, no.<\/p>\n\n\n\n
        For the npm-distributed Datadog CI CLI, Node.js and npm are required.<\/p>\n\n\n\n
        However, Datadog CI CLI also provides standalone binaries that do not require you to install Node.js separately.<\/p>\n\n\n\n
        Q6. Can I use Datadog CLI without installing the Datadog Agent?<\/h3>\n\n\n\n
        Yes.<\/p>\n\n\n\n
        Pup and Datadog CI CLI are independent tools.<\/p>\n\n\n\n
        They can communicate with Datadog services without requiring a local monitoring Agent.<\/p>\n\n\n\n
        Q7. Can I manage Datadog dashboards and monitors using CLI?<\/h3>\n\n\n\n
        Yes. Pup CLI supports operations for managing monitors, dashboards, SLOs, and other platform resources.<\/p>\n\n\n\n
        Q8. Can I use Datadog CLI in GitHub Actions?<\/h3>\n\n\n\n
        Yes.<\/p>\n\n\n\n
        Datadog CI CLI is specifically designed for CI\/CD integration.<\/p>\n\n\n\n
        Pup can also be used in automation when appropriately authenticated.<\/p>\n\n\n\n
        Q9. Is Datadog CLI free?<\/h3>\n\n\n\n
        The CLI tools are available without a separate installation charge. However, Datadog services, API-driven operations, Synthetic tests, and other monitored resources may be subject to your organization’s subscription, limits, or usage charges.<\/p>\n\n\n\n
        Q10. What is the difference between Datadog CLI and Datadog Agent?<\/h3>\n\n\n\n
        The CLI communicates with Datadog APIs to perform management or automation tasks.<\/p>\n\n\n\n
        The Datadog Agent collects telemetry from infrastructure and applications and forwards it to Datadog.<\/p>\n\n\n\n
        The Agent’s own CLI is specifically for administering that installed Agent.<\/p>\n\n\n\n
        Q11. Should I install both Pup and datadog-ci?<\/h3>\n\n\n\n
        Install both if you need general Datadog administration and CI\/CD automation.<\/p>\n\n\n\n
        Otherwise, install only the tool required for your workflow.<\/p>\n\n\n\n
        \n\n\n\n
        27. Best Practices for Production Environments<\/h1>\n\n\n\n
        When using Datadog CLI tools in production, follow these recommendations:<\/p>\n\n\n\n
          \n
        1. Download software from official Datadog repositories and trusted distribution channels.<\/li>\n\n\n\n
        2. Verify standalone binaries using published checksums and signatures where available.<\/li>\n\n\n\n
        3. Pin approved CLI versions in production automation.<\/li>\n\n\n\n
        4. Use OAuth2 where appropriate for interactive Pup access.<\/li>\n\n\n\n
        5. Use narrowly scoped machine credentials for unattended automation.<\/li>\n\n\n\n
        6. Store credentials in a secure secrets manager.<\/li>\n\n\n\n
        7. Never commit API or application keys to a Git repository.<\/li>\n\n\n\n
        8. Confirm the Datadog site and organization before making changes.<\/li>\n\n\n\n
        9. Prefer read-only access for monitoring and troubleshooting tasks.<\/li>\n\n\n\n
        10. Treat commands that delete, modify, or create resources as production changes requiring review.<\/li>\n\n\n\n
        11. Avoid mixing production and nonproduction credentials.<\/li>\n\n\n\n
        12. Keep CLI upgrades controlled and repeatable.<\/li>\n\n\n\n
        13. Use command-specific help before relying on syntax in automation.<\/li>\n\n\n\n
        14. Monitor API rate limits and the cost of billable operations.<\/li>\n\n\n\n
        15. Do not confuse Datadog Agent installation procedures with Pup or Datadog CI CLI installation.<\/li>\n<\/ol>\n\n\n\n
          \n\n\n\n
          28. Conclusion<\/h1>\n\n\n\n
          Datadog provides command-line tools that help developers, DevOps engineers, and SRE teams automate observability and monitoring workflows.<\/p>\n\n\n\n
          For general Datadog management, Pup CLI<\/strong> provides access to monitors, dashboards, logs, metrics, SLOs, and many other supported resources.<\/p>\n\n\n\n
          For CI\/CD automation, Datadog CI CLI<\/strong> enables Continuous Testing, Synthetic monitoring workflows, and integrations with development pipelines.<\/p>\n\n\n\n
          Installing these tools is straightforward:<\/p>\n\n\n\n