Creating a useful website monitor in 360 Monitoring

Open your 360 Monitoring service and confirm the website allowance, check frequency and available notification features. Choose a stable public HTTPS URL that does not require a personal session. Avoid URLs containing secret tokens or customer information.

1. Go to the website-monitoring area and add a website. Give it a label that identifies the service and environment, such as a production storefront rather than an ambiguous domain nickname.
2. Enter the complete URL, including HTTPS and the intended hostname. Review redirect handling and choose the check type supported by your plan.
3. Select monitoring locations relevant to your visitors. Additional locations help distinguish a regional path problem from a wider outage.
4. Set an appropriate interval and threshold. Where supported, check for expected content or the absence of an error phrase so a misleading success page does not look healthy.
5. Configure the alert recipients and channels. Use an address or channel available even when the monitored website is down.
6. Save the monitor and review its first successful checks. Confirm the response, timing and certificate information match the intended site.

Use the supported notification test or a harmless controlled test monitor. Do not deliberately break a production site just to generate an alert. Confirm who receives the message, what information it contains and who owns the response.

DNS time, connection time, time to first byte and total response duration describe different stages. A single slow check can reflect the network path; a repeated change across locations deserves investigation. Synthetic checks are also different from real visitors' browser performance.

Compare the exact URL and monitoring location, then inspect firewall or CDN logs. The monitoring bot may be challenged while your browser has a valid session. Use the provider's current bot and address documentation for a narrow exception when justified, instead of disabling website security.

• Reducing false alerts and responding to 360 Monitoring incidents
• Adding server metrics to 360 Monitoring safely
• Checking whether a website outage affects everyone or one connection
• Improving website performance with LiteSpeed, NVMe and account optimisation
• Monitoring a public service port with 360 Monitoring

• 360 Monitoring
• 360 Websites
• 360 False Positives