Getting Started with Catchpoint: Setup and First Synthetic Monitor

Catchpoint is an enterprise-grade internet performance monitoring platform used by Fortune 500 companies to track application availability, performance, and user experience across global networks. If you're new to Catchpoint, the initial setup can feel overwhelming — there are dozens of node types, test configurations, and alerting options. This guide walks you through everything from account setup to running your first synthetic monitor.

What Is Catchpoint?

Catchpoint is not a simple uptime checker. It's a comprehensive Internet Performance Monitoring (IPM) platform that measures performance from the perspective of real users located around the world. Catchpoint runs tests from over 2,500 monitoring nodes across backbone networks, ISPs, cloud providers, and wireless carriers — giving you a view of your application performance that internal monitoring tools simply cannot replicate.

Key capabilities include:

• Synthetic monitoring — scripted browser, API, and network tests run on a schedule
• Real User Monitoring (RUM) — JavaScript snippet captures actual user interactions
• BGP monitoring — tracks routing changes and network path anomalies
• DNS monitoring — detects DNS failures and propagation issues
• Traceroute and network analytics — identifies where latency originates

Organizations use Catchpoint to detect performance degradations before customers notice, validate CDN performance, enforce SLAs, and debug complex network-level issues.

Account Setup

Step 1: Request a Trial or Enterprise Account

Catchpoint is an enterprise product without a self-serve signup. You'll need to request a demo or trial through their website. Once provisioned, you'll receive credentials for the Catchpoint portal at portal.catchpoint.com.

Step 2: Navigate the Portal

The Catchpoint portal is organized around several key sections:

• Test Library — all your configured synthetic tests
• Dashboards — real-time and historical performance views
• Alerts — notification rules and escalation policies
• Settings — node configuration, integrations, user management

Spend a few minutes familiarizing yourself with the left navigation before creating your first test.

Step 3: Configure Your Team

Under Settings > Users, invite team members and assign roles. Catchpoint uses role-based access control:

• Super Admin — full access including billing
• Admin — manage tests, alerts, and users
• Editor — create and modify tests
• Viewer — read-only access to dashboards and reports

Set up at least one admin account and configure your team before going further.

Node Selection: Where Tests Run From

One of Catchpoint's most powerful features is its global node network. When creating a test, you specify which nodes run it. Choosing the right nodes matters:

Node Types

Selecting Nodes

For most teams starting out, choose 5–10 backbone nodes covering your primary user regions. If your users are in North America and Europe, select nodes in:

• New York, Los Angeles, Chicago (US backbone)
• London, Frankfurt, Amsterdam (EU backbone)

You can always expand to more nodes as your monitoring matures.

Creating Your First Synthetic Monitor

Step 1: Choose a Test Type

Navigate to Test Library > Add Test. Catchpoint offers several test types:

• Web Test — full browser page load with Chromium
• Transaction Test — multi-step browser automation
• API Test — HTTP/HTTPS endpoint validation
• DNS Test — nameserver response monitoring
• Traceroute Test — network path analysis
• Ping Test — ICMP availability check

For your first monitor, start with a Web Test targeting your homepage or a critical URL.

Step 2: Configure the Web Test

Basic configuration:

Test Name: Homepage Performance Monitor
URL: https://yoursite.com
Test Frequency: Every 5 minutes
Nodes: Select 5-10 backbone nodes

Advanced settings to configure:

• Script Type: Choose "URL" for simple page loads or "Script" for custom Selenium-based flows
• Viewport: Set desktop (1920x1080) and/or mobile (375x812) viewports
• Connection: Default (node's native connection) or throttled (3G simulation)
• DNS Override: Optional — useful for testing behind load balancers

Step 3: Set Thresholds

Thresholds define when a test result is flagged as a warning or failure:

Response Time Warning: 2000ms
Response Time Critical: 5000ms
Availability: Below 99%

For a homepage, industry benchmarks suggest:

• Good: Under 1.5 seconds
• Acceptable: 1.5–3 seconds
• Poor: Over 3 seconds

Set your thresholds based on your SLA commitments and historical baseline.

Step 4: Configure Alerts

Click Alerts in the test configuration. Create an alert rule:

1. Trigger condition: "Response time exceeds critical threshold for 2 consecutive checks"
2. Notification channels: Email, Slack, PagerDuty, or webhook
3. Escalation policy: Who gets notified if the primary contact doesn't acknowledge within 15 minutes

Avoid alerting on a single failed check — network blips cause false positives. Require at least 2 consecutive failures before triggering.

Step 5: Save and Activate

Click Save & Start. The test will begin running from your selected nodes immediately. Within 5–10 minutes, you'll see your first data points in the dashboard.

Reading Your First Results

The Test Dashboard

Once data starts flowing, navigate to your test's dashboard. You'll see:

• Response Time Trend — line chart showing performance over time, by node
• Availability — percentage of successful checks
• Waterfall Chart — per-resource breakdown of page load (for web tests)
• Node Comparison — side-by-side performance across regions

Understanding the Waterfall

The waterfall chart is one of Catchpoint's most useful diagnostic tools. It shows the time spent on each phase:

• DNS — domain name resolution time
• Connect — TCP connection establishment
• SSL — TLS handshake (for HTTPS)
• Send — time to send the request
• Wait (TTFB) — server processing time
• Receive — time to download the response

If your DNS phase shows 200ms while connection is only 20ms, you have a DNS performance problem. If TTFB is consistently high, the issue is server-side.

Comparing Nodes

Use the node comparison view to identify geographic performance disparities. If your US nodes show 800ms response times but European nodes show 3500ms, you likely need a CDN or European data center.

Setting Up Your Second Test: API Monitor

After your first web test is running, add an API test for a critical endpoint:

Navigate to Add Test > API Test:

URL: https://api.yoursite.com/health
Method: GET
Expected Response Code: 200
Expected Response Body: {"status":"ok"}
Frequency: Every 1 minute
Nodes: 3-5 backbone nodes

For API tests, you can validate:

• HTTP status codes
• Response body content (exact match or regex)
• Response headers
• Response time thresholds
• JSON schema compliance

Common Setup Mistakes to Avoid

1. Testing only from backbone nodes Backbone tests show ideal performance. Your real users are on last-mile ISPs that can be 2–3x slower. Add last-mile nodes once your baseline is established.

2. Setting alerts too sensitive Alerting on a single failed check creates alert fatigue. Require 2–3 consecutive failures before paging anyone.

3. Ignoring the waterfall Don't just monitor total response time. The waterfall tells you where the time is going, which is what matters for optimization.

4. Not testing mobile networks If your site has significant mobile traffic, add wireless (LTE) nodes. Mobile network performance often differs dramatically from desktop.

5. Monitoring only your homepage Critical user journeys (checkout, login, API calls) matter more than the homepage. Add transaction tests for your most important flows.

Integrating Catchpoint with Your Workflow

Slack Integration

Navigate to Settings > Integrations > Slack. Add your webhook URL and specify which alert rules should post to which channels. Keep performance alerts in a dedicated #performance-alerts channel separate from general engineering notifications.

PagerDuty Integration

For on-call workflows, connect Catchpoint to PagerDuty under Settings > Integrations > PagerDuty. Map Catchpoint alert severities to PagerDuty urgency levels:

• Catchpoint Warning → PagerDuty Low urgency
• Catchpoint Critical → PagerDuty High urgency

CI/CD Integration

Catchpoint supports webhooks that can trigger performance tests on deploy events. This is covered in depth in our post on Catchpoint CI/CD integration.

Next Steps

With your first monitors running, you have the foundation of an internet performance monitoring program. From here:

1. Add transaction tests for critical user flows (login, checkout, search)
2. Enable RUM to capture real user performance data alongside synthetic
3. Build dashboards for your engineering and ops teams
4. Set up BGP monitoring if you manage your own IP space or care about routing stability
5. Schedule a baseline review after 2 weeks to understand your normal performance patterns

Catchpoint provides a depth of insight that simple uptime checkers can't match. The investment in setup pays off when you're able to detect and diagnose performance issues in minutes rather than hours.

Complementing Catchpoint with Functional Testing

Catchpoint tells you if your application is responding and how fast. It doesn't tell you if your application is doing the right things. Combine Catchpoint's performance monitoring with functional test automation — tools like HelpMeTest let you write plain-English test scenarios that verify business logic, user flows, and application behavior without writing code.

Performance + functional coverage together gives you complete confidence in your application quality.