Page History
...
Table 4-1 Pre-defined roles for Precise
Role | Description | ||
---|---|---|---|
Precise manager | Allowed to install all technologies, administrate all technologies, monitor and tune all technologies. Included permissions:
| ||
Precise guest | Allowed to monitor the default environment. | ||
<Techology> manager | Allowed to install, monitor and administer the specified technology. Included permissions:
| ||
Precise Monitor | Allowed to monitor and tune all technologies. Included permissions:
|
Anchor | ||||
---|---|---|---|---|
|
...
Table 4-2 Resource permissions for nodes based by scope
Scope | Description | ||
---|---|---|---|
Technology | You need to specify in the role dialog the nodes it is associated to. The role can be associated to a specific node, or to the “all” node option. If the “all” (default) node option is selected, new attached nodes are added automatically to the existing list of roles for that role. | ||
Environment | The node association is based on the environment's node.
| ||
AppTier | The node association is based on the AppTier's node. | ||
Instance | The node association is based on the instance's node. |
Defining a role
You can define a role via the Role Settings dialog box.
...
The user can view the environment in StartPoint; the data which the user can view, and the operations he can perform are based on the roles given to him. See “About About role management in Alerts” on page 169Alerts.
Table 4-3 Permissions needed to perform an operation
Operation | Required permission | Required resource | ||
---|---|---|---|---|
Install instance | ADMINISTRATE.INSTALL | The instance’s technology.
| ||
Edit/uninstall instance | ADMINISTRATE.INSTALL | The instance. | ||
Set instance AppTiers | ADMINISTRATE.EXECUTE | The instance. | ||
Set instance customized columns | ADMINISTRATE.EXECUTE | The instance. | ||
Apply update | ADMINISTRATE.INSTALL | Precise technology on all nodes. | ||
Change instances customized column headers | ADMINISTRATE.EXECUTE | Precise technology on all nodes. | ||
Apply license | ADMINISTRATE.EXECUTE | Precise technology on all nodes. | ||
Add node | ADMINISTRATE.INSTALL | Precise technology on all nodes. | ||
Edit/remove node | ADMINISTRATE.INSTALL | Precise technology on the node. | ||
Add environment | ADMINISTRATE.EXECUTE | Precise technology on the node the environment belongs. | ||
Edit/remove/customize columns environment | ADMINISTRATE.EXECUTE | The environment. | ||
Change environments customized column header | ADMINISTRATE.EXECUTE | Precise technology on all nodes. | ||
Add AppTier | ADMINISTRATE.EXECUTE | The AppTier’s environment. | ||
Edit/remove AppTier | ADMINISTRATE.EXECUTE | The AppTier. | ||
Manage roles and users | ADMINISTRATE.EXECUTE | Precise technology on all nodes. | ||
Manage clusters | ADMINISTRATE.EXECUTE | The cluster’s technology. | ||
Manage downtime | ADMINISTRATE.EXECUTE | The instance. | ||
Manage SLA availability | ADMINISTRATE.EXECUTE | The instance’s technology. | ||
Manage SLA response time or service time | ADMINISTRATE.EXECUTE | The instance’s and Precise technology on the nodes the user wants to manage. | ||
Manage grouping | ADMINISTRATE.EXECUTE | Precise technology on the node the group is defined and on the technology the group is defined. | ||
Manage locations | ADMINISTRATE.EXECUTE | Precise technology on the node the location is defined. | ||
View Environment in StartPoint | MONITOR.VIEW | The environment. | ||
Create Support file | ADMINISTRATE.EXECUTE | Precise technology |
Anchor | ||||
---|---|---|---|---|
|
...
- On the Settings menu, click SLA.
- In the SLA Settings dialog box, on the relevant tab, from the Technology list, select the technology for which you want to add an SLA definition and click Edit.
- In the SLA Settings - Edit SLA Definition dialog box, perform one of the following steps:
- For all technologies except ‘Other'. In the SLA name text box, type the name of the new SLA definition.
- For a technology of type ‘Other’. From the AppTier list, select an AppTier.
- For SAP. From the Activity type list, select the relevant activity type.
- Select a value in the node list; the SLA can be defined on a single node, or on all nodes. The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
- Click Filter to populate the Select list with items.
To display a smaller, more focused set of items, type a string expression that contains the character string common to all the items that you want to add to the SLA definition, combined with wildcard characters, into the text box. For example, suppose you want to define an SLA definition for the SAP AppTier that contains only the SAP transactions that are executed by the Human Resources department. If all such SAP transactions start with the letters “HR,” you can type the string HR% in the Filter text box to display only Human Resources department transactions in the Select list.
If the name of the item that you want to add to the SLA definition does not appear in the Select list, type its name into the Free text box. You can also use this text box to add a pattern to the SLA definition instead of selecting distinct transactions.
...
To delete a response time SLA definition1.
- On the Settings menu, click SLA.
...
- In the SLA Settings dialog box, on the relevant tab, from the Technology list, select the technology for which you want to add an SLA definition and click Delete.
Managing service time
Service Time SLAs refer to the net duration needed to process a request, from the time the request arrived until the time the service that is associated with the request was completed.
...
You can add a service time SLA definition via the SLA Settings dialog box.
To add a service time SLA definition1.
- On the Settings menu, click SLA.
...
- In the SLA Settings dialog box, on the relevant tab, from the Technology list, select the technology for which you want to add an SLA definition and click Add.
...
- In the SLA Settings - Add SLA Definition dialog box, perform one of the following steps:
...
- For all technologies except
...
- ‘Other’.
...
- In the SLA name text box, type the name of the new SLA definition.
...
- For a technology of type
...
- ‘Other’.
...
- From the AppTier list, select an AppTier.
...
- Select a value in the node list; the SLA can be defined on a single node, or on all nodes.
...
- The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
...
- Click Filter to populate the Select list with items.
To display a smaller, more focused set of items, type a string expression that contains the character string common to all the items that you want to add to the SLA definition, combined with wildcard characters, into the text box.
...
- For example, suppose you want to define an SLA definition for the SAP AppTier that contains only the SAP transactions that are executed by the Human Resources department. If all such SAP transactions start with the letters “HR,” you can type the string HR% in the Filter text box to display only Human Resources department transactions in the Select list.
...
- If the name of the item that you want to add to the SLA definition does not appear in the Select list, type its name into the Free text box. You can also use this text box to add a pattern to the SLA definition instead of selecting distinct transactions.
To add a pattern to the SLA definition1.
- Use the arrow buttons to move items to the list on the right. To delete an item from the list, select it and click Remove.
...
- Specify time values, in seconds, for Near-breach and Breach thresholds and click OK.
You can fine-tune the threshold up to milliseconds, for example 1.02 seconds.
...
You can edit a service time SLA definition via the SLA Settings dialog box.
To edit a service time SLA definition1.
- On the Settings menu, click SLA.
...
- In the SLA Settings dialog box, on the relevant tab, from the Technology list, select the technology for which you want to add an SLA definition and click Edit.
...
- In the SLA Settings - Edit SLA Definition dialog box, perform one of the following steps:
...
- For all technologies except
...
- ‘Other’.
...
- In the SLA name text box, type the name of the new SLA definition.
...
- For a technology of type
...
- ‘Other’.
...
- From the AppTier list, select an AppTier.
...
- Select a value in the node list; the SLA can be defined on a single node, or on all nodes.
...
- The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
...
- Click Filter to populate the Select list with items.
To display a smaller, more focused set of items, type a string expression that contains the character string common to all the items that you want to add to the SLA definition, combined with wildcard characters, into the text box.
...
- For example, suppose you want to define an SLA definition for the SAP AppTier that contains only the SAP transactions that are executed by the Human Resources department. If all such SAP transactions start with the letters “HR,” you can type the string HR% in the Filter text box to display only Human Resources department transactions in the Select list.
If the name of the item that you want to add to the SLA definition does not appear in the Select list, type its name into the Free text box. You can also use this text box to add a pattern to the SLA definition instead of selecting distinct transactions.
To add a pattern to the SLA definition1.
- Use the arrow buttons to move items to the list on the right. To delete an item from the list, select it and click Remove.
...
- Specify time values, in seconds, for Near-breach and Breach thresholds and click OK.
You can fine-tune the threshold up to milliseconds, for example 1.02 seconds.
...
You can delete a service time SLA definition via the SLA Settings dialog box.
To delete a service time SLA definition1.
- On the Settings menu, click SLA.
...
- In the SLA Settings dialog box, on the relevant tab, from the Technology list, select the technology for which you want to add an SLA definition and click Delete.
Managing availability
Availability SLAs indicate the lowest acceptable level of an instance’s availability.
...
You can edit an availability SLA definition via the SLA Settings dialog box.NOTE
Info |
---|
You cannot add or delete Availability SLA definitions, but you can edit them at any time. |
To edit availability SLA definitions1.
- From the Settings menu, click SLAs.
...
- In the SLA Settings dialog box, click the Availability tab.
...
- From the Technology list, select the technology for which you want to edit an SLA definition.
...
- In the table, select an instance. Then click Edit.
...
- In the SLA Settings - Edit SLA Definition dialog box, type the new SLA value (in percent) and click OK.
Anchor | ||||
---|---|---|---|---|
|
By defining Precise locations, you can logically divide your organization into geographical or organizational groups. Defining locations this way can help you to isolate local performance problems and also gain a better understanding of system behavior patterns.
Location definitions are based on the IP addresses of client machines. You can define a location that is based on one IP address or based on a range of IP addresses. Location definitions affect Insight and Precise for Web.
The table in the Location Settings dialog box displays a list of all locations currently defined, the specific IP addresses or IP address ranges that are part of the location, and the time and date of the last update. You can only define locations for newly loaded data, not for previously loaded data.
An activity with a specific IP address is assigned to the best-fit location. For example: Location A has an IP address range from 10.1.0.0 to 10.1.0.255 while location B is defined for IP addresses 10.1.0.77 and 10.1.0.79. In this case, an activity with the IP address 10.1.0.79 is assigned to location B, not A.
...
You can add a location via the Location Settings dialog box.NOTE
Info |
---|
When you insert IP ranges, verify that you do not create an invalid overlap. For example: 211.2.2.2-223.0.0.0 and 222.2.2.2-224.0.0.0 overlap and create an invalid overlap. 211.2.2.2-223.0.0.0 and 223.0.0.1-224.0.0.0 or 211.2.3.3-222.1.2.9 are valid overlaps, if overlapping is checked as the selected node. If all nodes was selected, the overlapping check will be performed on all nodes. |
To add a location1.
- On the Settings menu, click Location.
...
- In the Location Settings dialog box, click Add.
...
- Select a value from the node list; the location can be defined on a single node or on all nodes.
...
- The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
...
- In the Location Settings - Add dialog box, click Filter to populate the Select list with items.
To display a smaller, more focused set of items in the Select list, type a string expression that contains the character string common to all the IP addresses you want to add to the SLA definition, combined with wildcard characters, into the text box.
For example: If you define a Chicago location and all IP addresses in this location start with “10.6,” you could type the string 10.6* in the Filter box to display only IP addresses that belong to this location.
...
- To specify a range of IP addresses for the location, type the first and last address into the From...To text boxes.
...
- Use the arrow buttons to move items to the list on the right.
- To delete an item from the right list, select it and click Remove.
...
- Click OK.
Editing a location
You can edit a location via the Location Settings dialog box.
Info |
---|
...
When you insert IP ranges, verify that you do not create an invalid overlap. For example: 211.2.2.2-223.0.0.0 and 222.2.2.2-224.0.0.0 overlap and create an invalid overlap. 211.2.2.2-223.0.0.0 and 223.0.0.1-224.0.0.0 or 211.2.3.3-222.1.2.9 are valid overlaps, if overlapping is checked as the selected node. If all nodes was selected, the overlapping check will be performed on all nodes. |
To edit a location1.
- On the Settings menu, click Location.
...
- In the Location Settings dialog box, click Edit.
...
- Select a value from the node list; the location can be defined on a single node or on all nodes.
...
- The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
...
- In the Location Settings - Edit dialog box, click Filter to populate the Select list with items.
To display a smaller, more focused set of items in the Select list, type a string expression that contains the character string common to all the IP addresses you want to edit to the SLA definition, combined with wildcard characters, into the text box.
...
- For example: If you define a Chicago location and all IP addresses in this location start with “10.6,” you could type the string 10.6* in the Filter box to display only IP addresses that belong to this location.
...
- To specify a range of IP addresses for the location, type the first and last address into the From...To text boxes.
...
- Use the arrow buttons to move items to the list on the right.
- To delete an item from the right list, select it and click Remove.
...
- Click OK.
Deleting a location
You can delete a location via the Location Setting dialog box.
To delete a location1.
- On the Settings menu, click Location.
...
- In the Location Settings dialog box, select the location you want to remove and click Delete.
Anchor | ||||
---|---|---|---|---|
|
Grouping settings are relevant for displaying information in Insight. In Insight, the graphs in the AppTier area compare performance attributes of various entities for each AppTier. This can be useful in pinpointing problem areas. In cases where the information in the graphs is too granular, you can create a higher-level view of the graph by grouping entities together.
For example, examining a graph that shows SQL Server Login Names reveals that many users use the system. It is difficult to understand from the graph who actually uses the database for normal application purposes and who uses it for administrative or other purposes. It is even more difficult to understand the geographical or organizational distribution of system users.
An effective way to obtain such information is to group entities (Login Names in this example). By grouping login names into designated groups, you can obtain a higher-level understanding of system usage and performance.
...
You can view existing groups via the Grouping Settings dialog box.
To view existing groups1.
- On the Settings menu, click Grouping.
...
- In the Grouping Settings dialog box, from the Technology list, select the technology for which you want to view existing groups. The values in the Group list change according to the selected technology.
...
- From the Group list, select the group whose definition you want to view. The group table populates with information on the selected group.
Adding a group
You can add a group via the Grouping Settings dialog box.
To add a group1.
- On the Settings menu, click Grouping.
...
- In the Grouping Settings dialog box, select a technology and group.
...
- Click Add.
...
- In the Grouping Settings — Add dialog box, in the Group text box, type the name for the group you want to create.
...
- Select a value from the node list; the grouping can be defined on a single node or on all nodes.
...
- The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
...
- Click Filter to populate the Select list with items.
To display a smaller, more focused set of items in the Select list, type a string expression that contains the character string common to all the values you want to add to the group, combined with wildcard characters, into the text box.
For example: If you define a group of login names and you want to view a list of all the login names that start with “U,” you can type the string U% (or %) in the Filter box to display only login names that start with “U.” If a specific value does not appear in the list, use the Free text box to enter the value.
...
- Use the arrow buttons to move items to the list on the right.
- To delete an item from the right list, select it and click Remove.
...
- Click OK. A new group is added to the group list.
Editing a group
You can edit a group via the Group Settings dialog box.
To edit a group1.
- On the Settings menu, click Grouping.
...
- In the Grouping Settings
...
- dialog box, select a technology and group.
...
- Click Edit.
...
- In the Grouping Settings — Edit dialog box, in the Group text box, edit those fields for the group that need to be changed.
...
- The filter button will retrieve the data from the selected node. If all nodes was selected, the operation will be performed on all nodes and the result will be a combination of all results.
...
- Click Filter to populate the Select list with items.
To display a smaller, more focused set of items in the Select list, type a string expression that contains the character string common to all the values you want to add to the group, combined with wildcard characters, into the text box.
For example: If you define a group of login names and you want to view a list of all the login names that start with “U,” you can type the string U% (or %) in the Filter box to display only login names that start with “U.” If a specific value does not appear in the list, use the Free text box to enter the value.
...
- Use the arrow buttons to move items to the list on the right.
- To delete an item from the right list, select it and click Remove.
...
- Click OK. An existing group is edited for the group list.
Deleting a group
You can delete a group via the Grouping Settings dialog box.
To delete a group1.
- On the Settings menu, click Grouping.
...
- In the Grouping Settings dialog box, select a technology and group to remove.
...
- Click Delete.
Anchor | ||||
---|---|---|---|---|
|
PMDB data is summarized into hourly-based time units. In large environments with a high volume of transactions, the PMDB can use a lot of disk space. To reduce disk space consumption, Precise automatically aggregates hourly data into daily, weekly, and monthly data. Aggregation saves space, but it eliminates the raw details of hourly performance data. To specify the hours for which you want data maintained, use the Hour Group option.
The Hour Group option divides the week into hour groups. The default groups are day, morning, night, and weekend. During the installation process, you can create your own hour groups or change the defaults to whatever is appropriate for your environment. For example, you could define a peak hour every day between 10 AM and 11 AM.
When you have declared the hour groups you want, you can further define which performance data is collected within each hour group.NOTE
Info |
---|
Changing the hour group settings does not apply to information already stored in the PMDB. The new information will only be used for calculations that are related to future information. |
To configure hour groups1.
- On the Configuration bar, click
...
- Hour Groups.
...
- In the Hour Group Settings dialog box, do one of the following tasks:
...
- Disable the use of hour groups by clearing the Use hour group definition for calculations check box.
...
- Disabling hour groups affects the baseline calculation. Old hour groups already stored in the PMDB remain enabled.
...
- Mark an hour or a sequential set of hours with the mouse. The Hour Group Settings - Edit dialog box opens with the day and time duration set. Select the preferred hour group from your organization's hour groups as listed in the table. Each group appears in a different color.
...
- Click Edit. The Hour Group Settings - Edit dialog box opens with no day or time duration set. Specify the day of the week and the time duration you want and select the preferred hour group from your organization’s hour groups, as listed in the table. Each group appears in a different color.
...
- To change the name of a group, click Rename and type the new name in the relevant table cell.
...
- For example, to change “Customized 4” to “Peak,” select the Customized 4 row, click Rename, and type
Peak
in the name text box on the table.
...
- Click OK.
Anchor | ||||
---|---|---|---|---|
|
The Alerts, issued by Alerts, are based on information collected by Insight agents, agents of Precise products, or Report Manager agents. For most of the metrics, Alerts enables you to launch the relevant Precise product without returning to the StartPoint screen.NOTE
Info |
---|
In order to enable the Alerts settings screen, the user must have ADMIN.VIEW role permissions. |
To configure Alerts general settings1.
- On the Settings menu, click Alerts General Settings.
...
- In the Alerts General Settings dialog box, select the appropriate tab.
Setting alerts defaults on the General tab
The alert defaults affect the view of the various tables and graphs in Alerts. You can set the alert defaults to fine-tune the view according to your preferences.
The General tab includes the following parameters:•
- Display alert history over the last [hours]. This parameter affects all history table columns (in the Metric tab, Instances tab, and AppTiers table), maximum, minimum, and average counters (in the Current tab). You can set the history period up to 168 hours (week).
After modifying this parameter you must restart the Alerts FocalPoint to apply the new setting.
...
- Display only top n metrics or events. Sets the maximum number of Metrics or Events to display in the Metric viewer, Event viewer, and the Main Area of the Metric tab. Lowering the value improves the User Interface response time.
To set alerts defaults on the General tab1.
- Specify the display parameters.
...
- Click OK to save the parameters.
Setting an Email server for actions on the Email tab
The Email tab allows you to set an external email server, through which Alerts can send email actions to a specified address. The email actions are automatically triggered by alerts, after configuring email actions for a metric.
The Email tab includes the following parameters:•
- Integrate Alerts with an email server. Select this option box to enable Alerts to send email actions.
...
- Email server name or IP address. Set the mail server name or IP address. The mail server must be recognized by the network of the Precise installation.
...
- Alerts email messages should be sent by. Set the address you want to appear in the sent by field in email actions.
To set an Email server for actions on the Email tab1.
- From the Email tab, check mark
...
- Integrate Alerts with an Email
...
- server.
...
- Specify the details regarding the Email server.
Anchor | ||||
---|---|---|---|---|
|
The SNMP tab lets you set the details of an external SNMP manager that receives the metric status from Alerts through SNMP traps, and to configure a port through which you can perform SNMP Get commands. See “About About setting Alerts SNMP connectivity” on page 176connectivity.
The SNMP tab includes the following parameters:•
- Integrate Alerts with SNMP console. Select this option box to enable SNMP functionality.
...
- Server name or IP address. Set the server name or IP address of the SNMP manager.
...
- SNMP Trap Port. Set the SNMP Trap port of the SNMP manager.
...
- SNMP Trap version. Set the SNMP Trap version of the SNMP manager.
...
- SNMP Port. Set the SNMP port of the Alerts FocalPoint server that listens to the SNMP requests.
...
- SNMP Version. Set the SNMP version of the Alerts FocalPoint server that listens to the SNMP requests.
To set an SNMP server for actions on the SNMP tab1.
- From the SNMP tab, check mark
...
- Integrate Alerts with SNMP
...
- console.
...
- Specify the details of the SNMP console for receiving Alerts SNMP traps.
Anchor | ||||
---|---|---|---|---|
|
The MOM tab lets you set the details of an external MOM server that receives the metric status from Alerts. Specify the details of the MOM application server that will receive the alerts from Precise Alerts. See “About About Alerts MOM connectivity” on page 182connectivity.
The MOM tab includes the following parameters:•
- Integrate Alerts with Microsoft Operations Manager. Select this option box to enable MOM functionality.
...
- Server name or IP address. Insert the server name or IP address of the MOM server.
...
- User name. Insert the user name of the administrator on the MOM server.
...
- Password. Insert the password.
...
- Domain. Insert the domain.
To set a MOM server for actions on the MOM tab1.
- From the MOM tab, check mark
...
- Integrate Alerts with Microsoft Operation
...
- Manager.
...
- Specify the details of the MOM application server that will receive the alerts from Precise Alerts.
Anchor | ||||
---|---|---|---|---|
|
The Instances tab allows you to modify the association properties of all instances within a selected AppTier. You can associate or disassociate instances with alerts, enable or disable SNMP actions for each instance, and add a default email address for each server.
You can display instances within a specific AppTier and their general settings, by selecting it from the AppTier list box. The following table describes the properties displayed for each instance.
Table 4-4 4 Instance association tableProperties
Properties | Description |
---|---|
Instance |
...
Instance name. |
Server |
...
Indicates the server name where the instance is running. |
Alerts |
...
Reported | Indicates whether alerts are reported for the instance or not. |
...
SNMP | Indicates whether SNMP actions are enabled for the instance or not. When enabled, all the metrics that sample the instance are automatically set with SNMP actions. When disabled, all metrics that sample the instance are set with no SNMP actions. |
Default |
...
Displays the default email address of the recipient. This email address is used as a default in the email definition in the Actions tab. |
...
See |
...
...
To edit instance settings1.
- From the Instances tab, select the instance that you want to edit and then click Edit.
...
- In the Instance Settings dialog box, set the Instance properties and click OK.
In case of a busy system, to improve the system performance, you can check the Do not report alerts for this instance option box of instances that are not important to sample.
...
The Alerts, issued by Alerts, are based on information collected by Insight agents, agents of Precise products, or Report Manager agents. For most of the metrics, Alerts enables you to launch the relevant Precise product without returning to the StartPoint screen.
Info |
---|
...
In order to enable the Alerts Metrics settings screen, the user must have ADMIN.VIEW or ADMIN.UPDATE role permissions. |
To configure Alerts metric settings1.
- On the Settings menu, click Alerts Metric Settings.
...
- In the Alerts Metric settings dialog box, select the appropriate tab.
Anchor | ||||
---|---|---|---|---|
|
The Settings dialog box allows you to edit the properties of each metric that is available in your Precise environment, and the Cross-AppTiers metrics (FocalPoints, Agents, Processes, and Licenses) available in the Precise-generated ‘i3 Status’ environment. You can also add customized metrics to an AppTier (excluding the Cross-AppTiers), or delete customized metrics.
To edit a metric setting for one or all instances, from an AppTier (or Cross-AppTier) of the same technology1.
- From the AppTier list box, select the required AppTier (or Cross-AppTiers). The table in the Settings tab displays all the metrics and their metric set.
...
- From the Metrics table, select the required metric.
...
- Click Edit.
If you click Edit according to the instructions above, you next need to edit the metric properties. See “Editing metric properties” on page 65 Editing metric properties.
To add a customized metric to an AppTier of the same technology1.
- From the AppTier list box, select the required AppTier. The table in the Settings tab displays all the metrics and their metric set of the selected AppTier.
...
- Click Add.
If you click Add according to the instructions above, you next need to create a customized metric. See “Creating customized metrics” on page 63. Creating customized metrics.
Anchor | ||||
---|---|---|---|---|
|
Alerts allows you to monitor any performance aspects using pre-defined metrics for each AppTier. For data that is not collected by any of the pre-defined metrics, you can create new customized metrics. (Only users with Administrator privilege are allowed to define customized metrics.)
For example, you can create a customized metric that uses a UNIX shell that collects data about the memory size allocated for specific processes (in this case, the metric type is Table because it collects multiple values). The metric will return the data by using a host script. Alerts will display the collected data as a list in the Current tab. The History tab will display the processes behavior over time. The Events tab will trace the alert levels produced by this metric including its failures (Not Sampled status).
When creating a customized metric, it is associated with all instances of an existing AppTier. The customized metrics are part of the Customized set. You can also edit the Thresholds, Sampling, and Actions for each customized metric individually.
Info |
---|
...
To support customized metrics that use scripts in Precise servers, Alerts InformPoint must be installed. If InformPoint is not automatically installed on the specific server where you want to run customized metrics, you can install InformPoint on that particular server manually. Use the Agent Installer's Servers screen to install the InformPoint. For more information, see the Precise Installation Guide. |
See “About About creating customized metrics” on page 184metrics.
To create a customized metric1.
- On the Precise bar, click Settings>Alerts Metric Settings.
...
- Select the Settings tab. From the AppTier list box, select the AppTier for which you want to create the customized metric (Cross-AppTiers cannot include customized metrics).
...
- Click Add.
...
- On the Metric Properties dialog box, in the Metric name text box, type a name for the new metric.
...
- From Sample this metric by running options, select either stored procedure or executable file.
...
- In the Executable/Stored procedure textbooks, type the command line that runs the required stored procedure or executable file.
...
- In the Metric's response type option, select the metric type, either single value or item list (multiple values).
...
- If necessary, select Alert when value drops below the designated thresholds and click Save.
...
Select the Description tab. In the Description box, type a description of the new metric and click Save.
...
Info To move from one tab to the next you must first save the changes made in the previous tab.
...
- Edit the settings of the customized metric in the remaining tabs (Scheduling, Thresholds, Actions, and Customize) as required. Click Save after editing each tab's settings.
...
- Click Close. The new customized metric is created.
To delete a customized metric from an AppTier1.
- On the Precise bar, click Settings>Alerts Metric Settings. The Settings dialog box opens.
...
- Select the Settings tab.
...
- On the Settings tab, from the AppTier list box, select the AppTier for which you want to delete the customized metric.
...
- From the Metrics list, select the metric you want to delete (only metrics of the Customized set can be deleted).
...
- Click Delete.
Enabling and disabling metrics on the Activities tab
In the Activities tab, you have quick customization options to enable or disable metrics. These operations can also be performed in the settings tab of this dialog, except the focus in the settings tab is on only enabling or disabling metrics.
To disable all metrics for all instances of all environments1.
- From the AppTier list box, select the required AppTier (or Cross-AppTiers). The table in the Activities tab displays all the enabled metrics and their metric set.
...
- Click Disable all metrics.
...
- Click Save to save the settings.
To enable an Availability metric for all instances of all environments1.
- From the AppTier list box, select the required AppTier (or Cross-AppTiers). The table in the Activities tab displays all the enabled Availability metrics and their metric set.
...
- Click Enable Availability metrics.
...
- Click Save to save the settings.
To enable/disable metrics from the various sets for a specific instance1.
- Select the Environment, AppTier, and instance.
...
- Check any metric to enable it, or uncheck any metric to disable it.
...
- Click Save to save the settings.
Copying metric properties on the Copy Metric Settings tab
Metric settings you set on the Activities tab, or in the settings tab, can be copied to other instances using the Copy Metric Settings tab. To copy the settings to other instances, follow the steps as given on the Copy Metric Settings tab.
To copy metric properties on the Copy Metric Settings tab:1. Under “Source Definitions”
- Under Source Definitions, select the Environment, AppTier, and Instance you want to copy.
...
- On the table, check mark the metrics you want to copy.
...
- Check mark the settings group you want to copy.
...
- Under Destination Instances, click Populate destination Instances.
...
- On the table, check mark the destination instance(s).
...
- Click Execute to copy the selected metric settings.
Anchor | ||||
---|---|---|---|---|
|
You can edit the properties of each metric that is available in your Precise environment, including Cross-AppTiers metrics, such as: FocalPoints, Agents, Processes, and Licenses.
Alerts issues alerts according to the metric properties, which must be adjusted to your individual environment and organization preferences. The metric definitions must be accurate and adequate. Sampling frequencies and periods require careful considerations. Thresholds need to be set in accordance with the performance level you want to meet.
In addition, alerts must reach the relevant personnel, or in severe cases, management representatives immediately and regardless of their location. Subsequently, the threshold-exceeding values must be examined.
Alerts enables you to adjust the metric definitions through the Metric Properties dialog box.
If you had previously selected Edit or Add for alerts metric settings on the Settings tab, you next need to edit the metric properties.
The Metric Properties dialog box includes the following tabs:•
- Description
...
- Scheduling
...
- Threshold
...
- Actions
To edit metric properties for one or all instances, from an AppTier (or Cross-AppTier) of the same technology•
- In the Settings tab, click Edit or Add.
...
- See
...
...
- tab.
...
- Click the appropriate settings tab (Scheduling, Threshold, or Action)
About setting metric sampling properties on the Scheduling tab
Alerts copies the scheduling settings for the source instance.
To set the metric sample properties1.
- From the Metric Properties dialog box, select the Scheduling tab.
...
To set the sampling rate, in the Sample metric every <...> boxes, set the time (day, hours, and minutes) to the frequency, in which you want Alerts to sample the metric. If you do not want to sample this metric, select the Disable metric sampling radio button.
...
Info Time slice metrics’ sampling parameters are usually disabled for editing.
...
To modify the sampling base, in Start sampling at <...> boxes, set the time (day, hours, and minutes) in which Alerts starts to sample the metric (the day parameter is available in case the sampling rate is a week and above). The default is: Sunday, 00:00 AM.
Info
...
These sampling parameters are useful for metrics whose sampling rate is once a day or more. For example, if sampling every 24 hours (1 day), the metric will be sampled every midnight. For sampling it at 3:00 am, change the time parameters to 3:00.
...
- In the Analyze metric over the last <...> boxes, set the sampling period for which you want to analyze the metric.
...
- The Sampling period is the time frame for retrieving statistical data from the monitored product. The sampling period is used only in metrics that return statistics for a period of time.
...
- To sample the metric during downtime period, check Sample this metric even during downtime.
...
- If the metric monitors an important performance aspect, check This is a key metric.
...
- Critical alerts related to a key metric are indicated by an exclamation point.
Anchor | ||||
---|---|---|---|---|
|
Alerts defines “copy threshold settings” from the source instance.
The Thresholds tab allows you to define your performance requirements, and to ignore or consider specific items or conditions. Alerts will then be issued logically and according to your specific configuration.
Because some alerts are calculated based upon total instance running time, a false alert may sometimes be issued. For example, assume the Top Programs sub-metric of the Top Activities metric for SQL Server AppTier is assigned a 10% Near-Critical threshold and a 20% Critical threshold. If a program runs only 10 seconds during the time slice and there are no other programs running on the instance, it will issue a false alert because it exceeds the defined threshold (10 seconds out of a total running time of 10 seconds is 100% of instance running time). This occurs though the program ran for only 1.1% of the time slice total time [10 seconds/(60 seconds x 15 min)]. This false alerts issue is resolved by using a Minimum value setting defined on the Thresholds tab of the Metric Properties dialog box.
The Minimum value setting is a minimum value in seconds of MS-SQL time below which an alert will not be issued. Suppose you do not want to issue an alert for the Top Programs sub-metric if it does not reach 15% of the MS-SQL time. You would then set a Minimum value of 135 seconds (15 min time slice x 60 seconds/min x 15%). No alarm will be issued until the defined minimum value is exceeded.
Info |
---|
...
Minimum value is only relevant for list metrics whose unit value is given as a percentage. |
Alerts comes with a default set of thresholds defined to suit general needs. You should tune these thresholds, as required, in relation to the setup and definitions of your environment.
There are two types of metrics:•
- Single value metrics. These are metrics that collect only a single value. An alert is issued when its value exceeds the predefined threshold (for example the Availability metric). Parent Single Value metrics include sub-metrics (child metrics). Each child metric has its own thresholds and may be enabled or disabled individually (for example the General Behavior metric).
...
- List metrics. These are metrics that collect a dynamic list of items identifying each item by its description and value (for example the Locked sessions metric). Parent List metrics include sub-metrics (child metrics). Each child metric has its own thresholds and may be enabled or disabled individually (for example the Top Activities metric).
To edit a Sub-Metrics threshold1.
- From the Metric Properties dialog box, select the Thresholds tab.
...
- Select the sub-metric you want to edit.
...
- Click Edit.
...
- In the Metric Properties - Edit thresholds dialog, enter the required value in the Critical Threshold and Near-critical Threshold text boxes.
...
- To consider only specific items when sampling data, include them in the Include list text box.
...
- To ignore specific items when sampling data, include them in the Exclude list text box.
When entering list items, verify that they are separated by a semicolon. Use the percent sign (%) as a wildcard. For example, Alerts%; %Alerts; %Alerts%.
...
- To disable a sub-metric, clear the check mark in the Enable Sub-Metric checkbox. If a List metric type, a disabled sub-metric will not be sampled. If a Single value metric type, a disabled sub-metric will be sampled (retrieve a value), however, this will not generate an alert (the sub-metric will always be green).
...
- Click OK. Repeat steps 2 through 7 for each sub-metric to be defined.
...
- In the Minimum value <...> text box at the bottom of the Threshold tab dialog, enter the minimum value necessary for Alerts to consider the item.
...
- To save your definitions, choose whether to save them either for the selected instance, or for all the environments” instances. Then click Save and Close.
About metric properties for Action settings
Alerts copies the action settings from the source instance. Alerts provides the following action types when an alert is raised:•
...
- Message Box
...
- Program
...
- SNMP
...
- MOM
See “About About metric properties for Action settings” on page 170. See “About settings, About setting Alerts SNMP connectivity” on page 176. See “About Alerts MOM connectivity” on page 182connectivity, and About Alerts MOM connectivity.
Anchor | ||||
---|---|---|---|---|
|
...
- Report also when one or more instances are not loading data into the PMDB.
- Report also when the status of one or more agents agent is “Stopped”Stopped.
The default Refresh Rate setting is 15 minutes and this amount can be changed.
Precise. Performance intelligence from click to storage. Learn more > >
...
...