LOGGING-MIB :: agentLogMessagesReceived

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LOGGING-MIB › agentLogMessagesReceived

agentLogMessagesReceived

Module: LOGGING-MIB

OID (symbolic): LOGGING-MIB::agentLogMessagesReceived

OID (numeric): 1.3.6.1.4.1.7244.2.14.2.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of messages received by the log process. This includes messages that are dropped or ignored.

What is agentLogMessagesReceived?

This counter tracks the total number of messages received by the logging process, including ones later dropped or ignored. It's the top-level throughput figure admins compare against the dropped-message counter to gauge logging subsystem health.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7244.2.14.2.1
snmpwalk -v2c -c public <target> LOGGING-MIB::agentLogMessagesReceived

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.7244.2.14.2.1.1
snmpget -v2c -c public <target> LOGGING-MIB::agentLogMessagesReceived.1

Start monitoring Quanta network switch (syslog-style event log) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LOGGING-MIB::agentLogMessagesReceived OID value, configure state conditions and alerts, and monitor any Quanta network switch (syslog-style event log) from a single console.

How to Use in IPNetwork Monitor

Select a Quanta network switch (syslog-style event log) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type agentLogMessagesReceived into the Find box to locate it in the OID tree, then select it and click OK. The number of messages received by the log process. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.7244quantaQUANTA-SWITCH-MIB
1.3.6.1.4.1.7244.2switchQUANTA-SWITCH-MIB
Numeric OIDNameModule
1.3.6.1.4.1.7244.2.14loggingLOGGING-MIB
1.3.6.1.4.1.7244.2.14.2agentLogStatisticsGroupLOGGING-MIB
1.3.6.1.4.1.7244.2.14.2.1agentLogMessagesReceivedLOGGING-MIB