Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: System Center 2012 - Operations Manager
This section provides guidance on configuring and tuning this management pack.
Best Practice: Create a Management Pack for Customizations
Security Configuration
Tuning Performance Threshold Rules
By default, Operations Manager saves all customizations such as overrides to the Default Management Pack. As a best practice, you should instead create a separate management pack for each sealed management pack that you want to customize.
When you create a management pack for the purpose of storing customized settings for a sealed management pack, it is helpful to base the name of the new management pack on the name of the management pack that it is customizing, such as “SUSE Linux Enterprise Server Customizations”.
Creating a new management pack for storing customizations of each sealed management pack makes it easier to export the customizations from a test environment to a production environment. It also makes it easier to delete a management pack, because you must delete any dependencies before you can delete a management pack. If customizations for all management packs are saved in the Default Management Pack and you need to delete a single management pack, you must first delete the Default Management Pack, which also deletes customizations to other management packs.
Run As credentials are used for all rules and monitors in the SUSE Linux Enterprise Server Management Pack. More information on required privileges and configuration of Run As credentials can be found in Accessing UNIX and Linux Computers in Operations Manager.
Run As Profile Name | Associated Rules and Monitors |
---|---|
UNIX/Linux Action Account |
All rules and monitors other than those specified with the UNIX/Linux Privileged Account |
UNIX/Linux Privileged Account |
All syslog alerting rules |
The following table lists performance threshold monitors that have default thresholds that might require additional tuning to suit your environment. Evaluate these monitors to determine whether the default thresholds are appropriate for your environment. If a default threshold is not appropriate for your environment, you should obtain a baseline for the relevant performance counters, and then adjust the thresholds by applying an override to them.
Monitor Name | Default Threshold | Default Repeat Count |
---|---|---|
Logical Disk Free Space |
Critical: 5%, 1000MB |
1 |
Logical Disk % Free Space |
5 |
1 |
Logical Disk % Free Inodes |
5 |
1 |
Logical Disk Avg. Disk sec/Transfer |
.05 |
5 |
Operating System Total Percent Interrupt Time |
10 |
3 |
Operating System Total Percent DPC Time |
15 |
3 |
Operating System Total Percent Processor Time |
95 |
3 |
Operating System Available MBytes |
2.5 |
3 |
Operating System Available MBytes Swap |
2.5 |
3 |
Physical Disk Avg. Disk sec/Transfer |
.05 |
5 |
Processor Percent Processor Time |
95 |
3 |