A notification that Topaz sends to make designated staff aware of performance issues. Alerts can be sent via a variety of media (e-mail, pager, SMS, SNMP trap) and can be configured to trigger a variety of actions.

The ability to specify one or more alerts as being subordinate to another, dominant, alert. When a subordinate alert is triggered after its dominant alert is triggered, Topaz suppresses the subordinate alert's defined actions.

A set of properties that define when, why, and how to send alert notices in Topaz. You create alert schemes in the Topaz Admin Centre.

The Topaz server responsible for managing Topaz alerts.

Real-time monitoring of the availability, performance, and service levels of applications, with the goal of alerting operations groups to performance problems before users experience them.

The percentage of time that a business process, monitored infrastructure component, or service is up and running.

A configuration component that enables you to define customized views for the BAC application.

A standard prefix for all the virtual-user entities (for example, profiles, transactions, and so forth).

Method invocation.

A user-defined value that can be assigned to any element in the deployment hierarchy and is used to efficiently manage monitors across an enterprise.

The top-level node in the deployment hierarchy, representing a company's entire monitoring infrastructure.

A SiteScope entity that tracks the status of one aspect of the Topaz environment. Monitors are set up to report when any Topaz component ceases to work correctly. A monitor reports a status of good, warning, or error.

A component used by Topaz to collect data. Topaz monitors include the Topaz Business Process Monitor, the Topaz Client Monitor, and SiteScope.

A deployment in which Topaz displays more than one language in the same report. That is, Topaz can save data in more than two character sets. This applies to management data (profile or user names), and profile data (error messages returned by the Topaz Business Process Monitor).

Performance boundaries that enable Topaz to organize performance data in a meaningful way.

A program for monitoring infrastructure machines whose data you integrate into Topaz, in order to view and analyse reports on server performance.

A group of SiteScope monitors, which you create in SiteScope. SiteScope groups help you organize performance data in SiteScope reports according to your monitoring and tracking priorities. SiteScope groups can contain monitor subgroups to ease the administration of monitoring large multi-server environments.

A measured SiteScope value. Transaction time, database query time, and CPU utilization are all examples of SiteScope measurements.

A program that tracks the status of one aspect of the monitored environment. A monitor reports a status of OK, warning, or error, based on criteria that you can control.

An entity that you define in a Topaz profile database, and to which you connect in a SiteScope, in order to enable Topaz to integrate SiteScope data into Topaz reports and root-cause analysis.

Service level agreement - An agreement, usually between an organization and a service provider, that outlines standards and expectations of service levels. .