When true, this agent will recognize HTTP errors in the range
of 400 through 409 and will treat them as unavailable
transactions. When false or when this object isn't supported,
they will be treated as successful transactions.
This object allows such error pages to be tracked at the
possible expense of having user typo's treated as poor service
on the part of the web server.
This object affects all reports and exceptions generated by
this agent. Accordingly, modification of this object should be
performed by a manager acting in the role of administrator. In
particular, management software should not require or enforce
particular configuration of this object - it should reflect
the preferences of the site administrator, not the software
author.
Parsed from file rfc3729-Application-Performance-Measurement-APM.mib.txt
Company: ietf_rfcs
Module: APM-MIB
apmHttp4xxIsFailure OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "When true, this agent will recognize HTTP errors in the range of 400 through 409 and will treat them as unavailable transactions. When false or when this object isn't supported, they will be treated as successful transactions. This object allows such error pages to be tracked at the possible expense of having user typo's treated as poor service on the part of the web server. This object affects all reports and exceptions generated by this agent. Accordingly, modification of this object should be performed by a manager acting in the role of administrator. In particular, management software should not require or enforce particular configuration of this object - it should reflect the preferences of the site administrator, not the software author." ::= { apm 5 }
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.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.12 | apmThroughputExceptionMinTime | 0 | 0 | Because the responsiveness for throughput-oriented transactions is divided by the elapsed time, it can be very sensitive to short… |
1.3.6.1.2.1.16.23.13 | apmNotifications | 2 | 2 | None |