DataReel Reporting Agent Documentation Live demo Downloads

Reports and status page

Each computer's report is a plain text file, easy to read, grep and diff. The server keeps the latest one per computer.

Report format

Reports are saved as <hostname>_windows_report_agent.txt in reports_dir. The header lines are KEY: value pairs, and each section starts with its name and a colon and ends with END and the name:

DataReel Reporting Agent report from host pc-0142
VERSION: 3.4
HOSTNAME: pc-0142
ETIME: 1792971236
DATETIME: Sun Oct 25 19:33:56 2026

SERVICE TAG AND BARCODE:
...
END SERVICE TAG AND BARCODE

INSTALLED WINDOWS PATCHES:
Date:  2026-10-14
 Patch: 2026-10 Cumulative Update for Windows 11 Version 25H2 for x64-based Systems
...
END INSTALLED WINDOWS PATCHES

ETIME is the report time in seconds since 1970 (UTC), for check-in age calculations.

Sections

SectionContents
SERVICE TAG AND BARCODEService tag (BIOS serial number, the Dell service tag on Dell computers) and asset tag from WMI
IP ADDRESSIPv4 addresses of the network adapters that are up
PERFORMANCECPU count and use (sampled over 5 seconds), memory total, available and used, commit charge, processes, threads, uptime
DISK USAGESize, used, free and percent used of each local fixed drive
NETWORKPer adapter that is up: link speed, bytes, packets, errors and discards received and sent, totals since the adapter came up
USERSProfile folders in users_dir
ALL INSTALLED PROGRAMSName and version of every program in the 64-bit and 32-bit uninstall registry keys
WINDOWS DEFENDER ALERTSCritical, error and warning events from the Defender event log for event_lookback_days
INSTALLED WINDOWS PATCHESWindows Update installation history
HOT FIXESInstalled hotfixes from WMI (Win32_QuickFixEngineering)

Hook uploads

A hook upload sends a report from another source with the agent: a Defender full scan run by hand, a vendor tool's export, a backup job's result. The report server's hook.php takes it, signed like a report, and the DataReel System Monitor shows it on the computer's host page with its own format, alert rules and display, set by a manifest on the server (DRSM plugins/uploads/<id>). Each upload hook is a file in C:\ProgramData\DataReel\ReportingAgent\uploads.d:

[upload]
id=defender_scan
title=Defender threat history
format=csv

From an administrator prompt, export the data and queue it. --now asks the service to send it within a few seconds; without it the file goes with the next report. A tool can also write its file to C:\ProgramData\DataReel\ReportingAgent\uploads\<id> (under a name that starts with a dot or ends in .tmp, then renamed).

powershell "Get-MpThreatDetection | Select-Object InitialDetectionTime,ThreatID,ActionSuccess,Resources | Export-Csv -NoTypeInformation C:\scans\threats.csv"
"C:\Program Files\DataReel\ReportingAgent\drra_svc.exe" submit --hook defender_scan --now C:\scans\threats.csv
"C:\Program Files\DataReel\ReportingAgent\drra_svc.exe" uploads

drra_svc.exe uploads lists the upload hooks and their state, and send-uploads sends the queued files at once. Sent files are kept in sent\ next to the queue, and the report's UPLOADS section has each hook's state. The server only takes a hook that has a manifest, from a registered computer, about itself; set [hooks] manifest_dir in server.ini (see Server settings). Formats: drsm-lines, kv-sections, json, csv, xccdf-results, text and html. Hook uploads use the HTTPS delivery method.

Usage for trends

PERFORMANCE, DISK USAGE and NETWORK are name=value lines that a monitor such as the DataReel System Monitor can graph. The names match the DRSM Linux metrics where there is one. The network counters are running totals, so take the difference between two reports for a rate. Idle virtual adapters with no traffic are left out. report.php shows them as a Usage panel.

PERFORMANCE:
cpu_count=4
cpu_used_pct=7.2
mem_total_mb=16364
mem_available_mb=12307
mem_used_pct=24.8
commit_limit_mb=17388
commit_used_mb=3740
uptime_seconds=11230
END PERFORMANCE

DISK USAGE:
drive=C: size_mb=510963 used_mb=108062 free_mb=402901 used_pct=21.1
END DISK USAGE

NETWORK:
adapter="Ethernet" if_index=10 speed_mbps=1000 rx_bytes=91234664 tx_bytes=37097265 rx_errors=0 tx_errors=0 ...
END NETWORK

Fleet status page

status.php in the upload pages folder lists every computer with its state, worst first. See it on the live demo.

StateWhen
Needs attentionNo report for missing_days, an empty or bad report, or a Windows Defender detection, failed action or disabled protection
WarningA late report, Windows updates older than patch_max_age_days, a missing required program or an unwanted program
OKNone of the above

The tiles at the top filter the list, the column headers sort it, and the search box matches computer names, users, service tags, IP addresses and problems. report.php?host=<name> shows one computer: its problems, hardware, users, Defender events, installed programs with a filter, Windows updates, hotfixes and the report file. Both pages are read only and need the admin login. Set the rules in server.ini:

[status]
required_apps = "Microsoft 365 Apps*, Google Chrome"
required_apps_skip_hosts = "srv-*"
unwanted_apps = "uTorrent*, CCleaner*"

Live demo and sample fleet

tools/gen_sample_fleet.py writes reports for a made up fleet that covers every state: current, late and missing check-ins, empty and bad reports, computers behind on updates, missing and unwanted programs and Defender detections. php/install_demo.sh installs the status pages in a folder of their own with such a fleet and no login, which is how the live demo runs:

$ php/install_demo.sh --apply /var/www/html/windows_reporting_agent/demo

Status page script

bash/run_windows_laptop_inventory.sh is the original status page. It reads the reports and builds an HTML and a text page that list every computer by check-in state (reported in the last 24 hours, in the last 15 days, not for more than 15 days, or an empty or unreadable report) with pass and fail lists. It uses the DRSM configuration (~/.drsm.sh or $BASEdir/etc/drsm.sh) and runs from cron. Set SYSLOG_DIR at the top of the script to your reports_dir.

# crontab: update the status page every 30 minutes
*/30 * * * * $HOME/windows_reporting_agent/bash/run_windows_laptop_inventory.sh > /dev/null 2>&1

DRSM

The DataReel System Monitor shows Windows computers on its dashboard next to the Linux hosts. DRSM never connects to a Windows computer: its wra collector runs the Windows plugins on the monitor host against each computer's last report in WRA_REPORTS_DIR. The simplest way to get the reports there is the agent's file share delivery to a share on the monitor host. Reports that arrive by HTTPS on another server have to be copied over.

DRSM pluginChecks
windows/checkinThe computer reported recently and completely, agent version
windows/defenderDefender threats, protection turned off, old definitions
windows/patchesAge of the newest Windows patch
windows/appsRequired and forbidden programs
windows/resourcesCPU, memory, disk and network from the usage sections, for the trends page
# DRSM etc/hosts/_defaults.conf
WRA_REPORTS_DIR=/path/to/reports

# DRSM etc/hosts/pc-0142.conf
HOST=pc-0142
PLATFORM=windows
COLLECTOR=wra
PROBES=""
PLUGINS="windows/checkin windows/defender windows/patches windows/apps windows/resources"

DRSM 1.32-beta2 and later include these plugins. For DRSM 1.31, the drsm/ folder of this distribution has the same plugins and an installer, drsm/install.sh, that only lists what it would copy until run with --apply (add -t and the DRSM folder if it is not ~/drsm). See the DRSM documentation for the plugin settings.