Generic devices in Atera allow you to monitor basic network availability of assets that do not support SNMP or Atera agent installation.

Monitoring is performed through ICMP (ping) requests sent from a designated Windows agent within the same network.

This method provides simple online/offline visibility for devices such as switches, printers, UPS units, and other non-SNMP hardware, without requiring additional configuration.

Frequently Asked Questions FAQ

Q: What is a generic device in Atera?

A: A generic device is a network-connected asset monitored via ICMP ping rather than an installed agent or SNMP configuration.
This type of monitoring is ideal for simple devices that don’t support agent deployment or SNMP polling — such as printers, switches, UPS units, or IP-based appliances.

Generic devices allow you to maintain visibility into basic network connectivity (online/offline status) without complex setup.

• Monitor Non-SNMP Switches, Printers, UPS and More (Add a Generic Device)

Q: How does generic device monitoring work?

A: The assigned Windows monitoring agent (an endpoint with the Atera agent installed) performs ping checks every 120 seconds.

• If the monitored device responds to the ping, it is shown as Online.
• If no response is received, it is marked Offline, and Atera generates an alert.

The monitoring agent must be online and able to reach the device via the network for accurate status reporting.

Q: How do I add a generic device in Atera?

A:

1. Navigate to New > Monitored device > Generic.
2. Fill in the required details:
   • Device name
   • Customer and site
   • Monitoring agent (must be online and in the same network)
   • IP address or hostname
3. Click Add to begin monitoring.

Atera will automatically start pinging the device every two minutes, and you can view its current status and alert history in the device console.

Q: What data is collected for a generic device?

A: Monitoring is limited to basic connectivity (online/offline) based on ping responses.
No hardware or software inventory data, SNMP metrics, or performance information is collected for generic devices.

Q: What are typical use cases for generic devices?

A:
Generic devices are best suited for simple assets that don’t support advanced monitoring. Common examples include:

• Network switches and routers without SNMP enabled
• Printers or copiers
• UPS units and power controllers
• IoT appliances or non-agent network devices

They are used primarily for ensuring uptime and basic reachability.

Q: Why might a generic device show as offline when it’s actually running?

A: Common causes of false offline/online readings include:

• Firewalls or ACLs blocking ICMP ping requests.
• Network instability or packet loss between the monitoring agent and the device.
• The monitoring agent being offline, outdated, or disconnected.

To troubleshoot, confirm that:

• The agent can ping the device manually.
• ICMP is allowed through the network path.
• The agent device is online and functioning correctly.
   
• Firewall settings for Atera

Q: Can I monitor assets that don’t have an IP address?

A: No. Generic devices require a valid IP address or hostname to perform ping checks.
Non-networked assets (such as standalone hardware) can be added as manual or custom assets through CSV import or asset management.

Q: Can I bulk import or export generic devices?

A:

• Bulk CSV import of generic devices is not currently supported.
• However, you can use the Atera API to create or manage multiple generic devices programmatically.
• For exports, analytical reporting (available in higher-tier plans) includes generic device data.
   
• API
• Atera's analytical reports

Q: Can I change or reassign the monitoring agent for a generic device?

A: Yes. From the device console, click Edit → Change Monitoring Agent to assign another Windows agent on the same network.
This is particularly useful if the original monitoring agent is offline or being replaced.

Q: What kind of alerts do generic devices generate?

A: Generic devices generate availability alerts when they fail to respond to ping requests.
These alerts appear:

• In the device console, showing online/offline transitions.
• In the main Alerts dashboard alongside all other device alerts.

Alerts can also automatically create tickets within your Atera ticketing system, depending on your automation and workflow configuration.

Q: Are generic devices included in asset or auditor reports?

A:

• By default, only agent-installed devices appear in standard asset and auditor reports.
• Generic devices are included in analytical reports (available on higher plans).
• If you require full reporting coverage for generic devices, ensure your subscription tier supports advanced reporting.
   

Q: Can I trigger automation or scripts for generic device alerts?

A: No. Atera does not currently support auto-remediation or scripts triggered directly from generic device alerts.
However, alert notifications can still generate tickets or be used in custom automation workflows via the API.

Q: What are the limitations of generic device monitoring?

A:

• Limited to ICMP ping status (no SNMP, agent metrics, or performance data).
• Requires a monitoring agent in the same network.
• Cannot monitor non-IP or offline network assets.
• Bulk imports must be handled through the API (not CSV).

For more advanced monitoring, use SNMP for network devices or agent-installed endpoints for full metrics and automation.

Q: What are best practices for using generic devices?

A:

• Assign a stable, online monitoring agent in the same network as the device.
• Ensure ICMP traffic is allowed through firewalls.
• Use generic devices only for assets that cannot be monitored with SNMP or an Atera agent.
• Periodically verify device reachability and alert accuracy.
• Review reporting options to include generic devices where relevant.
   

Q: Is generic device monitoring included in my Atera subscription?

A: Yes. Generic device monitoring is included at no additional cost in all Atera subscription plans.