ART-MIB
AI MIB Summary
The ART-MIB module enables the monitoring of Application Response Time metrics, specifically capturing latency and throughput data for networked applications to facilitate performance analysis and troubleshooting.
The MIB module for Application Response Time measurement.
Main OID:
art.1.3.6.1.4.1.141.2.1.5
76
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
76 total| Object Name |
|---|
frontier OBJECT IDENTIFIER .1.3.6.1.4.1.141 |
mibdoc2 OBJECT IDENTIFIER .1.3.6.1.4.1.141.2 |
netscout2 OBJECT IDENTIFIER .1.3.6.1.4.1.141.2.1 |
artThe MIB module for Application Response Time measurement. MODULE-IDENTITY .1.3.6.1.4.1.141.2.1.5 |
protocolDir2TableContains the ART augmentations to RMON-2. SEQUENCE OF ProtocolDir2Entry .1.3.6.1.4.1.141.2.1.5.1 |
protocolDir2EntryContains the ART augmentations to RMON-2. ProtocolDir2Entry .1.3.6.1.4.1.141.2.1.5.1.1 |
protocolDir2ArtConfigThis object describes and configures the probe's support for
application response time monitoring for the protocol.
When the probe creates entries in this table for
all protocols that it understands, it will set the entry to
notSupported(1) if it doesn't have the capability to track
application response time for this protocol.
If the value of this object is supportedOff(2), the probe
supports tracking of application response time, but is
configured to not track response time for any control
entries or data sources.
If the value of this object is supportedOn(3), the probe
supports tracking of application response time for this
protocol, and will allow creation of entries in the
artControlTable for the associated protocol.
Whenever this value changes from supportedOn(3) to
supportedOff(2), the probe shall delete all related entries
in the artTable and artSummaryTable.rw Enumeration .1.3.6.1.4.1.141.2.1.5.1.1.1 |
artControlTableThis table lists the data sources (typically, probe
interfaces) for which application response time collection
is enabled, and additionally controls the generation of
ART reports in the artTable and artSummaryTable. SEQUENCE OF ArtControlEntry .1.3.6.1.4.1.141.2.1.5.2 |
artControlEntryA conceptual row in the artControlTable.
Creation of a row enables ART collection and report
generation for the corresponding data source.
The artControlRspTime{1..6} objects are used to categorize
the request-response pairs observed during an ART sample
interval.
The NMS is responsible to ensure that:
artControlRspTime1 <= artControlRspTime2
artControlRspTime2 <= artControlRspTime3
artControlRspTime3 <= artControlRspTime4
artControlRspTime4 <= artControlRspTime5
artControlRspTime5 <= artControlRspTime6
and that:
artControlRspTime6 <= artControlRspTimeout
If these relationships do not hold, the probe rejects any
attempt to set the artControlStatus object to active(1).
Suggested default values for the time ranges are:
artControlRspTime1 25 milliseconds
artControlRspTime2 50 milliseconds
artControlRspTime3 100 milliseconds
artControlRspTime4 200 milliseconds
artControlRspTime5 400 milliseconds
artControlRspTime6 800 milliseconds
The table is implicitly indexed by data source,
using the DataSource identifier corresponding to
the data source. ArtControlEntry .1.3.6.1.4.1.141.2.1.5.2.1 |
artControlIndexA unique index for this artControlEntry. Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.1 |
artControlDataSourceThe source of data for application response-time collection,
i.e., the data source (typically, a probe interface) for
which ART statistics are to be collected and reports generated.
This object shall not be modified if the associated
artControlStatus is equal to active(1).rw DataSource .1.3.6.1.4.1.141.2.1.5.2.1.2 |
artControlTimeRemainingThe number of seconds remaining in the current report
interval. When this value reaches zero, the probe deletes
any existing reports for the associated data source, creates
a new report corresponding to the just-expired interval,
copies the current value of artControlDuration to this
object, and starts a new collection interval.
The value of this object is latched in artControlDuration
whenever it is written to using SNMP, allowing automatic
restart of collection using the same duration.
If this object is overwritten while the associated
artStatus is equal to active(1), the current collection
for the associated data source is abandoned, and a new
collection started using the new interval.
Setting this value to 0 abandons current collection and
disables report generation for the associated data source.
(This is not recommended
The probe should delay the initial countdown of this
object in order to align report intervals to 12:00 AM UTC.rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.3 |
artControlDurationThis object is used to latch the value of artTimeRemaining
for automatic collection restart at the end of a collection
interval.ro Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.4 |
artControlRspTime1The first of six time values used to categorize the response
times observed during the report interval.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.5 |
artControlRspTime2The second of six time values used to categorize the response
times observed during the report interval.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.6 |
artControlRspTime3The third of six time values used to categorize the response
times observed during the report interval.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.7 |
artControlRspTime4The fourth of six time values used to categorize the response
times observed during the report interval.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.8 |
artControlRspTime5The fifth of six time values used to categorize the response
times observed during the report interval.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.9 |
artControlRspTime6The sixth of six time values used to categorize the response
times observed during the report interval.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.10 |
artControlRspTimeoutThe maximum interval that the probe will wait for a server
response to a client request. Requests older than this value
are abandoned, and counted as artTimeouts in the artTable and
as artSummaryTimeouts in the artSummaryTable.
This object may not be changed while artControlStatus is set
to active(1).rw Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.11 |
artControlRptStartTimeThe time at which collection of the currently available
reports was started.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.141.2.1.5.2.1.12 |
artControlRequestedSizeThe maximum number of report rows to be generated in the
artTable for the associated data source. If set to -1, the
maximum number of report rows shall be determined by the
probe based on available resources.rw Integer32 (-1..65535) .1.3.6.1.4.1.141.2.1.5.2.1.13 |
artControlGrantedSizeThe maximum number of report rows in the artTable granted by
the probe for the associated data source. The value of this
object may be less than the requested size.ro Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.14 |
artControlGeneratedRptsThe number of report sets that have been generated by this
entry.
The NMS may use this value to poll for the availability of
a new report set. It may also sample this value before and
after a sweep of the artTable or artSummaryTable in order
to verify that a new report set was not generated during
the sweep.ro Integer32 .1.3.6.1.4.1.141.2.1.5.2.1.15 |
artControlDroppedFramesThe total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.
This count does not include packets that were not counted
because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.ro Counter32 .1.3.6.1.4.1.141.2.1.5.2.1.16 |
artControlOwnerThe entity that configured this entry and is therefore using
the resources assigned to it.rw OwnerString (RMON-MIB) .1.3.6.1.4.1.141.2.1.5.2.1.17 |
artControlStatusThe status of this control table entry.
An entry must not exist in the active state unless all
objects in the entry have an appropriate value.
If this object is not equal to active(1), all associated
entries in the artTable and artSummaryTable shall be
deleted.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.141.2.1.5.2.1.18 |
artTableThis table provides sets of application response time
reports. Each row of the table corresponds to a report.
Existing reports are deleted by the probe at the expiration
of each sampling period, and replaced with new reports for
the just-ended period. Generation of reports is controlled
using the objects in the artControlTable.
The maximum number of report rows in this table is the sum
of each of the artControlGrantedSize object values in
the artControlTable.
Note that this table is shared by all data sources,
although reports are generated independently for each
data source. SEQUENCE OF ArtEntry .1.3.6.1.4.1.141.2.1.5.3 |
artEntryA conceptual row in the artTable.
Each row corresponds to an application response time
report for an individual {data source, application-protocol,
client, server} quadruple.
Rows are created and deleted by the probe, and all objects
are read-only to the NMS.
Rows are indexed (in effect) by data source, application
protocol identifier, server address, and client address.
Note that only the client and server address index
components correspond to objects in the table. ArtEntry .1.3.6.1.4.1.141.2.1.5.3.1 |
artServerAddressThe address of the server.
This is identified as an octet string with specific
semantics and length as identified by the
protocolDirLocalIndex component of the index. OCTET STRING .1.3.6.1.4.1.141.2.1.5.3.1.1 |
artClientAddressThe address of the client.
This is identified as an octet string with specific
semantics and length as identified by the
protocolDirLocalIndex component of the index. OCTET STRING .1.3.6.1.4.1.141.2.1.5.3.1.2 |
artAvgRspTimeThe average response time, in milliseconds, observed
during the report interval. Specification of milliseconds
as the time units does not require the probe to maintain
one-millisecond time granularity.
Response time is measured as the number of milliseconds,
as observed by the probe, between the final packet
of an application-layer request PDU from client to
server and the first packet of a response PDU from
server client.
This object is the arithmetical mean of the individual
response times observed during the interval. Only server
responses that the probe has successfully paired with
client requests are included in the calculation.
Additional semantics of 'response time' may depend on
the application being monitored.ro Integer32 .1.3.6.1.4.1.141.2.1.5.3.1.3 |
artMinRspTimeThe minimum response time, in milliseconds, observed
during the report interval.
This object is the minimum value of the individual
response times observed during the interval. Only server
responses that the probe has successfully paired with
client requests are included in the calculation.ro Integer32 .1.3.6.1.4.1.141.2.1.5.3.1.4 |
artMaxRspTimeThe maximum response time, in milliseconds, observed
during the report interval.
This object is the maximum value of the individual
response times observed during the interval. Only server
responses that the probe has successfully paired with
client requests are included in the calculation.
The probe should use wait for for artControlRspTimeout
milliseconds before abandoning the wait for a server
response.ro Integer32 .1.3.6.1.4.1.141.2.1.5.3.1.5 |
artTotalResponsesThe total number of client requests that have been
successfully paired with a corresponding server response
during the report interval.
Requests that have been timed-out by the probe are not
counted by this object.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.6 |
artRsps1The first of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required less than artRspTime1
milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.7 |
artRsps2The second of seven counters used to categorize the response
times observed during the report interval. This object
is a count of responses that required at least artRspTime1
milliseconds but less than artRspTime2 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.8 |
artRsps3The third of seven counters used to categorize the response
times observed during the report interval. This object
is a count of responses that required at least artRspTime2
milliseconds but less than artRspTime3 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.9 |
artRsps4The fourth of seven counters used to categorize the response
times observed during the report interval. This object
is a count of responses that required at least artRspTime3
milliseconds but less than artRspTime4 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.10 |
artRsps5The fifth of seven counters used to categorize the response
times observed during the report interval. This object
is a count of responses that required at least artRspTime4
milliseconds but less than artRspTime5 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.11 |
artRsps6The sixth of seven counters used to categorize the response
times observed during the report interval. This object
is a count of responses that required at least artRspTime5
milliseconds but less than artRspTime6 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.12 |
artRsps7The seventh of seven counters used to categorize the
response times observed during the report interval. This
object is a count of responses that required at least
artRspTime6ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.13 |
artClientOctetsThe total number of octets observed in client requests
during the report interval. If the application-layer PDU has
been fragmented into multiple packets, all octets in each of
the packets are included in this count.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.14 |
artClientOverflowOctetsThe number of times the associated artClientOctets counter
has overflowed.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.15 |
artClientHCOctetsThe high-capacity version of artClientOctets.ro Counter64 .1.3.6.1.4.1.141.2.1.5.3.1.16 |
artServerOctetsThe total number of octets in server responses
during the report interval. If the application-layer PDU
has been fragmented into multiple packets, all octets in each
of the packets are included in this count.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.17 |
artServerOverflowOctetsThe number of times the associated artServerOctets counter
has overflowed.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.18 |
artServerHCOctetsThe high-capacity version of artServerOctets.ro Counter64 .1.3.6.1.4.1.141.2.1.5.3.1.19 |
artRetriesThis total number of application-layer client retries
observed during the report interval.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.20 |
artTimeoutsThe number of times the probe has timed-out a client
request while waiting for a server response during the
report interval. Timeouts may occur due to server
congestion or failure, network congestion or failure,
or probe congestion.ro Counter32 .1.3.6.1.4.1.141.2.1.5.3.1.21 |
artConformance OBJECT IDENTIFIER .1.3.6.1.4.1.141.2.1.5.4 |
artMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.141.2.1.5.4.1 |
artMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.141.2.1.5.4.2 |
artSummaryTableThis table provides sets of application response time
summary reports. Each row of the table corresponds to a
report.
Existing reports are deleted by the probe at the expiration
of each sampling period, and replaced with new reports for
the just-ended period. Generation of reports is controlled
using the objects in the artControlTable.
Note that this table is shared by all probe data sources,
although reports are generated independently for each
data source. SEQUENCE OF ArtSummaryEntry .1.3.6.1.4.1.141.2.1.5.5 |
artSummaryEntryA conceptual row in the artSummaryTable.
Each row corresponds to an application response time
report for an individual {data source, application-protocol,
server} triple. Values in the each row correspond to the
summary of response time information of all clients of
the associated server, whereas the rows in the artTable
contain detailed information for {data source, application-
protocol, client, server} quadruples.
Rows are created and deleted by the probe, and all objects are
read-only to the NMS.
Rows are indexed (in effect) by data source, application
protocol identifier, and server address.
Note that only the server address index component
corresponds to an object in the table. ArtSummaryEntry .1.3.6.1.4.1.141.2.1.5.5.1 |
artSummaryServerAddressThe address of the server.
This is identified as an octet string with specific
semantics and length as identified by the
protocolDirLocalIndex component of the index. OCTET STRING .1.3.6.1.4.1.141.2.1.5.5.1.1 |
artSummaryClientsThe number of clients of this server for which requests
were successfully paired with server responses during
the report interval.ro Integer32 .1.3.6.1.4.1.141.2.1.5.5.1.2 |
artSummaryAvgRspTimeThe average response time, in milliseconds, observed
during the report interval. Specification of milliseconds
as the time units does not require the probe to maintain
one-millisecond time granularity.
Response time is measured as the number of milliseconds,
as observed by the probe, between the final packet
of an application-layer request PDU from client to
server and the first packet of a response PDU from
server client.
This object is the arithmetical mean of the individual
response times observed during the interval. Only server
responses that the probe has successfully paired with
client requests are included in the calculation.
Additional semantics of 'response time' may depend on
the application being monitored.ro Integer32 .1.3.6.1.4.1.141.2.1.5.5.1.3 |
artSummaryMinRspTimeThe minimum response time, in milliseconds, observed
during the report interval.
This object is the minimum value of the individual
response times observed during the interval. Only server
responses that the probe has successfully paired with
client requests are included in the calculation.ro Integer32 .1.3.6.1.4.1.141.2.1.5.5.1.4 |
artSummaryMaxRspTimeThe maximum response time, in milliseconds, observed
during the report interval.
This object is the maximum value of the individual
response times observed during the interval. Only server
responses that the probe has successfully paired with
client requests are included in the calculation.
The probe should use a reasonable timeout period before
abandoning the wait for a server response.ro Integer32 .1.3.6.1.4.1.141.2.1.5.5.1.5 |
artSummaryTotalResponsesThe total number of client requests that have been
successfully paired with a corresponding server response
during the report interval.
Requests that have been timed-out by the probe are not
counted by this object.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.6 |
artSummaryRsps1The first of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required less than artControlRspTime1
milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.7 |
artSummaryRsps2The second of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required at least artControlRspTime1
milliseconds but less than artControlRspTime2 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.8 |
artSummaryRsps3The third of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required at least artControlRspTime2
milliseconds but less than artControlRspTime3 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.9 |
artSummaryRsps4The fourth of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required at least artControlRspTime3
milliseconds but less than artControlRspTime4 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.10 |
artSummaryRsps5The fifth of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required at least artControlRspTime4
milliseconds but less than artControlRspTime5 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.11 |
artSummaryRsps6The sixth of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required at least artControlRspTime5
milliseconds but less than artControlRspTime6 milliseconds.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.12 |
artSummaryRsps7The seventh of seven counters used to categorize the response
times observed during the report interval. This object is a
count of responses that required at least artControlRspTime6ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.13 |
artSummaryClientOctetsThe total number of octets observed in client requests
during the report interval. If the application-layer PDU has
been fragmented into multiple packets, all octets in each of
the packets are included in this count.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.14 |
artSummaryClientOverflowOctetsThe number of times the associated artClientOctets counter
has overflowed.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.15 |
artSummaryClientHCOctetsThe high-capacity version of artSummaryClientOctets.ro Counter64 .1.3.6.1.4.1.141.2.1.5.5.1.16 |
artSummaryServerOctetsThe total number of octets in server responses
during the report interval. If the application-layer PDU
has been fragmented into multiple packets, all octets in each
of the packets are included in this count.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.17 |
artSummaryServerOverflowOctetsThe number of times the associated artSummaryServerOctets
counter has overflowed.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.18 |
artSummaryServerHCOctetsThe high-capacity version of artSummaryServerOctets.ro Counter64 .1.3.6.1.4.1.141.2.1.5.5.1.19 |
artSummaryRetriesThis total number of application-layer client retries
observed during the report interval.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.20 |
artSummaryTimeoutsThe number of times the probe has timed-out a client
request while waiting for a server response during the
report interval. Timeouts may occur due to server
congestion or failure, network congestion or failure,
or probe congestion.ro Counter32 .1.3.6.1.4.1.141.2.1.5.5.1.21 |