Skip to main content
Setup time: 2 Min
Set up our All Quiet Ping Monitor to ping your hosts or IP addresses anytime. The monitor is set up within a few clicks. After setting it up, we’ll create incidents to inform you if anything is wrong.

​
1. Create All Quiet Ping Monitor

Sign in to your All Quiet account.

​
Create Integration

  1. Click on the Inbound Integrations tab.
  2. Click on + Create.

​
Select Ping Monitor as the integration’s type

  1. Enter a Display Name for your integration, e.g. “IP Monitor”.
    Pick a name that makes it obvious which service the Ping monitor belongs to.
  2. Select a Team.
  3. Select Ping Monitor as the integration’s type.
  4. Click Create Inbound Integration.

​
2. Configure your Ping Monitor

Once you’ve set up the “Ping Monitor”, it’s time to configure it. This can be done on the the integration’s page.
  1. Select the Host you want to monitor, e.g an IP address. If you want to monitor different hosts, simply set up several monitors.
  2. Select the Timeout, the duration after which the monitor should time out and considered to be failed.
  3. Select how often the Monitor should retry the request before creating an incident if something is wrong.
  4. Interval: Select how often the monitor should be triggered.
  5. Select the severity of incidents triggered for Degraded monitor results.
  6. Select the severity of incidents triggered for Down monitor results.
  7. To finish your setup, click Save Monitor Settings.
You can always pause your monitor by activating the toggle at the top of the settings and saving.
Your Ping Monitor is now set up, configured and running.

​
Test your Monitor

We recommend testing your monitor after setting it up to see if it works as expected. After saving the monitor,
  1. Click “Execute” in the Last Response section.
  2. You’ll find the result below. Here, the monitor fails…

​
Incident creation from Monitor

A failed monitor will create an All Quiet incident, visible on your incidents overview.

​
How Ping Monitoring Status Handling Works

When Ping monitoring checks a target, the system compares the new status with the most recent one. If the status has changed (for example, from Up to Down or from Down to Up), the system processes the result fully. This includes updating records, sending notifications, and managing incidents. If the status remains the same (for example, Up to Up or Down to Down), the system stops early without further processing. This prevents duplicate alerts and avoids unnecessary incident creation. You can also see this in the Response Logs at the bottom of the Ping Monitor Settings page. The reponse logs will only show one entry per status change, but will update the timestamp based on the last ping for the given status. This behavior differs from other inbound integrations, which create a new incident whenever an alert is received if there is no open incident yet. Ping monitoring is designed to reduce noise by only acting when a real status change occurs.
If you close an incident manually and the status has not changed, the system will not create a new incident for the same issue. This helps you stay focused on real changes, reduces unnecessary noise, and keeps incident management cleaner.