list_website_checkpoints
List available checkpoint locations for website monitoring, including geographic regions and types (external/internal), to use when creating website monitors.
Instructions
List available checkpoint locations for website monitoring in LogicMonitor (LM) monitoring.
Returns: Array of checkpoint locations with: id, name, geographic region, status, type (internal/external).
What are checkpoints: Global testing locations from which LogicMonitor runs synthetic website checks. Think "test my website from New York, London, Tokyo" - checkpoints are those global vantage points.
When to use:
Check available checkpoint locations before creating website monitors
Verify geographic coverage for multi-region testing
Select appropriate locations for SLA monitoring
Plan website monitoring strategy
Checkpoint types:
External (Cloud): LogicMonitor-managed locations around the world (US-East, EU-West, Asia-Pacific, etc.)
Internal (Collector-based): Tests run from your own collectors (test internal apps, VPNs, private networks)
Common checkpoint locations:
North America: US-East, US-West, US-Central, Canada
Europe: EU-West (Ireland), EU-Central (Frankfurt), UK
Asia-Pacific: Singapore, Sydney, Tokyo
South America: São Paulo
Use cases:
Global SLA monitoring: Test from regions where customers are located
CDN verification: Ensure content delivery works worldwide
Regional compliance: Monitor from specific geographic locations
Multi-region performance: Compare response times across locations
Failover testing: Verify DR sites accessible from all regions
Best practices:
Select checkpoints near your user base
Use multiple checkpoints for critical services (avoid false positives from single location issues)
Mix internal and external checkpoints for comprehensive coverage
Consider timezone differences for result interpretation
Workflow: Use this tool to discover available locations, then use those checkpoint IDs when creating website monitors via "create_website".
Related tools: "list_websites" (existing monitors), "create_website" (configure checkpoints), "get_website" (verify checkpoint configuration).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Comma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields. |