Operations Manager 2007 Glossary
Aplica-se a: Operations Manager 2007 R2, Operations Manager 2007 SP1
| Term | Definition |
|---|---|
action account |
The Windows account that is used by the MonitoringHost.exe processes to gather data from providers and to run actions, such as scripts, command-line batch files, on monitored devices. |
agent |
The component that is installed on a Windows-based computer that performs management. The agent collects data, compares sampled data to predefined values, creates alerts, and runs responses. |
Agentless Exception Monitoring (AEM) |
A feature in Operations Manager that allows the collection of client application crash data to a single location on a management server, resulting in data that can then be analyzed by your company for patterns. In addition, the Management Server can forward the AEM data to Microsoft for analysis rather than having each individual client forward the data. |
agentless-managed computer |
A computer without an agent that is monitored by a management server or a proxy agent. |
agent-managed computer |
A computer that has an agent installed on it and that reports to a management group. |
alert |
An indication of a significant event requiring attention. Alerts are created by rules and monitors. |
alert severity |
The property of an alert that indicates its seriousness; for example, Service Unavailable, Security Issue, Critical Error, Error, Warning, Information, and Success. |
Audit Collection Services (ACS) |
A service that collects and forwards all security events from monitored computers to a central database. ACS requires Operations Manager 2007. |
class |
A definition of an item that can be discovered and managed. A class can be targeted by monitors, rules, discoveries, and tasks. |
command shell |
In Operations Manager 2007, a customized instance of Windows PowerShell that provides a collection of Operations Manager 2007-specific cmdlets. |
company knowledge |
An editable field of a rule or monitor where you can capture any relevant information about the required steps to resolve an alert that was raised by the rule or monitor. |
data warehouse database |
The database that stores operations data for long periods of time. This data is then used by the Operations Manager 2007 Reporting Server to build reports. By default, this database is named OperationsManagerDW. |
data warehouse server |
The server that hosts the OperationsManagerDW database. |
discovery |
An element in a management pack that defines logic for locating monitored objects and their properties and relationships between different objects. |
gateway server |
A server role in Operations Manager 2007 that enables the monitoring of computers that lie outside of the Kerberos trust boundaries (Kerberos realm) of the management group. |
group |
A logical set of objects that can be used to define the scope of overrides, views, user roles, and notifications. |
heartbeat |
A message generated by an agent that tells its management server that the agent is functioning. It also informs Operations Manager about the current rules that are evaluated by the agent, and if it is necessary, it requests updates. |
management group |
The basic functional unit of an Operations Manager 2007 implementation that can perform monitoring. It must contain a SQL Server 2005 or SQL Server 2008 database server, a root management server, one or more Operations consoles, and one or more agents. In addition, it can also contain a reporting server, a gateway server, an Audit Collection Services server, and additional collector management servers. |
management pack |
A container for a set of logic for monitoring or managing a device, application, or service. |
management server |
The component of an Operations Manager management group that is responsible for communication with agents, databases, and the root management server. |
model |
In Operations Manager, a software representation of hardware, software, services and other logical components that are in your environment. The model captures the nature of those components and the relationships between them. |
monitor |
In Operations Manager, an element in a management pack that defines logic for determining the health state of an object. A monitor can set health state. |
Operations console |
The Operations Manager interface that you use to perform monitoring, administration, authoring, and reporting functions. |
Operations Manager Connector Framework |
An interface to the System Center Data Access service that allows applications to synchronously communicate with the root management server. |
Operations Manager Health Explorer |
A feature of Operations Manager where you can view and then take action on alerts, state changes, and other significant issues generated by monitoring objects on your network. |
Operations Manager Reporting server |
The server role that is responsible for building and presenting reports. |
OperationsManager database |
A SQL Server 2005 or SQL Server 2008 database, named OperationsManager by default, which stores configuration data, operations data, and security data. |
override |
A mechanism by which the default behavior of a rule, monitor, or discovery can be changed for a specific target, group, or object. |
product connector |
A software component that is used to synchronize data between Operations Manager and other management systems. |
product knowledge |
Content, embedded in rules and monitors, that contains information from the management pack author about the causes of an alert and suggestions on how to fix the issue that caused an alert to be raised. |
reference relationship |
In a model, a reference relationship indicates that participating objects work with one another with none of the dependencies or restrictions that exist in the hosting or containment relationships. For example, a network router and an Exchange Mailbox server may work together in providing e-mail services. In addition to working with the Exchange Server, the network router works with any other server or device that it routes network traffic for. Also, the Exchange Mailbox server works with all the other Exchange Servers and certain global catalog servers in the organization to provide e-mail services. |
reporting data warehouse |
An Operations Manager 2007 component that manages the OperationsManagerDW database and that can be independently installed. |
resolution state |
The state of an alert in relation to its status in the resolution cycle, and includes default resolution states such as New, Acknowledged, and Resolved. |
root management server |
The first management server installed for a management group that performs unique functions in the management group. Specifically, it hosts the SDK and Config services and is the target server that all consoles attach to. |
rule |
In Operations Manager 2007, an element in a management pack that defines the events and performance data to collect from computers, and what to do with the information after it is collected. A rule cannot set a health state. |
Run As account |
A Windows account that can be associated with a Run As profile, and can use Windows Authentication, NTLM, Basic, or Digest methods of authentication. |
Run As profile |
A profile that associates an identity with a module so that it can run as that identity. |
synthetic transaction |
A method that can be used to test the availability or performance of a specific service or application from the perspective of an end user. In Operations Manager 2007, these are initiated by rules and monitors. |
System Center Data Access service |
A Windows service that runs on the root management server in each management group, and that allows client applications to access Operations Manager data and functionality. |
System Center Operations Manager Health service |
The Windows-based service responsible for executing management packs as part of the Operations Manager agent and server components. |
task |
In Operations Manager 2007, an element in a management pack that is manually initiated by an Operator to run a predefined command or script against a monitored object. |
user role |
A combination of a profile and a scope. A profile defines actions that a user is allowed to perform. A scope defines the objects on which the actions can be performed. |
view |
In the Operations Manager Operations console, a display of a filtered set of data from the OperationsManagerDB database. |
Web Console |
The browser-based interface that allows you to access the monitoring and reporting workspaces according to your user role. |