Datadog Agent Installation & Impact – Windows TrueScan Systems
Datadog Agent Installation & Impact – Windows TrueScan Systems
- Purpose
This document describes the installation steps, prerequisites, and expected system impact of deploying the Datadog Agent on Windows-based TrueScan devices, enabling monitoring and visibility within the Datadog platform.
- Scope
- Applies to all Windows-based TrueScan systems
- Covers:
- Prerequisites
- Datadog Agent installation on Windows
- Validation steps
- Expected performance and operational impact
- Excludes application-level instrumentation unless explicitly enabled later
- Overview
Each TrueScan device is represented as a Host in Datadog.
A host becomes visible once the Datadog Agent (Windows service) is installed and successfully communicates with Datadog.
The agent:
- Runs as a background Windows service
- Collects system-level metrics only by default
- Does not modify application code or system configuration
- Prerequisites
4.1 Access & Permissions
- Local Administrator access on the Windows TrueScan system
- Datadog Administrator or Agent Install permissions
- Ability to download installers from the internet
4.2 System Requirements
|
Requirement |
Details |
|
OS |
Windows Server / Windows 10 / Windows 11 (64-bit) |
|
CPU |
x86_64 |
|
RAM |
Minimum 512 MB available |
|
Disk |
~200 MB free space |
|
Network |
Outbound HTTPS (TCP 443) access to Datadog |
4.3 Network Requirements
Ensure outbound connectivity to Datadog endpoints:
- *.datadoghq.com
- Port: 443 (HTTPS)
No inbound firewall rules are required.
- Installation Steps (Windows)
5.1 Obtain Datadog API Key
- Log in to Datadog
- Navigate to Organization Settings → API Keys
- Copy the API key (required during installation)
5.2 Download Datadog Agent (Windows)
- Navigate to Integrations → Agent → Windows
- Download the Datadog Agent MSI installer
5.3 Install Datadog Agent
- Log in to the TrueScan system as Administrator
- Run the downloaded .msi installer
- When prompted:
- Enter the Datadog API Key
- Confirm Datadog site (datadoghq.com)
- Complete the installation wizard
5.4 Agent Service Initialization
After installation:
- A Windows service named DatadogAgent is created
- Service starts automatically
- Agent begins sending metrics immediately
- Verification & Validation
6.1 Verify Agent Service
- Open Services (services.msc)
- Confirm:
- DatadogAgent → Status: Running
- Startup Type: Automatic
6.2 Verify Agent Status (Command Line)
Open Command Prompt (Admin):
"C:\Program Files\Datadog\Datadog Agent\bin\agent.exe" status
Expected:
- Agent running
- No connectivity errors
- Metrics collection enabled
6.3 Verify Host in Datadog UI
- Go to Infrastructure → Hosts
- Search for the TrueScan hostname
- Confirm:
- Status: Up
- OS: Windows
- Metrics visible (CPU, Memory, Disk)
- Expected Impact on Windows TrueScan Systems
7.1 Performance Impact
|
Resource |
Expected Impact |
|
CPU |
< 1–2% average |
|
Memory |
~150–250 MB |
|
Disk I/O |
Minimal |
|
Network |
Small outbound HTTPS traffic |
✔ Impact is negligible and suitable for production systems.
7.2 Security Impact
- Agent runs with least privilege
- Uses encrypted outbound communication
- No inbound ports opened
- No credential harvesting or keystroke monitoring
7.3 Application Impact
- No impact on TrueScan application behavior
- No restarts required post-installation
- No configuration files altered outside Datadog directories
- Operational Considerations
Logging
- Agent logs stored under:
- C:\ProgramData\Datadog\logs\
Updates
- Agent updates are manual unless auto-update is enabled
- Updates do not require system reboot