APM-MIB Table View

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.

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.

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.

A client machine may have multiple addresses during a period
of monitoring. The apmNameTable assigns a long-lived
identifier to a client and records what addresses were
assigned to that client for periods of time. Various
implementation techniques exist for tracking this mapping but
if an agent is unable to track client address mappings, it may
map client identifiers to client addresses rather than to
distinct client machines.
          
A particular apmNameClientID should be a constant attribute of
a particular client. When available, the agent may also record
the machine name and/or user name which may be valuable for
displaying to humans. The apmNameMachineName and
apmNameUserName are relatively constant, changing only if
these attributes actually change on the client.
          
The agent will store a historical log of these entries, aging
out old entries as the log becomes too large. Since this table
contains information vital to the interpretation of other
tables (e.g., the apmReportTable), the agent should ensure that
          
the log doesn't age out entries that would be referenced by
data in those tables.
          
Note that an entry for a clientID is active from its
StartTime until the StartTime of another entry (for the same
clientID) that supersedes it, or 'now' if none supersede
it. Therefore, if a clientID only has a single entry, it is by
definition very new and should never be aged out. No entry for
a clientID should be aged out unless it has been updated by a
new entry for the client (i.e., with an updated address) and
only if the new entry is 'old' enough.
          
To determine how old is old enough, compute the maximum value
of Interval * (NumReports + 1) of all entries in the
apmReportControlTable (the '+ 1' is to allow a reasonable
period of time for the report to be downloaded). Then take the
larger of this value and the age in seconds of the oldest
entry in the current transaction table. If an entry for a
clientID is superseded by another entry whose StartTime is
more than this many seconds ago, then the older entry may be
deleted.

Parameters that control the creation of a set of reports that
aggregate application performance.

The data resulting from aggregated APM reports. Consult the
definition of apmReportControlAggregationType for the
definition of the various types of aggregations.

This table contains transactions that are currently running
or have recently finished.

This table creates filters so that a management station can
get immediate notification of a transaction that has had poor
          
availability or responsiveness.
          
Each apmExceptionEntry is associated with a particular type of
transaction and is applied to all transactions of that
type. Multiple apmExceptionEntries may be associated with a
particular type of transaction. A transaction type is
identified by the value of the apmAppDirAppLocalIndex
component of the index.
          
Because the quality of a transaction is not known until it is
completed, these thresholds are only applied after the
transaction has completed.