Monitoring
Application Programming
Interface
|
Monitoring
Application Programming
Interface
|
|
MAPI is implemented by the ResourceManager class that integrates three different components:
the MAPI Profiler Agent
The MAPI Profiler Agent is able to gather monitoring information about JVM resources of the monitored target. It not only collects JVMPI events but also filters and processes them on-line, to offer concise monitoring indicators during service execution. The JVMPI-based monitoring functions are immediately portable on any host that runs the JVM version 2.
According to the SNMP terminology, the MAPI SNMP Agent acts as an SNMP manager that interrogates the standard SNMP agent available on a target to obtain monitoring data about local OS resources. The MAPI SNMP Agent not only provides a uniform Java interface by wrapping possibly non-Java SNMP agents, but also implements several local optimizations of the SNMP protocol. In addition, it simplifies the configuration phase of the security parameters needed in SNMPv3, by integrating with the SOMA distributed security infrastructure.
In addition, the ResourceManager can exploit the MAPI*ResManager classes to achieve visibility of OS resources by integrating with platform-dependent monitoring functions via JNI. These functions are implemented as native libraries with the same interfaces for different platforms (MAPI WindowsRM DLL on Microsoft Windows NT 4.0, MAPI SolarisRM SO on SUN Solaris 7, and MAPI LinuxRM SO on SuSE Linux 6.2). ResourceManager is in charge of loading at run-time the correct native library for the current monitored target, to provide platform independence. In this way, MAPI*ResManager permits to obtain OS resource monitoring data also when SNMP agents are not available on the target host.
Figure 2 shows the MAPI set of methods that provide monitoring parameters summarizing the current state of the monitored target, and in particular of the SOMA agents running on it. Administrators of SOMA-based services (or even autonomous software-based service managers) can use MAPI to obtain management information at runtime to adapt service provision. In a runtime scenario, the overhead is obviously critical, and monitoring results should be promptly and immediately available to managers (see the performance page). For this reason, MAPI can tune its intrusion to service-specific time constraints: all MAPI methods have a msec invocation parameter that indicates the time interval for refreshing monitoring indicators. This time interval is propagated to all MAPI components to update the statistics of collected JVMPI events, to interrogate SNMP agents, and to invoke native monitoring libraries.
Figure 2. The ResourceManager class interface.
|
|
||||
 |
 |
|
||
|
Page
updated on
|
In
case of problems, or if you find any bug, please contact us.
|
|||