SNMP Monitoring Templates
An SNMP monitoring template defines which OIDs INFRAX collects from a device, how values are transformed, and which thresholds trigger alerts. SNMP connection settings are configured separately under Parameters -> SNMP, while the template itself is selected in the Monitoring template block.
What a monitoring template does
A template describes monitoring for a specific SNMP device type. It ties together the vendor, device class, device type, device model, and the rule set INFRAX uses to collect data.
The template stores the Vendor (PEN code), Device class, Device type, and Device model. That makes it easier to match the template to the right hardware.
Rules define which OIDs to poll, how to compute values from formulas, and how to present the result in the table.
Metrics can have warning and critical thresholds, plus a check formula: current value, average of three values, or each of the last three values.
One template can be assigned to many identical nodes, so you do not have to repeat the same setup for every device.
How to open the template page
Template management is available from the SNMP administration area and from node settings.
Through application settings
- Open Settings
- Go to Monitoring
- Open SNMP
- Select the Monitoring templates tab
The same page also has a References tab, which opens the OID and CMDB references used while building templates.
Through node settings
- Open a network node
- Go to Parameters -> SNMP
- Use the Monitoring template block to select or create a template
Template list
The Monitoring templates tab shows all templates in a table. You can filter it, sort it, and open a template by clicking a row.
What the list shows
- ID - the template identifier
- Vendor - the PEN code and, if available, the vendor name
- Device type - the human-readable device type
- Device model - the model the template is meant for
How to use the list
- Click Add to create a new template
- Click a template row to open the editor
- Use the table filters to find the template you need faster
Template editor
The template editor opens in a modal window and uses the same labels as the application. The available tabs match the current UI.
| Tab | What it does |
|---|---|
| Parameters | Set the vendor, class, type, and model. This tab also contains Download, Upload, Duplicate, and Delete. |
| Collection rules | The main table of metrics, tables, and collection rules. |
| Network nodes | The nodes that use this template, with actions to add or remove the assignment. |
| Change history | Template snapshots, change review, and restore actions. |
| JSON | Visible only in debug mode and shows the raw JSONB content of the template field. |
Download and Upload work with a JSON file of the template. This is useful for moving templates between installations or making structural changes through import.
Metric collection rules
Collection rules define how INFRAX gets data from the device. In the current editor, rules are grouped by module class and module, and each group can contain individual metrics.
Rule structure
| Field | Meaning |
|---|---|
| Metric | What is being measured; selected from the CMDB reference. |
| Collection type | SNMP for a direct OID poll or Code (formula) for a calculated value. |
| OID | The SNMP parameter identifier, for example 1.3.6.1.2.1.2.2.1.10. |
| Transform | How the result is processed before saving: No transform, Code (formula), or Mapping. |
| Unit | The unit label, for example bytes, percent, or degree. |
Adding a group and a rule
- On the Collection rules tab, click Add table
- Set the Module class, Module, and, if needed, the Table label (table_key)
- Inside the group, click Add rule
- Fill in the Metric, Collection type, OID, Transform, and other fields
- Save the template
If you do not know the right OID, open SNMP References and find it in the OID browser. That page also contains vendor OIDs and MIB descriptions.
Threshold rules
Each metric in a template can have alert rules. They turn a threshold breach into a warning or a critical state.
| Parameter | Choose |
|---|---|
| Severity | Warning, Critical, or Recovery |
| Formula | Current, Average (3), or Each (3) |
| Condition | Compare the value to the threshold: greater than, less than, equal to, and other operators. |
| Value | The threshold that triggers the rule. |
Example
- Warning - current value is above 70%
- Critical - each of the last three readings is above 90%
This works well for CPU load, temperature, and other metrics where both short spikes and sustained breaches matter.
Assigning a template to a node
A template is assigned to a specific node and does not inherit from the parent folder. That is intentional, because devices inside the same folder can use different templates.
Monitoring template block
The Parameters -> SNMP view provides these actions:
- Select - open the template list and assign a template to the node
- Clear - remove the template assignment
- Save template - write the node changes
- Edit template - open the current template editor
- Test metric collection - validate the template without writing data to the database
- Configure with AI assistant - create or fix a template from the node's SNMP snapshot
Selecting a template on the node does not modify the template itself. If you need to change rule structure, open the template editor separately and save the changes there.
Test metric collection
Test collection is launched from the Monitoring template block in node settings. It checks which rules match on the real device, but it does not save anything to the database.
What the result shows
- How many rules matched and how many values were collected
- Collection errors if an OID is unavailable or a formula fails
- Warnings when the device responses look unexpected
- A detailed breakdown by tables, metrics, and rules
Test collection is a trial run. It does not create monitoring history and does not affect the current node data.
AI assistant
The AI assistant can create a new template or fix an existing one from the node's SNMP snapshot. INFRAX Cloud connectivity is required.
How it works
- In the Monitoring template block, click Configure with AI assistant
- Choose Create a new template or Fix the current template
- If needed, add a prompt note and upload an additional MIB ZIP archive
- Start generation and wait for the stages to finish
| Stage | What the system does |
|---|---|
| SNMP data collection | The system captures a snapshot of the available OIDs on the device. |
| Mapping to MIB descriptions | The collected OIDs are matched against MIB descriptions and uploaded archives. |
| AI template generation | The AI builds the set of metrics, tables, and formulas. |
| Validation and optimization | The system checks correctness and simplifies the template when needed. |
| Test metric collection | The new template is verified against the device. |
| Template apply | The template is saved and can be assigned to the node. |
The result window lets you Test the template, Apply it, Choose for similar devices, or Download template JSON.
JSON import and export
The Parameters tab includes Download and Upload. They work with a template JSON file and are useful for moving templates between installations or making structural edits through import.
When this is useful
- Copying a working template to another environment
- Making bulk changes to the template through JSON
- Keeping a backup before experimenting with rules
When debug mode is enabled, the editor shows a JSON tab with the raw JSONB content of the template field. It is useful for checking data after import or save.
Change history
The template keeps a change history. On the Change history tab, you can review snapshots, inspect their contents, and restore a previous version.
What the history provides
- Date and time of the save
- The user who made the change
- A comment and the number of metrics
- Snapshot review and restore from history
Before restore, the current version is stored in history, but the active template edits will be replaced by the selected snapshot.