HTTP Devices in Atera allow you to monitor the availability and content of websites or web-based services by checking a specific URL or IP for both connectivity and expected page content.
This feature is ideal for monitoring:
Internal or public websites
Web dashboards and login portals
Web services where a specific element or phrase must always appear (e.g., “Welcome”, “200 OK”, or company branding text)
Frequently Asked Questions
Q: What is an HTTP device and how does it work in Atera?
A: An HTTP device checks both the availability and content integrity of a website or web application.
A monitoring agent (a Windows device within the same network) regularly connects to the specified URL and looks for a static keyword pattern on the page.
If the connection fails, or the expected keyword is missing, Atera marks the device as Offline and generates an alert. This ensures you’re notified not only when a server is unreachable, but also when the page loads incorrectly or serves blank content.
Q: What do I need to set up HTTP monitoring in Atera?
A: To create an HTTP device, you’ll need:
A valid URL or IP address for the site you want to monitor.
A static keyword or pattern that reliably appears on the page during normal operation.
A Windows monitoring agent that can access the website (same LAN or VPN).
Once configured, Atera automatically checks the page every 2–5 minutes and updates the device’s status.
Q: How do I add an HTTP device in Atera?
A: To set up monitoring:
Navigate to New > Monitored device > HTTP.
Enter the device name and URL of the page to monitor.
Specify the static keyword pattern you expect to see.
Assign the device to a customer/site.
Choose a monitoring agent (must be online and have access to the site).
Click Add.
Monitoring begins immediately, and you can view results, uptime graphs, and alert history from the device console.
Q: What is the purpose of the static keyword pattern?
A: The static keyword (or pattern) acts as proof that the page is loading correctly.
If the keyword disappears or changes, Atera interprets it as a sign that the web content failed to load properly—even if the server is up and responding to HTTP requests.
For example:
Monitoring
example.comfor the keyword “Welcome to Example” ensures alerts trigger if the homepage loads blank or displays an error message instead.
Q: How often does Atera check HTTP devices?
A: The monitoring interval for HTTP devices typically ranges from 2 to 5 minutes, depending on agent configuration and network conditions.
While intervals are standardized, in practice checks may appear slightly more frequent due to local network or caching factors.
Q: What triggers an alert for HTTP devices?
A: An alert is generated in any of the following cases:
The page is unreachable (HTTP error, DNS failure, or timeout).
The static keyword pattern is missing or altered.
The monitoring agent cannot access the URL due to network or firewall restrictions.
Alerts appear in the HTTP device console and alongside other device alerts in your Atera Alerts view.
Q: Can HTTP monitoring detect content issues even when the server is online?
A: Yes. HTTP monitoring doesn’t just check connection status—it verifies page integrity.
Even if the server responds with a “200 OK” status, you’ll still receive an alert if the expected keyword pattern isn’t found.
This helps catch issues like broken web apps, login errors, or empty pages.
Q: Can HTTP devices monitor internal or non-public websites (e.g., behind a VPN)?
A: Yes, as long as the assigned monitoring agent has network access to the URL.
For example, if the site is accessible only through a VPN or local network, assign an agent that can reach that internal address.
If the agent cannot access the page, the monitoring check will fail or the device may not be added successfully.
Q: What should I check if I can’t add or monitor an HTTP device?
A:
Verify the URL is accessible from the monitoring agent’s network.
Make sure the static keyword actually appears on the page’s HTML.
Confirm no firewall, proxy, or filtering is blocking the agent’s access.
Ensure the agent is online and up to date.
Review the agent’s internal logs (
C:\Program Files\ATERA Networks\AteraAgent\Packages\AgentPackageInternalPoller\log.txt) if issues persist.
Q: Can HTTP device monitoring be automated or trigger scripts when alerts occur?
A: No. Currently, Atera does not support automatic scripts or remediation actions directly tied to HTTP device alerts.
However, you can monitor alert trends manually or integrate alert data into external automation workflows via the Atera API.
Q: Can I manage HTTP devices using the API?
A: Yes. The Atera API supports creation, management, and reporting of HTTP devices.
You can automate the addition of new monitored sites or bulk-manage existing ones, bypassing manual setup in the web interface.
Q: How can I edit or reassign the monitoring agent for an HTTP device?
A:
Open the HTTP device console.
Click Edit.
Select Change Monitoring Agent and choose another online agent in the same network.
Reassigning the monitoring agent is useful when the current one is offline or being replaced.
Q: Where can I view alerts, uptime graphs, and history for HTTP devices?
A:
Go to the HTTP device console to view its real-time status, alert logs, and uptime graph.
HTTP device alerts also appear alongside other alerts in your Atera Alerts view and can be included in reports.
Note: The uptime graph may display as “Down” whenever any open alert exists for that device, not only HTTP check failures.
Q: Can I monitor web servers by checking their ports instead of page content?
A: Yes. If you only need to verify whether a web server’s port (e.g., 80 or 443) is responding, use TCP Device Monitoring instead.
TCP monitoring checks basic network reachability, while HTTP devices verify both connectivity and content correctness.
Q: What alternatives exist if HTTP monitoring isn’t suitable?
A:
Use TCP devices to check port connectivity (80/443).
Use SNMP devices for more detailed network or service metrics.
Use Generic devices for ICMP (ping)-based reachability checks.
Each option provides different levels of depth depending on your monitoring needs.
Q: Is HTTP device monitoring included in my Atera plan?
A: Yes. HTTP device monitoring is included in your existing Atera subscription at no additional cost.
Summary of best practices
Choose stable keyword patterns that always appear on a correctly functioning page.
Assign a monitoring agent that can access the URL (LAN or VPN).
Verify your firewall and proxy allow outbound HTTP/HTTPS requests from the agent.
Use TCP monitoring for port availability and HTTP monitoring for full website validation.
Regularly review the HTTP device console to track performance and avoid false positives.
