Understand how tracer agents execute monitors from multiple geographic locations.

Agents

Agents are distributed workers that execute your monitors and journeys. They run in data centers worldwide, providing geographic coverage and redundancy.

Managed Agents

tracer provides managed agents in these regions:

Region	Location	Code
US East	Virginia, USA	`us-east`
US West	Oregon, USA	`us-west`
EU West	Ireland	`eu-west`
EU Central	Frankfurt, Germany	`eu-central`
Asia Pacific	Singapore	`ap-southeast`
Turkey	Istanbul	`tr-istanbul`

Agent Capabilities

All managed agents support:

URL/HTTP monitoring
API monitoring
TCP monitoring
DNS monitoring
Browser journeys (Playwright)
Visual testing

Selecting Locations

When creating a monitor, select which locations to run from:

Monitor: Production API
Locations:
  - us-east
  - eu-west
  - ap-southeast

Benefits of multiple locations:

Geographic redundancy
Detect regional outages
Measure latency from user regions
Verify CDN effectiveness

For global services, run from at least 3 regions covering major user populations.

Agent Status

View agent status in Settings > Agents:

Status	Description
Healthy	Agent operating normally
Degraded	Experiencing issues, runs may be delayed
Offline	Agent unavailable

Agent Health Checks

Agents report health via:

Heartbeat signals (every 30 seconds)
Run completion metrics
Resource utilization

How Agents Work

Run Execution

Scheduler assigns run to agent
Agent pulls monitor configuration
Agent executes the check
Results sent back to tracer
Results processed and stored
Alerts evaluated

Run Distribution

When multiple locations are selected:

Locations: [us-east, eu-west, ap-southeast]
Interval: 5 minutes

Each location runs independently every 5 minutes, resulting in 3 runs per interval (one from each location).

Failover

If an agent is unavailable:

Runs are automatically rescheduled to healthy agents
Alert evaluations account for agent outages
No action required from you

Agent IP Addresses

If you need to allowlist tracer traffic, here are the agent IP ranges:

US East

52.X.X.X/24
54.X.X.X/24

EU West

52.X.X.X/24
54.X.X.X/24

IP addresses may change. For current IPs, see your dashboard at Settings > Agents > IP Addresses or use our API.

Dynamic IP List

Fetch current IPs via API:

curl https://api.tracer/v1/agents/ips

Response:

{
  "us-east": ["52.1.2.3", "52.1.2.4"],
  "eu-west": ["54.1.2.3", "54.1.2.4"],
  ...
}

Private Agents

For monitoring internal services behind firewalls, deploy private agents.

Use Cases

Internal APIs not exposed to internet
Development/staging environments
On-premise infrastructure
VPN-protected services

Deployment

Private agents are deployed as Docker containers:

docker run -d \
  --name izli-agent \
  -e AGENT_TOKEN=your-agent-token \
  -e AGENT_NAME=internal-datacenter \
  izli/agent:latest

Getting an Agent Token

Go to Settings > Agents
Click Add Private Agent
Copy the agent token
Use in your deployment

Private Agent Configuration

# docker-compose.yml
version: '3'
services:
  izli-agent:
    image: izli/agent:latest
    environment:
      AGENT_TOKEN: ${AGENT_TOKEN}
      AGENT_NAME: internal-dc-1
      AGENT_LOCATION: internal
    restart: always

Kubernetes Deployment

apiVersion: apps/v1
kind: Deployment
metadata:
  name: izli-agent
spec:
  replicas: 1
  selector:
    matchLabels:
      app: izli-agent
  template:
    metadata:
      labels:
        app: izli-agent
    spec:
      containers:
        - name: agent
          image: izli/agent:latest
          env:
            - name: AGENT_TOKEN
              valueFrom:
                secretKeyRef:
                  name: izli-secrets
                  key: agent-token
            - name: AGENT_NAME
              value: k8s-agent