APM-MIB :: apmAppDirResponsivenessType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAPM-MIBapmAppDirResponsivenessType

apmAppDirResponsivenessType

Module: APM-MIB

OID (symbolic): APM-MIB::apmAppDirResponsivenessType

OID (numeric): 1.3.6.1.2.1.16.23.1.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: not-accessible

Description: This object describes and configures the agent's support for application performance measurement for this application. There are 3 types of measurements for different types of applications:

Transaction-Oriented applications have a fairly constant workload to perform for all transactions. The responsiveness metric for transaction-oriented applications is application response time (from first request to final delivery of service) and is measured in milliseconds. This is commonly referred to as end-user response time.

Throughput-Oriented applications have widely varying workloads based on the nature of the client request. In particular, throughput-oriented applications vary widely in the amount of data that must be transported to satisfy the request. The responsiveness metric for throughput-oriented applications is kilobits per second.

Streaming-Oriented applications deliver data at a constant metered rate of speed regardless of the responsiveness of the networking and computing infrastructure. This constant rate of speed is generally specified to be below (sometimes well below) the nominal capability of the infrastructure. However, when the infrastructures cannot deliver data at this speed, interruption of service or degradation of service can result. The responsiveness metric for streaming-oriented applications is the ratio of time that the service is degraded or interrupted to the total service time. This metric is measured in parts per million.

Note that for some applications, measuring more than one responsiveness type may be interesting. For agents that wish

to support more than one measurement for a application, they will populate this table with multiple entries for that application, one for each type.

OID Breakdown

Upper-level ancestors (7 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.16rmonLBHUB-BOOM-MIB
Numeric OIDNameModule
1.3.6.1.2.1.16.23apmAPM-MIB
1.3.6.1.2.1.16.23.1apmMibObjectsAPM-MIB
1.3.6.1.2.1.16.23.1.1apmAppDirTableAPM-MIB
1.3.6.1.2.1.16.23.1.1.1apmAppDirEntryAPM-MIB
1.3.6.1.2.1.16.23.1.1.1.2apmAppDirResponsivenessTypeAPM-MIB