Page History
...
| Icon | Name | Description |
|---|---|---|
 | Back | During a work session, Precise products keep track of where you have navigated to. The Back, Forward, and History buttons enable you to navigate between previously visited views. The Back control displays your previous view. |
 | Forward | Enables you to navigate to the next view. This button is only enabled if you clicked Back, or if you chose a history option. |
 | Stop | Stops a request for information from the server. |
 | Refresh | Updates the data currently displayed. |
 | Home | Navigates to the highest level entity, usually the instance or AppTier (all instances). The time frame settings remain the same. |
 | Send | Opens new email message in your email program with the link to the current environment in context. |
 | Help | Opens the online help in context. |
 | Favorites | Enables you to add or remove favorites in your Precise Favorites list. See Adding, viewing, and deleting Favorites on page 15. |
 | Settings | Lets you define Precise settings in StartPoint. See Launching StartPoint on page 18. |
About the Print function
...
- Click Print on the Precise bar.
- In the Print Option dialog, select the area(s) of the screen you want to print or save.
- Click OK.
- On the resizable preview screen, the dashed line on the right indicates the right margin. Change table column widths to ensure the information you want to print or save is within this margin.
- Click the Print or Save icon at the top right-hand side of the screen, follow the displayed dialog box instructions and click Print or OK.
| Anchor | ||||
|---|---|---|---|---|
|
The Favorites function allows you to save a specific location in Precise and to retrieve the same location later without having to navigate to it. For this purpose, a friendly user interface similar to the familiar Favorites option in the Internet Explorer has been implemented.
...
- Right-click the graph.
- Select Export to ASD Portlet.
- Insert a name in the name field that clearly describes the graph view.
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
StartPoint can be launched via AdminPoint.
...
The amount of partially filtered rows depends on the number of different combinations of values of the protected identifiers. To control the amount of partially filtered rows, version 8.5 introduced Two-phase filtering.
| Anchor | ||||
|---|---|---|---|---|
|
This filtering mechanism works as follows:
...
This way we can protect our most important identifier and at the same time avoid flooding the PMDB with low values of that identifier.
| Anchor | ||||
|---|---|---|---|---|
|
Products that consider Service Time (Avg) as more important than Service Time (Summed) and also use Service Time (Avg) as the default sort field have additional considerations.
...
Precise for Oracle uses the Two phase filtering technique as follows:
- Program. After the first aggregation phase, all records that are not part of the top 300 are partially filtered by protecting all programs, modules, and users. All other identifiers are converted to _I3OTHER_ and then the second aggregation phase takes place. The partially filtered records compete with the original top 300 records. When an ERP extension is installed, the user is overridden by the ERP user. In this case it will not protect the user any more. If many SAP users executed the same SAP transaction, after second aggregation phase all of them will be aggregated into one record. So, this protected SAP transaction is promoted and may make it into the top 300 programs.
- Statement. After the first aggregation phase, all records that are not part of the top 500 are partially filtered by protecting all statements and execution plans. All other identifiers are converted to _I3OTHER_ and then the second aggregation phase takes place. The partially filtered records compete with the original top 500 records.
...
Precise for SQL Server and Precise for Sybase implement a similar top n filtering mechanism. Both technologies generate and filter only one set of records: each record contains a combination of database, user, program, login, machine, statement, and batch.
The Two-phase filtering technique is used as follows:
...
As specified above, by default only top 500 statements will be loaded. To change the default: go to AdminPoint>Warehouse>Processes and select Load Data process of the SQL Server or Sybase technology>Parameters.
Web
Precise for Web has both pre-aggregation and post-aggregation filtering.
...
For each of the two sets you can configure the maximum number of rows to be loaded. Top records will be loaded based on a formula that weights both average service time and number of executions as described in Ranking formula.
By default, top 1000 URL records and top 100 Page records will be loaded each 15 minutes. In both sets, the weight of executions is MEDIUM. If you want to focus on the worst average response time, change the weight of executions to LOW. If you want to focus on the top resource consumers, change the weight of the executions to HIGH.
...