In this section: |
Resource Governor Usage Monitoring facility allows you to monitor requests as they are submitted by users, and logs information about request usage. This information includes the usage statistics associated only with data retrieval or data manipulation in the case of MODIFY or MAINTAIN. This request information is stored in Resource Governor Usage Monitoring tables. You can specify the Monitor Preference, which allows you to change what information is collected for monitored data sources.
The Web Console enables you to administer Resource Management.
You can:
Access to these tasks is provided by the Resource Management link on the toolbar.
The following image shows the hierarchical navigation menu that is available when the Resource Management link is selected.
In this section: |
The Resource Management ribbon provides options for configuring Resource Management, as shown in the following image.
The following sections provide detailed explanations for each option in the ribbon.
Note: You can also access these options by right-clicking Resource Management - Active/Inactive in the navigation pane.
When you enable Resource Management, it automatically turns on monitoring. However, you can disable and re-enable monitoring at any time.
The reporting server will write all information regarding monitored sources to a log file. This log file is then archived to the Resource Management repository at predetermined intervals or limits, while the server is running. The current log is also archived when the server starts or when the administrator submits a job from the Web Console of a running server.
The intervals or limits can be configured from the Logging Properties option in the Resource Management Web Console. When configured, the log file of an active server will be archived based on the maximum number of sessions and/or the days set or based on a scheduled job configured by the administrator.
Note: Logging properties can also be set under the Workspace, Logs and Traces, Resource Management Logs option from the Web Console main menu bar.
Logging properties can be configured in the Resource Management Web Console. When configured, the log files will be archived based on the maximum number of sessions and days set or based on a scheduled job configured by the administrator.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Logging Properties.
The Resource Management Logging Properties window opens, as shown in the following image.
The following options are available:
The number of archived files kept. The default value is 10.
The number of sessions recorded in the active log file before the log is archived and a new log is started. The default value is 10000.
The number of days an active log file is kept open before it is archived and a new log is started. The default value is 1.
When set to No, automatic archiving is active and based on the two settings above.
When set to Yes, only the rmlog_history_entry is shown and the administrator has to configure the schedule archive settings. Selecting Yes will cause a restart of the server and you will need to schedule the archive job.
After the server restarts, the web console will refresh. Click the Resource Management option on the toolbar. Right-click Resource Management - Active/Inactive in the navigation pane and select Logs.
Select Schedule Save log job. The Manage Schedule pane opens. Select the Schedule the procedure check box to see additional options. The recommended schedule settings are as follows:
When this option is selected, a context menu is shown with the following options:
These give the administrator the option to archive the current log file (a new log file is automatically started), as well as view previous archive jobs including any that were submitted due to server restart, and any of the intervals or limits mentioned above having been reached.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Archive, and then select Submit Archive job.
The Select an Option dialog box opens, as shown in the following image.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Archive, and then select View Archive jobs.
The Deferred List opens showing the saved logs, as shown in the following image.
Select this option to show a list, if any, of previous log files that have not been archived.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select List Unarchived.
The Resource Management Unarchived logs list opens listing the non archived logs, as shown in the following image.
Repository data can be deleted once it has been used or reported on. This deletion can be by date range or, if sufficient data has been stored, the data can be deleted if it is more than one, three, or six months old.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Maintenance, and select Submit Maintenance job.
The Resource Management Repository Maintenance pane opens, as shown in the following image.
Note: If the range of data is older than one month, the options on the Repository Maintenance pane will be slightly different than shown in the above image.
Note: Caution should be used when using this utility. Make sure you have a backup of the data before you proceed.
The Submit Repository Maintenance Job window opens.
A Deferred Execution pane opens confirming your request.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Maintenance, and select View Maintenance jobs.
The Deferred List pane opens, as shown in the following image.
The Configuration command has the following options:
These give the administrator the option to see current configuration settings, as well as change the viewable application directories, perform migration, change a license key, and remove the current Resource Management configuration.
Setting monitor properties enables you to select global settings and the component levels to be monitored. Components are split into two categories, Procedure and Command. The information that Resource Governor monitors is stored in the Usage Monitoring tables. The default settings are: Global Data request Monitoring set to off and component level set to Command. Session records are always captured.
To set Resource Management Properties:
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Configuration, and select Properties.
The Resource Governor Properties page opens, as shown in the following image.
Note: By default, all options are selected except Reference Field.
The Resource Governor Properties pane has the following options:
The date that Resource Management was configured or reconfigured.
The repository that is being used.
The data adapter connection of the current configuration.
The owner/schema name for the relational adapter that Resource Governor will use to create the repository tables.
The number of application data sources and relational pass-thru data sources that have been enabled for monitoring. This will show Global monitor enabled if Data Request Monitoring is On. See the Global Settings section below for more information.
The number of application data sources and relational pass-thru data sources that have been disabled by setting the monitoring setting to OFF.
The number of procedures that have been excluded from monitoring.
The date the repository was modified using the Repository Maintenance page.
The last time the repository updated to include data from a log file.
For more information on the other settings on this page, see How to Configure Resource Management Using a FOCUS or Relational Repository.
You can configure the application path to set the viewable directories for Resource Governor.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Configuration and select Configure Application Path.
The Application Path pane opens, as shown in the following image.
For more information on how to migrate Resource Management, see Migrating the Resource Management Repository.
A license key is required to run Resource Governor. You can change the license key you are using from within Resource Management at any time.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Configuration, and select Change License Key.
The Resource Management Configuration pane opens showing your current license, as shown in the following image.
You can remove Resource Management from the server from the Resource Management Configuration pane. This is required if you want to change the repository type from FOCUS to relational, or relational to FOCUS.
or
From the navigation pane, right-click Resource Management - Active/Inactive, select Configuration, and select Remove.
The Resource Management Confirmation pane opens.
In this section: |
When you right-click the Resource Governor node, a context menu is available, as shown in the following image.
The following sections provide detailed explanations for each option in this context menu.
Setting monitor properties enables you to select global settings and the component levels to be monitored. Components are split into two categories, Procedure and Command. The information that Resource Governor monitors is stored in the Usage Monitoring tables. The default settings are: Global Data request Monitoring set to Off and component level set to Command. Session records are always captured.
For more information on setting monitor properties, see Setting Monitor Properties.
Repository data can be deleted once it has been used or reported on. This deletion can be by date range or, if sufficient data has been stored, the data can be deleted if it is more than one, three, or six months old.
For more detailed information on how to work with Repository Maintenance, see Working With Repository Maintenance.
In this section: |
When you right-click an application directory, a context menu is available, as shown in the following image.
The following sections provide detailed explanations for each option in this context menu.
Monitoring Data Sources can be set at the Application level to monitor all Data Sources or at the individual level.
The Properties for Application pane opens.
The Properties for Application Pane pane has the following fields/options:
Is the date the synonym was first accessed.
Is the date the synonym was last accessed.
The number of data sources with monitoring on.
The number of data sources with monitoring off.
The number of data sources not being monitored.
The total number of data sources in the selected application directory.
The number of procedures with monitoring on.
The number of procedures with monitoring off.
The total number of procedures in the selected application directory.
For more information on setting monitor status, see How to Set Monitor Status at the Application Level.
Data sources in an application can have monitoring turned on or off at the application level. When On is selected, the Usage Monitor will collect information about all requests for all data sources in the application. When Off is selected, no monitored data for data sources in the Application is collected.
If Application monitoring has never been used, the Monitor Status will be Not Set. This is the default value.
To set monitor status for an application:
The Properties for Application pane opens.
When you right-click an application directory and select Manage Monitoring, a context menu is available, as shown in the following image.
Data sources must be monitored to provide monitor data, which can then be used to analyze performance.
The Add Data Sources to Monitor pane opens to display all synonyms in the selected application directory, as shown in the following image.
The Add Data Sources to Monitor - Status pane opens displaying the selected data sources with monitoring enabled, as shown in the following image.
The data sources you selected now appear in the tree, as shown in the following image.
You can remove a data source from being monitored as follows.
A confirmation window opens, as shown in the following image.
Note: You can monitor Data Sources at the application level and then use the Remove Data Sources from Monitor option to exclude individual Data Sources within the application that you do not want to monitor.
By default, all Application Data Source procedures are monitored. You can remove a procedure from being monitored as follows.
A list of available procedures opens.
The Remove Procedures from Monitor - Status pane opens, confirming that the selected procedure was removed.
To have the ability to add procedures, they will need to be removed from monitoring first. For more details, see How to Remove a Procedure From Being Monitored.
The Add Procedures to Monitor pane opens to display all procedures in the selected application directory, as shown in the following image.
The Add Procedures to Monitor - Status pane opens displaying the selected procedures with monitoring enabled, as shown in the following image.
The procedures you selected now appear in the tree under the selected application directory.
In this section: |
When you right-click a relational adapter folder, a context menu is available, as shown in the following image.
The following sections provide detailed explanations for each option in this context menu.
Note: If there is only one connection name available, the properties for that connection will be shown immediately.
The Properties for Relational Adapter for the selected connection pane opens, as shown in the following image.
The Properties for Relational Adapter pane has the following fields/options:
Allows you to select the connection name from the drop-down menu.
Is the date the relational adapter was first accessed.
Is the date the relational adapter was last accessed.
The number of data sources with monitoring on.
The number of data sources with monitoring off.
The number of data sources not being monitored.
The total number of data sources in the selected application directory.
The number of procedures with monitoring on.
The number of procedures with monitoring off.
The total number of procedures in the selected application directory.
When you right-click a relational adapter and select Manage Monitoring, a context menu is available, as shown in the following image.
In the example shown, the MS SQL Server is the adapter selected for relational source monitoring.
Monitoring relational data adapter sources means monitoring SQL direct passthru requests to relational sources that do not use synonyms. Relational sources must be monitored to provide monitor data, which can then be used to analyze performance or govern usage.
Note: The following procedure can only be done if a relational adapter has been configured.
To monitor relational sources:
The Add Data Sources to Monitor pane opens, as shown in the following image.
The Add Data Sources pane opens, as shown in the following image.
The Add Data Sources pane reopens displaying the selected data sources with monitoring enabled.
You can remove a data source from being monitored as follows.
A confirmation window opens.
By default, all relational procedures are monitored. You can remove a procedure from being monitored as follows.
The Remove Procedures from Monitor pane opens, as shown in the following image.
The Remove Procedures from Monitor pane opens, showing the list of available procedures.
The Remove Procedures from Monitor - Status pane opens, confirming that the selected procedure was removed.
To have the ability to add procedures, they will need to be removed from monitoring first. For more details, see How to Remove a Procedure for a Relational Adapter From Being Monitored.
The Add Procedures to Monitor pane opens.
The Add Procedures to Monitor - Status pane opens displaying the selected procedures with monitoring enabled, as shown in the following image.
WebFOCUS |