Plugin: go.d.plugin Module: snmp
Monitor Kyocera Printer (printer) with Netdata over SNMP. Netdata recognizes the device automatically by its sysObjectID (recognized across 1 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration.
Netdata’s SNMP collector matches the device to the kyocera-printer.yaml profile via sysObjectID/sysDescr, then polls the OIDs it declares.
This integration is supported on all platforms.
This integration supports multiple instances configured side-by-side.
Auto-detected as Kyocera Printer via sysObjectID/sysDescr.
The default configuration for this integration does not impose any limits.
The default configuration for this integration is not expected to impose a significant performance impact on the system.
You can configure the snmp collector in two ways:
| Method | Best for | How to |
|---|---|---|
| UI | Fast setup without editing files | Go to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job. |
| File | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit go.d/snmp.conf and add a job. |
Important
UI configuration requires paid Netdata Cloud plan.
SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site’s SNMP hub.
Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.
Configure the snmp collector from the Netdata web interface:
The configuration file name for this integration is go.d/snmp.conf.
The file format is YAML. Generally, the structure is:
update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2
You can edit the configuration file using the edit-config script from the
Netdata config directory.
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
There are no configuration examples.
On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this Kyocera Printer profile adds the metrics below. Each is collected only where the device exposes the matching OID — inclusion means the profile requests it; availability depends on the device model and software.
5 metrics in 3 groups; each row is a chart context usable in alerts.
| Group | Metrics |
|---|---|
| System / Alert | 1 |
| System / Memory | 3 |
| System / Uptime | 1 |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_kcprtAlertStateCode | {code} | per kcprt_alert_state_display_index, kcprt_alert_state_display | Alert state code |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_kcprtMemoryDeviceStatus | {status} | per kcprt_memory_device_index, kcprt_memory_device_location, kcprt_memory_device_type | Current status of this device |
snmp.device_prof_kcprtMemoryDeviceTotalSize | By | per kcprt_memory_device_index, kcprt_memory_device_location, kcprt_memory_device_type | Total size of the memory device |
snmp.device_prof_kcprtMemoryDeviceUsedSize | By | per kcprt_memory_device_index, kcprt_memory_device_location, kcprt_memory_device_type | Used size of the memory device |
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_systemUptime | s | device | Time since the system was last rebooted or powered on. |
There are no alerts configured by default for this integration.
Want a personalised demo of Netdata for your use case?