Global Accelerator:Origin probing

How it works

Origin probing sends probe packets from detection points deployed around the world to your origin server, simulating real user traffic. By default, each detection point probes your origin every 5 minutes.

When availability drops, two mechanisms help you respond:

• Network diagnostics: Run an immediate on-demand check, or configure automatic diagnostics to trigger when availability falls below a threshold you set. By default, results from the past hour are displayed; you can filter to view results from up to the past 30 days.

• Alert rules: Get notified through CloudMonitor when availability drops below a configured threshold, enabling real-time response to end-to-end network issues.

Prerequisites

Before you begin, ensure that you have:

• A GA instance in the Available state

• A basic bandwidth plan purchased and attached (required for subscription billing)

• An acceleration area, listener, and endpoint group configured for the instance. See Add and manage acceleration areas and Add and manage intelligent routing listeners

Create an origin probing task

1. Log on to the GA console.

2. In the left navigation pane, click Origin Probing.

3. On the Origin Probing page, click Create Origin Probing Task.

4. In the Create Origin Probing Task dialog box, configure the parameters and click OK.

1. In the confirmation message, click OK.

After the task is created, wait 3 to 5 minutes, then click View How to Create Alert to go to the CloudMonitor console and set up alert rules.

Run network diagnostics

1. Log on to the GA console.

2. In the left navigation pane, click Origin Probing.

3. On the Origin Probing page, click the ID of the task you want to diagnose.

4. On the task details page, click the Network Diagnostics tab and choose a diagnostic method:

   • On-demand: Click Diagnose to run an immediate check.

   • Automatic: Click Set Automatic Diagnostics, configure Status and Trigger condition, and click OK.

   After starting a diagnostic, the check takes approximately 1 minute to complete.

5. On the Network Diagnostics tab, review the results. The results default to the past hour. Select a custom time range to view results from up to the past 30 days.

   

Create an alert rule

1. Log on to the GA console.

2. In the left navigation pane, click Origin Probing.

3. On the Origin Probing page, click Create Alert Rule. You are redirected to the CloudMonitor console.

4. On the Alert Rule page, click Create Alert Rule.

5. In the Create Alert Rule panel, configure the following parameters and click OK.

For parameters not listed here, see Create an alert rule.

View monitoring results

1. Log on to the GA console.

2. In the left navigation pane, click Origin Probing.

3. On the Origin Probing page, click the ID of the task you want to review.

4. On the Monitor tab, view the origin probing results. The Monitor tab has three sections:

   Section	What it answers
   Overview	Current availability and any active alerts. To view alert rules and history, create a threshold-triggered alert rule first (see Create an alert rule).
   Availability analysis	Availability statistics over a selected time range. Use this to identify when degradation started and how long it lasted.
   Probing result (Last 6 hours)	Per-probe details, filterable by Internet service provider or result status. Use this to identify which detection points or ISPs are affected. Call DescribeApplicationMonitor to query the detection points of a task.

   

More operations

Example

Suppose you use Global Accelerator to improve performance for example.com. Beyond instance-level bandwidth monitoring, you want comprehensive, real-time visibility into end-to-end connectivity from your users to your origin server.

Default probing

Create an origin probing task with the default 5-minute frequency to continuously track origin availability. The following figure shows the configuration used in this example.

API reference