Apache HTTP Server Management Pack for System Center – Operations Manager
Supported ConfigurationsSupported Versions of Apache HTTP ServerVersion 2.2 Version 2.4 Supported Installations of Apache HTTP ServerApache HTTP Server installations are discovered and supported for monitoring when:Apache HTTP Server was installed from a package provided by the Linux distribution vendor (i.e. from the distribution repository)Apache HTTP Server was compiled and installed from source, using the default file and directory locationsSupported Operating SystemsAll versions of Linux supported by the current version of Operations ManagerPrerequisitesThe System Center Linux agent must be installed on the managed computer. For agent prerequisites, see: Supported UNIX and Linux Operating System Versions (http://go.microsoft.com/fwlink/?LinkID=244214) Files in this Management PackThe following table describes the files that are included in this management pack:
Management Pack PurposeThe Apache HTTP Server Management Pack provides both proactive and reactive monitoring of Apache HTTP Server running on managed Linux computers. The monitoring provided by this management pack includes availability and configuration monitoring, performance data collection, and default thresholds. You can integrate the monitoring of Apache HTTP Server components into your service-oriented monitoring scenarios. In addition to health monitoring capabilities, this management pack includes reports, diagnostics, tasks, and views that enable near real-time diagnosis and resolution of detected issues. For details on the discoveries, rules, monitors, views, and reports contained in this management pack, see Appendix: Management Pack Contents. Monitoring Scenarios
Configuring the Apache HTTP Server Management PackThis section provides guidance on configuring and tuning this management pack. Best Practice: Create a Management Pack for Customizations Deploying and Enabling the CIM Provider Tuning Performance Threshold Monitors Best Practice: Create a Management Pack for CustomizationsBy 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 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 “AIX 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.
The Apache CIM provider package is automatically deployed during the installation of the Linux agent Operations Manager, if Apache HTTP Server is detected at that time. This detection and automatic installation occurs when installing the Linux agent for the first time on a computer, and it also occurs when upgrading a previous agent version to the current version. If the Apache HTTP Server is installed to the Linux computer after the Operations Manager agent is installed, the CIM Provider can be manually installed through the following mechanisms: Installing the Apache CIM Provider: Copy the appropriate “scx” installation bundle to the target computer. The available packages can be found on the Management Server in the Operations Manager program files directory, under \Server\AgentManagement\UnixAgents\DownloadedKits. For example, an Ubuntu 14.04 x64 server would require the scx-1.6.0- Run the installation package with the --upgrade --force switches. This will reinstall the package but not modify any existing configuration customization:
The “scx” installation bundle contains .rpm or .deb packages for OMI and the Operations Manager agent providers, as well as bundles for additional software monitoring, such as Apache HTTP Server. If you prefer to install the CIM Provider with native package managers such as RPM or DPKG, you can extract the bundle to access the .rpm or .deb packages:
Enabling the CIM Provider In order to enable monitoring, the apache-cimprov module must be loaded into the Apache HTTP Server configuration (and the Apache HTTP Server must be restarted). Operations Console tasks and a script on the Linux computer are provided to simplify this configuration. Enabling the CIM Provider from Operations Console In the Apache HTTP Servers view, select the Apache server that you wish to manage and run the Load Monitoring Module task. To unload the module, run the Unload Monitoring Module task. These tasks will restart the Apache HTTP Server. Note: when the apache-cimprov module is unloaded, it will remain in a monitored state until OMI server is restarted and the periodic management pack discovery or Update Discovered Properties task is run. Enabling the CIM Provider from the Linux Computer To enable the CIM Provider, run the apache_config.sh script with the “-c” argument:
To disable the CIM Provider, run the apache_config.sh script with the “-u” argument
Note: when the apache-cimprov module is unloaded, it will remain in a monitored state until OMI server is restarted and the periodic management pack discovery or Update Discovered Properties task is run. Automating Loading of the Apache Module Note: loading of the apache-cimprov module will restart the Apache HTTP Server and will cause a brief period of unavailability for the web server. The Management Pack task to load the apache-cimprov module can be run with PowerShell. This is useful for automating the deployment. The example script below illustrates use of the Start-SCOMTask cmdlet to invoke the Management Pack task for instances of Apache HTTP Servers that do not have the Apache module loaded.
Required Access for CIM Provider InstallationRun As AccountThe Run As Account used for the Load and Unload Apache Module tasks is the Run As account associated the UNIX/Linux Privileged Account Run As Profile for the Linux computer. Sudo Configuration In order to use the sudo elevation to load or unload the Apache module with the Management Pack task, the configuration script must be authorized for sudo elevation (without password) for the user account in /etc/sudoers. The following example illustrates the command requiring authorization.
Upgrading the CIM Provider to a new versionThe CIM Provider will be upgraded automatically to the latest available version when upgrading the Linux agent for Operations Manager to the latest available version. Enabling Remote HTTP MonitoringThe Apache HTTP Server includes several optional rules and monitors that implement remote monitoring of the web sites hosted on the Apache server. Remote monitoring of web site availability and performance can offer additional insights into the end-to-end health of the web server environment. Each of these remote monitoring rules and monitors is disabled by default. In order to use them, they should be enabled with overrides. Because the Virtual Host configuration on the Linux computer may not have complete information necessary to remotely access the website (such as proxy configuration, URL, authentication, etc), be sure to override the configuration of the rule or monitor to supply required configuration as well. The remote monitoring rules and monitors are: Monitors: Apache Virtual Host Web Request Status Code Apache Virtual Host Web Request Total Response Time Rules Apache Virtual Host Total Web Response Time Collection For information on configuration of overridable properties for these remote HTTP probe rules and monitors, reference the documentation for the Microsoft.SystemCenter.WebApplication.UrlProbe probe action module type. Tuning Performance Threshold MonitorsThe 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.
Katalog: ContentLibrary ContentLibrary -> Windows 8 Client Management Pack Guide ContentLibrary -> Microsoft® fast™ Search Server 2010 for SharePoint® Management Pack Guide for Operations Manager 2007 Download 180.05 Kb.
|
Bosh sahifa
Aloqalar Bosh sahifa Apache HTTP Server Management Pack for System Center – Operations Manager
|