Bulk-generate OIDs with AI Copilot

You can use the AI-generated OIDs button on the SNMP device page to discover and add multiple OIDs at once, with monitoring conditions, severities, and thresholds pre-suggested by AI Copilot.

There are two modes to choose from:

• AI Copilot suggestions — AI Copilot uses the SNMP device model to suggest the most relevant OIDs.
• AI Copilot suggestions + MIB file — Add a MIB file (by URL or upload) on top of the device model for more accurate, device-specific results.

To bulk-generate OIDs:

1. From Devices (on the sidebar), open the relevant SNMP device. The SNMP Device page appears.
2. Click AI-generated OIDs. The Discover OIDs with AI Copilot window appears.

3. Select a mode:

•  Option A — AI Copilot suggestions: AI Copilot automatically generates suggested OIDs based on the device model. No further input needed. 

• Option B — AI Copilot suggestions + MIB file Either:

  • Paste a MIB URL into the Enter MIB URL field, or
  • Click Upload MIB file and select a .mib (or .txt) file from your device.

  Then click Generate.

Note: A MIB is a text file from the device vendor that documents the SNMP metrics available on that device. Adding it gives AI Copilot vendor-specific context, producing more accurate OID suggestions than the device model alone.

4. Review the generated OIDs. For each row, AI Copilot pre-populates the OID, Description, and where applicable a suggested Condition Type, Condition Value, and Severity. 
5. Choose which OIDs to add:
   • To pull current values for an OID, check the box in the Show values column.
   • To monitor an OID and trigger alerts based on the suggested condition, check the box in the Monitor column.
   • To select all rows at once, use the checkboxes in the Show values and Monitor column headers.
6. Click Add OIDs (bottom right). The selected OIDs are added to the device. Monitored OIDs immediately begin generating alerts based on their conditions.

Add OIDs 

Add OIDs (Object Identifiers) for the specific parameters you want to monitor on your SNMP device. OID values provide the status of the specific OID on the device. For example, you can use an OID for system uptime to check how long a device has been running or an OID for ink levels to monitor your printers. These values update every 2 minutes. Please note that the update interval for OID values cannot be changed. When adding an OID here, you will see the number of the OID displayed along with its current value on the device.

Note: OIDs can be added in three different ways — bulk-generated with AI Copilot, AI-generated one at a time, or added manually.

To add an OID value:

1. From Devices, click the relevant SNMP device.

The SNMP Device page appears.

2. Click Add OID.

The Add OID value window appears.

2. Select from:

• Copilot: OID generator: Type what you need in plain language (e.g., "ink level"). Then click Generate to see the OID, its value, and description.
• Manually discover OIDs: Enter the OID value (full or partial). Then click Discover.

3. Click Add OID. 

The OID value is added. 

Note: Parent and leaf OIDs (or any MIB objects for that matter) are logically organized in a hierarchy called a tree structure. A parent OID branches off into leaf OIDs. A leaf OID is the actual MIB object and has no children. Only leaf OIDs return MIB values from monitored devices. When you enter a parent OID, you will see a list of all the leaf OIDs under it.

The Monitored OIDs section is where you can set up alert conditions to receive alerts when the Condition Value is matched.

Set up SNMP alert conditions

To set up conditions for SNMP alerts:

1. Click Add OID, under Monitored OIDs.

The Add OID Monitor window appears.

2. Select from:

• AI Copilot: OID generator: Type what you need in plain language (e.g., "ink level"). Then click Generate to see the OID, it's value, and description.
• Manually discover OIDs: Enter the OID value (full or partial). Then click Discover.

3. Click Add monitor OID.

The OID value is added. 

3. Fill in the fields to set up the conditions (severity, condition type, and value) under which you want the alert to be triggered. Then click Add OID Monitor.

SNMP alerts will appear when your specified conditions are matched. If you select the parent OID, an alert will appear if the value of any of the leaf OIDs under it matches the condition.

Note:

• Deleted SNMP alerts will not regenerate until the original issue that triggered the alert has been resolved.
• The Monitor History graph will display the activity as 'Down' if an alert (of any type) is open for the monitored device. 

Automatic Monitoring

Atera automatically monitors some specific parameters on Linux-based devices as well as printers.

Linux-Based Device Monitoring: Atera automatically monitors OIDs on Linux-based devices (routers, firewalls, PCs etc.) for the following parameters:

• 5-minute load average (laLoad, laConfig, laErrorFlag)
• Available swap memory (memAvailSwap, memMinimumSwap, memSwapError )
• Available disk space (dskMinPercent, dskPercent, dskErrorFlag)

The actual OIDs for these parameters:

1.3.6.1.4.1.2021.10.1.3.2: 5 minutes load average
1.3.6.1.4.1.2021.10.1.4.2: 5 minutes load average threshold
1.3.6.1.4.1.2021.10.1.100.2: Flag set to 1 when 5 minutes load average crosses the threshold.
1.3.6.1.4.1.2021.4.4.0: Available or unused swap space (KB)
1.3.6.1.4.1.2021.4.12.0: Available swap space threshold (KB)
1.3.6.1.4.1.2021.4.100.0: Flag set to 1 when available swap space goes below threshold.
1.3.6.1.4.1.2021.9.1.9.1: Used disk space percentage.
1.3.6.1.4.1.2021.9.1.5.1: Free disk space percentage threshold.
1.3.6.1.4.1.2021.9.1.100.1: Flag set to 1 when disk free space goes below threshold.
1.3.6.1.4.1.2021.9.1.9.2: Disk #2 used space percentage.
1.3.6.1.4.1.2021.9.1.5.2: Disk #2 free space percentage threshold.
1.3.6.1.4.1.2021.9.1.100.2: Flag set to 1 when disk #2 free space goes below threshold.

The OIDs and factory-set thresholds are pulled from the device itself. These OIDs appear within the device console, and will generate Atera alerts. If you don’t wish to receive these alerts, the OIDs can be deleted from the device console.

For each parameter, we display the factory threshold, current value, and a flag that the device sets to 1 if the current value crosses the threshold (an Atera alert is generated when that flag is set to 1).

If you’re interested, you can view a full list of OIDs for Linux-based devices.

Note: The automatic OID monitoring feature appears on Linux-based devices added to Atera after July 27, 2020 (the feature release date). If you would like to add these OIDs to SNMP devices added prior to this date, you can manually import the OIDs from within the device console.

Printer Monitoring: Atera automatically extracts carefully selected alerts from the alerts table of the Printer MIB, and they are displayed alongside other alerts in Atera. The triggers causing alerts to display within Atera include:

These specific alerts are extracted and displayed within Atera automatically, and can't be changed. As on other alerts, tickets can easily be created or assigned to proactively handle the issues. 

Note: If you don't wish for these alerts to be triggered automatically when adding the printer as an SNMP device in Atera, you can select Type Other.