Execute REST Call
The Execute REST call event gives you the capability to fire an alert to any service or program that has the ability to receive REST calls.
When you create a REST alert event for the first time, you'll notice that there's a "place-holder" example already in the Body. However, you'll need to change the format according to the tool you're working with:
You'll need to have the specific address for whatever service or program you're wanting to fire the alert through here. *Most* services will have some sort of documentation on where to find this address, and what needs to be included in the body (i.e.: a security token) in order for things to work. See API Webhook Integrations for examples on how to use this alert with popular services.
-
Common tasks
- Variable Substitution
- Auto-Saving of Data
- Running as a service
- Handling Multiple Targets
- Named Configurations
- Reporting
- Session Manager
- Local Network Discovery (LND)
- Exporting data for further analysis
- Route Changes
- Dynamic DNS Tracking
- Backing up PingPlotter Data
- Sharing PingPlotter data with others
-
Understanding output
- Discovering a route between you and a target
- Interpreting Results - A Quick Example
- Finding the source of the problem
- Finding the source of the problem - part 2
- Interpreting Results - Longterm Monitoring
- Interpreting Results - Gamers
- Interpreting ISP Problems | PingPlotter
- Interpreting Results - Bad Hardware
- Interpreting Results - Bandwidth Saturation
- Building a Compelling Case
- VoIP Troubleshooting Guide
Test end-user internet
PingPlotter Cloud helps solve network problems for other people.
PingPlotter CloudNeed an earlier version?
Versions one through four are available in the legacy manual.
Legacy Manual