• Contents Contents
  • Apache HTTP Server Management Pack Guide
  • Guide History
  • Supported Configurations
  • Apache HTTP Server was installed from a package provided by the Linux distribution vendor (i.e. from the distribution repository)
  • All versions of Linux supported by the current version of Operations Manager
  • Files in this Management Pack
  • Management Pack Purpose
  • Configuring the Apache HTTP Server Management Pack
  • Best Practice: Create a Management Pack for Customizations
  • Deploying and Enabling the CIM Provider
  • Required Access for CIM Provider Installation
  • Upgrading the CIM Provider to a new version
  • Tuning Performance Threshold Monitors
    		•

    Apache HTTP Server Management Pack for System Center – Operations Manager




    Download 180.05 Kb.
    bet2/3
    Sana22.12.2019
    Hajmi180.05 Kb.
    1   2   3

    Apache HTTP Server Management Pack for System Center – Operations Manager


    Microsoft Corporation

    Published: 2016

    Send feedback or suggestions about this document to mpgfeed@microsoft.com. Please include the management pack guide name with your feedback.

    The Operations Manager team encourages you to provide feedback on the management pack by providing a review on the management pack’s page in the Management Pack Catalog (http://go.microsoft.com/fwlink/?LinkID=82105).


    Copyright


    This document is provided "as-is". Information and views expressed in this document, including URL and other Internet website references, may change without notice. You bear the risk of using it.

    Some examples depicted herein are provided for illustration only and are fictitious.  No real association or connection is intended or should be inferred.

    This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.

    © 2015 Microsoft Corporation. All rights reserved.

    Microsoft, Active Directory, Windows, and Windows Server are trademarks of the Microsoft group of companies.

    All other trademarks are property of their respective owners.


    Contents



    Contents


    Apache HTTP Server Management Pack Guide 4

    Guide History 4

    Supported Configurations 5

    Supported Versions of Apache HTTP Server 5

    Supported Installations of Apache HTTP Server 5

    Supported Operating Systems 5

    Prerequisites 5

    Files in this Management Pack 5

    Management Pack Purpose 5

    Monitoring Scenarios 6

    Configuring the Apache HTTP Server Management Pack 6

    Best Practice: Create a Management Pack for Customizations 6

    Deploying and Enabling the CIM Provider 7

    Enabling Remote HTTP Monitoring 10

    Tuning Performance Threshold Monitors 10

    Appendix: Management Pack Contents 12

    Monitored Apache HTTP Server 12

    Apache Virtual Host (Linux) 14

    Apache SSL Certificate (Linux) 18

    Apache HTTP Server Management Pack Guide


    The Apache HTTP Server Management Pack helps you monitor installations of Apache HTTP Server running on Linux computers that are managed by System Center Operations Manager.

    The Apache HTTP Server Management Pack alerts you to problems with components such as web sites and certificates so you can continuously monitor the services on which your business depends.

    This guide was written based on the 7.6.1065.0 version of the Apache HTTP Server Management Pack.



    Guide History




    Release Date

    Changes

    04/16/2015

    Original release of this guide

    10/12/2016

    General Availability Update


    Supported Configurations

    Supported Versions of Apache HTTP Server


    • Version 2.2

    • Version 2.4

    Supported Installations of Apache HTTP Server

    Apache 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 locations

    Supported Operating Systems

    • All versions of Linux supported by the current version of Operations Manager



    Prerequisites


    The 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 Pack


    The following table describes the files that are included in this management pack:

    File name

    Display name

    Microsoft.Oss.Library

    Microsoft Monitoring Library for Open Source Software

    Microsoft.ApacheHTTPServer.Library.mpb

    Microsoft Apache HTTP Server Library

    Management Pack Purpose


    The 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




    Monitoring scenario

    Description

    Associated rules and monitors

    Apache HTTP Server Health

    Availability and performance monitoring for Apache HTTP Server instances

    See Appendix: Management
    Pack Contents

    Virtual Host Health

    Availability and performance monitoring for Virtual Host instances

    See Appendix: Management
    Pack Contents

    Virtual Host SSL Certificate Health

    Availability and performance monitoring for SSL Certificate instances

    See Appendix: Management
    Pack Contents


    Configuring the Apache HTTP Server Management Pack


    This 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 Customizations


    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 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.

    Deploying and Enabling the CIM Provider


    Monitoring of Apache HTTP Server requires that the corresponding CIM Provider s deployed to the managed computer. The CIM Provider package includes an OMI Provider, which is registered with the Linux agent for Operations Manager, as well as an Apache module (mod_cimprov), which exposes data about the Apache HTTP Server to the OMI provider. The Apache module (mod_cimprov) must be loaded in the Apache HTTP Server configuration to enable monitoring.

    Deploying the CIM Provider

    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-.universald.1.x64.sh package.

    • Run the installation package with the --upgrade --force switches. This will reinstall the package but not modify any existing configuration customization:


    sudo sh ./scx-1.6.0-156.universald.1.x64.sh --ugprade --force

    • 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:

    sudo sh ./scx-1.6.0-156.universald.1.x64.sh --extract

    cd scxbundle.*

    sudo ./apache-cimprov-1.0.0-423.universal.1.x86_64.sh --extract

    cd apache_24 #For Apache HTTP Server version 2.4

    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:



    sudo /opt/microsoft/apache-cimprov/bin/apache_config.sh -c

    To disable the CIM Provider, run the apache_config.sh script with the “-u” argument

    sudo /opt/microsoft/apache-cimprov/bin/apache_config.sh -u

    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.



    $MgmtServerName = "localhost"

    ipmo "C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Powershell\OperationsManager\OperationsManager.psd1"

    New-SCOMManagementGroupConnection $MgmtServerName

    #Get the installation task

    $InstallTask = Get-SCOMTask -Name:"Microsoft.ApacheHTTPServer.LoadModule.Task"

    $DiscoverTask = Get-SCOMTask -Name:"Microsoft.ApacheHTTPServer.DiscoverServer.Task"


    #Get instances of Apache installations

    $InstallationClass = Get-SCOMClass -Name:"Microsoft.ApacheHTTPServer.Installation"


    ForEach ($Instance in Get-SCOMClassInstance -class:$InstallationClass){

    #Check if CIM module is already installed

    $isManaged = $Instance.'[Microsoft.ApacheHTTPServer.Installation].IsManaged'.Value

    if ($isManaged -eq $false){

    $Name = $instance.Path
    #Prompt for approval to install

    $Input = Read-Host "Load Apache module to $Name (Y or N) ? This will restart the Apache server."

    if ($Input.Trim() -eq "Y"){

    #Invoke the installation task

    $TaskOut = Start-SCOMTask -Task:$InstallTask -Instance:$Instance

    #Get the task output, and wait for it to complete.

    $MyBatch = $taskout.batchid
    if ($MyBatch -ne $null){

    $ResultStatus = "Started"

    while ($ResultStatus -eq "Started")

    {

    $MyResult = Get-SCOMTaskResult -BatchID:$MyBatch -EA SilentlyContinue



    [string]$ResultStatus = $MyResult.Status

    Start-Sleep -s 3

    }

    }

    $MyResult.Output



    Write-Output $ResultStatus
    If ($ResultStatus -eq "Succeeded"){

    Write-output "Triggering on-demand discovery."

    $TaskOut = Start-SCOMTask -Task:$DiscoverTask -Instance:$Instance

    }

    }



    }

    }



    Required Access for CIM Provider Installation

    Run As Account

    The 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.



    monuser ALL=(root) NOPASSWD: /opt/microsoft/apache-cimprov/bin/apache_config.sh


    Upgrading the CIM Provider to a new version


    The 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 Monitoring


    The 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 Monitors


    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

    Apache HTTP Server Pct Busy Workers

    80

    3

    Apache HTTP Server Total Pct CPU

    80

    3

    Apache HTTP Server Used KBytes Memory

    Warning: 262144
    Critical: 524288

    2

    Apache Virtual Host Total Requests per Second

    100

    3

    Apache Virtual Host Errors per Minute - Client

    10

    3

    Apache Virtual Host Errors per Minute - Server

    1

    3

    Apache Virtual Host Web Request Total Response Time

    Warning: 5
    Critical: 10

    1

    Apache SSL Certificate Expiration

    Warning: 21
    Critical: 7

    1




    Download 180.05 Kb.
    1   2   3




    Download 180.05 Kb.
    Bosh sahifa
    Aloqalar
        Bosh sahifa
    Mühazirə


    Apache HTTP Server Management Pack for System Center – Operations Manager

    Download 180.05 Kb.