Discovery, maintenance, and representation of entities in a managed system environment

Discovery, maintenance, and representation of entities in a managed system environment are described. Apparatus described herein includes one or more agents that run on respective serves that are managed within a management system, and that generate discovery data in response to a discovery rule. The apparatus also includes a management server that is adapted to transmit the discovery rules for execution by the agent, and to receive the discovery data from the agent. Methods described herein include defining the rules for discovering data about an entity on the server, and receiving the discovery data in response to the rule being executed in an environment in which the entity is deployed. Several types of user interfaces for presenting the discovery data are also disclosed.

TECHNICAL FIELD

This invention relates to discovery, maintenance, and representation of entities in a managed system environment.

BACKGROUND

Enterprise management systems, such as the Microsoft Operations Manager (MOM) available from Microsoft Corporation of Redmond, Wash., enable customers to manage many different components within their enterprises, including, but not limited to: servers, applications, devices, services, sites, desktops, and line of business applications. The list of managed components continues to grow and change constantly. With this growth and expansion, it becomes an increasing challenge to manage and usefully represent the state and status of each managed component. Another challenge arises in discovering, managing, and updating the many relationships between these managed elements.

SUMMARY

Discovery, maintenance, and representation of entities in a managed system environment are described herein. One or more agents that run on respective servers are managed within a management system, and generate discovery data in response to a discovery rule. A management server is adapted to transmit the discovery rules for execution by the agent, and to receive the discovery data from the agent. A user interface described herein enables the definition of rules for discovering data about an entity on a given server, and the discovery data is received in response to the rules being executed in an environment in which the entity is deployed.

Several types of user interfaces for presenting the discovery data are also disclosed. Computer-readable media for performing the foregoing functions are also provided.

DETAILED DESCRIPTION

An overall process performed by the teachings herein can include enabling definition of one or more rules for discovering data about at least one entity related to, for example, a computer-based server. This aspect of the overall process is shown in more detail inFIG. 1, which illustrates an implementation in the context of an operations management system.

The overall process also can include receiving discovery data in response to the rules being executed in an environment in which the entity is deployed. This aspect of the overall process is shown in more detail inFIG. 2, which illustrates an implementation in the context of performing data discovery in an operations management system.

FIG. 1illustrates a management system100featuring various components and data flows associated with performing service discovery. An author105drafts one or more discovery rules110that are designed to discover information about one or more services or entities115that are managed within the management system100. A suitable example of the management system100is the Microsoft Operations Manager (MOM) system, available from Microsoft Corporation. Further background on the MOM system is readily available from the Microsoft website.

Generally, such a management system100enables the author105to specify rules110that can perform a variety of management-related functions within the management system100. Examples of these rules110are the discovery rules110discussed herein. These discovery rules110can be collected from the author105via a user interface120, and forwarded to a management server125. The management server125can embody these discovery rules110into discovery scripts to be run later, and can load these discovery rules and related scripts into management packs (MPs)130. The management server125can store the MPs130into a data store135for later retrieval.

The management server125is generally responsible for coordinating the management of remote entities, such as managed servers140. One managed server140is shown inFIG. 1for clarity and conciseness, but not limitation. Periodically, the MPs130are made available for download by or to the managed servers140, and thus new MPs130are imported by the managed servers140, as indicated by the line145. The transmission of MPs130to the managed servers140can be implemented as either a push or pull model, or any combination of the foregoing.

A management system agent150on the managed server140receives the MPs130, and extracts therefrom the discovery script155embodying the discovery rules110drafted by the author105. The management system agent150then forwards the discovery script155to a host process160. The host process160may be spawned specifically for executing the discovery script155, or may be standing-by, having already been created. The discovery script155can be stored in a script storage structure165for convenience. The script storage structure165can take the form of a buffer, cache, or other form of relatively temporary memory location, and be implemented in connection with any suitable data structure.

The discovery script155can be defined to execute at any interval deemed appropriate by the author105, for example, hourly, daily, weekly, or the like. At the interval specified in the discovery script155, it is executed on the managed server140by the host process160to discover one or more entities115. The discovery script155can be configured to discover information about any entity115within the domain of a given managed server140. Examples of the entities115that can be discovered include any physical or logical device, any service, or any other component on the managed server140.

Not only can the devices, services, or other components be discovered, but the relationships among the foregoing can also be discovered. For convenience, the different entities115that may be discovered on the managed servers140may be grouped into classes, with the discovery rules110locating specific instances of each class existing on a given managed server140. The discovery rules110can also define the properties of each instance of a given class, and define the relationships among classes or instances of classes. To perform the foregoing functions, the discovery script155may utilize services such as the ACTIVE DIRECTORY™ service available from Microsoft, may refer to a system registry or other equivalent file structure indicating how the managed server140is configured, or the like.

The flexibility offered by the rule generation and execution process described above can enable customers using the management system100to evolve beyond managing their enterprises at a computer-by-computer level. Customers may not wish to manage each computer or other such entity in their enterprise on this type of a piecemeal basis, but instead may wish to manage on a “service” level, or a “group of services” level. Thus, the management approaches progresses beyond managing a set of physical devices toward managing a set of services or logical entities within the enterprise. For example, if a given enterprise includes a messaging and collaboration service such as the EXCHANGE SERVER™ service offered by Microsoft, the customer may not be as concerned with how many computers implement the service, or with the status of each computer, but instead may be more concerned with logical groups within the deployment of EXCHANGE SERVER, such as a group of servers designated as a “routing group”. Other examples of entities115can include logical or physical disk drives, lists of SQL instances, and attributes of respective computers, such the version of the operating system they are running, a language identifier, or the like.

FIG. 2illustrates components and data flows200associated with the management system100when reporting discovery data after execution of the discovery script155. As the discovery script155executes on the given managed server140, it locates and gathers data about entities115in response to the discovery rules110. This data is referred to generally herein as discovery data205. As the discovery data205is located, the host process160can store it for convenience in a data storage structure210, which may be implemented similarly to the script storage structure165discussed above in connection withFIG. 1.

The following is sample XML code that may be suitable for implementing the discovery data205:

At a suitable time, the host process160can forward the discovery data205to the management system agent150. The discovery data205pertaining to the entity115can be reported back alone, or can be combined with discovery data205pertaining to other entities115within the managed server140. Also, the discovery data205can be reported immediately upon discovery, or can be collected for some time before reporting, as may be appropriate in particular applications. The processing for the discovery data205can be similar to processing other data items such as alerts, events, and other types of performance-related data in scripts.

In any event, the discovery data205can be reported to the management server125, more particularly, to a database connector component215. The database connector component215functions to organize the discovery data205, and can further function to provide state context for various instances of the discovery data205as received by the management server125. In one embodiment of the process flow200, the discovery script155as executed at the level of a given managed server140at a given time is stateless, in that it does not maintain any memory or history of what it may have found on the given managed server140before.

Assume, for example, that at a first time t0, the discovery script155executes to find three instances of a SQL server on the given managed server140. Assume that later, at a time t1, the discovery script155executes to find only two instances. In this embodiment, the discovery script155at time t1does not know what was found previously at to, because of its stateless nature. However, the database connector component215can maintain state context of what discovery data205resulted from various executions of the discovery script155at respective items. Therefore, the database connector component215can analyze various instances of a history of the discovery data205, and can determine that one less instance of the SQL server exists at time t1as compared to what existed previously at time t0. Therefore, the database connector component215can provide state context at the level of the management server125that may be missing at the level of the managed servers140.

In an alternative embodiment, the managed servers140can be made more state-aware, such that they only report discovery data205back to the management server125when a given execution of the discovery script155results in discovery data205that is different from previous discovery data205. In other words, the discovery data205is reported to the management server125only when the discovery data205changes. This alternative embodiment can reduce the volume of message flow between the managed servers140and the management server125.

The database connector component215can also validate the discovery data205as reported by the various management system agents150. For example, a given discovery script155may locate an instances of a given class “X” on a given managed server140, and report this instance as part of the discovery data205. As part of its analysis of the discovery data205, the database connector component215can validate all classes included in the discovery data205by comparing them to, for example, a schema listing all valid classes. This schema may be stored in the data store135, for example. If the given class “X” as reported in the discovery data205is invalid, the database connector component215can detect this condition as part of its analysis, and report this condition accordingly.

In any event, when the discovery data205is validated, the database connector component215loads it into the data store135. Assuming the data store135is implemented as a database, tables within this database can be populated with the discovery data205.

An illustrative but non-limiting object model for suitable for implementing a discovery script155for locating discovery data205is now described. The discovery script155can create discovery data205by calling a method to fill an object containing the discovery data205, as follows:
objDiscData=ScriptContext.CreateDiscoveryData

After filling the discovery data object205, the script can call a method to submit the discovery data205to the management server125, as follows:
ScriptContext.Submit(objDiscData)

The following describes the object DiscoveryData, which is returned by the CreateDiscoveryData, and also describes other objects used by the DiscoveryData object.

The discovery data object has the following properties and methods:Method CreateCollection( ): DiscoveryCollectionThis method Creates an empty DiscoveryCollection object and returns it.Method AddCollection(DiscoveryCollection obj)Adds a collection object to the discovery data205. A single instance of the discovery data205may contain multiple collection objects.Property CollectionCount: IntegerSupports “Get” method. Returns the collection count of the current discovery data object.
DiscoveryCollection Object

The discovery collection object contains the instances discovered for a specific Class and for a specific scope. For example, a discovery collection object can contain a list of all SQL instances on a given machine “SERVER01”.

Methods and properties are as follows:Property ClassID:StringSupports “Get” and “Set”. ClassID identifies the target class of which the collection contains instances. ClassID can be either a name that identifies the class, such as “SQLInstance”, or a GUID such as “{5C46EDA4-AA2B-11D2-86B0-00A0C9AFE085}”.Method AddScopeFilter(String KeyPropertyId, String Value)Adds a scope filter to the collection. A scope filter identifies the target set of instances that this collection is to contain. For example, if the collection contains a list of SQL Instances on Machine SERVER01, the scope can be defined by calling:objCollection.AddScopeFilter(“MachineName”,“SERVER01”)If the collection contains information about a specific SQL Instance, such as SQL1, then the following scope filter can be added as well:obj Collection.AddScopeFilter(“SQLInstanceName”,“S QL1”)The KeyPropertyID parameter can be either a name of a property or a GUID of the property.Method AddScopeProperty(String PropertyId)Adds a property to the property list that identifies the properties of the Class that this collection has discovered. For example, if the collection contains a list of SQL Instances on machine “SERVER01”, where each instance also contains the DBCount property, then this method can be called as follows:Method AddScopeProperty(“DBCount”)The parameter PropertyID can be either the name of the property or the GUID.Property ScopeFilters:StringSupports “GET”. Returns a list of current scope filters in the collection as a string.Property ScopeProperties:StringSupports “GET”. Returns a list of properties that this collection contains.Method CreateInstance( ):DiscoveryInstanceCreates a DiscoveryInstance object and returns it.Method AddInstance(DiscoveryInstance obj)Adds a DiscoveryInstance object to the collection.Property InstanceCount:IntegerReturns the number of instances in the collection object.
DiscoveryInstance Object

This object can represent the properties collected for an instance. A collection object contains a list of instances, while each instance is represented with this object.

The methods and properties of this object are as follows:Method AddProperty(String PropertyID, String Value)This method adds a property, value pair to the instance data. The PropertyID can be either a name or a GUID. The property specified here is added to the collection as a Scope Property, and can be a non-key property of the class. For example this method can be called as follows:objInstance.AddProperty(“DBCount”,“12”)Method AddKeyProperty(String KeyPropertyID, String Value)This method adds a key property value to the instance object, in which the key property is used to identify the instance in question. Example usage for this method is as follows:objInstance.AddKeyProperty(“SQLInstanceName”,“S QL”)Property InstanceInfo: StringSupports “GET”. Returns a string which summarizes the contents of the instance object.

A sample script for discovering a list of SQL instances on a given machine follows:

//// scenario: discover the list of SQL Instances on machine SERVER01// including the DBCount Property//Dim objDiscData   // discovery dataDim objSQLInstCollection // disc data for SQL Instance on SERVER01Dim objInstance   // discovery data for one SQL Instance// create the discovery eventobjDiscData = ScriptContext.CreateDiscoveryData// create collection for the result for SQL Instances on SERVER01objSQLInstCollection = objDiscData.CreateCollection// specify that Collection is for SQLInstance ClassobjSQLInstCollection.ClassID = “SQLInstance”// specify that collection contains results for only on machine SERVER01objSQLInstCollection.AddScopeFilter(“MachineName”,“SERVER01”)// specify that collection will also contain the DBCount property of// the SQL InstanceobjSQLInstCollection.AddScopeProperty(“DBCount”)//// after some queries, assume script has discovered the SQL Instances//  SERVER01\SQL1  with DBCount=10,  SERVER01\SQL2  withDBCount=3//// create the instance that will contain info for SERVER01\SQL1objInstance = objSQLInstCollection.CreateInstance//// specify the SQLInstance Name which identifies the instance of// SQLInst classobjInstance.AddKeyProperty(“SQLInstanceName”,“SQL1”)// specify the DBCount propertyobjInstance.AddProperty(“DBCount”,“10”)// add the Instance to the collectionobjSQLInstCollection.AddInstance(objInstance)//// add the instance FERITF/SQL2 to the collection as wellobjInstance = objSQLInstCollection.CreateInstanceobjInstance.AddKeyProperty(“SQLInstanceName”,“SQL2”)objInstance.AddProperty(“DBCount”,“3”)objSQLInstCollection.AddInstance(objInstance)//// add the collection to the discovery dataobjDiscData.AddCollection(objSQLInstCollection)//// discovery data is ready to be sent, send itScriptContext.Submit(objDiscData)// DONE...

The user interface120can take several different forms in various implementations of the teachings herein, and can present the discovery data205received from the various managed servers140in a variety of ways. The data presented by these various forms of the user interface120are based on discovery data205as can be stored in the data store135.

FIG. 3illustrates an implementation of the user interface120that provides a state view300of the discovery data205. The state view300can be activated by, for example, clicking on the field305labeled “State”. Within area310, column315lists several computers discovered on various managed servers140, along with a name for each computer. These names may be discovered from the computer itself, or the names may be pulled from an entry provided by a service such as ACTIVE DIRECTORY. The illustrative roles320are examples of classes that might be defined by MPs130and referenced by the discovery rules110. These classes are discovered by the discovery scripts155as they are executed on the various managed servers140. Because area310is arranged as a two-dimensional grid, with roles320forming one axis and computers315forming the other, each cell within this grid can contain an icon325indicating the state of each given role320on each given computer315. The meaning of each of the illustrative icons325is given in the legend shown inFIG. 5.

The state of a given role320on a given computer315can be shown in more detail, for example, by clicking on a cell330, which represents the intersection of the role “SQL” with the computer “CPICK01E”. In response to user input to cell330, the state view300presents additional data in a field335. The contents of this field335are indicated by the banner340, which indicates the computer “CPICK01E” and the role “SQL”. Within field335, a set of properties are shown for the SQL role or class, along with corresponding icons representing the state of each property. A column350lists a name for each instance of the role320as it appears on the computer315, and an icon355indicates an overall status of each instance350.

FIG. 4illustrates an implementation of the user interface120that provides a computer view400of the discovery data205. The computer view400can be activated by, for example, by clicking on the field405labeled “Computers and Groups”. An area410lists the names and several parameters relating to computers, the names of which are listed in a column415. Each computer is listed in a respective row420.

Additional information on a given computer415can be obtained by clicking on the row420corresponding to that computer420. Assuming that a user clicks on the row420, area425is populated with further details pertaining to the computer named “BRETTE03E”. A series of tabs430organize this information for convenience within area425. By clicking on the tab labeled “Roles”, the user can receive a list of roles in area425. Items435represent particular classes of entities115found on the managed server140corresponding to the row420that was clicked to present the data shown in area425. Items440represent respective instances of each class435. For each instance440of a class435, a set of properties445is presented. For example, table450presents the respective properties of three instances of the class “disk” found on the computer “BRETTE03E” by the discovery script155.

FIG. 5illustrates an implementation of the user interface120that provides a diagram or topological view500of the discovery data205. The diagram view500can be activated by, for example, clicking on a field505. The diagram view500includes an area510that presents icons515representing the various managed servers140within the management system100, along with an icon520representing the management server125. The diagram view500also associates a further respective icon525with each of the icons515and520, to indicate the state or status of the entities represented by the icons515and520. The diagram view500can also include a legend530that can be displayed on command to explain the meaning of each of the icons515,520, and525.

FIG. 6illustrates a computing environment600for efficiently processing time-bounded messages, and for fully or partially implementing the computing, network, and system architectures described herein. More particularly, the computing environment600may be suitable for implementing and/or supporting various components described herein, including but not limited to aspects of the user interface120, the management server125, the managed servers140, the database connector component215, the host process160, and the like.

Exemplary computing environment600is only one example of a computing system and is not intended to suggest any limitation as to the scope of use or functionality of the architectures. Neither should the computing environment600be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary computing environment600.

The computer and network architectures in computing environment600can be implemented with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, client devices, hand-held or laptop devices, microprocessor-based systems, multiprocessor systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, gaming consoles, distributed computing environments that include any of the above systems or devices, and the like.

The computing environment600includes a general-purpose computing system in the form of a computing device602. The components of computing device602can include, but are not limited to, one or more processors604(e.g., any of microprocessors, controllers, and the like), a system memory606, and a system bus608that couples the various system components. The one or more processors604process various computer executable instructions to control the operation of computing device602and to communicate with other electronic and computing devices. The system bus608represents any number of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.

Computing environment600includes a variety of computer readable media which can be any media that is accessible by computing device602and includes both volatile and non-volatile media, removable and non-removable media. The system memory606includes computer readable media in the form of volatile memory, such as random access memory (RAM)610, and/or non-volatile memory, such as read only memory (ROM)612. A basic input/output system (BIOS)614maintains the basic routines that facilitate information transfer between components within computing device602, such as during start-up, and is stored in ROM612. RAM610typically contains data and/or program modules that are immediately accessible to and/or presently operated on by one or more of the processors604.

Computing device602may include other removable/non-removable, volatile/non-volatile computer storage media. By way of example, a hard disk drive616reads from and writes to a non-removable, non-volatile magnetic media (not shown), a magnetic disk drive618reads from and writes to a removable, non-volatile magnetic disk620(e.g., a “floppy disk”), and an optical disk drive622reads from and/or writes to a removable, non-volatile optical disk624such as a CD-ROM, digital versatile disk (DVD), or any other type of optical media. In this example, the hard disk drive616, magnetic disk drive618, and optical disk drive622are each connected to the system bus608by one or more data media interfaces626. The disk drives and associated computer readable media provide non-volatile storage of computer readable instructions, data structures, program modules, and other data for computing device602.

Any number of program modules can be stored on RAM610, ROM612, hard disk616, magnetic disk620, and/or optical disk624, including by way of example, an operating system628, one or more application programs630, other program modules632, and program data634. Each of such operating system628, application program(s)630, other program modules632, program data634, or any combination thereof, may include one or more embodiments of the systems and methods described herein.

Computing device602can include a variety of computer readable media identified as communication media. Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, other wireless media, and/or any combination thereof.

A user can interface with computing device602via any number of different input devices such as a keyboard636and pointing device638(e.g., a “mouse”). Also, the user can use a mobile phone as a client to practice the teachings herein. More particularly, the user interface120as shown inFIGS. 1-5may be adapted as appropriate to be supported by a mobile phone used by the author105. Other input devices640(not shown specifically) may include a microphone, joystick, game pad, controller, satellite dish, serial port, scanner, and/or the like. These and other input devices are connected to the processors604via input/output interfaces642that are coupled to the system bus608, but may be connected by other interface and bus structures, such as a parallel port, game port, and/or a universal serial bus (USB).

A display device644(or other type of monitor) can be connected to the system bus608via an interface, such as a video adapter646. In addition to the display device644, other output peripheral devices can include components such as speakers (not shown) and a printer648which can be connected to computing device602via the input/output interfaces642.

Computing device602can operate in a networked environment using logical connections to one or more remote computers, such as remote computing device650. By way of example, remote computing device650can be a personal computer, portable computer, a server, a router, a network computer, a peer device or other common network node, and the like. The remote computing device650is illustrated as a portable computer that can include any number and combination of the different components, elements, and features described herein relative to computing device602.

Logical connections between computing device602and the remote computing device650are depicted as a local area network (LAN)652and a general wide area network (WAN)654. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. When implemented in a LAN networking environment, the computing device602is connected to a local network652via a network interface or adapter656. When implemented in a WAN networking environment, the computing device602typically includes a modem658or other means for establishing communications over the wide area network654. The modem658can be internal or external to computing device602, and can be connected to the system bus608via the input/output interfaces642or other appropriate mechanisms. The illustrated network connections are merely exemplary and other means of establishing communication link(s) between the computing devices602and650can be utilized.

In a networked environment, such as that illustrated with computing environment600, program modules depicted relative to the computing device602, or portions thereof, may be stored in a remote memory storage device. By way of example, remote application programs660are maintained with a memory device of remote computing device650. For purposes of illustration, application programs and other executable program components, such as operating system628, are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computing device602, and are executed by the one or more processors604of the computing device602.

Although embodiments for discovery, maintenance, and representation of entities in a managed system environment have been described in language specific to structural features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary implementations of efficiently processing of time-bounded messages.