Setup time: 2 Min
Set up our All Quiet HTTP Monitor to ping your website 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 Website / HTTP Monitor

Sign in to your All Quiet account.

​
Create Integration

  1. Click on the Integrations > Inbound tab.
  2. Click on Create New Integration.

​
Select Website / HTTP Monitor as the integration’s type

  1. Enter a display name for your Monitor, e.g. HTTP Monitor.
  2. Select a team.
  3. Select Website / HTTP Monitor as the integration’s type.
  4. Click Create Inbound Integration.

​
2. Configure your Website / HTTP Monitor

Once you’ve set up the “Website / HTTP Monitor”, it’s time to configure it. This can be done on the the integration’s page.
  1. Select your Method (HEAD, GET, POST, PUT, DELETE or PATCH) and enter the URL you want to Monitor. If you want to monitor different URLs, simply set up several monitors.
  2. Optionally, you can add Headers in JSON format.
  3. Select your Authentification method (None, Basic or Bearer).
  4. Select the Timeout, the duration after which the monitor should time out and considered to be failed.
  5. You may add the the number of days after which your SSL certificate expires. By adding the days until the expiration, your can make sure to either downgrade the monitor or let it fail before the expiration day. This ensures you won’t miss the expiration.
  6. Interval: Select how often the monitor should be triggered.
  7. Select the severity of incidents triggered for Degraded monitor results.
  8. Select the severity of incidents triggered for Down monitor results.
  9. To finish your setup, click Save Monitor Settings.
  10. You can always pause your monitor by checking the box at the top of the settings.
Your 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 “Test Monitor”.
  2. You’ll find the result below.

​
Outbound IP Addresses

The outbound IP addresses used for HTTP monitoring are dynamic and can be retrieved from the following endpoints: While these IP addresses are generally stable, we do not guarantee their persistence. It’s recommended to regularly check these endpoints for any changes.

​
Incident creation from Monitor

If the monitor fails, you will see that in the results… …as well as in your incidents overview. An All Quiet incident is created from your HTTP Monitor.

​
How HTTP Monitoring Status Handling Works

When HTTP 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. This behavior differs from other inbound integrations, which create a new incident whenever an alert is received if there is no open incident yet. HTTP 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.