retrycount: the number of attempts to retry the request, 0 or greater.responsetimethreshold: the response time threshold in seconds, if this is surpassed, a warning alert will be generated.requesturl: the URL of the request, either or.The discovery script performs some basic validation, but the XML configuration should be edited carefully in order to prevent inadvertent errors due to invalid configuration. Multiple requests can be defined in the configuration file by adding another element. Assign a RunAs account for the designated Watcher NodeĪll configurable elements of the WebMon URL Monitoring Management Pack can be set in the webmonconfig.xml on the Watcher Node.Edit the properties of the WebMon Request RunAs Profile. In the Administration section of the Operations Manager console, click RunAs Profiles.Create a new RunAs account to be used by the watcher node, or determine an existing account to use.If any sites are to be monitored with NTLM/Integrated authentication, a RunAs Profile must be configured.If this needs to be changes, edit the properties of the WebMon Discovery object, and adjust the schedule accordingly. The default interval for the object discovery is 15 minutes.
#Start webmon update#
If the webmonconfig.xml file is deployed to a non-default location, override the script arguments and update the first parameter (c:\webmon\webmonconfig.xml) to reflect the actual script location.Select the server designated as Watcher Nodes, and override the object discovery to be “enabled.”
#Start webmon windows#
Right click the “WebMon Discovery” object under “Discovered Type: WebMon Watcher Node,” and choose Overrides->Override the Object Discovery->For a Specific Object of Class: Windows Server.Access the Authoring section of the Opeartions Manager console, click the Change Scope link and limit the scope to WebMon Watcher Node.Import the WebMon.xml file using the Import Management Pack function in the Operations Manager console, under administration.Edit the configuration file with the desired settings (see the XML configuration section below).Copy the sample webmonconfig.xml to a location on a local disk drive of each node intended to be a watcher node (the default path is C:\webmon\webmonconfig.xml).To deploy the WebMon URL Monitoring Management Pack: The advantage of this management pack over the SCOM the Web Application monitoring implementation for basic web monitoring is that it can be rapidly deployed and configured by simply editing the XML configuration file.
These include state views for the Watcher Nodes, two Request classes, and a performance view displaying the historical response time for all requests. A set of views are also created under the Web Application folder in the Monitoring section of the SCOM console. The monitors are rolled-up into an aggregate monitor used for alerting for each Request class.
The Request and Secure Request classes are identical, except the Secure Request class utilizes NTLM/Integrated authentication through a RunAs profile. The management pack implements three classes: 1) WebMon Watcher Node, which hosts 2) WebMon Request and 3) WebMon Secure Request classes. All configuration for each monitored URL is performed by editing a single XML file on the Watcher Node. This management pack for SCOM 2007, is intended to provide basic web monitoring for multiple web sites while being very easy to deploy. Notes on deploying and configuring the MP are as follows:
The WebMon URL Monitoring management pack that I described in the previous post, can be downloaded here.
0 kommentar(er)
