Supported URLs
A monitor accepts a public HTTP or HTTPS URL. Use the complete address, including its scheme. HTTPS uses port 443 and HTTP uses port 80. Non-default ports are rejected. A path and query string are supported, but do not put passwords, access tokens or personal information in a URL: the full URL is saved and included in monitoring emails.
The URL cannot include a username, password or fragment. Hostnames such as localhost, names ending in .localhost or .local, and private or reserved IP addresses are rejected. A hostname is also rejected if any address returned by the worker's DNS lookup is private or reserved. These checks run again during monitoring and for every redirect target.
There is no support for internal endpoints, custom request headers, Basic authentication, bearer tokens, POST requests or request bodies. The worker sends an unauthenticated HTTP GET request. Choose a public health endpoint that exposes only the information you intend to publish.
Create a monitor
On the dashboard, provide a name of 1 to 100 characters and a URL of up to 2,048 characters, then select Add monitor. The form reports an error if the address is unsupported or cannot be resolved to an accepted public address during creation.
An account can hold 10 monitors in total. Paused monitors count toward the limit. Delete a monitor you no longer need before adding another when the limit has been reached.
A newly created monitor starts as active and pending. The worker takes the first due check asynchronously. Read getting started for the full setup flow.
Edit a name or URL
Open a monitor and select Edit. Update the name, the URL or both, then select Save. Changing only the name keeps the monitoring state and history.
Changing the URL resets the current state to pending and schedules a new check. It also resets stored certificate metadata and closes any open incident without a recovery email. Existing check results and incidents stay attached to the monitor, so its history can contain observations from both addresses. Create a separate monitor when you need an independent history for a different service.
Pause and resume
Select Pause on a monitor detail page to stop scheduled checks. Pausing resets its current state, closes an open incident without a recovery email and stops the currently observed interval at the pause time. It does not delete existing history or automatically retract an email already queued.
Select Resume to make the monitor active again. Resuming resets its state to pending and makes it due for a new check. Paused time is excluded from observed uptime. UpBastion has no scheduled maintenance windows; pausing and resuming are manual actions.
Delete a monitor
Select Delete on the monitor detail page and confirm the browser prompt. Deletion removes the monitor, its check results, incidents and associated queued notifications from the application database. The application has no undo or recycle bin for this action.
Account deletion is a separate action. See account and data and the privacy policy for its scope.
Choose a meaningful endpoint
A homepage checks the publicly reachable website. A public health endpoint can check an application or a dependency when you build that behavior into the endpoint. UpBastion evaluates the returned status code and does not verify the endpoint's JSON fields.
Use Choose the right URLs to monitor to plan your monitors. Troubleshooting covers rejected addresses and checks blocked by firewalls.