শেয়ার

Getting started

AllInOneMonitor watches your websites, APIs, SSL certificates, domains, DNS, ports and servers around the clock and tells you the moment something breaks. This page takes you from a new account to your first alert and a public status page in about ten minutes.

1. Create your account

Open Start free (/register), enter your name, e-mail address and a password of at least 8 characters. If the site owner requires e-mail verification you receive a link that is valid for 24 hours; open it, then sign in at /login.

Every account gets its own organisation (named after you). Monitors, servers, alert channels, status pages and team members all belong to an organisation, and you can be a member of several (your own and the ones you are invited to). The organisation switcher is at the top of the left sidebar.

Signing in from a new address sends you a "new device" e-mail. You can turn two-factor authentication on under Settings → Security (authenticator app or e-mail code, plus backup codes).

2. Add your first monitor

Go to Monitors → Add monitor.

  1. Pick the type. For a website choose HTTP(S); see Monitors for every type.
  2. Give it a name and the target, for example https://www.example.com.
  3. Choose the check interval. The intervals you can pick depend on your plan (the free plan starts at 5 minutes; paid plans go down to 30 seconds).
  4. Leave Confirmations at 2: a failure must be seen twice in a row (or from two locations) before the monitor is declared down. That filters out single network hiccups.
  5. Save. The first check runs within a minute; the status changes from Pending to Up or Down.

The monitor page shows the current status, response time, the uptime for 24 hours / 7 / 30 / 90 / 365 days, a response-time chart, the last results per location and the incidents.

Targets must be public addresses. Private, loopback, link-local and cloud-metadata addresses are refused unless the administrator of the installation allows private targets.

3. Set up an alert channel

By default the owner of the monitor receives an e-mail when it goes down and when it recovers (you can turn that off under Settings → Notifications). For anything else go to Alert channels → Add channel:

  • E-mail to any address
  • Telegram bot, Discord, Slack and Microsoft Teams webhooks
  • SMS and WhatsApp (when the site owner has configured a provider and your plan includes them)
  • Mobile push through Pushover, ntfy or Gotify
  • A generic webhook to your own code

Mark a channel as default and every monitor without its own channel list uses it. Use the Test button to send a sample message. Details for each channel are in Alerts.

4. Publish a status page

Status pages → New status page creates a page at /status/<slug>. Add the monitors (and servers) you want to show as components, give it your logo and colour, and share the link. Visitors can subscribe by e-mail to incident updates. Paid plans add password protection, your own domain and white-labelling. See Status pages.

5. What happens when something breaks

  1. A check fails. The monitor stays Up until the failure is confirmed (the number of confirmations you chose, or that many locations on multi-location plans).
  2. The monitor turns Down, an incident opens automatically, an alert is written to your bell and every mapped channel is notified.
  3. When the next check passes the monitor is Up again, the incident is resolved with its duration and a recovery message goes out.
  4. Everything is kept: results per location, incidents with their timeline, the notification log with the answer of every provider.

Acknowledge an incident on its page to stop escalation; add public updates and they appear on the status page and go to its subscribers. See Incidents.

Next steps

  • Install the read-only server agent with one command to see CPU, memory, disks, services and more: Servers.
  • Connect cPanel/WHM, DirectAdmin, Plesk or Cloudflare: Integrations.
  • Invite colleagues with roles: Team.
  • Automate with the REST API and webhooks: API.
  • Schedule weekly reports by e-mail: Reports.

What's new in 2.1

  • Transaction and browser monitors: multi-step HTTP journeys and real-browser page loads with paint and layout-shift timings, plus the Performance page: Synthetic monitoring.
  • Database and mail server monitors: MySQL/MariaDB, PostgreSQL, MongoDB, Redis, Memcached, SMTP, IMAP, POP3 and FTP: Database and mail server monitors.
  • Diagnostics: run ping, traceroute, MTR, DNS and HTTP timing from several locations at once, and pick locations by region or let them be spread automatically: Diagnostics and location pools.
  • Insights and Topology: anomalies, flapping, grouped alerts, dependencies, root-cause suggestions and an optional AI summary: Insights and intelligence.
  • Server agent 2.1: databases and caches, web server and PHP-FPM status, mail queue, JetBackup, Kubernetes, IIS and SQL Server, signed self-update: Servers.
  • Twelve new integrations, from CyberPanel and aaPanel to AWS, Google Cloud, Azure and Kubernetes: Integrations.
  • Agencies and resellers: client organisations, white label, shared client reports and reseller billing: Agencies and resellers.
  • Phone and browser push: install the web app, turn on push under Devices & push, and use the Browser & app push alert channel: Mobile app and push.

The full list is in the Changelog.

এই পেজটি কি সহায়ক ছিল?

একটি ক্লিক আমাদের এই ডকস উন্নত করতে সাহায্য করে।

এই পেজ শেয়ার করুনসাধারণ লিংক - কোনো ট্র্যাকার নেই, ক্লিক না করা পর্যন্ত কিছু লোড হয় না।