topic Re: Is it possibly to list the request url and verification/validation text for HTTP monitors from DQL? in DQL

Is it possibly to list the request url and verification/validation text for HTTP monitors from DQL?

jgillotti1 — Wed, 10 Sep 2025 19:39:52 GMT

Is it possibly to list the request url and verification/validation text for HTTP monitors from DQL?

I can get the steps guid from dt.entity.http_check but do not know how to retrieve/parse the json from step.

Is this possible? Any sample queries?

Thank you

Re: Is it possibly to list the request url and verification/validation text for HTTP monitors from DQL?

jgillotti1 — Thu, 11 Sep 2025 19:27:44 GMT

Is there a topology for this entity that joins and display the step information?

When I describe dt.entity.http_check, I see steps but do not know how to join or query?

Is this possible?

field	data_types
dt.system.table	string
dt.system.environment	string
lifetime	timeframe
gcpZone	string
runs_on	record
icon	record
assignedLocations	array
manuallyAssignedApplications	array
lastModificationSource	string
managementZones	array
entity.type	string
entity.name	string
entity.detected_name	string
id	string
modificationTimestamp	timestamp
customIconPath	string
entity.conditional_name	string
oneAgentCustomHostName	string
lastModifiedBy	string
entity.customized_name	string
steps	array
boshName	string
tags	array
contains	record
dt.security_context	array
calls	record
createdBy	string
awsNameTag	string
isEnabled	boolean
lastExecutionTimestamp	timestamp
syntheticMonitorFrequency	long
monitors	record

Re: Is it possibly to list the request url and verification/validation text for HTTP monitors from DQL?

t_pawlak — Mon, 15 Sep 2025 12:48:32 GMT

Short answer: partly.

Request URL — yes from DQL, but not from the entity itself. You can read it from Synthetic HTTP step execution details events (result.statistics.url).
Verification/validation text (e.g., “content contains …”) — no via DQL. That lives in the monitor definition and must be read via the Synthetic API.

Here u have example dql:

fetch events | filter event.kind == "SYNTHETIC_EVENT" and isNotNull(result.statistics.url) // step *details* records | fields timestamp, dt.entity.http_check, // monitor entity ID dt.entity.http_check_step, // step entity ID step.sequence_number, step.name, result.statistics.method, result.statistics.url, result.statistics.response_status_code, result.status.category | sort timestamp desc | limit 200