APM-MIB DEFINITIONS ::= BEGIN

IMPORTS

    MODULE-IDENTITY, OBJECT-TYPE,

    NOTIFICATION-TYPE,

    Counter32, Unsigned32                        FROM SNMPv2-SMI

    TEXTUAL-CONVENTION, RowStatus, TimeStamp,

    TimeInterval, TruthValue, DateAndTime,

    StorageType                                  FROM SNMPv2-TC

    MODULE-COMPLIANCE, OBJECT-GROUP,

    NOTIFICATION-GROUP                           FROM SNMPv2-CONF

    SnmpAdminString                              FROM SNMP-FRAMEWORK-MIB

    rmon, OwnerString                            FROM RMON-MIB

    protocolDirLocalIndex                        FROM RMON2-MIB;

--  Application Performance Measurement MIB

apm MODULE-IDENTITY

    LAST-UPDATED "200402190000Z"  -- February 19, 2004

    ORGANIZATION "IETF RMON MIB Working Group"

    CONTACT-INFO

        "Author:

                     Steve Waldbusser

             Phone:  +1-650-948-6500

             Fax :   +1-650-745-0671

             Email:  waldbusser@nextbeacon.com

         Working Group Chair:

                     Andy Bierman

                     Cisco Systems, Inc.

             Postal: 170 West Tasman Drive

                     San Jose, CA USA 95134

                Tel: +1 408 527-3711

             E-mail: abierman@cisco.com

         Working Group Mailing List: <rmonmib@ietf.org>

         To subscribe send email to: <rmonmib-request@ietf.org>

        "

    DESCRIPTION

        "The MIB module for measuring application performance

        as experienced by end-users.

        Copyright (C) The Internet Society (2004). This version of

        this MIB module is part of RFC 3729; see the RFC itself for

        full legal notices."

    REVISION "200402190000Z"    -- February 19, 2004

    DESCRIPTION

        "The original version of this MIB Module, published as

        RFC3729."

    ::= { rmon 23 }

apmMibObjects OBJECT IDENTIFIER ::= { apm 1 }

apmConformance OBJECT IDENTIFIER ::= { apm 2 }

apmCompliances    OBJECT IDENTIFIER ::= { apmConformance 1 }

apmGroups         OBJECT IDENTIFIER ::= { apmConformance 2 }

AppLocalIndex ::= TEXTUAL-CONVENTION

    STATUS       current

    DESCRIPTION

        "A locally arbitrary unique identifier associated with an

        application or application verb.

        All objects of type AppLocalIndex are assigned by the agent

        out of a common number space. In other words, AppLocalIndex

        values assigned to entries in one table must not overlap with

        AppLocalIndex values assigned to entries in another

        table. Further, every protocolDirLocalIndex value registered

        by the agent automatically assigns the same value out of the

        AppLocalIndex number space.

        For example, if the protocolDirLocalIndex values { 1, 3, 5, 7 }

        have been assigned, and the apmHttpFilterAppLocalIndex values

        { 6, 8, 9 } have been assigned:

            - Assignment of new AppLocalIndex values must not use the

              values { 1, 3, 5, 6, 7, 8, 9 }.

            - AppLocalIndex values { 1, 3, 5, 7 } are automatically

              assigned and are associated with the identical value of

              protocolDirLocalIndex. In particular, an entry in the

              apmAppDirTable indexed by a value provides further

              information about a protocol indexed by the same value

              in the protocolDirTable of RMON2.

        The value for each supported application must remain constant

        at least from one re-initialization of the entity's network

        management system to the next re-initialization, except that

        if an application is deleted and re-created, it must be

        re-created with a new value that has not been used since the

        last re-initialization.

        The specific value is meaningful only within a given SNMP

        entity. An AppLocalIndex value must not be re-used until the

        next agent restart."

    SYNTAX       Unsigned32 (1..2147483647)

ProtocolDirNetworkAddress ::= TEXTUAL-CONVENTION

    STATUS       current

    DESCRIPTION

        "A network level address whose semantics and encoding are

        specified by an associated protocolDirLocalIndex

        value. Objects of this type must specify which

        protocolDirLocalIndex value is used. This value is encoded

        according to the encoding rules for the identified

        protocolDirectory entry.

        For example, if the associated protocolDirLocalIndex indicates

        an encapsulation of ip, this object is encoded as a length

        octet of 4, followed by the 4 octets of the ip address,

        in network byte order.

        Objects of this type may allow this value to be the zero

        length string. If so, they must identify they meaning of this

        value."

    SYNTAX        OCTET STRING (SIZE(0..255))

DataSourceOrZero ::= TEXTUAL-CONVENTION

    STATUS       current

    DESCRIPTION

        "Identifies the source of the data that the associated

        function is configured to analyze. This source can be any

        interface on this device.

        In order to identify a particular interface, this

        object shall identify the instance of the ifIndex

        object, defined in [4], for the desired interface.

        For example, if an entry were to receive data from

        interface #1, this object would be set to ifIndex.1.

        If the source of the data isn't an interface or cannot be

        localized to an interface, this object would be set to 0.0"

    REFERENCE    "The DataSource textual convention is defined in

                 RFC 2021 [5]."

    SYNTAX       OBJECT IDENTIFIER

RmonClientID ::= TEXTUAL-CONVENTION

    STATUS      current

    DESCRIPTION

         "A long-lived unique ID assigned to an end-system. This ID is

         assigned by the agent using an implementation-specific

         algorithm.

         Because a client machine may be assigned multiple addresses

         over any time period it can be difficult to attribute

         behavior to a particular client based solely on its

         address. A ClientID may be assigned to provide a more

         stable handle for referencing that client. The entity that

         assigns the ClientID may use various implementation

         techniques to keep track of a client but if the assigning

         entity is unable to track client address mappings, it may map

         client identifiers to client addresses rather than to

         distinct client machines.

         This is named ClientID because it helps to solve a problem

         seen in network clients (servers usually have well-known,

         long-lived addresses). However, ClientID's may be assigned to

         any end-system regardless of its role on the network."

    SYNTAX      Unsigned32 (0..4294967295)

TransactionAggregationType ::= TEXTUAL-CONVENTION

    STATUS      current

    DESCRIPTION

        "Specifies one of 4 different techniques for aggregating

        transactions.

        The metrics for a single transaction are the responsiveness of

        the transaction and whether the transaction succeeded (a

        boolean). When such metrics are aggregated in this MIB Module,

        these metrics are replaced by averages and distributions of

        responsiveness and availability. The metrics describing

        aggregates are constant no matter which type of aggregation is

        being performed. These metrics may be found in the

        apmReportTable.

        The flows(1) aggregation is the simplest. All transactions

        that share common application/server/client 3-tuples are

        aggregated together, resulting in a set of metrics for all

        such unique 3-tuples.

        The clients(2) aggregation results in somewhat more

        aggregation (i.e., fewer resulting records). All transactions

        that share common application/client tuples are aggregated

        together, resulting in a set of metrics for all such unique

        tuples.

        The servers(3) aggregation usually results in still more

        aggregation (i.e., fewer resulting records). All transactions

        that share common application/server tuples are aggregated

        together, resulting in a set of metrics for all such unique

        tuples.

        The applications(4) aggregation results in the most

        aggregation (i.e., the fewest resulting records). All

        transactions that share a common application are aggregated

        together, resulting in a set of metrics for all such unique

        applications.

        Note that it is not meaningful to aggregate applications, as

        different applications have widely varying characteristics. As a

        result, this set of aggregations is complete."

    SYNTAX      INTEGER {

                  flows(1),    -- Least Aggregation

                  clients(2),

                  servers(3),

                  applications(4) -- Most Aggregation

                }

-- The APM Application Directory Group

-- The Application Directory Table contains a record for every

-- application monitored by this agent. This table is also used to

-- configure whether or not an application will be measured and which

-- bucket boundaries will be used for the application.

--

-- The bucket boundaries define the break-points between bins of a

-- histogram analysis for that application. As an example of how this

-- works, consider an entry representing response-time for http.

-- If the boundaries are set as follows:

-- Boundary1: 500 milliseconds

-- Boundary2: 1 second

-- Boundary3: 2 seconds

-- Boundary4: 5

-- Boundary5: 15

-- Boundary6: 60

--

-- If the following measurements are made (all in milliseconds):

-- 377, 8645, 1300, 487, 1405, 775, 1115, 850, 945, 1054, 7745, 9380

--

-- A report run during this interval would report the following

-- counts:

-- Bucket1: 2

-- Bucket2: 3

-- Bucket3: 4

-- Bucket4: 0

-- Bucket5: 3

-- Bucket6: 0

-- Bucket7: 0

apmAppDirTable OBJECT-TYPE

    SYNTAX      SEQUENCE OF ApmAppDirEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "The APM MIB directory of applications and application

        verbs. The agent will populate this table with all

        applications/verbs of any responsivenessType it has the

        capability to monitor. Since the agent populates this table

        with every entry it has the capability to monitor, the

        entries in this table are read-write, allowing the management

        station to modify parameters in this table but not to add new

        entries or delete entries (however, entries may be

        disabled). If new entries are added to the apmHttpFilterTable

        or the apmUserDefinedAppTable, the agent will add the

        corresponding entries to this table.

        It is an implementation-dependent matter as to how the agent

        sets these default parameters. For example, it may leave

        certain entries in this table 'off(0)' if the agent developer

        believes that combination will be infrequently used, allowing

        a manager that needs that capability to set it to 'on(1)'.

        Some applications are registered in the RMON2 protocol

        directory and some are registered in other tables in this

        MIB Module. Regardless of where an application is originally

        registered, it is assigned an AppLocalIndex value that is the

        primary index for this table.

        The contents of this table affect all reports and exceptions

        generated by this agent. Accordingly, modification of this

        table 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 table - it

        should reflect the preferences of the site administrator, not

        the software author. As a practical matter, this requires

        management software to allow the administrator to configure

        the values it will use so that it can be adapted to the site

        policy."

    ::= { apmMibObjects 1 }

apmAppDirEntry OBJECT-TYPE

    SYNTAX      ApmAppDirEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "The APM MIB directory of applications and application

        verbs. An entry will exist in this table for all applications

        for which application performance measurement is supported."

    INDEX { apmAppDirAppLocalIndex,

            apmAppDirResponsivenessType }

    ::= { apmAppDirTable 1 }

ApmAppDirEntry ::= SEQUENCE {

    apmAppDirAppLocalIndex            AppLocalIndex,

    apmAppDirResponsivenessType       INTEGER,

    apmAppDirConfig                   INTEGER,

    apmAppDirResponsivenessBoundary1  Unsigned32,

    apmAppDirResponsivenessBoundary2  Unsigned32,

    apmAppDirResponsivenessBoundary3  Unsigned32,

    apmAppDirResponsivenessBoundary4  Unsigned32,

    apmAppDirResponsivenessBoundary5  Unsigned32,

    apmAppDirResponsivenessBoundary6  Unsigned32

}

apmAppDirAppLocalIndex OBJECT-TYPE

    SYNTAX      AppLocalIndex

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "The AppLocalIndex assigned for this application Directory

        entry."

    ::= { apmAppDirEntry 1 }

apmAppDirResponsivenessType OBJECT-TYPE

    SYNTAX      INTEGER {

                  transactionOriented(1),

                  throughputOriented(2),

                  streamingOriented(3)

                }

    MAX-ACCESS  not-accessible

    STATUS      current

    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."

    ::= { apmAppDirEntry 2 }

apmAppDirConfig OBJECT-TYPE

    SYNTAX      INTEGER {

                  off(1),

                  on(2)

                }

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "This object describes and configures support for application

        performance measurement for this application.

        If the value of this object is on(2), the agent supports

        measurement of application performance metrics for this

        application and is configured to measure such metrics for all

        APM MIB functions and all interfaces.  If the value of this

        object is off(1), the agent supports measurement of

        application performance for this application but is configured

        to not measure these metrics for any APM MIB functions or

        interfaces.  Whenever this value changes from on(2) to off(1),

        the agent shall delete all related entries in all tables in

        this MIB Module.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 3 }

apmAppDirResponsivenessBoundary1 OBJECT-TYPE

    SYNTAX      Unsigned32

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "The boundary value between bucket1 and bucket 2. If this

        value is modified, all entries in the apmReportTable must be

        deleted by the agent.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 4 }

apmAppDirResponsivenessBoundary2 OBJECT-TYPE

    SYNTAX      Unsigned32

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "The boundary value between bucket2 and bucket 3. If this

        value is modified, all entries in the apmReportTable must be

        deleted by the agent.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 5 }

apmAppDirResponsivenessBoundary3 OBJECT-TYPE

    SYNTAX      Unsigned32

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "The boundary value between bucket3 and bucket 4. If this

        value is modified, all entries in the apmReportTable must be

        deleted by the agent.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 6 }

apmAppDirResponsivenessBoundary4 OBJECT-TYPE

    SYNTAX      Unsigned32

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "The boundary value between bucket4 and bucket 5. If this

        value is modified, all entries in the apmReportTable must be

        deleted by the agent.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 7 }

apmAppDirResponsivenessBoundary5 OBJECT-TYPE

    SYNTAX      Unsigned32

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "The boundary value between bucket5 and bucket 6. If this

        value is modified, all entries in the apmReportTable must be

        deleted by the agent.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 8 }

apmAppDirResponsivenessBoundary6 OBJECT-TYPE

    SYNTAX      Unsigned32

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "The boundary value between bucket6 and bucket 7. If this

        value is modified, all entries in the apmReportTable must be

        deleted by the agent.

        The value of this object must persist across reboots."

    ::= { apmAppDirEntry 9 }

-- Scalars related to the Application Directory table

apmBucketBoundaryLastChange OBJECT-TYPE

    SYNTAX     TimeStamp

    MAX-ACCESS read-only

    STATUS     current

    DESCRIPTION

        "The value of sysUpTime the last time that any bucket boundary

        in any appDirEntry was changed. This object can help to

        determine if two managers are both trying to enforce different

        configurations of this table."

    ::= { apmMibObjects 2 }

apmAppDirID OBJECT-TYPE

    SYNTAX     OBJECT IDENTIFIER

    MAX-ACCESS read-write

    STATUS     current

    DESCRIPTION

        "This object allows managers to avoid downloading application

        directory information when the directory is set to a known

        (usually fixed) configuration.

        If the value of this object isn't 0.0, it signifies

        that the entire contents of the apmAppDirTable,

        apmHttpFilterTable, apmUserDefinedAppTable and

        protocolDirTable are equal to a known state identified

        by the value of this object. If a manager recognizes this

        value as identifying a directory configuration it has a local

        copy of, it may use this local copy rather than downloading

        these tables. Note that it may have downloaded this local copy

        (and the ID) from another agent and used this copy for all

        other agents that advertised the same ID.

        If an agent recognizes that the entire contents of the

        apmAppDirTable, apmHttpFilterTable,

        apmUserDefinedAppTable and protocolDirTable are equal to

        a known state to which an ID has been assigned, it should set

        this object to that ID.

        In many cases when this feature is used, the application

        directory information will be in read-only memory and thus the

        tables may not be modified via SNMP requests. In the event

        that the tables are writable and a modification is made, the

        agent is responsible for setting this object to 0.0 if it

        cannot determine that the state is equal to a known state.

        An agent is not obligated to recognize and advertise all such

        registered states as it may not have knowledge of all states.

        Thus, a manager may encounter agents whose DirectoryID value

        is 0.0 even though the contents of the directory were equal to

        a registered state.

        Note that the contents of those tables includes the

        protocolDirLocalIndex and appLocalIndex values. In other

        words, these values can't be assigned randomly on each agent,

        but must be equal to values that are part of the known

        state. While it is possible for a manager to download

        application directory details using SNMP and to set the

        appropriate directoryID, the manager would need to have some

        scheme to ensure consistent values of LocalIndex variables

        from agent to agent. Such schemes are outside the scope of

        this specification.

        Application directory registrations are unique within an

        administrative domain.

        Typically these registrations will be made by an agent

        software developer who will set the application directory

        tables to a read-only state and assign a DirectoryID to that

        state. Thus, all agents running this software would share the

        same DirectoryID. As the application directory might change

        from one software release to the next, the developer may

        register different DirectoryID's for each software release.

        A customer could also create a site-wide application directory

        configuration and assign a DirectoryID to that configuration

        as long as consistent values of LocalIndex variables can be

        ensured.

        The value of this object must persist across reboots."

     ::= { apmMibObjects 3 }

-- APM HTTP Filter Table

-- The HTTP Filter Table creates virtual applications which measure the

-- performance of certain web pages  or sets of web pages. Some

-- circumstances where this is particularly useful are:

--

--      - An Intranet or ASP scenario where a business application is

--        running on one or more web pages or scripts.

--        (i.e., /expense/submit.cgi?employeeID=3426&...)

--      - A web-hosting scenario where one wants to measure the

--        service level for a particular customer

--      - An e-commerce scenario where the performance of certain

--        pages needs to be monitored more closely.

--        (i.e., shopping cart, shipping, credit card authorization)

apmHttpFilterTable OBJECT-TYPE

    SYNTAX      SEQUENCE OF ApmHttpFilterEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A table that creates virtual applications which measure the

        performance of certain web pages or sets of web pages.

        When an entry is added to this table, the agent will

        automatically create one or more entries in the

        apmAppDirTable (one for each responsivenessType it is

        capable of measuring).

        Note that when entries exist in this table some HTTP

        transactions will be summarized twice: in applications

        represented here as well as the HTTP application. If entries

        in this table overlap, these transactions may be summarized

        additional times.

        The contents of this table affect all reports and exceptions

        generated by this agent. Accordingly, modification of this

        table 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 table - it

        should reflect the preferences of the site administrator, not

        the software author."

    ::= { apmMibObjects 4 }

apmHttpFilterEntry OBJECT-TYPE

    SYNTAX      ApmHttpFilterEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A virtual application which measure the performance of certain

        web pages or sets of web pages."

    INDEX { apmHttpFilterIndex }

    ::= { apmHttpFilterTable 1 }

ApmHttpFilterEntry ::= SEQUENCE {

    apmHttpFilterIndex              Unsigned32,

    apmHttpFilterAppLocalIndex      AppLocalIndex,

    apmHttpFilterServerProtocol     Unsigned32,

    apmHttpFilterServerAddress      ProtocolDirNetworkAddress,

    apmHttpFilterURLPath            OCTET STRING,

    apmHttpFilterMatchType          INTEGER,

    apmHttpFilterOwner              OwnerString,

    apmHttpFilterStorageType        StorageType,

    apmHttpFilterRowStatus          RowStatus

}

apmHttpFilterIndex OBJECT-TYPE

    SYNTAX      Unsigned32 (0..65535)

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "An index that uniquely identifies an entry in the

        apmHttpFilterTable."

    ::= { apmHttpFilterEntry 1 }

apmHttpFilterAppLocalIndex OBJECT-TYPE

    SYNTAX      AppLocalIndex

    MAX-ACCESS  read-only

    STATUS      current

    DESCRIPTION

        "The AppLocalIndex that represents HTTP transactions

        that match this entry.

        This object is read-only. A value is created by the agent from

        an unused AppLocalIndex value when this apmHttpFilterEntry is

        created."

    ::= { apmHttpFilterEntry 2 }

apmHttpFilterServerProtocol OBJECT-TYPE

    SYNTAX      Unsigned32 (1..2147483647)

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The protocolDirLocalIndex value of the network level protocol

        of the apmHttpFilterServerAddress."

    ::= { apmHttpFilterEntry 3 }

apmHttpFilterServerAddress OBJECT-TYPE

    SYNTAX      ProtocolDirNetworkAddress

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "This entry will only represent transactions coming from the

        network address specified in this object.

        This is represented as an octet string with

        specific semantics and length as identified

        by the associated apmHttpFilterServerProtocol object.

        If this object is the zero-length string, then this entry will

        match one of the addresses represented by the 'host' component

        of the associated apmHttpFilterURLPath object, where the

        format if a URL [9] is

        http://<host>:<port>/<path>?<searchpart>."

    ::= { apmHttpFilterEntry 4 }

apmHttpFilterURLPath OBJECT-TYPE

    SYNTAX      OCTET STRING (SIZE(0..65535))

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "This entry will only represent HTTP transactions

        where the URL path component in the request matches this

        value. This value represents the requested path regardless of

        any substitution that the server might perform.

        Prior to the matching, the URL is stripped of any server

        address or DNS name and consists solely of the path name on

        that server.

        If the length of this object is zero, then this entry will

        match if the associated apmHttpFilterServerAddress match. If

        the length of that object is also zero, then this entry will

        match nothing.

        The value of the associated apmHttpFilterMatchType dictates

        the type of matching that will be attempted."

    ::= { apmHttpFilterEntry 5 }

apmHttpFilterMatchType OBJECT-TYPE

    SYNTAX      INTEGER {

                    exact(1),

                    stripTrailingSlash(2),

                    prefix(3)

                }

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The matching algorithm used to compare the URL pathname.

        If the value is exact(1), then the pathname component will be

        compared with the associated apmHttpFilterURLPath and

        will only be associated with this entry if it matches exactly.

        If the value is stripTrailingSlash(2), then the pathname

        component will be compared with the associated

        apmHttpFilterURLPath and will only be associated with this

        entry if it matches exactly or if the pathname ends with a '/'

        symbol and matches apmHttpFilterURLPath if the '/' symbol is

        removed from the pathname. This option exists for those paths

        where an optional trailing slash is possible but for which a

        prefix match would be too broad.

        If the value is prefix(3), then the pathname component will be

        compared with the associated apmHttpFilterURLPath and will

        only be associated with this entry if the beginning of the

        pathname matches every octet of this value. Octets that extend

        beyond the length of this value are ignored."

    ::= { apmHttpFilterEntry 6 }

apmHttpFilterOwner OBJECT-TYPE

    SYNTAX      OwnerString

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The entity that configured this entry and is

        therefore using the resources assigned to it."

    ::= { apmHttpFilterEntry 7 }

apmHttpFilterStorageType OBJECT-TYPE

    SYNTAX      StorageType

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The storage type of this apmHttpFilterEntry. If the value of

        this object is 'permanent', no objects in this row need to be

        writable."

    ::= { apmHttpFilterEntry 8 }

apmHttpFilterRowStatus OBJECT-TYPE

    SYNTAX      RowStatus

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The status of this apmHttpFilterEntry. No objects in this row

        may be modified while the row's status is 'active'."

    ::= { apmHttpFilterEntry 9 }

apmHttpIgnoreUnregisteredURLs OBJECT-TYPE

    SYNTAX      TruthValue

    MAX-ACCESS  read-write

    STATUS      current

    DESCRIPTION

        "When true, APM measurements of HTTP transactions will only

        measure transactions relating to URLs that match a filter in

        the apmHttpFilterTable. Thus, measurements for the HTTP

        application will present aggregated statistics for

        URL-matching HTTP transactions and measurements for the HTTP

        GET application verb will present aggregated statistics for

        URL-matching HTTP GET transactions.

        This will be used in environments that wish to monitor only

        targeted URLs and to ignore large volumes of internet web

        browsing traffic.

        This object affects all APM 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.

        The value of this object must persist across reboots."

    ::= { apmMibObjects 5 }

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 499 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 typos 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.

        The value of this object must persist across reboots."

    ::= { apmMibObjects 6 }

-- The APM User-Defined Application Table

-- Many application protocols will never be registered with a

-- standards body (and thus included in a protocol directory standard)

-- because they are custom, in-house or proprietary

-- applications. Nevertheless, implementation strategies exist for

-- monitoring the end-user experience of these applications.

--

-- This read-only table provides a means for the agent to advertise

-- which user-defined applications it is monitoring and to associate

-- each with an AppLocalIndex value. It is an implementation-dependent

-- matter as to how the agent learns how to monitor these

-- applications.

apmUserDefinedAppTable OBJECT-TYPE

    SYNTAX      SEQUENCE OF ApmUserDefinedAppEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A table that advertises user-defined applications that the

        agent is measuring.

        The agent will automatically create one or more entries in the

        apmAppDirTable (one for each responsivenessType it is

        capable of measuring) for each entry in this table.

        Note that when entries exist in this table some

        transactions can be summarized more than once if there is

        overlap between applications defined here and applications

        defined in the protocol directory or in the httpFilter table."

    ::= { apmMibObjects 7 }

apmUserDefinedAppEntry OBJECT-TYPE

    SYNTAX      ApmUserDefinedAppEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A user-defined application that the agent is measuring, along

        with its AppLocalIndex assignment.