The options in the Authoring workspace let you create new monitoring scenarios so you can change or add monitoring in an existing management pack or create a new management pack for an application that does not have one.
For more information about Authoring, see Operations Manager Authoring Guide. The sections below describe the different options in the Authoring workspace and link to the specific sections of the Authoring Guide describing that feature in complete detail.
Management Pack Templates
Management Pack Templates let you create complete monitoring scenarios with minimal input. After you complete a wizard, the management pack template creates monitors, rules, and even classes to implement the particular scenario. You do not have to understand the management pack elements that are created because you can continue to use the template to perform configuration. The template modifies the underlying elements when necessary.
| Template | Description |
|---|---|
|
Monitor ASP.NET applications and web services from server- and client-side perspectives to get details about application availability and performance. |
|
|
Monitor the availability and performance of a database. You can execute sample queries from one or more watcher nodes. |
|
|
Monitor the availability and performance of a wanted process or verify that an unwanted process is not running. |
|
|
Monitor the availability of an application that is listening on a specific TCP port. You can perform tests from one or more watcher nodes. |
|
|
Monitor a UNIX or Linux log file for a specific log entry one a specific computer or group of computers. |
|
|
Monitor that a particular process installed on a UNIX or Linux computer runs. |
|
|
Create availability monitoring tests for one or more web application URLs and run these monitoring tests from internal locations. |
|
|
Monitor the availability of a web application by using synthetic transactions. |
|
|
Monitor the availability and performance of a service running on one or more Windows-based computers. |
Distributed Applications
Distributed Applications let you group multiple features that are part of a single application. The health of each included object is used to calculate an overall health for the application itself. This health can be used to support alerts, views, and reports.
Groups
Groups contain a particular set of managed objects. They are used to scope views, reports, and certain monitoring scenarios. Criteria can be provided to automatically populate a group based on properties of the objects, or you can add specific objects to a group.You can create new groups and edit existing groups. You can also view the current members of a group. After it has been created, a group can be used in the Monitoring workspace for scoping views, the Reporting workspace for scoping reports, or in the Authoring workspace for overrides, management pack templates, or service level objects.
Management Pack Objects
The Management Pack Objects section provides access to the different elements that are included in the management packs installed in your management group. Depending on the kind of element, you can create new elements, edit existing elements, or view existing elements.
|
An attribute is a property of a class in a management pack. You can add additional attributes to collect additional information about managed objects. These attributes can be used to support group membership or accessed by monitors or rules. |
|
|
Monitors are workflows that run on an agent and determine the current health of an object. Each monitor uses a particular data source as the event log, performance data, or a script to collect its information. |
|
|
Object Discoveries are workflows that run on an agent and discover objects to manage. You cannot create new object discoveries in the Operations console. You can view existing object discoveries in management packs and use overrides to modify the frequency that they run and other parameters that different discoveries may accept. |
|
|
Overrides are used to change parameters on workflows including monitors, rules, and discoveries. Overrides are created from the property page of the workflow that they apply to. This option lets you view and modify existing overrides. |
|
|
Rules are workflows that run on an agent that create an alert, collect information for analysis and reporting, or run a command on a schedule. Each rule uses a particular data source as the event log, performance data, or a script to collect its information. |
|
|
Service Level Tracking lets you compare the availability of managed objects to a specific object. This option lets you create new Service Level Objectives and edit existing Service Level Objectives. |
|
|
Tasks are workflows that run when you request them in the Operations console. Agent tasks run on one or more agent computers. Console tasks run on the Operations console workstation. |
|
|
Views display managed objects and collected data in the Operations console. Views are created and modified in the Monitoring workspace. This option displays the existing views that are available for each target class. |