Changing the automatic monitoring of users and processes
PATROL for Microsoft SQL Server automatically monitors processes that are blocking other processes and processes that are idle. The MonProbUsers, BlockerProcs, and IdleProcs parameters monitor resources used by processes or users and check for processes that are blocking other processes and idle processes. BMC PATROL provides menu commands that enable you to change the automatic monitoring settings in the following ways:
- Turning auto user monitoring off and on
- Changing the blocked detection time
- Changing the idle detection time
- Enabling and disabling blocked process and idle process monitoring
- Changing the problem alert method used by the MonProbUsers, BlockerProcs, and IdleProcs parameters
- Excluding specific users or processes from monitoring
Turning auto user monitoring off and on
Turning auto user monitoring off stops the MonProbUsers collector parameter from detecting and collecting information about idle or blocking processes, which stops the IdleProcs and BlockerProcs parameters from going into an alarm state.
You can turn Auto User Monitoring off or on by using the KM Commands > KM Admin > User Monitoring Admin > Configure Auto User Monitoring menu command from the Server application menu.
Changing the blocked detection time
In PATROL for Microsoft SQL Server, a blocking process is a process that blocks other users for at least the minimum amount of time configured for blocked detection time. The default blocked detection time is 3 minutes. You can change it at any time.
You can change the blocked detection time for all users and processes from the Server application pop-up menu by using the KM Commands > KM Admin > User Monitoring Admin > Configure Auto User Monitoring menu command.
You can change the blocked detection time for a specific user or process from the Users application pop-up menu by using the KM Commands > KM Admin > Change Local Defaults > Blocked Detection Time menu command. However, once that user instance is deleted, the blocked detection time for that user or process returns to the amount of time set in the Configure Auto User Monitoring dialog box.
Changing the idle detection time
In PATROL for Microsoft SQL Server, an idle process is a process that has not been active for at least the minimum amount of time configured for idle detection time. The default idle detection time is 20 minutes. You can change it at any time for all users and processes or for a specific user or process.
You can change the idle detection time for all users and processes from the Server application pop-up menu by using KM Commands > KM Admin > User Monitoring Admin > Configure Auto User Monitoring menu command.
You can change the idle detection time for a specific user or process from the Users application pop-up menu by using the KM Commands > KM Admin > Change Local Defaults > Idle Detection Time. However, once that user instance is deleted, the idle detection time for that user or process returns to the amount of time set in the Configure Auto User Monitoring dialog box.
Enabling and disabling blocked process and idle process monitoring
To enable or disable monitoring of blocked or idle processes, you can enter configuration variables for idle and blocked process monitoring through the PATROL Console for Windows or by using PATROL Configuration Manager. For information about how to add pconfig variables, see Adding or modifying pconfig variables manually.
For idle processes, the configuration variable should appear as follows:
/MSSQLServer/ AgentHostName /idle_procs_monitoring_enabled
Setting the value of this pconfig variable to 0 (zero) disables idle process monitoring. Setting this pconfig variable to any other value enables idle process monitoring.
For blocked processes, the configuration variable should appear as follows:
/MSSQLServer/ AgentHostName/blocked_procs_monitoring_enabled
Setting the value of this pconfig variable to 0 (zero) disables blocked process monitoring. Setting this pconfig variable to any other value enables blocked process monitoring.
Changing the problem alert method used by the MonProbUsers, BlockerProcs, and IdleProcs parameters
By default, a blocking process or idle process does not create a Users application icon. By default, the BlockerProcs and IdleProcs parameters provide a report if the MonProbUsers collector parameter detects a blocking or idle process. You can change the default so that the MonProbUsers collector parameter generates a Users application icon for each idle process and blocking process it detects.
You can change the problem alert method from the Server application pop-up menu by using the KM Commands > KM Admin > User Monitoring Admin > Configure Auto User Monitoring menu command.
The recovery actions generated by the MonProbUsers, BlockerProcs, and IdleProcs parameters are also effected by the changes made using the ARA settings menu command. For more information, see Using automatic recovery actions.
Excluding specific users or processes from monitoring
By default, the sa, probe, repl_publisher, and repl_subscriber logins and their processes are excluded from the automatic monitoring feature, but you can include these logins or exclude other logins from monitoring at any time.
You can exclude or include logins from monitoring from the Server application pop-up menu by using the KM Commands > KM Admin > User Monitoring Admin > Exclude Specific User menu command.