Because the responsiveness for throughput-oriented
transactions is divided by the elapsed time, it can be very
sensitive to short-term performance variations for
transactions that take a short period of time. For example,
when downloading a very short file, a single dropped packet
could double or triple the total response time.
Further, for very short transactions, the fixed transaction
costs (handshake, setup time, authentication, round-trip time)
may dominate the total response time for the transaction.
This object controls the minimum number of seconds that an
throughput-based transaction must exceed before an exception
can be generated for it. If this object is set to zero, then
all throughput-based transactions are candidates for
exceptions.
Parsed from file rfc3729-Application-Performance-Measurement-APM.mib.txt
Company: ietf_rfcs
Module: APM-MIB
apmThroughputExceptionMinTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Because the responsiveness for throughput-oriented transactions is divided by the elapsed time, it can be very sensitive to short-term performance variations for transactions that take a short period of time. For example, when downloading a very short file, a single dropped packet could double or triple the total response time. Further, for very short transactions, the fixed transaction costs (handshake, setup time, authentication, round-trip time) may dominate the total response time for the transaction. This object controls the minimum number of seconds that an throughput-based transaction must exceed before an exception can be generated for it. If this object is set to zero, then all throughput-based transactions are candidates for exceptions." DEFVAL { 10 } ::= { apm 12 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.16.23.0 | apmNotifications | 2 | 2 | None |
1.3.6.1.2.1.16.23.1 | apmMibObjects, apmAppDirectoryTable | 15 | 106 | The APM MIB directory of applications and application verbs. Some of these applications are registered in the RMON2 protocol dire… |
1.3.6.1.2.1.16.23.2 | apmConformance, apmBucketBoundaryLastChange | 2 | 9 | The value of sysUpTime the last time that any bucket boundary in any appDirectyEntry was changed. This object can help to determi… |
1.3.6.1.2.1.16.23.3 | apmHttpFilterTable | 1 | 9 | A table that creates virtual applications which measure the performance of certain web pages or sets of web pages. Note that when… |
1.3.6.1.2.1.16.23.4 | apmHttpIgnoreUnregisteredURLs | 0 | 0 | When true, this agent will only monitor URLs registered in the apmHttpFilterTable. This will be used in environments that wish to… |
1.3.6.1.2.1.16.23.5 | apmHttp4xxIsFailure | 0 | 0 | When true, this agent will recognize HTTP errors in the range of 400 through 409 and will treat them as unavailable transactions.… |
1.3.6.1.2.1.16.23.6 | apmUserDefinedAppTable | 1 | 4 | A table that advertises user-defined applications that the agent is measuring. Note that when entries exist in this table some tra… |
1.3.6.1.2.1.16.23.7 | apmNameTable | 1 | 7 | A client machine may have multiple addresses during a period of monitoring. The apmNameTable assigns a long-lived identifier to a… |
1.3.6.1.2.1.16.23.8 | apmReportControlTable | 1 | 15 | Parameters that control the creation of a set of reports that aggregate application performance. |
1.3.6.1.2.1.16.23.9 | apmReportTable | 1 | 18 | The data resulting from aggregated APM reports. Consult the definition of apmReportControlAggregationType for the definition of t… |
1.3.6.1.2.1.16.23.10 | apmCurrentTable | 1 | 8 | This table contains all transactions that have been started but have not yet finished. |
1.3.6.1.2.1.16.23.11 | apmExceptionTable | 1 | 9 | This table creates filters so that a management station can get immediate notification of a transaction that has had poor availab… |
1.3.6.1.2.1.16.23.13 | apmNotifications | 2 | 2 | None |