d self-described at runtime. They provide a generic MBean class with default behaviour for dynamic instrumentation of resources. 12.10.4 Management Information When an NMS manages a number of EMS, different functions are expected from the JMX Agent. Autonomous notifications are sent by the EMS to the NMS through the JMX Agent. The functions provided by this feature are: Autonomous notification when a managed object has been discovered in a man- agement domain. Notifications are also sent when a managed object has been deleted from the domain or when there is a change in the attribute of the man- aged object. Notification that alerts of some severity has been raised in a particular NE. Notification when an alert of any severity has been cleared. Notifications sent by the EMS can be configured to be forwarded to one or more higher level manager. The higher level manager can be configured to reject notificat- ions from a particular EMS. Notification forwarding can be configured at runtime. The NMS can obtain details about the EMS by sending queries to the various EMS through the JMX Agent. Details can be obtained such as EMS host name, version number and threads being used. The details exposed to the NMS for querying are the total number of Alerts gen- erated, the total number of Events generated and the details associated with each alert or event generated, such as severity, owner name and configuration of trap fil- ters. The management information provided by the JMX Agent to the NMS is the same across different protocols. 12.10.4.1 Management Information Main Group Notifications are unsolicited messages sent by the JMX Agent to the management system. JMX Agent supports a feature for sending notifications to the higher level manager. The JMX Agent registers itself as an Alert Observer and Event Observer which enables the JMX Agent to receive notification. Autonomous notifications are sent in both SNMP and TL1. JMX Agent sends autonomous notifications whenever an alert is received/updated by the system. When the JM