Synthetic monitoring

Test your apps, and every hop on the way

Schedule HTTP, DNS, TLS, TCP and ICMP tests from the collectors you already run, every minute to every 15 minutes. Each run records availability and timing, and can trace the network path to the target hop by hop.

Start free Book a demo Read the docs

HTTP · DNS · TLS · TCP · ICMP
Hop-by-hop paths
Runs on your collectors

Checkout quote APIHTTP server · every minute · shop.acme.examplePassing

Availability100%Runs180Median response214 msP95 response652 ms

Response time · last hourChange 4821 at 14:02 · rollback at 14:3114:0014:1514:3014:4515:00

PathMapTable · 3

CollectorAvailMedianLossStatus

ams-edge-01ams-dc1100%221 ms0%Passed

web-prod-14us-east-1100%206 ms0%Passed

Tracix cloudGateway collector · no path100%214 ms–Passed

How it works

From a target to a result from every site

Tests run on collectors you already operate, so they see your apps from the offices, data centers and clouds your users work from.

01Pick a testHTTP server, DNS server, TLS certificate, TCP connect to a port, or ICMP ping.
02Set a scheduleEvery minute to every 15 minutes, with randomized start times so collectors do not probe in lockstep.
03Choose whereRun it on every collector in a policy, or on your workspace's gateway collector.
04MeasureEach run records availability and timing, and can trace the network path to the target.
05CompareResults line up by collector, so one failing site stands out from the rest.

Network paths

See the path to your app, hop by hop

Turn on network measurements and every run traces the route to the target: TCP probes to the app's port, or ICMP to the DNS resolver. Each hop shows its address, the network that owns it, its round-trip time and its loss.

Hops that do not answer show as gaps, never as guesses
Loss from a router rate-limiting ICMP is told apart from loss at the target
Each collector's runs are kept separate, so you can compare paths from different sites

Path · ams-edge-01 to shop.acme.exampleTCP to port 443 · run at 14:58:02Reached

ams-edge-01Collector · ams-dc1

110.20.0.1Private address0.4 msloss 0%

210.20.1.2Private address0.6 msloss 0%

3198.51.100.1AS64500 · Example Transit2.8 msloss 0%

4*No reply, often filtered or rate-limited

5198.51.100.77Router ICMP rate limit; the target lost nothing9.6 msloss 30%

6203.0.113.1AS64510 · Example Cloud11.9 msloss 0%

203.0.113.24shop.acme.example · port 44312.4 msloss 0%

Where tests run

Tests run from the places your users are

A test belongs to a collector policy, and every collector enrolled in it runs the test and reports its own results. Use collectors in offices, data centers and clouds, or your workspace's gateway collector for a view from outside your network.

HTTP server
Availability and response time, failing on status codes you do not accept.
DNS server
How long a domain takes to resolve, with an ICMP path to the resolver.
TLS certificate
Days to expiry, chain validity, key, TLS version and handshake time.
TCP and ICMP
Connect time to a port, or round-trip time, jitter and loss to a host.

Checkout quote APIHTTP server test · every minute

policy network-edge · signed configuration

Collector ams-edge-01On your network, in ams-dc1

HTTPS request · TCP path to port 443

shop.acme.exampleReached in 12.4 ms, no loss

All tests

Every test, with its availability and status

The list shows each test's availability, latency, loss and trend for the time range you pick. Open a test for its charts, its collectors and the path of every run.

TLS tests chart the days left before a certificate expires
Runs a collector could not measure, such as ICMP without permission, never count against availability
Collectors that need an update or rejected the test's configuration are flagged

Synthetic testsLast hour

Tests9Availability99.6%Vantage points4Failing1

TestAvailLatencyStatus

HTTPCheckout quote API100%214 msPassing

DNSacme.example100%18 msPassing

TLSshop.acme.example:443Certificate expires in 23 days100%41 msPassing

TCPpayments-api.internal:8443100%0.9 msPassing

ICMPdist-sw-07100%0.6 msPassing

TCPsftp.partner.example:22Connection refused0%–Failing

Better together

Proof from the outside, next to the evidence inside

Synthetic results share a workspace with real user data, endpoint tests and network devices, so a failing check leads to the hop, the device or the service behind it.

Test types

What each test measures, and where it can run

Every test type runs on collectors in your policies. The gateway collector in your workspace runs some of them, without path tracing.

Test	Measures	Network path	From the gateway collector
HTTP server	Availability and response time, with accepted status codes	TCP to the app's port	Yes, without the path
DNS server	Resolution time	ICMP to the resolver	Yes, without the path
TLS certificate	Days to expiry, chain, key, TLS version, handshake time	TCP to the port	Yes, without the path
Agent to server (TCP)	Connect time to a port	TCP to the port	Yes, without the path
ICMP ping	Round-trip time, jitter and packet loss	Always traced	No
Page load and multistep	Not available yet	Not available yet	Not available yet

Tests run every 1, 2, 5, 10 or 15 minutes. On Linux, tracing hops needs the collector installed with --enable-network-path, which grants CAP_NET_RAW.

FAQ

Questions teams ask before they move their checks

Talk to an engineer

Can Tracix run browser tests, or measure bandwidth and call quality?

Not as synthetic tests. Page load and multistep tests need a browser engine on the collector, which is not available yet. Separate iperf throughput and RTP call-quality probe packages exist for collectors, but their results arrive only as metrics, with no dedicated view yet.

Where do tests run from?

From collectors you run, in offices, data centers or clouds, and from your workspace's gateway collector. There is no global network of Tracix probe locations, and the gateway cannot run ICMP tests or trace paths.

Can a synthetic test alert me?

Not yet. Alert rules for synthetic tests are not available. Each test shows its availability, its failed runs and the collectors that failed.

What does path tracing need on Linux?

Raw-socket permission. Install the collector with --enable-network-path to grant it CAP_NET_RAW. Without it, tests still measure the target but cannot trace the hops.

Create your first test in minutes

Pick a test type and a target, choose the collectors that run it, and results arrive after the first interval.

Start free Read the docs

Test your apps, and every hop on the way

From a target to a result from every site

See the path to your app, hop by hop

Tests run from the places your users are

HTTP server

DNS server

TLS certificate

TCP and ICMP

Every test, with its availability and status

Proof from the outside, next to the evidence inside

What each test measures, and where it can run

Questions teams ask before they move their checks

Create your first test in minutes