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.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.” 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. ![]()
0 Comments
Leave a Reply. |