Agent Health Dashboard

Overview of Qualys Cloud Agent health across your estate.

Detection Source not available for this subscription. The Qualys API rejected the vuln_detection_source parameter, so the data was pulled without it. The Detection Source column will be empty in this report and you will not be able to distinguish Cloud Agent vs. Scanner detections. To enable it, contact Qualys Customer Support and ask for the Vulnerability Detection Sources feature. Learn more: Introducing Vulnerability Detection Sources in VMDR.

Agent Health

Live health reported by the Cloud Agent health check (QID 45619).

Additional Agent Findings

Additional agent health detections that need review, kept separate from the agent health check (QID 45619).

Health Distribution

Health Pipeline

How This Data Is Collected

API call details, leveraged QIDs, and how to reproduce this pull yourself

▾

The API Call

This dashboard makes a single POST request to the Qualys Host List Detection API v4.0:

POST https://<your-platform>/api/4.0/fo/asset/host/vm/detection/

Request Parameters

Parameter	Value	Why
action	list	List host detection data
qids	45619,105961,45592,45484	Restrict output to only the four Information Gathered QIDs this tool uses
show_igs	1	Required — IG-type QIDs are excluded from detection output by default
vuln_detection_source	1	Includes the detection source (Cloud Agent, Scanner) per detection. Requires the Vulnerability Detection Sources feature; if the subscription rejects it, the tool automatically retries without it and shows a warning

Authentication is HTTP Basic (your Qualys API credentials) plus the required X-Requested-With header.

Reproduce It Yourself

curl -s -X POST \
  -u "USERNAME:PASSWORD" \
  -H "X-Requested-With: curl" \
  -d "action=list&qids=45619,105961,45592,45484&show_igs=1&vuln_detection_source=1" \
  "https://<your-platform>/api/4.0/fo/asset/host/vm/detection/"

The response is XML: one <HOST> per asset with a <DETECTION_LIST> of matching QIDs. Large subscriptions can take a minute or more.

QIDs Leveraged

QID	Title	What this tool extracts
45619	Qualys Agent Health	The primary health report: overall status (Good/Poor/Bad/Not Provisioned/Tool Error), service state, backend connectivity, per-module health, certificates, and errors. Drives status badges, metric cards, pipeline, and Details.
105961	EOL/Obsolete Software: Qualys Cloud Agent Detected	Hosts running an end-of-support agent version. Drives the EOS Agents card and EOS Version column.
45592	Qualys Cloud Agent Not Installed	Hosts that support Cloud Agent but have none installed (scanner-detected). Drives the Not Installed status and deployment-opportunity card.
45484	Qualys Correlation Identifier Status	Whether agentid-service is running plus its Correlation ID and ports. Drives the Correlation Svc Down card and Correlation ID column.

How Each Host Is Classified

If QID 45619 is present, the overall status comes from its health report. If the report lacks an explicit status, one is derived: Bad if the service is stopped, the backend is unreachable, an enabled module is unhealthy, or a high/critical error exists; Poor if other errors exist; otherwise Good.
No 45619 report but QID 45592 present → Not Installed.
Neither present → Unknown (no health report returned).
QIDs 105961 and 45484 are supplemental annotations (EOS version, correlation service) independent of overall status.

Agents

Host	FQDN	Status	Detection Source	EOS Version	Correlation ID	Service	Backend	Modules	Issues	Last Scan

Agent health data is fetched live from the Qualys API.

Agent Health Monitor