Node reference: Collectors and network

Node reference: Collectors and network

These nodes reach private infrastructure through your agents — the part SaaS probes can't do. Add them from the Collectors and Network palette groups.

DB Collector

Runs a read-only SQL query against your database and validates the result — for example, "the order the web test just placed really is in the orders table".

What you fill in

Field	What to enter
Database Type	PostgreSQL, MySQL, MariaDB, MSSQL, Oracle or SQLite.
Run via Machine Agent (optional)	Pick the machine agent installed next to the database to reach private databases the platform can't. Supported through an agent: PostgreSQL, MySQL, MariaDB, SQLite; for MSSQL and Oracle leave this empty so the query runs from the platform.
Connection String	Where the database lives, as host:port/database.
Username / Password	A read-only database user. Store the password as a secret and reference it, e.g. {{db_pass}}.
SQL Query	A SELECT statement. Supports {{variable}} values — e.g. use the {{orderId}} an earlier API Test extracted.
Validation Mode	Not Empty, Row Count Match (with Expected Row Count) or Contains Value (with Expected Value).
Max Rows / Timeout (seconds)	Caps on result size and query time.

What it outputs

The row count, column names and rows, plus the first row for easy assertions — e.g. {{firstRow.status}} — and a flag telling you whether the result was truncated at Max Rows.

Example: query SELECT COUNT(*) AS n FROM orders WHERE created_at > NOW() - INTERVAL 1 DAY with Validation Mode Not Empty proves orders are still flowing.

MySQL 8: when the query runs through a machine agent, create the database user with the mysql_native_password authentication plugin.

Log Collector

Reads a log file on one of your hosts through the machine agent and checks it for the lines you expect (or don't expect).

What you fill in

Field	What to enter
Machine Agent	The agent on the host that has the log file.
File Path	The log file to read, e.g. /var/log/app/batch.log. Supports {{variable}} values.
Validation Patterns	One or more patterns (plain text or regex) to search for — add as many as you need.
Expected Content	Optional exact text that should appear in the log.
Time Window (seconds)	Only consider recent log entries within this window.
Timeout (ms)	How long to wait for the agent to respond.

What it outputs

The matching lines and how many matched, whether the file exists, and its size — assert on these to prove, say, that the nightly batch logged "BATCH COMPLETED" and "0 errors" in the last 15 minutes.

Network Probe

Checks reachability, latency, DNS, TLS or HTTP health of a target from one of your network agents — from inside your network, where it matters.

What you fill in

Field	What to enter
Network Agent	The agent to probe from.
Probe Type	Ping (ICMP), TCP Connect, DNS Lookup, HTTP Check, or TLS Certificate.
Target / Port	Host, IP or URL to probe (the form hints at the right shape per probe type).
Per-type options	Ping/TCP: Count (samples) and Timeout (ms). DNS: Record Type and an optional Resolver. HTTP: Method, Timeout (ms) and an optional Request Body.
Pass criteria	Max avg latency (ms), Max packet loss (%) and — for HTTP — Expected HTTP status. The node fails if any is exceeded.
Result wait timeout (ms)	How long to wait for the agent to report its result.

What it outputs

Latency statistics (average, min/max, p95/p99), packet loss and jitter — ready for assertions or for an AI Analyze node to reason over.