SRC-PE 2.0.x Network Guide > Configuring Applications to Communicate with an SAE with SDX Admin
> Monitoring NIC Proxies on Solaris Platforms
Monitoring NIC Proxies on Solaris Platforms
You can use MBeans to monitor NIC proxies. MBeans are a feature of the Java Management Extension (JMX) software. If you want to monitor the MBeans for NIC proxies, your Web application server must include a JMX agent.
NIC proxies create one instance of an MBean called NicProxyMgmt to provide information about the role of the NIC proxy to the JMX agent. The way you view the MBeans depends on the particular Web application server and the interfaces that its JMX agent provides. Table 15 shows the information that this MBean provides.
You can reset the values of many NicProxyMgmt MBean properties to zero.
To reset the NicProxyMgmt MBean properties to zero:
- Execute the reset counters operation through the mechanism that the JMX agent for your Web application server provides.
Table 15 shows which counters the reset operation affects.
Table 15: Information That the NicProxyMgmt MBean Provides
|
|
|
nicProxyName
|
Name of the NIC proxy. Different NIC proxies may exist, providing different functionality.
|
No
|
numKeysCachedLocally
|
Number of key-value pairs that are cached in the NIC proxy (the bigger the cache, the less likely the NIC proxy will have to involve the distributed NIC components in lookups across the network).
|
No
|
numLookups
|
Number of times that the Web application containing this NIC proxy has requested the NIC proxy to look up a data key.
|
Yes
|
numLookupErrors
|
Number of lookups that have failed.
|
Yes
|
numKeysNoMatch
|
Number of lookups in which the provided key does not map to any value.
|
Yes
|
numKeysOneMatch
|
Number of lookups in which the provided key maps to exactly one value.
|
Yes
|
numKeysMultiMatch
|
Number of lookups in which the provided key maps to more than one value.
|
Yes
|
lookupTimeAvg
|
For the 100 most recent (successful and unsuccessful) lookups, the average time (in milliseconds) of the lookup.
|
Yes
|
lookupTimeMin
|
For the 100 most recent (successful and unsuccessful) lookups, the minimum time (in milliseconds) of the lookup.
|
Yes
|
lookupTimeMax
|
For the 100 most recent (successful and unsuccessful) lookups, the maximum time (in milliseconds) of the lookup.
|
Yes
|